One of the most requested feature is finally here! Now you can plan your trip or flight with our route planner.

How does it work?

Just use Distance & planning, which is a feature you might already be familiar with, and select the forecast type you need.

For example VFR:

Several points for discussion:

• All winds are relative to the direction of movement by default, i.e. the green arrow pointing to the right is a tailwind, the red arrow pointing to the left is a headwind. You can change direction of movement (form bottom to top, from left to right) or set absolute directions (north up).
• Do you think any particular forecast type or values are lacking?

@stitch Do not be sad, cross section will be soon (it is almost finished, just some UI glitches are missing), but this is even bigger thing with higher priority :-) You will love it!

And here we are, it is alive!

Since the previous beta test was useful and thanks a lot to everyone for joining in, we decided to continue with beta testing. The new version is ready!

What's new in version 35.0.0

• New hurricane tracker with history and newly also with forecast (if available for selected hurricane)
• Added HRRR models for North America
• Fixed bounds for local models
• Tens of bugfixes and improvements

Dev changes (for plugin developers)

• Whole client is now in TypeScript
• Removed @plugins/product-descriptions
• Local model bounds are now 2D array of coordinates: [lat, lon][][]
• Renamed wRender to weatherTableRenderer in @plugins/detail-render
• Removed monkey patching of @plugins/detail-render, @plugins/pois-libs, @plugin/detail and @plugin/picker. It should not affect internal API, but just in case...
• Huge amount of other internal changes without changing client API

(cc: @rittels, @jakubvrana, @vicb, @johnckealy)

How to report an issue from testing?

Just post a comment in this thread below :-) If you provide us with:

• a step-by-step manual how reproduce the error
• what exactly is wrong
• what it should do correctly

It will help us a lot! Thanks.

Please, try to not duplicate other reports. If you found someone else already report the same issue, just upvote his/her post.

How to join beta?

Open https://www.windy.com/beta-test address and follow the instructions. You can leave beta test at any time. To leave the test, just click "BETA" sign on Windy logo (or visit mentioned address again) and follow the instructions as well. In a case of a total disaster, delete the beta=1 cookie for the windy.com domain and refresh the page.

Beta test is available only for desktop (browser) version.

Feel free to disccuss anything! Not just bug reports :-) Thank you for your help!

Do you like Windy and happen to enjoy programming as well? Join us! We are looking for a javascript developer, ideally with sense for UI/UX, but a full stack developer will find their place here too!

We are a small startup with a global outreach and exponential growth. Our service is used by millions of people around the globe, and yet there is just a handful of us. That is why we need help!

We offer extensive workload, freedom and unlimited space for a self-realization.
In return, we expect responsibility, technical (self) education, enthusiasm and interest in Windy. We are looking for someone who is not afraid of hard work and is ready to move forward.

We do not waste our time on endless meetings nor make up a meaningless tasks. We are going after our goal and look for a partner - you.

(Prague internship or remote if based outside of Prague)

You can reach us at (czech website):
https://www.startupjobs.cz/nabidka/16365/javascript-developer

Or send your CV/portfolio to:
hiring@windy.com

🎉 Update released! 🎉

It took us a while until we returned back to the route planner. Thank you for your patience. What is new:

• add speed option (the most wanted feature here in this thread)
• add 250hPa flight level for IFR view

Thank you all for your feedback, it helps us a lot :-)

As this is one of the most desirable features, it has reached the top of our todo list. We cannot promise any exact date, but we are working on it :-)

We have released new sounding plugin. It took us a while, but we firmly believe it was worth the wait.
 

 
 
What's new:

• radiosonde measurements, so not only the forecast, but also the actual measured values with a two-week history (a huge thanks to @mhaberler, @rittels, @wetterheidi and others for their help and giving Windy their awesome radiosonde plugin)
• skew-T log-P diagram support and "non-skew-t" improvements (inspirated by @vicb, @rittels and @johnckealy amazing plugins - thanks!)
• multiple forecast models
• fullscreen support
• mouse tool for finding thermals conditions
• cloud estimation based on relative humidity
• ability to zoom (and drag when zoom is applied)

 
Are you missing any additional functionality? Do you have an idea for improvement? Did you find a bug? Please let us know!

