# Known reason for WeatherData being currently unreliable?

GROUPS:
 Albert Retey 5 Votes I am using WeatherData every now and then and found that at some times (like today and yesterday) it is very unreliably, while at other times it works reasonably well. Currently it is really slow and returns Missing["NotAvailable"] or \$Failed for almost every request and weather station. At other times I can get the same data (e.g. temperature values for a given date-range and weatherstation) quickly and reliably. My guess is that there might be some problems with the underlying infrastructure, but this of course is just a wild guess. Does anyone know any details or where/how I could find out whether such problems currently exist? I would also appreciate any hints about how I could ensure that the client side setup is not causing any problems and is set up for optimal results (e.g. data-paclet versions and states, timeouts, ... ?)
3 months ago
10 Replies
 it looks like it now does work alright again, after delivering hardly any result for about 24h. I would still like to know anything that I could do about it, including getting information about server problems or a place where to most efficiently report such problems...
3 months ago
 current state is that it doesn't work. Seems to be an on and off situation at the moment...
3 months ago
 Sam Carrettie 2 Votes You should always post minimal code reproducing the issue, even if things seem obvious to you. Also please format code properly. It is all in the rules: https://wolfr.am/READ-1ST I can confirm, at least: In[1]:= WeatherData["Chicago", "Temperature"] Out[1]= Missing["NotAvailable"] But W|A seems to work. So probably they get WeatherData from a different source that is acting out currently. You can always use W|A workaround: data = WolframAlpha["Chicago temperature from 1995 to 2000", "TimeSeriesData"]; DateListPlot[data, PlotTheme -> "Wide"] 
3 months ago
 Albert Retey 1 Vote You are of course right about the missing code example, I originially didn't think answers would contain code and thus didn't think about providing an example. But showing code of course always clarifies things, actually I am using something like this: data = WeatherData["EDDM","Temperature",{{2016,1,1},{2016,1,31}}] that is, I need data from a specific weather station and I need temperatures for a given time period in the resolution that the weather station provides. That's why I would prefer a more specific call syntax like WeatherData (or AirTemperatureData) over the WolframAlpha free form input, but I of course would appreciate a workaround anyway. I tried e.g. this: WolframAlpha["EDDF temperature from 01/01/2016 to 01/31/2016", "TimeSeriesData"] or this: WolframAlpha["weatherstation EDDF temperature from 01/01/2016 to 01/31/2016", "TimeSeriesData"] but could not get any temperatures for a weatherstation from it. Would you have a suggestion how that could be achieved?And of course I still would be interested in any information about what the actual problem with WeatherData is and whether I can do anything about it :-)
3 months ago
 Try location where the weather station is: WolframAlpha["Frankfurt airport temperature from 01/01/2016 to 01/31/2016", "TimeSeriesData"] 
3 months ago
 Albert Retey 1 Vote Thanks Sam, I understand you are trying to help. Looks like my example was not precise enough. The problem is that it isn't that easy to come up with something that WolframAlpha understands for other weatherstations, e.g. WMO68817 is a weatherstation near or in Cape Town. I know I can do something like this to get a nearby city if I have the name of the weatherstation:  GeoNearest[Entity["City"], WeatherData["WMO68817", "Coordinates"]] and then I could use that city in a call to WolframAlpha. But that would not guarantee that the data would come from that weatherstation: there are approximately 5 weatherstations which could be near or in Cape Town and any of them would be valid source for that answer. For my purposes it is unfortunately important that I know where exactly the weatherstation is located and I need a general solution which can be automated. Please do not feel like I am demanding a solution for that, I just want to make clear that in my situation a workaround using WolframAlpha unfortunately seems not that straightforward. That is why I would like to get more information if and what I could do to make WeatherData work more reliable or get information why it doesn't work.
3 months ago
 Yes, I agree, I just hope they will fix it. Note this also fails: AirTemperatureData["EDDM", {{2016, 1, 1}, {2016, 1, 31}}]