Condition temperature is wrong | The WeatherAPI Community Customer Community

We use several weatherstations for our business (cumulus drizzle) and noticed that one weatherstation provides a wrong actual temperature for days, always exactly -1.3°C instead of 10°C at the moment, as weatherstations in the neighborhood report. -1.3°C is very cold, a winter temperature, we have pleasant temperatures here ...
Don't you ensure the correctness of provided values by comparing with stations nearby?
Can you exclude a weatherstation with incorrect values?
We use the geolookup call `/hourly/geolookup/conditions/q/46.7963469,14.4352882.json`

Please WU, give me feedback on this issue.
BR from Austria

meo

2 Posts
0 Reply Likes

Posted 1 year ago

1 year ago

Victoria Gardner, Official Rep

658 Posts
93 Reply Likes

BR, would you please give me some of the station IDs so I may look into this?

Victoria Gardner
victoria.gardner@ibm.com

Comment

1 year ago

Victoria Gardner, Official Rep

658 Posts
93 Reply Likes

I'm guessing that you're referring to IMAGDALE22, Haus Morak. One of the problems with attempting to smooth data, as you're suggesting, is that different PWS can be "nearby" but in very different locations nonetheless. As far as I can tell, it's more than 1000 feet higher (300+ meters) than other nearby stations. It may be that their temperature gauge is broken, and they don't need it. Other parts of their data do seem to vary.

But I'm checking into this more.

(Edited)

Comment

1 year ago

meo

2 Posts
0 Reply Likes

Dear Victoria,

Thank you for your replies. Yes, it concerns IMAGDALE22.
It seems to be broken, the PWS always reports the same temperature. And it's a wrong one, definitely. Would be nice, if stations with wrong data are excluded for requests based on coordinates... We thought that we get triangle data when requesting coordinates and not a specific station. Or at least verified data, so that we don't have to survey the quality on our part.

Many thanks and kind regards,
Siegfried (meo)

Comment