Topic: Weather underground historical data is not available now

[pimohdaimaoh]

hello WU users,

Its seems the data for WU is already disabled, even the trend Grapths on my page seems getting error
I guess WU restrictions of using weather data, while us sending our DATA to them for free seems unfair.

Im thinking removing my WPS sending to WU all this time, o maybe theres another way you know how to recover this?

[AboutAndAround]

Looks like the old website "hack" is gone too. Sigh.

[jotross]

 :-(Yes. Old HACK is gone!  No longer able to download historical data and paste into spreadsheet. I can copy and paste table form but process is convoluted. Also choosing “Custom” no longer an option. PLEASE bring these features back!

[saratogaWX]

I see that queries using the /weatherstation/WXDailyHistory.asp query are now getting the following response:

<!-- curl fetching 'https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KCASARAT1&month=05&day=19&year=2019&format=1&graphspan=day' -->
<!-- HTTP stats:  RC=503 dest=23.33.60.222 port=443 (from sce=74.208.252.86)
      Times: dns=0.004 conn=0.019 pxfer=0.054 get=0.631 total=0.685 secs -->
<!-- headers:
HTTP/1.1 503 Service Unavailable
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: text/html
Content-Length: 174
Cache-Control: max-age=0
Expires: Sun, 19 May 2019 19:41:30 GMT
Date: Sun, 19 May 2019 19:41:30 GMT
Connection: keep-alive
Set-Cookie: speedpin=4G; expires=Sun, 19-May-2019 20:11:30 GMT; path=/; domain=.wunderground.com; secure
Set-Cookie: ci=TWC-Connection-Speed=4G&TWC-Locale-Group=US&TWC-Device-Class=desktop&X-Origin-Hint=dna&TWC-Network-Type=wifi&TWC-GeoIP-Country=US&TWC-GeoIP-Lat=40.0438&TWC-GeoIP-Long=-75.3883&Akamai-Connection-Speed=1000+&TWC-Privacy=exempt; path=/; domain=.wunderground.com; secure
Property-id: drupal-prod
X-RequestSource: AkamaiProdProxy
TWC-Privacy: exempt
TWC-GeoIP-LatLong: 40.0438,-75.3883
TWC-GeoIP-Country: US
TWC-Device-Class: desktop
TWC-Locale-Group: US
TWC-Connection-Speed: 4G
X-RequestSource: AkamaiDefaultDNA

I can't tell if this is a deliberate discontinuation of that function, or just a service outage.
I've sent a query to Victoria Gardner at IBM (TWC/WU) asking about that service .. I'll let you know what I hear back.

n.b -- if the service is now deprecated on the WU site, then I'll look at reworking the WU-History-inc.php, and the CU-HWS script sets to use the WU API instead.

[WSWeather]

I can't tell if this is a deliberate discontinuation of that function, or just a service outage.

Considering the other legacy stuff that is returning errors now too (and has been for well over 24 hours now), I suspect this is the end.

[saratogaWX]

Perhaps.. I'll wait for Victoria's answer about it before launching into a re-coding scramble.  The closest thing on the WU/TMC API is the
query like

Code: [Select]

https://api.weather.com/v2/pws/history/all?stationId=<WUID>&format=json&units=e&date=<YYYYMMDD>&apiKey=<your-api-key> which returns a JSON of one day's readings at 5 minute intervals (288 readings in all) with each reading looking like:

Code: [Select]

{
"observations": [{
"stationID": "KCASARAT1",
"tz": "America/Los_Angeles",
"obsTimeUtc": "2019-05-18T07:04:58Z",
"obsTimeLocal": "2019-05-18 00:04:58",
"epoch": 1558163098,
"lat": 37.27470016,
"lon": -122.02295685,
"solarRadiationHigh": 0.0,
"uvHigh": 0.0,
"winddirAvg": 212,
"humidityHigh": 84,
"humidityLow": 84,
"humidityAvg": 84,
"qcStatus": 1,
"imperial": {
"tempHigh": 49,
"tempLow": 49,
"tempAvg": 49,
"windspeedHigh": 0,
"windspeedLow": 0,
"windspeedAvg": 0,
"windgustHigh": 0,
"windgustLow": 0,
"windgustAvg": 0,
"dewptHigh": 44,
"dewptLow": 44,
"dewptAvg": 44,
"windchillHigh": 49,
"windchillLow": 49,
"windchillAvg": 49,
"heatindexHigh": 49,
"heatindexLow": 49,
"heatindexAvg": 49,
"pressureMax": 30.07,
"pressureMin": 30.07,
"pressureTrend": -0.04,
"precipRate": 0.00,
"precipTotal": 0.00
}
}, {
...
}
}
]
}


