http://www.webthingsconsidered.com/2007/05/17/yahoo-broke-their-geocode-api/ Tue, 08 Jun 2010 04:57:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.webthingsconsidered.com/2007/05/17/yahoo-broke-their-geocode-api/comment-page-1/#comment-215 Ryan Tue, 17 Jul 2007 17:42:04 +0000 http://www.webthingsconsidered.com/?p=214#comment-215 Not anymore. It was fixed that Saturday, about 3 days after the bug popped up. Saved me from having to do major data surgery. Not anymore. It was fixed that Saturday, about 3 days after the bug popped up. Saved me from having to do major data surgery.

]]> http://www.webthingsconsidered.com/2007/05/17/yahoo-broke-their-geocode-api/comment-page-1/#comment-214 AdamD Tue, 17 Jul 2007 17:39:18 +0000 http://www.webthingsconsidered.com/?p=214#comment-214 Still broken? Still broken?

]]> http://www.webthingsconsidered.com/2007/05/17/yahoo-broke-their-geocode-api/comment-page-1/#comment-217 Ryan Fri, 18 May 2007 18:43:33 +0000 http://www.webthingsconsidered.com/?p=214#comment-217 I'd expect that too, but two days later and still nothing, with no more than an "our apologies" from Y! in their yws-maps Y! group that they posted after the initial bug report. Definitely time to switch to Google's API. Or better yet, put a layer in between that can use either one. I’d expect that too, but two days later and still nothing, with no more than an “our apologies” from Y! in their yws-maps Y! group that they posted after the initial bug report. Definitely time to switch to Google’s API. Or better yet, put a layer in between that can use either one.

]]> http://www.webthingsconsidered.com/2007/05/17/yahoo-broke-their-geocode-api/comment-page-1/#comment-216 AdamD Thu, 17 May 2007 19:42:37 +0000 http://www.webthingsconsidered.com/?p=214#comment-216 That's definitely an error. I'd expect that to get fixed soon. Pretty annoying. That’s definitely an error. I’d expect that to get fixed soon. Pretty annoying.

]]>