Hiking in different altitudes (Android app)
-
Imagine that in the next 3 days you plan to hike from 500 meters altitude to 3000 meters in a mountain range. If you want to see the forecast to all these locations, it is problematic in the current app (Android).
For example, these locations: 1) Olympos National Park or 2) Zonaria Central Macedonia
The first one says altitude 1834 meters and the second one 2643 meters. You can confirm these altitudes by scrolling on the left, lets say, the Basic ECMWF and finally it says some things like Sunrise, Sunset, Dusk ... and the Elevation...
The point is that the models give fully different forecasts, something that does not happen for small cities with a stable altitude.
For example if you get into Zonaria Central Macedonia, compare forecasts, the GFS says that the maximum temperature in the next 2 days will be 32-32 C, while the METEOBLUE says 18-19 C. This isn't because "they disagree", but because they are referring to different altitudes.
So do you plan to fix somehow this issue? Maybe a linear regression mapping on front-end could be enough?
Finally, if I plan to hike the next days to 3 or 4 thousand meters altitude, what is the optimal way to use the current Android app for forecasting?
-
S Suty moved this topic from Windy Premium on
-
The low or medium resolution global models are not accurate for temperature forecast in mountains. Their orography model is too coarse to give a high calculation precision.
To know the discrepancy between the estimated elevation by the selected model and the real elevation you can look at Sounding forecast.
I agree, a corrected temperature could be provided by Windy with an algorithm based on the average decreasing of temperature per altitude meters.
It is what Meteoblue does more or less with its point forecast model. This Swizz model is quite good in mountain for temperature forecast.
-
@idefix37 thank you for the answer.
Two more questions:
-
On the sounding forecast there is the ICON model which does not exist in compare forecasts, while the METEOBLUE exists in compare forecasts but not in sounding. Why does it happen?
-
Wouldn't it be more practical to show the reference altitude (model elevation) in the compare forecasts mode? 5 altitutes: the average geographical altitude of the region and each model's reference elevation of that region.
-
-
- Meteoblue just provides data at surface, not at higher levels. So there is no way to make a sounding forecast with this model.
- Model elevation and location elevation would be a good information in Meteogram or in Compare table. But I do not think that the average elevation should be useful because it is roughly similar to the model altitude.
-
So, I mean, can I ask somehow the programmers team to put this feature in the coming updates? how? Are there somewhere suggestions for the next updates?
-
@kkantoutsis
Here your suggestions are forwarded to the development team by @Ondřej-Šutera.
I already asked to show the model elevation and location elevation in meteograms some years ago…
