@老刀2002 You probably need to check this post

@Pirzada-Malik Hello, we unfortunately don't have access to the radar data. In case you know about any source, please let us know and we will try implement these data for you in the app. Have a nice day, Niki

I faced a similar issue on Android where widget settings didn’t fully sync after changing units in the main app. What helped in my case: Removed the widget completely Cleared app cache (not data) Rebooted the phone Re-added the widget and then rechecked unit settings inside the app Sometimes widgets keep old cached values, especially after OS updates. For Android 13/14, checking background optimization and battery restrictions also helps, as widgets may not refresh properly. I usually verify system-level data separately as well, just to confirm values aren’t mismatched — using tools like an online reference helps cross-check things from a user perspective.

@Korina Hi It is possible to find somewhere vertical air movement direction and speed?

@Korina I was using Windy but had some questions. This article cleared up all my doubts at once and will be very useful for my future mountain climbing. Thank you.

@Francesco-Cancemi Right now I see Radar data over Sicily and South Italy [image: 1767113647207-a49eddf8-8eb0-4ce2-85ac-4062545a2056.jpeg]

@NataliaAndruk it would be amazing if WASD moved the map.

@Atalantia You are on satellite layer. As satellites look at the Earth from above, this is the cloud tops temperature.

@ViberAir-Dev Hello, you can use it for non commercial purposes.

@Korina said in A difference between reference time and update time: A difference between reference time and update time Frequently Asked Questions ARTICLE 13 26 12.9k Reply Korina 21 Feb 2020, 18:28 Each model has a different update time and it could be confusing what connection does it have with the update time. Here is the explanation: Reference time - is the time when a model starts a new forecast block. It consists of: Initialisation - data are entered into the model, this creates Initial conditions (initialisation time) and then model starts calculating conditions. Assimilation - normalisation on data and assembling data for computation. Computation - calculating the future atmospheric rates of change in time increments. Data extraction - extracting data into regular forecast intervals. Data storage - data are stored and written in accessible format. Data postprocessing - special postprocessing routines For example model ECMWF has an update interval 12 hours (or 6 hours interval for Premium users), that means the first reference time will be 00:00:00Z (Zulu time) and second one 12:00:00Z. Update time is time between the reference time and the actual update. The whole process of data computation takes approximately from 8 to 9 hours. So for ECMWF model the update times are 07:15:00Z and 19:15:00Z. See the exact update times here - When and how often are the weather data updated?. Where to find info about reference and update time: Thanks for the clarification! The distinction between reference time and update time makes a lot more sense now. It’s interesting to see how much processing goes into generating accurate forecasts.

@idefix37 Thanks a lot for looking into it ! I tried something different : importing my gpx file in the Flight planner plugin !!! and it kinda works : I do have to set an average speed which is not ideal but apart from that, the weather map changes with the position along the route. In the gpx file I'd like to display, for each point I have a timestamp and a position (lat/long). There is no speed in the file. But you are right that if you were to calculate the speed, it would be highly variable, anywhere btw 0 and 30kts.

@idefix37 Thank you!

@NNAC It is in the “Clouds, aviation” layer category. [image: 1764771083526-a5f0a789-f3fc-4429-8c27-78775b29a00f.jpeg]