windy-plugin-fp

rittels

Draw the flightplan and set the departure time.

Then: click Read Wx. This loads the forecast data for the route from the windy backend, and interpolates it for the time when you reach that point. I then calculate the ground speed, and with the GS, calculate the time you when you will read the next point.

Then: Open the routeplanner.

If you Read Wx when the routeplanner is open, it should update.

The purpose of the Read Wx button is to prevent continuous calls to the server, so it is only done once you have drawn the flightplan.

Hope it helps.

niio

@rittels I have the flight plan saved in a .gpx file. I opened windy, then opened the flight plan plugin, then loaded my saved flight plan. All the ground speeds in the waypoint list updated immediately with the surface altitude winds, even though the waypoints are all at 39kft. Pressing the 'Read Wx' button does nothing.

niio

@niio In addition, the altitude line in the route planner goes to 45k or 50ft on certain legs even though the waypoint altitudes are never that high. The wind speed and direction in the window that follows the airplane icon stays at surface, even though the map is showing wind and direction at 39kft.

niio

@niio I tried making a new flight plan and the 'read wx' button worked, at least in part. Three quarters of the waypoints updated with wind speed at altitude but some did not. I could not see an obvious connection between the ones that wouldn't update and a second click of the wx button did nothing more. So the original problem is with saved routes.

rittels

@niio

Thanks. There is indeed a bug in uploading the gpx file. I will try to fix it this weekend.

In the meantime, once you have uploaded, just set 'n new start time. This will reset the read weather data, then click read Wx again, and it should read correctly.

niio

@rittels I think the waypoints that did not update were over mountain ranges, so the improperly selected zero msl elevation wind chart would not have had any data.

igor 320

@rittels , good day sir! Is it possible to add a couple things to the plugin?

I would like to see more fine-grained interpolation of altitude for climbs/descents. For example, an altitude gain of 8625 ft (from 1375 to 10000 ft ) resulted in 5 readings:

1st leg for 1375 ft;
2nd - 3100 ft;
3rd - 4825 ft;
4th - 6550 ft;
5th - 8725 ft (the end of the 5th leg is where 10000 ft reading starts).

See screenshot: https://ibb.co/0GZZXLJ

I also would really appreciate if you can implement a vertical speed (in ft/min) to get more accurate calculations. On the screenshot above there's a final red dot which represents my own calculations for Top-Of-Climb point at 500 ft/min.

rittels

@igor-320

Good suggestion.

I should perhaps add a slider for vertical speed, in climb and descent. Also climb and descent airspeed, as percentage of cruise? The UI becomes rather crowded. Let me know what you think.

igor 320

@rittels I don't have any preference for this and a simple manual entry box would suffice everyone, imo. A screenshot below is taken from SkyDemon EFB for pilots. Indicated airspeed + vertical speed for climb/descent and that's about it, since we're only interested in actual travel time and weather forecast along a route.

https://i.ibb.co/0s77SGN/Capture.png

Thanks!

PS: is it possible to use ICON-D2 forecast model somehow? It has crispy 2.2 km resolution compared to hazy 9km from ECMWF.

rittels

@igor-320

thx.

I use the routeplanner requests, which only provide ECMWF data, for other models one has to fetch the data for each point, which will take a lot longer, but it is feasible, if you want to wait a minute or 5.

igor 320

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