GeoNames Forum

I have implemented a reverse geo-code lookup using the findnearestAddressJSON call, but in some cases, the returned JSON package is missing a bunch of data points. As I understand the function, should it not return the NEAREST known address?

I submit certain LAT/LON pairs and in many cases all I get returned is the city and state...no street name or address.

Can someone explain this?

Thanks...a ton!

Matt G.

It is difficult to say, without knowing the lat/lng we speak about. I would assume there is no other data available and this point.

Best

Marc

Okay,

I downloaded a bunch of retail chain files from various POI sites and wanted to test the accuracy of the LAT/LON data. The csv files contain both LAT/LON and the actual address of the store. What I am finding however, is that the LAT/LON data isn't very accurate. For instance, if I run the find nearest Address JSON with the lat/lon in the file, about half the time it finds only the city and state...sometimes it finds the STREET, but no number and almost never the correct ZIP?

However, if I plug the ADDRESS into a geocoder, the LAT/LON is actually a bit different. If I run the newly found LAT/LON into the findNearestAddressJSON...it 'slightly more often' finds an address that is very close to the actual.

My goal here is to be able to determine as close to the actual address from the LAT/LON pair. I was under the assumption that the findNearestAddressJSON would ALWAYS give an address, even if not totally accurate...hence NEAREST being in the title of the function. I can list the LAT/LON pairs if you like...

Geb

the service returns the closest address, if there is no house number available at this street segment then it does not return one. As simple as that.

That is what I figured, but when I use the INTERACTIVE map version...ANYWHERE I click in or around the same LATLON pair I DO get an address. Is there a difference between the two implementations of the Reverse Geocode?

Geb

The map on the documentation page is using the web service, they cannot be different. There is even a link below the address to the web service response at this location.

http://www.geonames.org/maps/reverse-geocoder.html

Marc