Dear Ivo and team,
thanks a lot for integrating this modell.
DWD writes
"Based on model runs at 00, 06, 09, 12, 15, 18 and 21 UTC, ICON-D2 provides new 27-hour forecasts every 3 hours. The model run at 03 UTC even covers a forecast period of 45 hours."
Currently, Windy tells me
"Updated 6h ago (ref 06Z)
Next update expected at: 03:28 PM, in 0h 58m 5s
Update interval: 6 - 7 hrs
Reference time: 2021-11-10T06:00:00Z"
Could you please explain?
Best regards, Daniel
Obviously it is very unlikely that there are "no clouds" next to a voxel of low cloud base.
I assume that it is either a renderer error, or (more likely) an artefact of the model output that clips all clouds that are < 50% coverage.
Either way, the usability of this data layer for VFR flight planning is very limited.
Wow, that was fast. Thank you very much indeed!
Dear Ivo and team,
thanks a lot for integrating this modell.
DWD writes
"Based on model runs at 00, 06, 09, 12, 15, 18 and 21 UTC, ICON-D2 provides new 27-hour forecasts every 3 hours. The model run at 03 UTC even covers a forecast period of 45 hours."
Currently, Windy tells me
"Updated 6h ago (ref 06Z)
Next update expected at: 03:28 PM, in 0h 58m 5s
Update interval: 6 - 7 hrs
Reference time: 2021-11-10T06:00:00Z"
Could you please explain?
Best regards, Daniel
Low clouds are clouds in the 0-7000ft layer. If I use this for VFR go/no-go decisions, I will never go flying again.
Obviously it is very unlikely that there are "no clouds" next to a voxel of low cloud base.
I assume that it is either a renderer error, or (more likely) an artefact of the model output that clips all clouds that are < 50% coverage.
Either way, the usability of this data layer for VFR flight planning is very limited.
When working with some layers of ECMWF, like Cloud Base, it looks to me as if some tiles are not loading.
Is this part of the model data or a windy bug? Maybe a developer can comment.
Thank you very much in advance.
@ivo said in Adding new ICON-D2 model:
@justinlimbo Model looks really good.
We will implement it
Do you have an ETA on the ICON-D2 implementation? Thanks :-)
Upload your own KML, GPX, GeoJSON file at https://www.windy.com/uploader
@marekd, you are probably aware of it already, but I just wanted to point out that after your (unbelievable quick) fix, not only your gusts but also your other data is showing zeros after some time on the route...
Wow, that was fast. Thank you very much indeed!
@marekd and dear windy developers
For me it seems like your "speed option" is not really working. Windy (still?) behaves likes the vessel speed is infinite, meaning it is calculating the weather along the route with the forecast at the route start time. See the two screenshots. First one is the wind map at the start of the route. Second is the wind map during the route at route point #2: the weather at the current location on the map is very different from the route view.
It is also obvious by changing the vessel speed (e.g. 1kt, 10kt, 100kt, 1000kt): the weather along the route never changes.
