The change was inadvertent and we apologize for the extra-effort and frustration that this has caused. It should be back to normal now.

Please let me know if you see anything else that hasn't reverted.

robyn

Seems that we are back to version 1 now... What a mess!

Same Problem here. We need the new Documentation please.

Hello,

today I had to notice that Placefinder has changed its API responses. By looking at the new responses in detail, I noticed a version value of "2". Unfortunately, the version 2 response is obviously different from the version 1 response, but there is no documentation for it. So I can't confidently change my API wrapper implementation to work with the new version...

So, please either reenable the old version 1 API or provide documentation for the version 2 API.

Hear, hear!

I need this too. Here Yahoo, take my money!

Hi,

We have the same requirement. Any suggestion about it?

I'm using Placefinder to get Geo-information data but as i read in the documentation of placefinder, the rate limits is not exceed 50000 requests per day.
My question here is : How i can increase the rate limits? Is there any payment for that? if Yes: how can I do that?

Thank you,
Mustafa

Could I also request the same.

It seems the Scottish regional area names are out of date, see topic here:

http://meta.stackoverflow.com/questions/131601/careers-2-0-county-area-issue
I did a quick test with an Aberdeen postcode as well which returned Grampian which again is incorrect:
http://en.wikipedia.org/wiki/Grampian
So I would think they are probably all wrong.

Seconded * a million. I had just started to rework my web application away from Google Location API in favour of the more generous Yahoo! rate limits, but this restriction has now blocked that work :( Same with JSONP.

Hi there,
I just wanted to raise your attention to some discrepancies in what is being returned by the PlaceFinder according to whether I am getting it in JSON or XML format. Most of them are really minor (i.e. they mostly concern the output format) but today I encountered one that was plain bad:

XML:
http://where.yahooapis.com/geocode?city=cave+creek&postal=85327&appid=(my_app_id)

JSON:
http://where.yahooapis.com/geocode?city=cave+creek&postal=85327&flags=J&appid=(my_app_ID)

The placefinder is always returning Pky in place of Pkwy. As a norm (including on USPS website) and road signs, i have seen it as Pkwy. Which one is right?

Nevermind, this was fixed now: http://meta.stackoverflow.com/questions/125810/obsolete-country-name-on-careers

Serbia and Montenegro (http://en.wikipedia.org/wiki/Serbia_and_Montenegro) have been broken up since 2006. Since then, Serbia (http://en.wikipedia.org/wiki/Serbia) and Montenegro (http://en.wikipedia.org/wiki/Montenegro) are separate countries, and as such it should be possible to select either of them.

The actual dissolution happened on 23 May 2006 after the Montenegrin independence referendum (http://en.wikipedia.org/wiki/Montenegrin_independence_referendum,_2006)

I'm making a mobile app where I fetch the GPS coordinates. Then I like to know the street the user is standing on (to be able to get the car parking regulations of that street from a database).
Right now when doing a reverse geocode request I only get one result even if I stand right between two streets. And since the GPS can have a accuracy of up to a couple of hundred meters that single result will almost always be wrong.
Is it possible to get multiple possible results so I can present a list of best guesses to the user so the user can pick manually from it?

Hi,

I have a problem with Zip code that ,for some city and state values I am not getting zip code value in the XML file where am storing that downloaded XML file in a label. While I am running the URL with the same city and state values for example (http://where.yahooapis.com/geocode?q=,,New York,NY) it was showing the zip code.

Can you please help me in this issue.

Regards ,

Suresh

Hi there,

Could someone please add a country parameter or bounding box parameter to the Yahoo placefinder API? I tried the parameter &country=za but for some reason the API still seems to think Pretoria is somewhere in the United States. Otherwise please add a place where we can specify a bounding box for the API to search in ? (I am not talking about the returned bounding box values)
If this does already exists could you please update your help/support documentation so that we can see how to use it?

just wanted to voice my support for this!
would love to see this added since it would make the api useable from javascript.
thanks!

See also: http://meta.stackoverflow.com/questions/90...t-exist-anymore

Netherlands Antilles (AN) is been dissolved since 10-10-10. The country does not exist anymore. It's now Curaao (CW), St. Maarten (SX) and BES - Bonaire, St. Eustatius and Saba (BQ).

Please update your country database. An up-to-date ISO 3166 table can be found here. Its legend says for Netherlands Antilles:

Requesting support for making requests over https.

Yeah - I had been testing with Calgary postal codes (which return the whole thing) but then I get a call saying why does this address in saskatchewan not supply the correct city - and I see it's because it returns only 1/2 the postal code.

Hummm. Now I need to seek out a different API.
That's too bad, I like the Yahoo! API.

I'm sad that I did all this code with results that return full postal codes, but once in production I get feedback the API doesn't return correct information.

Could you please add a callback for JSONP.