findNearbyPostalCodes webservice: unexpected result with maxRows=1

Tilburg — GMT

Hi, While evaluating the results of the findNearbyPostalCodes webservice for locations in The Netherlands, I ran into the following issue: I used the following queries: http://ws.geonames.org/findNearbyPostalCodes?lat=51.55&lng=5.09&style=LONG http://ws.geonames.org/findNearbyPostalCodes?lat=51.55&lng=5.09&style=LONG&maxRows=1 The result of the first query (without maxRows=1):


5009
Tilburg
NL
51.55
5.1166667
NB
Noord Brabant

MIDDEN-NOORD-BRABANT
1.843766967748772


5008
Tilburg
NL
51.55
5.1166667
NB
Noord Brabant

MIDDEN-NOORD-BRABANT
1.843766967748772


5007
Tilburg
NL
51.55
5.1166667
NB
Noord Brabant

MIDDEN-NOORD-BRABANT
1.843766967748772


5049
Tilburg
NL
51.55
5.1166667
NB
Noord Brabant

MIDDEN-NOORD-BRABANT
1.843766967748772


5056
Berkel-Enschot
NL
51.53000002
5.0866667
NB
Noord Brabant

MIDDEN-NOORD-BRABANT
2.235705232137345

The results of the second query (with maxRows=1):


5056
Berkel-Enschot
NL
51.53000002
5.0866667
NB
Noord Brabant

MIDDEN-NOORD-BRABANT
2.235705232137345

In my opinion, the second query should return the closest result, but as you see it doesn’t. Doesn’t that sort ascending on distance? Regards, Marco

Re:findNearbyPostalCodes webservice: unexpected result with maxRows=1

marc — GMT

Thanks Marco. This is was a bug and was fixed right now. Regards, Marc

Re:findNearbyPostalCodes webservice: unexpected result with maxRows=1

Anonymous — GMT

Hi Marc, Thank you for your quick response! Regards, Marco

Latest posts for the topic "findNearbyPostalCodes webservice: unexpected result with maxRows=1"

findNearbyPostalCodes webservice: unexpected result with maxRows=1

Re:findNearbyPostalCodes webservice: unexpected result with maxRows=1

Re:findNearbyPostalCodes webservice: unexpected result with maxRows=1