https://www.wunderground.com/blog/JeffMasters/weather-underg...
I never 'looked under the hood', but it seemed to be straining & breaking the load of mountains of new cruft code. Somehow not surprised to learn that this happened on IBM's watch these days when they seem to have lost the plot in so many other ways.
For Android, FlowX [1] is a great app that is my first go-to now (no relation other than as a happy user). This Earth map [2] is a great map for web.
Anyone have other recommendations for web/desktop?
[1] https://play.google.com/store/apps/details?id=com.enzuredigi... [2] https://earth.nullschool.net/#current/wind/isobaric/1000hPa/...
They combine multiple sources of data. Even if you don’t want to use their API, I’ve found their list of sources handy for European data (though finding what you need in Europe is still confusing as heck).
From memory, data might return normal json but with "" empty string instead of metric forecast but imperial forecast is there. Or the other way around. Or both empty. Or 0 values for variables that shouldn't be 0. Or error state json with not much info. Things like that.
So, you put months of work into a project, using an API that you knew was abandoned? And it's anybody's fault other than you own?
Very bad decision-making and handling at IBM and I will not be supporting any of their businesses in the future. It is not reliable and they shut down without notice.
Funny timing this morning - I wrote about my experience with this API in my Show HN a few hours ago, before I knew about this news: https://news.ycombinator.com/item?id=18235812
And another link for the lazy, the link to the WU community when we all noticed that this wreck was happening: https://apicommunity.wunderground.com/weatherapi/topics/weat...
--
Edit: A side anecdote. The API was so bad (in terms of service uptime) that I learned a lot about how to write retry logic for API calls on mobile. So many calls would fail for various reasons. But randomly. So for each API call you want to make, you should have 5-10 error cases to catch and then retry. Eventually you'd get a successful call!
(I switched to the free US NWS / NOAA API for All Clear Weather. It is better in performance but I miss a lot of the data available from WU, and the US-only thing is a downer too. All Clear: https://play.google.com/store/apps/details?id=com.allclearwe...)