Geocoder's integration with Yahoo Placefinder API appears broken as of Oct. 1, 2012. This post on the Yahoo Developer Network suggests, "Yahoo PlaceFinder API seems to have upgraded from version 1.0 to version 2.0 in the past few days."
http://developer.yahoo.com/forum/PlaceFinder-General-Discussion/PlaceFin...
Also see http://developer.yahoo.com/blogs/ydn/posts/2012/09/introducing-boss-geo-...
"We intend to shut down the current free versions of PlaceFinder and PlaceMaker on November 17, 2012."
We're currently using Geocoder in production with Yahoo as the geocoding mechanism. Is there a simple code change to make Geocoder compatible with the new API?
Comment | File | Size | Author |
---|---|---|---|
#16 | geocoder-use-current-yahoo-api-version-1800130-16.patch | 7.56 KB | B-Prod |
Comments
Comment #1
jtherkel CreditAttribution: jtherkel commentedI was able to get my site running again by modifying the last lines of sites/all/modules/contrib/geocoder/plugins/geocoder_handler/yahoo.inc. Will work on turning this into a patch. In the meantime, here's the code.
Comment #2
jtherkel CreditAttribution: jtherkel commentedAttached please find a patch that updates Geocoder to work with Yahoo Placefinder API v2. It also includes the ability to roll back to v1 in case Yahoo changes the API back.
Comment #3
poukram CreditAttribution: poukram commentedIt's work for me ! Thanks for this patch.
Comment #4
phayes CreditAttribution: phayes commentedDone!
Comment #5
phayes CreditAttribution: phayes commentedDone!
Comment #7
jpstrikesback CreditAttribution: jpstrikesback commentedAs of Nov 17 the free Yahoo Placefinder API will be shut down in favor of the new pay BOSS Placefinder API. Of note it now requires Oauth.
I'm updating this issue as it seems that people who would care are subscribed.
Comment #8
jtherkel CreditAttribution: jtherkel commentedOur deadline of Nov. 17 approaches quickly. Is anyone else working on updating the Yahoo code for the paid Yahoo BOSS Geo service? Or is it relatively easy to switch to another free provider? What about MapQuest?
Assuming we need Yahoo, here's what I might do (have not started yet).
1) Upload credit card info to get my OAuth key.
2) Temporarily hack sites/all/modules/contrib/geocoder/plugins/geocoder_handler/yahoo.inc to test functionality.
3) Add some fields to the settings page so site administrators can manage Yahoo's OAuth keys. On my D7 install, this shows up under admin/structure/types/manage/name_of_my_content_type/fields/field_geolocation, where field_geolocation is the relevant field's machine name.
How are you handling this issue?
Comment #9
that0n3guy CreditAttribution: that0n3guy commentedI have a large database that I am using yahoo on as well. I could use google but it sucks when your testing and you hit your 2500 query limit.
I did some quick searching and found a decent list: http://blog.programmableweb.com/2012/06/21/7-free-geocoding-apis-google-...
Comment #10
Simon Georges CreditAttribution: Simon Georges commentedComment #11
drywall CreditAttribution: drywall commentedWow. Been nearly a year and still no progress on this, at least my review of 7.x-1.x-dev doesn't appear to include any updates to Yahoo.
The MapQuest nominatum plugin is also wildly out of date. Good times!
Comment #12
markie CreditAttribution: markie commented@drywall
Here's a start of a patch that uses the example at http://developer.yahoo.com/boss/geo/docs/codeexamples.html#oauth_php. Also attached is the oauth,php_.txt. This needs to be placed in the plugins/geocoder_handler folder and renamed to oauth.php. The consumer key and secret key need to be added, I didn't have time to change the settings file, so just plug it into the yahoo.inc where it screams for it. This is completely untested, but a good starting point.. ping me if you have any questions.
Comment #13
benjy CreditAttribution: benjy commented@markie thanks, I had to make a couple more changes to get this working.
Replace this function with this version which checks the new place in the result set.
Specify the "J" flag to get a JSON result.
Comment #14
Simon Georges CreditAttribution: Simon Georges commentedHi!
Could anybody eventually provide a full working patch, for others to review and for me to then commit?
Comment #15
markie CreditAttribution: markie commented+1 for a patch request. I am not sure where that $args should go.
Comment #16
B-Prod CreditAttribution: B-Prod commentedThis patch makes use of the new Yahoo API, for placefinder requests to work...
This means some changes in the admin UI (consumer key and secret are necessary).
Comment #17
B-Prod CreditAttribution: B-Prod commentedHere is a patch against the current release (7.x-1.12). Fully tested and depoyed on a PROD environment.
Comment #18
Simon Georges CreditAttribution: Simon Georges commentedThanks for the patch!
Can anybody using Yahoo test and give some feedback about the patch before I take a look on it myself?
Comment #21
Pol