Mismatch between Webpage and API-Data

  • 1
  • Problem
  • Updated 6 years ago
Hi,

i am getting a lot of mismatches between the data on the webpage and the api call.

http://www.wunderground.com/cgi-bin/f...

Reports 0% POP for 8PM and 11PM

http://api.wunderground.com/api/47834...

Reports 10% POP for 8PM and 11PM

The same goes for the Forcecast Description

Website:

Mostly Clear High of 75F. Winds less than 5 mph.

API:

Clear with a chance of rain in the afternoon. High of 75F. Winds less than 5 mph. Chance of rain 20%.

The list goes on and on, I tried the following stations: pws:INORDRHE121
, pws:INRWCOLO2 and EDDK

They all report wrong values through the API

As is it now, the api somewhat useless returning the wrong values
Photo of Bunka Ronin

Bunka Ronin

  • 2 Posts
  • 0 Reply Likes
  • frustraded

Posted 6 years ago

  • 1
Photo of Bunka Ronin

Bunka Ronin

  • 2 Posts
  • 0 Reply Likes
I think i know what the problem seems to be,

looking at the API Data:

"forecast":{ "txt_forecast": { "date":"2:00 AM CEST"

Right now it is 21:30 PM CEST here, so the forecast data is simply outdated ( by 19! Hours), where as the forecast data from the website seems to be updated way more frequently.

(At 21:30 PM CEST the website forecast states: Source: BestForecast at 3:20 PM CEST on April 25, 2013)

So the API Data is 13 hours behind.

Is this a bug? Or is the data from the API call just updated every 24 hours?

Don't get me wrong on this, i like the api design and the 500 free calls per day, but weather data 19 hours old is just totally useless.

So could you please confirm whether this is a bug or the forecast api is just updated every 24h?

regards
Binka Boeren
Photo of Chris Bennett

Chris Bennett

  • 2 Posts
  • 0 Reply Likes
can we get a response on this? JSON seems to be off on almost everything, while the xml matches pretty closely, what gives, is there a bug in the JSON?
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
when I look at the origin files they seem the same. what are 3 URLs (main site, json, xml) that illustrate this point that you see? the spot check I give seems fine, but I want to recreate what you're seeing so I can investigate further.