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

@danielarnett Thank you for suggestion, we may add such feature in the future.

@rittels I forgot to mention that service ceiling climb rate (where normally aspirated engines loses their vertical performance down to around 100 ft/min) is also needed, so it will be 3 entries total for a climb phase:

vertical speed at sea level; vertical speed at service ceiling; and air speed.

In this case the final vertical speed (and thus, enroute time) will be dependent (calculated) on Min and Max values.

For example, if it set Max value to 500 ft/min (mean sea level) and Min value to 100 ft/min (e.g., at 16000 ft MSL) my vertical speed will be 400 ft/min at 4000 ft, 300 ft/min at 8000 ft etc.

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

@Korina Thank you for you quick response, I will try both solution.

@zach11 Hello, you will not be able to access Airfield data through our API, it is not a part of it.

@rittels
Yes it works now. Thanks for a great plugin.

@windy2022user

Hi. The closest you can get is to bookmark the address for the plugin:

www.windy.com/plugins/windy-plugin-airspaces

You will then get to a disclaimer message by Windy, but just click OK.

Also: You can bookmark www.windy.com/plugins

You can rearrange the plugins, by dragging them up and down, the order will be stored in your browser, but unfortunately not in your account.

@rittels It worked now, thank you 🙏

@wb7qni Hello, thank you for suggestion. There are currently no such plans, but if we gather enough feedbacks, it may change.

@rittels Thank you for the clarification! For cases with reduced vertical velocity, the trajectories are still highly valuable. And fun to work with. Best

@nbelicard. Fixed now.

@shashighedia
I guess @johnckealy is working on it

@petra-pik thanks for the heads up, didn't realise it

@rittels @jakubvrana @vicb If you have accessed the property bounds of any model/product (eg. W.products.iconEu.bounds), please change your codes.

We added into client version 34 support for general polygons, so instead of { west, east, north, south } object it is an array of [lat, lon] arrays: [[lat, lon], [lat, lon], ...].

All inner methods using bounds still have the same interface, only this property has been changed.

@johnckealy many thanks for the explanation- much appreciated.