Hello,

At this moment, querying data for current weather on city ID 2759661 results in Fog weather with 0 visibility.

Querying 24 hour forecast results in a fairly consistent Cloudy weather.

The current Fog weather forecast is severely wrong, when cross referenced with 24 hour forecast and outside sources. What is happening?

Category: API

Replies

bleak7 says:
August, Tuesday, 2018 at 12:09PM

Another read on current weather, in present it shows a UV index of 6 which is impossible and completely off the scale considering there's a cloudy sky.

Same city ID 2759661.

In general the current weather API seems to return some off the scale values that do not even coincide with a 24 hour forecast. The latter is way more accurate in data depiction.

Can I get some reply on this please?

bleak7 says:
August, Tuesday, 2018 at 5:14PM

Another weird API behaviour is that sometimes a 24 hour forecast gives me the current hour included, but most of the time it doesn't, starting with the next hour.

Which behaviour is the standard one? This is very disconcerting.

bleak7 says:
August, Tuesday, 2018 at 5:40PM

Another reading for current weather city ID 2759661 gives me 34 degrees which is impossible seeing as there should be at most 24 degrees at the moment according to previous hourly forecast and common sense.

Any chance for a reply?

John says:
August, Tuesday, 2018 at 9:08PM

Hello,

Thanks for the report - We'll forward it to our backend team to investigate.

To answer your other questions:

(1) The first hour returned by the forecast API is the next hour forecast, not current hour.

(2) Observation updates may be delayed up to 1 hour (for free plan users).

In the future, please post only one support question before you have received a response.

Thank you, John at Weatherbit

bleak7 says:
August, Wednesday, 2018 at 8:53AM

Thanks for the reply,

Regarding point 1:

Then you have a problem with your forecast API return. Example:

At 19:10:00 I run a GET on hourly forecast for a given city ID. The return result starts with hour 20 element. At 19:10:03 I run the same GET on hourly forecast for the same city ID. The return result starts with hour 19 element.

John says:
August, Wednesday, 2018 at 6:48PM

No problem - Happy to help!

Free plan responses are cached/delayed, it's likely you are seeing a cached response. Two possible solutions for this:

(1) Account for this in your application.
(2) Reduce the frequency of your API calls. Forecasts update at most once per hour.

Thanks,
John at Weatherbit

bleak7 says:
August, Wednesday, 2018 at 6:54PM

That's good to know, thanks for the tips.

Leave A Reply

What is 6 + 6?