anybody working on a trajectory plugin?
-
quality check.. this looks VERY usable - congratulations! @rittels
Google Earth kmz track: http://static.mah.priv.at/kmz/20190630-stiwoll-waldstein.kmz
Michael
-
Wow, amazing.
Thanks, Michael!! -
Color picker added. windy-plugin-traj@0.1.4.
-
@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
Michael
-
@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):
Michael
-
@mhaberler
https://community.windy.com/topic/7888/anybody-working-on-a-trajectory-plugin/11
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. -
@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
-
@mhaberler said in anybody working on a trajectory plugin?:
this trajectory has 5 segments with the following durations:
first segment: 1hr
segments 2,3,4: 3hrs
last segment: 2hrsit 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
-
@erisyardas point taken
How do I get onto hourly location increments?
-
@rittels
I can not load 0.1.4 (the one with color picker).
I can only load 0.1.3
Am I doing something wrong?@TomSlavkovsky
https://community.windy.com/topic/7574/available-windy-plugins
Q: windy-plugin-traj@0.1.4 is not (yet) available? -
@Gkikas-LGPZ which browser+OS?
edit: playing with Safari, Firefox, Brave, Chrome - all currently get stuck during segment generation
looks like a temporary network or server issue
edit #2: all working again
-
Stuck again, lol. CORS error. We are overloading their servers???
The polyline segments represent 3 hour segments, as provided by the pluginDataLoader. Starting 90 minutes past 2400 (GMT).
I added markers at the hour points. Should hopefully work once the server is responding again.I can add a facility to download and save trajectories, as .gpx.
Will do so later...
-
@Gkikas-LGPZ 0.1.5 latest. Will load 0.1.6 with markers, as soon as server active.
-
@rittels perfect!!
I see - the marks coming from the data import - makes sense nowgpx: really any format is fine
I am very curious to overlay forecast and actual tracks - have done so in the past with a ADS-B track from flightradar24 and trajectories from Meteoblue exported as GPX, eg last slide in http://static.mah.priv.at/public/alpenfahrt-vortrag+folien.pdf
