@idefix37 exactly

@rittels Thank you very much. It works again.
Congratulations for the great work.

@idefix37
Great, Thanks. It confirms my assumption.

@threlfa7 Hello, thank you for feedback, we will consider it.

@mtrunz anybody can verify independently this works?

hangs during "loading directly from npm" for me

@slonl Hello, please see the related thread here.

@mtrunz Hello, plugins were updated with the last version 36, more info here - https://community.windy.com/topic/20837/closed-v36-0-0.

@rittels Thank you for update. Just wanted to check since a user was asking.

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