Please, please, please, add the option to automatically load a plugin specified in the URL. It's annoying to always need to find my plugin in the list and open it manually. Also, it's hard to refer a plugin to other people, I need to give them instructions instead of just a URL.

I understand that there are some security concerns but can you allow this at least for the official plugins that show in the UI?

When doing it, please allow loading more plugins at the same time, the URL could be e.g. windy.com/?plugin=pg-mapa&plugin=airspaces.

Please remove my plugin Aladin wind (windy-plugin-aladin). The data source is gone and it's not probable that it will be back.

Please also remove the plugin Paragliding flyability (windy-plugin-pg) which is not mine. Its data source is also gone, https://pg-api.ovh/ is not even in the DNS anymore. This plugin didn't work for long periods in the past. I've contacted the author several times which always helped only for a short time.

This layer is extremely over-optimistic. It predicts heights for 1000 m or more higher than they are predicted by other methods (and then they really are). Take a look at the screenshot: The Thermals layer predicts 3200 m (which is extremely rare in Czechia) whereas it will actually be around 1890 m (as predicted by another method).

The method used by my plugin has its “proof” in the diagram:

I have no idea how the number coming from the Thermals layer is computed but it's most certainly wrong.

@ivo The plugins are great. Would it be possible to persist the plugins I loaded? Either by storing the loaded plugins in Local Storage or at least by putting the loaded plugins into URL (something like /?plugin=windy-plugin-pg).

windy-plugin-flymet: Displays layers useful for glider pilots from FLYMET in Czechia.

windy-plugin-aladin: Displays wind direction and speed in the picker according to the Aladin forecast in Czechia.

Let us know if we should add your plugin to the list

I've created windy-plugin-pg-mapa. I would like it to be published. Please let me know if you need me to do something else.

There's also a Windy API version at https://pg.vrana.cz/mapa/ which works only with GFS but it's available on mobiles too.

I've created a poor man solution to load the plugins I always use with a bookmarklet. Create a browser bookmark with this URL (strip the newlines if need to but e.g. Chrome does that automatically, keep javascript:):

javascript:
function loadPlugin(id) {
  document.querySelector('[href="#load"]').click();
  setTimeout(() => {
    const input = document.querySelector('[placeholder="Example: windy-plugin-hello-world"]');
    input.value = id;
    input.dispatchEvent(new InputEvent('input'));
    input.nextElementSibling.children[1].click();
  });
}
loadPlugin('windy-plugin-pg-mapa');
setTimeout(() => {
  W.broadcast.fire('rqstOpen', 'plugins');
  setTimeout(() => loadPlugin('windy-plugin-flymet'));
}, 3000);

Then open https://www.windy.com/plugins and click this bookmark. It will open the plugins I use.

@ivo You can count on me.

I've temporarily solved it by using an internal API:

W.tileInterpolator.createFun(interpolate => {
  var data = interpolate({lat, lon});
});

@marekd The plugins aren't available on mobile which is a deal breaker for me. But I'll probably create both the plugin and the app using API.

@korina @rittels, thanks for the explanation. The “issue” was with the newly available modelElevation. My plugin expected that there will be also temp-surface if there's modelElevation. It's great that modelElevation is now available for the other models.

In data returned from windyUrls.getMeteogramForecast, there used to be temp-surface. Now it disappeared for all models but ECMWF. Can you please bring it back?

@3wingweather You can now use an URL: https://www.windy.com/plugins/windy-plugin-airspaces.

Prosím o vyřazení pluginu windy-plugin-aladin, jeho datový zdroj vyschl.

A prosím o změnu titulku windy-plugin-pg-mapa na Paragliding takeoffs (smazat in Europe).

This layer is extremely over-optimistic. It predicts heights for 1000 m or more higher than they are predicted by other methods (and then they really are). Take a look at the screenshot: The Thermals layer predicts 3200 m (which is extremely rare in Czechia) whereas it will actually be around 1890 m (as predicted by another method).

The method used by my plugin has its “proof” in the diagram:

I have no idea how the number coming from the Thermals layer is computed but it's most certainly wrong.

@ivo You can count on me.

I compared the forecasted and observed wind at some paragliding spots in Czechia. This was the result:

1. Arome, IconEu
2. Aladin (local model not available in Windy)
3. GFS, ECMWF

Raw data: https://pg.vrana.cz/meteo/

This matches my random observations. If IconEu and ECMWF disagrees then IconEu is usually right.

@ivo Tak už tam jsou i celosvětová data. Jednak prosím o přejmenování na „Paragliding takeoffs“. A jednak prosím o instrukce, jak postupovat pro integraci přímo do Windy.

Please remove my plugin Aladin wind (windy-plugin-aladin). The data source is gone and it's not probable that it will be back.

Please also remove the plugin Paragliding flyability (windy-plugin-pg) which is not mine. Its data source is also gone, https://pg-api.ovh/ is not even in the DNS anymore. This plugin didn't work for long periods in the past. I've contacted the author several times which always helped only for a short time.

ECMWF contains airData.header.modelElevation but the other models don't have it. There's only airData.header.elevation which is the real elevation of the place and it could be off by 500 meters or more from the average elevation of the triangle considered by the model (e.g. in mountains). This makes sounding unusable with these models because we know the ground temperature (temp-surface) but we don't know where the surface is. There's no header.modelElevation and data['gh-surface'] contains only null.

Can we please get modelElevation for the other models too? I believe it must be somewhere otherwise the *-surface values wouldn't make sense.