[waiukuweather]

that is only hi/lo data so not very usefull?

[txweather.org]

Thanks for looking in to this Ken.

[pimohdaimaoh]

Perhaps.. I'll wait for Victoria's answer about it before launching into a re-coding scramble.  The closest thing on the WU/TMC API is the
query like

Code: [Select]

https://api.weather.com/v2/pws/history/all?stationId=<WUID>&format=json&units=e&date=<YYYYMMDD>&apiKey=<your-api-key> which returns a JSON of one day's readings at 5 minute intervals (288 readings in all) with each reading looking like:

Code: [Select]

{
"observations": [{
"stationID": "KCASARAT1",
"tz": "America/Los_Angeles",
"obsTimeUtc": "2019-05-18T07:04:58Z",
"obsTimeLocal": "2019-05-18 00:04:58",
"epoch": 1558163098,
"lat": 37.27470016,
"lon": -122.02295685,
"solarRadiationHigh": 0.0,
"uvHigh": 0.0,
"winddirAvg": 212,
"humidityHigh": 84,
"humidityLow": 84,
"humidityAvg": 84,
"qcStatus": 1,
"imperial": {
"tempHigh": 49,
"tempLow": 49,
"tempAvg": 49,
"windspeedHigh": 0,
"windspeedLow": 0,
"windspeedAvg": 0,
"windgustHigh": 0,
"windgustLow": 0,
"windgustAvg": 0,
"dewptHigh": 44,
"dewptLow": 44,
"dewptAvg": 44,
"windchillHigh": 49,
"windchillLow": 49,
"windchillAvg": 49,
"heatindexHigh": 49,
"heatindexLow": 49,
"heatindexAvg": 49,
"pressureMax": 30.07,
"pressureMin": 30.07,
"pressureTrend": -0.04,
"precipRate": 0.00,
"precipTotal": 0.00
}
}, {
...
}
}
]
}


Thanks for this ken, because even in our Weather34 page, it seems the WU graph trends cannot viewed it anymore, also affecting WU-Forecast.php which also cannot view-able anymore, well I will wait also for the feedback


Regards

-Mike-

[saratogaWX]

Mike,
Both the CU-HWS and WU-History-inc.php are down due to the WU issue.

The WU-forecast.php script died in March, 2019 when they turned off the old WU-API.  If you have a new PWS API ID from WU, you can use the WC-forecast.php script for that.  The old WU-forecast.php script is now deceased.

[lddaly]

WXDailyHistory.asp is also used by the WU-Graphs script: http://www.planoweather.com/wxwugraphs.php

[pimohdaimaoh]

Mike,
Both the CU-HWS and WU-History-inc.php are down due to the WU issue.

The WU-forecast.php script died in March, 2019 when they turned off the old WU-API.  If you have a new PWS API ID from WU, you can use the WC-forecast.php script for that.  The old WU-forecast.php script is now deceased.

I see, thanks for clarification. Will apply the new api key to wc-forecast later and wait for updates the rest

Regards
-Mike-

[Jáchym]

 I posted about this yesterday, all WU pages in Meteotemplate stopped working. I guess they moved to the new API system, which does not even have a functional documentation.

[saratogaWX]

I received word from Victoria Gardner and they have turned off (permanently) the old CSV query capability on the website.

Unfortunately, the PWS WU/API does not provide the full equivalent capability (missing month and year queries), and only specific date queries.

So.. for now, all scripts that used the CSV query are dead  (WU-History, etc).

[Jáchym]

