I've created windy-plugin-flymet. It displays layers from FLYMET in Windy. The advantages over the official website is easier time travel, combination with Windy forecast (e.g. wind) and usage together with other Windy plugins (e.g. PG map). I have the permission of the author (Petr Horák) to use the images.
Would also love to open a plugin from the URL. See discussion here: https://community.windy.com/topic/8925/how-to-document-a-plugin
It is considered a potential security threat. I though it was only possible to inject JS if the author of the plugin actively allows it, by appending a script element. I may be wrong?
There is a fetch error:
The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Header set Access-Control-Allow-Origin "*"
Thanks, this allows me to get plugins also on iPad and cell phone which was not possible with the app nor the mobile web. As it automatically opens the app I can’t save a bookmark. So I put your post in favorite.
@Oilyan @vsinceac I'm not sure what the problem is. I just tried it again and for me, it still works for me (both on PC and on mobile). You should be able to find the option to open it in the context menu (right-click on the map on PC; long tap on the map on mobile). You can move the picker afterward as well, just make sure not to clock on a city label as that opens the weather forecast and closes the plugin pane.
NWP forecasts are generally available to public in GRIB format, which contains a grid of rectangular cells - regularly distributed over the coverage area - for each parameter/level.
Parameters of NOAA's GFS 0.25° model (actually it is its full name; there is also GFS 0.5°), are well provided on grids with cells of 0.25° X 0.25° (lon/lat WGS84), one value by cell.
Thus, saying resolution 0.25° (or corresponding distance in km. on Earth at some latitude), is not an error; it corresponds to the distance between two values on the grid, i.e. to the resolution of the model as displayed on map (independently from the computed resolution in factory).
E.g. for lat=0°, distance between two values is 27.8 km for GFS 0.25°, while at mean Europe latitudes (lat=45°), the resolution is 20 km (see self-explaining image above).
For model values displayed on map as color shading (palette), or when user click on the map, intermediate values are extrapolated from neighbour cells values to the selected position (I don't know which extrapolation or smoothing algorithm Windy uses, there are many of them).
From my pov., the best would be to provide the resolution of a model in ° WGS84...
Defining the grid cell resolution as distance on Earth may be tricky, as it mainly depends on the latitude.
E.g., which would be the distance between two values of GFS 0.25° at levels at dozens of Km above the Earth?
Other models (e.g. DWD's ICON) are computed and provided in grids with hexagonal cells; they should generally be converted to square or rectangular grids in order to allow map renderers to handle them; here, the rendered resolution is not the same as the original one.
Hi. The close button on the mobile lhpane disappeared a while ago.
I add the following to bring it back:
< div class="mobile-header">
< div class="mh-closing-x iconfont clickable" onclick="W.plugins['windy-plugin-name-of-plugin'].close()">}< /div>