Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
Not long ago I wrote that Yahoo effectively shut down its Weather API by forcing OAuth 1.0. After what seems like an uproar by many developers Yahoo reversed it's decision (in a way) and re-enabled public access to the Weather API, but there is a catch. You have to use the new YQL way of fetching data and it seems very slow to respond.
I've put together an example of this new API, read about it here: Example Yahoo Weather YQL to fetch forecasts and render with JQuery.


It looks like the examples have been updated and from what I could gather it is possible to make a request to a YQL URL and fetch the data without authentication.

So it's possible to execute a query like this just by sending it as a URL parameter...
 YQL
select * from weather.forecast where woeid=1100661


...and get results back in the JSON format (or XML if you wish)...
yqlweather2.png


The whole URL request looks like this:
 URL
https://query.yahooapis.com/v1/public/yql?q=select+%2A+from+weather.forecast+where+woeid%3D1100661&format=json


All you have to do is URL Encode the YQL statement and pass it in using the 'q' URL paramether. The 'format' URL parameter specifies whether the weather data should be returned as JSON or XML. In case you are wondering, I looked up the WOEID here.



Of course you probably don't want to bring back all of the results so you can tailor that query using the YQL Console first...
yqlweather1.png


I'm glad Yahoo has reenabled public access but it is definitely too late in my opinion as I would imagine many like myself have switched from this API to something like OpenWeatherMap.

-i

Skip down to comments...
A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. If you spot something out of place, please do let me know.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
 
comments powered by Disqus
Other posts you may like...