Best posts made by jakubvrana

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.

@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.

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.

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.

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.

It works for me now too.

The plugins are actually available on mobile, there's just no menu item for them. If you open https://www.windy.com/plugins on mobile then you can use them. If you open this link from other app (not a browser) then you can use them even in the Windy app (which hijacks the opened URL and opens itself, at least on iOS).

Wind comparison allows selecting ECMWF, GFS and Icon as primary but Arome and Meteoblue not. I see no reason for it as both Arome and Meteoblue could be selected as a model for the map. Arome even stays as primary when showing the wind comparison and it is then in this weird state that it's both selected and disabled:

Meteoblue couldn't be primary for an unknown reason. Could it be just because it's named NEMS in the model selection and Meteoblue in the Wind comparison? Please unify this, it's confusing.

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.

@marekd Great, thanks.

This seems to be renamed to @windy/@plugins/plugin-data-loader. Is this change permanent or is it a bug? If permanent then please fix the docs and examples but I'd suggest keeping the original name.

@marekd, thanks for the update. Backwards compatibility is sacred for me so I'm surprised that you break it just to change a name, especially if there are official docs and examples around. I can understand that this was an omission but I don't understand not reverting it once reported. Can you please at least keep both names? (I don't know if some kind of aliases are possible here.)

My plugin https://www.windy.com/plugins/windy-plugin-pg-mapa now also uses data from DHV and covers the whole Europe. Can you please change the title and the description?

Czechia and Slovakia -> Europe
paragliding-mapa.cz -> paragliding-mapa.cz and dhv.de (please link https://www.dhv.de/db3/gelaende/)