Ken do you know anything about the API for rapid fire, i.e. current data? The link in the documentation is incorrect and leads to 7day summary instead... so I see no way to get current data via the API, only hourly etc. averages which is useless for template updates...

[txweather.org]

I received word from Victoria Gardner and they have turned off (permanently) the old CSV query capability on the website.

Unfortunately, the PWS WU/API does not provide the full equivalent capability (missing month and year queries), and only specific date queries.

So.. for now, all scripts that used the CSV query are dead  (WU-History, etc).

Thanks for the update Ken

[saratogaWX]

Ken do you know anything about the API for rapid fire, i.e. current data? The link in the documentation is incorrect and leads to 7day summary instead... so I see no way to get current data via the API, only hourly etc. averages which is useless for template updates...

Looking at https://docs.google.com/document/d/1KGb8bTVYRsNgljnNH67AMhckY8AQT2FVwZ9urj8SWBs/edit

The 'Current Conditions' query has the form:

Code: [Select]

https://api.weather.com/v2/pws/observations/current?stationId=<WU-STATION>&format=json&units=<[e|m]>&apiKey=yourApiKey
and returns (for my station on rapid-fire)

Code: [Select]

{
"observations": [{
"stationID": "KCASARAT1",
"obsTimeUtc": "2019-05-20T15:10:28Z",
"obsTimeLocal": "2019-05-20 08:10:28",
"neighborhood": "Scotland Dr. near Glasgow Dr.",
"softwareType": "WeatherDisplay:10.37S",
"country": "US",
"solarRadiation": 362.0,
"lon": -122.02295685,
"realtimeFrequency": null,
"epoch": 1558365028,
"lat": 37.27470016,
"uv": 0.8,
"winddir": 185,
"humidity": 95,
"qcStatus": 1,
"imperial": {
"temp": 50,
"heatIndex": 50,
"dewpt": 49,
"windChill": 50,
"windSpeed": 0,
"windGust": 1,
"pressure": 29.96,
"precipRate": 0.00,
"precipTotal": 0.00,
"elev": 375
}
}
]
}[/url]

The time appears to update with each query.  Since I have calm conditions, I can't tell if the wind speed/direction are following the station though.

[konz]

Please excuse my post if this is old information, but I just read this on the Weather Underground User Group on FB.  Seems like analytics wins over user requests.  I realize this would have been end of march 2019/beginning of april 2019.

 

[galfert]

I can't believe that says premium features! That translates to charged subscription fees are coming to use your own data. SMH.

We need a new solution other than WU.

[mldenison]

On my site, everything before 2019 still pulls up. 2019 is completely blank now.  WU is still loving my free data.

[txweather.org]

On my site, everything before 2019 still pulls up. 2019 is completely blank now.  WU is still loving my free data.

Previous data is cached unless refreshed. Back it up before it decides to refresh.

[Jáchym]

Absolutely appalling behavior...

cut you off from your own data without notice... rudeness and arrogance at its best

[pimohdaimaoh]

Absolutely appalling behavior...

cut you off from your own data without notice... rudeness and arrogance at its best

Yes, exactly while WU enjoys getting my weather data straight from my weather station
its like "PUNISHING" you on internet while USING your data resources. Its ok for them VIOLATING rules but if the ordinary like me doing which may violate their policy its no ok to them, such unprofessional behavior 

-Mike-

[waiukuweather]

maybe they have listened..because its working again

[saratogaWX]

Only parts are working.  Fetching data found

<!-- curl fetching 'https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KCASARAT1&month=05&day=21&year=2019&format=1&graphspan=day' -->
<!-- HTTP stats:  RC=404 dest=173.223.144.97 port=443 (from sce=74.208.252.86)
      Times: dns=0.028 conn=0.059 pxfer=0.357 get=0.165 total=0.523 secs -->
<!-- headers:
HTTP/1.1 404 Not Found
Server: Apache/2.2.15 (CentOS)
Pragma: no-cache
Access-Control-Allow-Origin: http://www.wunderground.com
Access-Control-Allow-Credentials: true
Content-Type: text/html

Yet the graph link shows just fine