Code contributor

@idefix37 @guy_bottlaender

Thanks, I have removed altitude values from AROME, more honest than using calculated values.

@ken

Thank you. I fixed the flat skewt a few days ago, but another bug crept into extra settings. Will fix later.

@bradleycw

Should work now.

I see the recovered data is no longer included from 6 Aug 21.

Data source: https://github.com/CSSEGISandData/COVID-19

@bradleycw needs some attention, sorry

@guy_bottlaender

Thank you.

Yes, geopotential height is not available for Arome, via Windy. I use calculated values, which is not ideal.

Would you recommend that I leave it out, or use ECMWF?

@idefix37 @dr-mdgrant-windy @marekd

The problem seems to come from the backend:

Weird values. It is very intermittent though. Speed does not appear to play a role, rather the number of waypoints. Probably an interpolation problem of some sort.

@vsinceac @javierbu

Thanks, should be working now.

Hi @vicb

How would write the package.json? how about:

"old_windy_version":{"33.0.0": "path_to_other.js"},
"main": "dist/plugin.js"

So if the version < 33.0.0, use path_to_other.js, else use main.

@jprous Thanks for letting me know. Should work now.

Bug slipped in when I updated the plugin for: https://community.windy.com/topic/16811/plugin-developers-stay-alert-we-are-refactoring-windy-com-client-codes-to-typescript/6

Really cool that you like my plugin!!! Dankie!!

@petehdgs

Try now. You can either use the picker, or go to settings and click: ctrl-click selects WP

then the picker will still see POIs