Multi model wind forecast arrows don't match table
-
This bug has been around at least 5 years. We are frankly sick of it. When you try to get a wind forecast for a particular point, the values in the table have zero relationship to the wind barbs depicted at the point. Please see image below.
(https://drive.google.com/file/d/1oK9ZAs77EgQVx0UpspFEz1Ogs7U6PwGb/view?usp=drivesdk)
As an aside, adding images to bug reports on a mobile browser is insanely difficult. Why don't you give us a file picker instead of forcing us to upload the image to Google drive and add the link to the post!
-
@stevecrye it's not just the app that's totally broken, the website shows the same errors!
The wind barbs from a point multi-model forecast have absolutely no, I'm saying zero, relationship to the numbers in the table! They're not even close. It's like the arrows are completely random. I don't know whether to believe the barbs, or believe the table values.
This is completely unacceptable!
Screenshot below.
https://drive.google.com/file/d/1oZ2_ZTdExW484Om0npnedN4Ydryql04a/view?usp=drivesdk
-
Ditto stevecrye, I'm seeing the same thing. Also, checking a point at a given hour via the app vs the website shows different results.
-
@stevecrye @msechrist
This bug has been reported and is planned to be fixed in v47 as said here -
@idefix37 thank you for replying and fingers crossed it it will get fixed!
Some extra information that might help you with troubleshooting it. If I force stop the app, open the app, don't change the first model to something other than ECMWF, it seems to work for the first point I pick on the map. But if I use the app for a while then move the location the bug will come back.
-
@idefix37 thank you again for this information. It begs the question: because the bug affects not just the app but also the website, can't they fix the website first?
I guess what I don't understand is the relationship between the code running on the back end servers and the version of the Android app.
If the back end servers were fixed, wouldn't the existing version of the Android app function correctly?
-
@stevecrye
Sorry I am not able to answer your question.
