Hello,

As a developer, paragliding enthusiast and traveller, I'm very interested in Windy plugins, as it would allow me to develop my dream feature: An improved paragliding sites map, inspired by paraglidingmap.com but much better because it would have Windy's performance and great features :)

Starting from the base windy pg overlay, here are a few ideas I would like to implement:

• Change icons based on site orientation, change icon color based on flyability (see below)
• Add a flyability feature (based on wind strength & orientation & others, something like paraglidingmap but better :) )
• Add a detailed popup for flyability
• Add an "open in google maps" feature
• Activate only at a certain zoom level (for performance reasons)
• From a click anywhere on the map, add a "where are the closest flyable options from here?" option
• etc.

Therefore, I have a few questions:

1. Do you think it is feasible?
2. Is the paragliding overlay developed as a plugin on your side, and is there any chance I could get access to the code?
3. If no to 2), I see you use pgearth API, is there a way to access the these infos from my plugin, or would I have to get all the infos on my own?
4. Would it be best to alter the overlay you already have (if it is even possible?), or to create a separate one?

Thank you

Hello,

A first preview version of my plugin is now published on NPM under the name windy-plugin-pg : https://www.npmjs.com/package/windy-plugin-pg

Github with an up-to-date readme: https://github.com/xVinCe/windy-plugin-pg

It only works at zoom levels > 8 to avoid having too many icons on the screen.
It updates in real-time when you press the play button :)

I am not very happy with how the icons look, I could use some help from a designer I guess ;)

@ivo My biggest limitation for the future is that I am limited to the wind layer, and can't access other infos.
Is there any chance that I may access other layers without displaying them in the future?
I would need at least wind gusts, rain and clouds (at ground level).

Hello,

A first preview version of my plugin is now published on NPM under the name windy-plugin-pg : https://www.npmjs.com/package/windy-plugin-pg

Github with an up-to-date readme: https://github.com/xVinCe/windy-plugin-pg

It only works at zoom levels > 8 to avoid having too many icons on the screen.
It updates in real-time when you press the play button :)

I am not very happy with how the icons look, I could use some help from a designer I guess ;)

@ivo My biggest limitation for the future is that I am limited to the wind layer, and can't access other infos.
Is there any chance that I may access other layers without displaying them in the future?
I would need at least wind gusts, rain and clouds (at ground level).

Hi,

When working on my plugin, I found that the dev mode is removed any time the bottom weather bar is displayed. the /dev is removed from the URL.

Is there a reason or is it a bug?

Thanks,

@tomslavkovsky I've had other priorities lately, but will start working on it again soon.

I also had to develop a proxy API for paragliding earth data, because they serve it over http when I can only use it in https in my plugin. Repo for this API is here: https://github.com/xVinCe/pg-api

So next thing I need to do is get a cheap server to host my API on (with https), and then get back to where I was on the plugin!

Thanks a lot @ivo, I should now be able to get a first version running, I'll work on it and publish a first version asap :)

@ivo I have started playing with my plugin, which you can find here:
https://github.com/xVinCe/windy-plugin-pg

I have used a small set of data (Andalucia) from paraglidingearth for testing purposes.

I can display the sites and orientation, but I'm stuck on a few issues:

1. I can't get the weather infos for the sites. I have tried an ugly temporary way (see flyability branch) by listening to pickerMoved and moving the picker programatically but it doesn't work. What I would need is a simple way to get the wind object from a given set of coordinates.
   1a. Later I would also like to check for nebulosity and rain but I don't know if it would be possible without going back to the server?
2. I can't get the zoom level. I hoped to find it in the store, but I didn't. I would like to use it to start displaying takeoffs at at certain zoom level, and landings when you get even closer.
3. For the full pge dataset, I have contacted them to get access to their API, but if there is a way to get them directly from Windy it would be best.

Thank you for your time.

@ivo thanks for your quick answer.

10 years exp in web dev. Never worked with leaflet but I'll learn.

I've forked your repo & setup my dev environment but wanted your input before investing too much time :)

For the example, I don't think it's necessary, unless it's very different to the boat tracking example.

Hello,

As a developer, paragliding enthusiast and traveller, I'm very interested in Windy plugins, as it would allow me to develop my dream feature: An improved paragliding sites map, inspired by paraglidingmap.com but much better because it would have Windy's performance and great features :)

Starting from the base windy pg overlay, here are a few ideas I would like to implement:

• Change icons based on site orientation, change icon color based on flyability (see below)
• Add a flyability feature (based on wind strength & orientation & others, something like paraglidingmap but better :) )
• Add a detailed popup for flyability
• Add an "open in google maps" feature
• Activate only at a certain zoom level (for performance reasons)
• From a click anywhere on the map, add a "where are the closest flyable options from here?" option
• etc.

Therefore, I have a few questions:

1. Do you think it is feasible?
2. Is the paragliding overlay developed as a plugin on your side, and is there any chance I could get access to the code?
3. If no to 2), I see you use pgearth API, is there a way to access the these infos from my plugin, or would I have to get all the infos on my own?
4. Would it be best to alter the overlay you already have (if it is even possible?), or to create a separate one?

Thank you

Vote 2: Arome