>Google has shut down its weather API without a word and stranded developers who relied on it to power their weather-related applications.<p>It was a private undocumentated API used internally. Using it was always a big risk.
I have a similar weather service. All this week I am getting lots of requests. Thank you Google!
And if you want to get more infofmation about free weather and forecast mapping service, and API welcome to
<a href="http://openweathermap.org/wiki/Main_Page" rel="nofollow">http://openweathermap.org/wiki/Main_Page</a>
I wrote about this some years ago.<p><pre><code> Since Google’s Weather API is completely officially undocumented it’s worth noting that in future it may be wise to use Yahoo’s weather API, which is fully and officially documented.
</code></pre>
* <a href="http://labs.phurix.net/posts/weather-tcl" rel="nofollow">http://labs.phurix.net/posts/weather-tcl</a>
When I was looking into using it there were articles talking about this being phased our sooner or later. I started using Wunderground/YQL as a backup source at that point.<p>Sometimes reading/researching pays dividends.
Aha! I was wondering about that. I have something that uses it, albeit not for the most important part of the site/page: <a href="http://www.meteo-veneto.net" rel="nofollow">http://www.meteo-veneto.net</a> (completely useless for those who don't live in the Veneto region of Italy), and I figured that was the problem, but was not sure. Thanks for posting this.<p>Not that big a deal, and I knew it was undocumented, so I guess I'll just go find another one. Recommendations? Needs to be accessible via Javascript.
FWIW, the iGoogle API started getting flaky a couple weeks ago, intermittently returning error responses. So there was a little bit of warning.<p>A couple of other (supported) weather API alternatives.<p>* <a href="http://www.worldweatheronline.com/free-weather-feed.aspx" rel="nofollow">http://www.worldweatheronline.com/free-weather-feed.aspx</a> -- free with attribution, paid option to remove attribution. (We ended up going with this for our site.)<p>* <a href="http://www.wunderground.com/weather/api/d/docs" rel="nofollow">http://www.wunderground.com/weather/api/d/docs</a> -- free at developer usage levels, free allowance for sending traffic to their site, can get kind of pricey if you use it a lot and weather isn't central to what you do.<p>Incidentally, either of these will deliver a lot more weather data than you were getting with iGoogle.
I am not sure it is correct to call a private undocumented API an "API". Just because you can access it over http or whatnot doesn't mean that it is an API for you to use.<p>The same would hold true for any website I make that has an internal API it uses to serve up pages. Sure, you can make a service that mimics the correct calls and gets the data, but don't be surprised when I change my routes around and your stuff stops working.