Hey guys. We would like to try public beta testing. Consider this as a pilot project :-)

What's new in version 34.0.0

• Added ICON-D2 model
• Provided login & registration on Windy.com website without redirecting
• Allowed "remember last location" as a start location in settings
• 3D globe is no more in test mode
• (Premium) Allowed "remember last overlay" as a start overlay in settings
• (Premium) Allowed "remember 1h/3h forecast setting" in settings
• Tens of bugfixes and improvements

Dev changes (for plugin developers)

• Finished Windy core refactor to TypeScript
• Added support for 3rd-party plugins to load specific plugin version for specific Windy version (see this thread for more info)
• Modules @windy/map, @windy/imaker, @windy/format, @windy/http, @windy/urls, @windy/location, @windy/user, @windy/hp, @windy/rhMessage and @windy/models are now named-exported only (no nore default export)
• Renamed @windy/location exported methods (titleWithLang -> getTitleWithLang, url -> setUrl, title -> setTitle), and removed deleteSearch
• Removed @windy/render in a favor of @windy/renderUtils. Emitter is exported as emitter variable
• Merged @windy/favs-extends and @windy/favs into @windy/favs
• Merged @plugins/user and @windy/user into @windy/user
• Removed mapChanged and globe-mapChanged bcast events
• Removed rootScope.map object in a favor of store.get('mapCoords')

How to report an issue from testing?

Just post a comment in this thread below :-) If you provide us with:

• a step-by-step manual how reproduce the error
• what exactly is wrong
• what it should do correctly

It will help us a lot! Thanks.

Please, try to not duplicate other reports. If you found someone else already report the same issue, just upvote his/her post.

How to join beta?

Open https://www.windy.com/beta-test address and follow the instructions. You can leave beta test at any time. To leave the test, just click "BETA" sign on Windy logo (or visit mentioned address again) and follow the instructions as well. In a case of a total disaster, delete the beta=1 cookie for the windy.com domain and refresh the page.

Beta test is available only for desktop (browser) version.

Feel free to disccuss anything! Not just bug reports :-) Thank you for your help!

Not yet, but we are considering some changes with an increasing number of plugins. For example:

• direct support for plugins on mobile devices
• auto-loading selected plugins
• user voting

@jakubvrana It is quite tricky now. The detail plugin has been rewritten to svelte, so it is now a part of inner svelte store. You can force it only when detail plugin has not been open yet:

W.broadcast.emit('rqstOpen', 'detail', { display: 'wind', source: 'url', ... });

But in a case it has been already open, I am affraid there is no way how to achive what you need :-/

@Arnaud-KAWKA Thank you so much! It has been added to the list available at https://www.windy.com/plugins

@vicb Thanks! Fix will be released today.

@vicb thanks! Has been applied!

@vicb Thanks for the report. It should be fixed now.

Beta test is closed, v39.0.0 has been released. Thank you all for your help!

BTW, I have merged v39 into master: https://github.com/windycom/windy-plugins

@vicb Thanks for the feedback! The only reason was to keep it as compatible as possible with the old version, that is all. We are making things too complicated for the developers already, so we have tried to make it so they do not have to deal with too much around the build.

Feel free to make this package and take care of it, I would be more than happy if someone takes over and I do not have to worry about it.

We will remove W global object and W.require as well in a favor of ESM. So do not use it. That is why the new compiler was created, so that we could prepare it for people beforehand and the codes would work properly with minimal changes.

@vicb We found some issues, so I think we will bugfix them this week. So we would like to release the new version next week. Feel free to ask for help if there is anything I can help with.

@rittels @vicb I have updated examples in plugins repo meanwhile :-) It is v39 branch: https://github.com/windycom/windy-plugins/tree/v39

Also, build system has been changed. Now rollup is used and can be simply modified to developer needs. The crazy obsolete riot architecture with JS inside HTML has been removed as well. Hope it helps.