cloudy cloudy

Author Topic: WU Almanac Fails With New API Key  (Read 312 times)

0 Members and 1 Guest are viewing this topic.

Offline gwwilk

  • Posts: 672
  • Lincoln, NE
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Southeast Lincoln Weather
WU Almanac Fails With New API Key
« on: February 27, 2019, 03:52:10 PM »
When will the new API Key work for the WU Almanac?  I tried mine this morning, and it didn't work. Then I reverted to my old API key, which does work.

Just wondering...
Regards, Jerry Wilkins
gwwilk@inebraska.com

Offline niko

  • syzygy
  • Global Moderator
  • Posts: 27,948
  • Crystal Ball broken! Please post the URL.
  • Northern California, U.S.A.
  • OS/Browser:
  • Win 7/Srvr 2008R2
  • Chrome 72.0.3626.119
Re: WU Almanac Fails With New API Key
« Reply #1 on: February 27, 2019, 04:00:04 PM »
I have seen posts from Ken indicating that the Almanac is not part of WU's future plan, so the answer to your question may well be "never".

Online Weather Display

  • Posts: 86,484
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Weather Display
Re: WU Almanac Fails With New API Key
« Reply #2 on: February 27, 2019, 04:23:47 PM »
its not clear if he is refering to WD's almanac or Ken's script

Offline gwwilk

  • Posts: 672
  • Lincoln, NE
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Southeast Lincoln Weather
Re: WU Almanac Fails With New API Key
« Reply #3 on: February 27, 2019, 05:45:03 PM »
its not clear if he is refering to WD's almanac or Ken's script
I'm talking about WD's function to access the WU Almanac under 'View/WU Almanac'.

If WU will no longer support the Almanac, does anyone know of an accessible alternate source for local record highs and lows?
Regards, Jerry Wilkins
gwwilk@inebraska.com

Online Weather Display

  • Posts: 86,484
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Weather Display
Re: WU Almanac Fails With New API Key
« Reply #4 on: February 27, 2019, 05:58:18 PM »
the new WU api is not compatible with the existing api

so do not use the new WU api for anything other than what I have mentioned to use it with (i.e using WU as the data source)


as per replacement
the new WU Api does have historical data
e.g
https://docs.google.com/document/d/1w8jbqfAk0tfZS5P7hYnar1JiitM0gQZB-clxDfG3aD0/edit
but even the all function you still need to supply a specific date, and so it just returns the hi/lo data for that date only

so that is no good

Online Weather Display

  • Posts: 86,484
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Weather Display
Re: WU Almanac Fails With New API Key
« Reply #5 on: February 27, 2019, 06:05:33 PM »
actually WD uses
http://classic.wunderground.com/
to get the almanac data
so that might keep on working after the api is shut down

but to get current condtions and the 5 day forecast,in that almanac screen in WD, you will need to get and use your own api key (once I convert those to the new api)

Offline gwwilk

  • Posts: 672
  • Lincoln, NE
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Southeast Lincoln Weather
Re: WU Almanac Fails With New API Key
« Reply #6 on: February 27, 2019, 08:02:54 PM »
Thanks, Brian!  I'll keep things as is for now, and see what develops.
Regards, Jerry Wilkins
gwwilk@inebraska.com

Online Weather Display

  • Posts: 86,484
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Weather Display
Re: WU Almanac Fails With New API Key
« Reply #7 on: February 27, 2019, 08:25:21 PM »
actually WD used to use the classic url
but that was problematic (i.e just was web page data scraping)
and changed to using the api
but the new api does not have that same almanac data

Online Weather Display

  • Posts: 86,484
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 72.0.3626.119
    • Weather Display
Re: WU Almanac Fails With New API Key
« Reply #8 on: March 05, 2019, 01:31:09 AM »
the classic url is not available anymore , so that is not an option any more to get the almanac data
and the new replacement api does not have it

so I have had to remove it..but have left where you can manually enter the almanac record max/min to be used for the custom tags etc