anybody working on a trajectory plugin?
I'd love to have it into the Windy platform
instead of running the plugin any time I need it.
Yeah!! email@example.com now working on ECMWF again.
Thx @ivo !!
Your traj plugin is working a treat.
Just one comment - is there a means of removing the trajectory traces from the panel without needing to refresh the Windy window and then resetting the plugin programs? The window panel gets rather busy with multiple traces overlaid on top of each other. It would be nice to be able clear the trace plots with a click of a button and start a fresh.
I have just noticed one issue with the Traj plugin....
when selecting the 100m level on the EC, the plugin gets set into a repetitive loop and the trace doesn't appear to be the correct path.
Sfc and all the other standard levels look fine.
There is a discrepancy between the levels available with the dataLoader and on the site. 1000h is available with the dataLoader, which I took the liberty to represent as 100m on Windy UI (perhaps better to just leave it out). 250h also not available in dataLoader, as @vicb said earlier.
@rittels Thanks for this phenomenal job!
this is already very useful - will do a balloon ride tomorrow early morning and see how that fares relative to the plot!
If I may add a suggestion:
if you select several altitudes on the plot it is hard to discern which track belongs to which altitude
why not choose different colors for each track in the plot and color the altitudes in 'Select levels' accordingly?
quality check.. this looks VERY usable - congratulations! @rittels
Google Earth kmz track: http://static.mah.priv.at/kmz/20190630-stiwoll-waldstein.kmz
Color picker added. firstname.lastname@example.org.
@rittels Thanks - this helps a lot to tell the different tracks apart, very useful!
do I understand this correctly: the traj plugin uses ECMWF data regardless which model is currently selected?
Hi, yes. It uses the pluginDataLoader module to load data for a point. I can select either GFS or ECMWF. Currently I only use ECMWF.
I can also read the selected model and apply it when loading data. One can then theoretically get a different trajectory for each model, at the same point, time and altitude. May be interesting.
@rittels will this plugin stay a plugin or become integral part of windy?
reason I'm asking: I want to create a how-to screen video for my fellow balloonists (many of which are from the "grey panther" section and not exactly geeks); probably for airspaces and better-soundings as well
I'd rather do that after things stabilize
I hope so......
It would be cool, but it is really a question for @ivo and team. I think it is the plan eventually.
@rittels meaning 'hope it becomes an integral part'?
@rittels I told my fellow balloonists about that plugin (we have a whatsapp group for winter Alps crossings) and they really like it!
the following suggestions came up:
(1) place a marker at fixed time intervals so you can tell where you'd be by then
maybe make the time per interval dependent on duration, like 15min, 30min, 1hr - I think a total of say 3-6 marks should do (have a look at the meteoblue example above, they mark hourly - good enough for a start)
(2) what I really wish I could do: take the forecast/s of a given point in time, and AFTER the flight overlay it with the actual track - but I guess going back in time is not realistic in windy
an almost as good solution would be to export the trajectories as gpx or kml/z, so they can be re-imported later together with the actual track
@stitch I played around with TS trajectories today
would you suggest FL140/180/240 are realistic altitudes for thunderstorms (IANAM - I am not a meteorologist :-)
this image from today would suggest roughly FL100-140 for best fit (6hrs, TS over Carnian Alps):
IMHO, 700 hPa (FL100) winds are representative to actual tstms movement in most cases.
Maybe, because at this height is located the center of gravity of a typical 30,000 ft high tstm.
mhaberler | Premium last edited by mhaberler
@rittels I only now discovered the feature where clicking trajectory segments reveals the start time of each segment - great!
I'm trying to understand the segment duration logic - I made a short screen video for a 12hr trajectory to show where I stumble
this trajectory has 5 segments with the following durations:
- first segment: 1hr
- segments 2,3,4: 3hrs
- last segment: 2hrs
it seems to me segments #2 and #5 definitely are polylines, but select as a single segment ?
NB: just trying to understand - not nitpicking ;-)
que es lo que quieres saber