Current conditions wind_kph values are all wrong

  • 1
  • Problem
  • Updated 5 years ago
Current conditions wind_kph values are all wrong, they are always 1. wind_mph looks fine
For example, Miami, Fl wind_kph=1 wind_mph=10
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
  • sad

Posted 5 years ago

  • 1
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
I see what you mean and fixed it on our development server. Just need to wait for code release to send out the fix.
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
Thank you Brendan for the quick response!
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
This is fixed in production now. Thanks for pointing out the bug.
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
The returned type has been changed!!!!
It used to be LONG now it is a STRING!

THIS IS REALLY REALLY BAD. ALL OF MY APPS CRASH BECAUSE OF THE CHANGE!!

PLEASE FIX IT ASAP!!!
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
wind_mph has number type
wind_kph has string type

New York,NY
"wind_kph": "15", (string)
"wind_mph": 9, (number)

Please fix this ASAP, because I cannot update my iOS app immediately, they have to be approved first.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
Looking at it right now...
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
This is fixed now. Let me know if it stops the crashes.
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
Hi Brendan, it looks good so far.
I think both issues are resolved. I already received a few emails about it.

Thank you so much for your fast response. You are the best!

I would like to also suggest something. Some other weather APIs use versioning system i.e. each update is part of a "release" and the API version has to be specified in the query. Last few API versions should be suppered in parallel and drop support the old versions only after a a year or two.
It would give developers enough time to test new features and WU to roll out bolder changes in low risk beta versions first.

I'm very happy with WU API, I tried most of the available alternatives and WU is far the best. It is not cheap but the quality of the forecast is pretty good and apart from this issue it was very reliable.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
Yeah, I know what you mean about versions. We are definitely checking out the right way to do this in the future that satisfies both previous versions and future enhancements. In this case this seemed like a bug worth fixing. But having a discreet version number would have saved the trouble in this case.