Posts made by jakubvrana

@marekd Great, thanks.

Awesome, I'm looking forward to it!

Would it be possible to add a link to the app to open plugins? The app already supports plugins but opening them is very cumbersome. I was able to load a plugin in the app using these steps:

1. Open some app which supports links but doesn't display them directly (e.g. WhatsApp works, Chrome or Facebook doesn't).
2. Open https://www.windy.com/plugins in it.
3. The OS (at least iOS) knows that there's an app which could open this link and opens the app instead.
4. Now I can load a plugin in the app.

I have many users interested in using my plugin in the Windy app.

The forecast from pluginDataLoader has these fields:

cbase: 4552
convPrecip: 0.1
day: "2019-11-05"
dewPoint: 278.5
gust: 8.0132
hour: 12
icon: 20
icon2: 20
isDay: 1
mm: 0.2
moonPhase: 7
origDate: "2019-11-05T13:00:00+01:00"
origTs: 1572955200000
pressure: 99904.47
rain: 1
rh: 76
snow: 0
snowPrecip: 0
temp: 282.5
ts: 1572951600000
weathercode: "OVC,CU,CS,,-,RA,,"
wind: 3.7
windDir: 234

Most of them are pretty self explanatory but can you please explain the meaning of icon, icon2, moonPhase and weathercode? Ideally at https://github.com/windycom/windy-plugins/blob/master/docs/WINDY_API.md#module-plugindataloader.

I'm interested mainly in displaying a simple weather icon - sunny, cloudy, rainy.

I make this request to https://api4.windy.com/api4/data/forecast:

{
  "model": "gfs",
  "lat": 49.9609,
  "lon": 14.6958, 
  "key": "---key---",
  "plugin": "windy-plugin-pg-mapa"
}

I receive this response:

{"header": {
  "model": "NOAA-GFS",
  "origLat": 50.53654293419482,
  "origLon": 14.889134366246362,
  "note": "Requested ECMWF data are FAKE and just for dev purposes."
}}

Note that I made a request for GFS but I got a ECMWF fake response. Also origLat and origLon doesn't match lat and lon which is probably related.

I would like to become a core Windy contributor and have my plugin windy-plugin-pg-mapa to be made an official Windy plugin.

@ivo said in How to document a plugin?:

Basicly the plugins are a slight security threat running JS in the same context. We plan to make nice plugin Gallery and loading/opening plugins much more easy, yet we do not believe that opening URL is good idea.

This way an attacker can submit an attacker can submit a link with malware JS plugin in path. We routinely check source code of published plugins to make sure this will not happen.

A simple solution which is not a security risk is to open a pre-filled form which the user has to confirm. E.g. https://www.windy.com/?plugin=windy-plugin-pg-mapa would open this:

The user then needs to click Load & activate.

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

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

The plugins are actually available on mobile, there's just no menu item for them. If you open https://www.windy.com/plugins 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).

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

I am trying to read wind information from various places on the map and display it (https://pg.vrana.cz/mapa/). The only way how to currently do it is by using Picker - open picker, call getParams() and close it. This is both cumbersome and it also has a lag. The lag is caused by this condition in picker.update():

var t = Date.now();
if (!this.popup || t - this.lastRender < 300)
  return;

this.latestValues is set only after this condition in createHTML(). The outcome is that calling getParams() in quick succession gives values for random places which were read first in 300 ms blocks. I propose this:

1. Set this.latestValues always, not just every 300 ms. If this would be too slow then set it to null and in getParams(), check if it's null. If it's null then set it there.
2. Make the interpolate() method public.

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

@jakubvrana I was able to solve it by this hack:

1. Install Header Editor.
2. Add rule Modify response header with header name Access-Control-Allow-Origin and value https://www.windy.com.
3. Add a second rule Modify response header with this custom function:

let access = false;
for (let i = 0; i < val.length; i++) {
  if (val[i].name == 'Access-Control-Allow-Origin') {
    if (access) {
      val.splice(i, 1);
    }
    access = true;
  }
}

I don't know why both these rules are needed, the first one shouldn't be needed. However if I don't add it then the headers are not modified.

@Okocedion Thanks for this plugin. However, it currently doesn't work due to this error:

Access to fetch at 'https://pg-api.ovh/sites/lng/12.390466781303324/15.862146468803326/lat/49.44939061604292/50.29198304347857/' from origin 'https://www.windy.com' has been blocked by CORS policy: 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.

The server returns the header twice:

HTTP/1.1 200 OK
Server: nginx/1.14.0 (Ubuntu)
Date: Wed, 30 Oct 2019 20:10:15 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 678
Connection: keep-alive
X-Powered-By: Express
Access-Control-Allow-Origin: *
ETag: W/"2a6-sPNj407SokPzs0acOOaRqsoVSiM"
Access-Control-Allow-Origin: *

Moreover, https://github.com/xVinCe/pg-api doesn't exist anymore so I couldn't try to fix this myself.