More information on how to read Thermals is provided under "info" icon

@idefix37 JMA was the first place I went to regarding researching models for Japan. LFM has only 10 hours of forecast so I was thinking more about using MSM.
Final choice depends on demand though, as LSM has much finer grid (2km vs 5km of MSM)

@gavin-q Consider picker just a preview tool, detail forecast is much more precise. When zooming, for example, picker data change quite a lot as different data tiles are used.

Example (speed and direction changes):
closest:

further away:

far away:

@tanpat Hello, it might be that windguru is using old v1 dataset for 1.3 km Arome but v2 for 2.5 km Arome. That is why 1.3 km Arome on windguru works and 2.5 km doesn't.

Since we're using v2 dataset (which is recommended by MF and is also documented - v1 isn't) we unfortunately won't be getting any data updates before v2 dataset is back and running.

@idefix37 There is something seriously wrong with merging AROME and ECMWF. Notice that after 5 days (that's when forecast step of ECMWF changes from 1h to 3h) forecast goes haywire. It is more visible with 1h forecast, but 3h forecast is wrong too. Multiple days (notice temperature going up and down - "red hills") get mashed up into one. We will investigate and fix this, thank you for the report.

3-hour step

1-hour step

NOAA GFS model has not been updated since yesterday 12:00 UTC due to connection problem to NOAA servers.

Update: Connection to NOAA servers has been restore and GFS model is updated again.

Hi @gavin-q, can we request full-screen screenshot next time you observe the discrepancy? I've tried to replicate your issue with no luck. Are you sure you've selected wind at the surface (which is shown in the basic forecast)?

@vicb Sorry, that is something we want to keep to yourselves yet.
We're open to discussion on what should be forecasted under which conditions though.

@gavin-q @Korina I was able to reproduce same error with clean Firefox installation (and other chrome-based browser as well)

https://www.windy.com/-25.486/30.301?-25.504,30.322,13,i:pressure,m:cWGagZF

While detail shows wind from around 260deg, picker and particles show wind from around 280deg. It might be that in low wind speeds, discrepancies between map (and picker which uses map data) and forecast detail happens.

As map data go through transformations during import (from source projection to web-mercator), slight differences happen and are most visible with low values (similar thing happens with low precipitation). Point forecast detail has slightly more accurate data while map is (due to these technical limitations) intended more for general situation overview.

I'll investigate this issue further now that I have something to lean on

@richardaneale While you can't directly modify color scale from app, it is synchronized via cloud. So logging on the web with the same account you have in the app and changing the scale will get transferred to the app.

This is my modified CAPE scale on the web:

And this is what it looks like in the app:

@mike-bosschaert thank you for letting us know (this is radar, not satellite by the way) and it's most likely interference that happened from 10:00 UTC to 11:00 UTC and it is located right around radar station itself.

Radar interference happens quite a lot. These are some other examples:

Hello @dawiese, do you mean showing it side by side, something like this?

To download this video just click with right mouse button on this link and select "Save link as..."

This video is licenced under Creative Commons licence (CC-BY 3) and can be used/modified freely in any possible way. Just mention Windy.com

Create your own animation at https://www.windy.com/animate

@mikecurt I've checked both NAM (https://www.nco.ncep.noaa.gov/pmb/products/nam/) and HRRR (https://rapidrefresh.noaa.gov/hrrr/). Can I ask for source that says that NAM or HRRR cover Canada? Thanks

@richardaneale While you can't directly modify color scale from app, it is synchronized via cloud. So logging on the web with the same account you have in the app and changing the scale will get transferred to the app.

This is my modified CAPE scale on the web:

And this is what it looks like in the app:

@richardaneale You can modify color scale for any layer (including CAPE Index) in the settings: https://www.windy.com/colors

@panagiog you can already do that a little bit by selecting forecasting weather in the bottom-right corner:

Then parameter of selected layer of your favorite places has colored background while cities remain transparent:

Is that what you're looking for?

@danfarina damn, you got quite a nose for these (:
Thanks for the report, fresh data is available now

@danfarina We have isolated the issue with HRRR updates and all should go smoothly from now on. If you see HRRR hasn't been updated for more than 2 hours, feel free to let us know again

@idefix37 There is something seriously wrong with merging AROME and ECMWF. Notice that after 5 days (that's when forecast step of ECMWF changes from 1h to 3h) forecast goes haywire. It is more visible with 1h forecast, but 3h forecast is wrong too. Multiple days (notice temperature going up and down - "red hills") get mashed up into one. We will investigate and fix this, thank you for the report.

3-hour step

1-hour step