Reverse geocoding is down due to popular demand.

Unfortunately the reverse geocoding services I provide is down as there are too many incoming request. This resulted in Yahoo services blocking the requests coming from my servers. When I wrote this service I never thought that it would be so popular as I wrote it has some sort of hack. But a few month done the line and there are about 500 000 requests per month.

If you are still interested in reverse geocoding your long/lats I published the source code used for the reverse geocoding service in github http://github.com/geomojo/ReverseGeocoder.

The recommanded solution for reverse geocoding to WOEID is by using the Flickr API flickr.places.findByLatLon.html

This can also be done using the YQL language:

http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20flickr.places%20where%20lon%3D-97.470929%20and%20lat%3D37.510042&diagnostics=true

Where the lon and lat parameters contains the lat/long you want to reverse geocode into a WOEID.

3 Responses to “Reverse geocoding is down due to popular demand.”

  1. shinren.pan says:

    hi,
    I used your webside to convert woeid
    and I also try to use flickr.places.findByLatLon.html
    why the woeids is different
    the lat = 24.771113
    lon = 121.026461

    sorry my bad English

  2. shinren.pan says:

    I see
    The flickr.places.findByLatLon.html has a accuracy parameter
    but , if I use the YQL. how can I set the accuracy

Leave a Reply

Spam Protection by WP-SpamFree