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 :-)

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

Hey guys, we just published a new version of our route planner. Just some small improvements.

Changelog:

• added switch to change direction of movement (relative/absolute wind and wave directions)
• added "reverse route" button
• route detail remains open when waypoints are changed or any changes are happening
• uncountable ammount of minor fixes

Thanks for your feedback, we have been working on another version :-)

@mikachu1983 Thank you for bringing it up! In fact, we have had some pretty fiery internal discussions about this issue. In short: it is currently not possible.

We dealt a lot with the following situations:

• If the terrain is lower than the model altitude, should we display the values? Even if they are interpolated?
• If the terrain is higher than the model altitude, should we clip the non-existing heights for that location?
• Or should we allow users to choose how they want to display it?

The result was: let's not deal with it for now, it is already too complicated. Let's wait for feedback and see how important it is for others.

@Kostya-Net I am sorry, but we will not change the logic. The API library is based on the code of our client, which does not assume that the map can be removed (the map is always visible on windy.com). It is not really an extension of the leaflet, leaflet is rather an extension of our API. Of course, the logic could be rewritten, but it is not a priority for us. Sorry about that.

Hey guys. The purpose of the windyInit method is to load all libraries and run their javascript, styles, etc... It is not mean to reset the map. Once the map is initialized, you should use just and only methods from the documentation (https://api.windy.com/map-forecast/docs).
So if you need to reset the map to your default settings, you should use documented methods to do this. Calling windyInit just and only load all libraries again and run their initialization. At this moment there is really ugly hack in our lib to keep it working as "reset map".

@saaneuvos GFS is at this moment free for all users. ICON do not. We are sorry, it was bug that 1h forecast was available. It is a premium feature for windy.com users. It is not available for API, unfortunately. Sorry for all troubles, but we have basically just fixed a bug.

@Gkikas-LGPZ It is fixed on desktop now. Mobile apps will be fixed with the next application release. Thanks again for the report.

@Gkikas-LGPZ Thank you for the report! I am unable to reproduce the error. It could be some issue for specific location, can you provide me with the URL where the error appears? Thanks!

Edit: Ok, found it, set ft as default unit is the key to the issue :-)

@saaneuvos Thanks for the report! We will look into it and let you know.

@szabolcs-gavallér Thanks for the suggestion! I think it could be changed to see the timeline even on mobile devices.

For future generations: There was a conflict between L.CanvasLayer plugin and our custom L.CavasLayer extension. After renaming the plugin it works now.

@kostya-net Sorry for the trouble. We are unable to reproduce the error. Can you please PM me the address where I can debug the error?
Unfortunately, former version is not available.