anybody working on a trajectory plugin?

mhaberler

traj 0.1.9 feedback:

the traj generated gpx: http://static.mah.priv.at/public/trajectory__2019-07-04T17_15_00.gpx
for comparison, a gpx cut out of a 'real' Garmin 695 tracklog: http://static.mah.priv.at/public/20190630-stiwoll-waldstein.gpx

import traj gpx directly into macOS Google Earth (fat UI), using import option 'Use KML-LineStrings': very nice UI, clicking the arrows gives detail at current point:
GE gpx import

for comparison: import gps695 gpx directly into GE UI (NB: dumb naming, traj much better):
Garmin GPX import

(NB: the GE GPX display code seems to be a bit buggy: de- and then re-selecting a track makes the selectable arrows vanish for both the traj and Garmin695 gpx files)

traj gpx does not import as gpsvisualizer.com Atlas - not sure why: https://gpsvisualizer.com/atlas/map?url=http%3A//static.mah.priv.at/public/trajectory__2019-07-04T17_15_00.gpx

gps 695 gpx imports fine as gpsvisualizer.com Atlas: https://gpsvisualizer.com/atlas/map?url=http%3A//static.mah.priv.at/public/20190630-stiwoll-waldstein.gpx&c=47.165141,15.293064&z=12&bg=osm

interestingly, both files properly import into the gpsvisualizer leaflet and displays: https://www.gpsvisualizer.com/map_input?form=leaflet and https://www.gpsvisualizer.com/draw/ - one would think its the same import code. No biggy.

In all cases the colors conveyed by the Garmin gpxx:DisplayColor tag are ignored. But they are in the gpx file and can be extracted somehow if needed, so no reason to jump extra hoops in the plugin code.

Exporting the elevation with the tag works fine, it's exactly the same as Garmin device exports it.

other than traj 0.1.8 gpx files, the 0.1.9 gpx files now properly import into JGPSTrackEdit.

to sum it up: I think the gpx export works good enough for now - everything from here on really is rearranging deck chairs IMO

I'm pretty happy with it and can do any extra hoops for say super-polished presentations with standard tools like gpsbabel, XML transform and gpsvisualizer.com which I use most

IMHO: milestone reached - good for the masses!

stitch

@mhaberler

like @Gkikas-LGPZ , I generally refer to 700hpa/600hpa as a mean steering wind. But then in northern Aust the summer Tstorms top out in the mid 30k ft to mid 40k ft levels.

With respect to southern Aust winter Tstorms, then I generally lower the TS tops to mid 20k to 30k ft level and would then look a the 800hpa and 700hpa levels.

You can see what the forecast CB tops are using "Cloud tops" (just ensure the model is highlighting cellular based clouds and not layered clouds like cirrostratus/altostratus etc).

I see you have used the radar/lightning window to correlate the Tstorm speed/motion to a wind height field - this is what I would do as well.
Be wary though of Tstorms that move/turn towards a different directions opposing the mean or normal Tstorm tracks (these anomalous movers could potentially turn into the severe variety of Tstorm).

There is no steadfast rule....just trial an error.

All the best with your forecasting ..... @mhaberler

mhaberler

@stitch thanks, really helpful!

once in a while we have a TS nearby at an event and it is unclear wether we can go for a launch or not; the traj feature helps narrow down the question

mhaberler

@rittels 0.2.0 feedback:

exported trajs now carry over a color - great!

the gpsvisualizer.com Atlas import snag is gone.

here is a traj gpx export example, warped into kml with these gpsvisualiser KML settings :

GE trajs

I think export is just fine now.

Since my birthday's coming up... how hard would it be to play traj's from different models?

mhaberler

stunning: all pressure levels exported, imported with gpsvisualizer to produce KML

have a look in Google Earth!

rittels

@mhaberler said in anybody working on a trajectory plugin?:

Since my birthday's coming up... how hard would it be to play traj's from different models?

easy: 0.2.1

just set the model at the bottom and the plugin will use it. Not sure if all the products are supported by the dataloader.

stitch

@rittels

Brilliant.......you just keep on delivering. 2 model trajectories

Thx!!!!!!!

mhaberler

@rittels GFS definitely works, ICON - need to re-check, NEMS seems not to work

perfect!

my last suggestion is already down to usability: append the model name to the export file basename, and each track's name after pressure - then clicking the traj in GE will also report the model, not just pressure; less confusion potential when comparing several model results

Herewith I've run out of suggestions!

mhaberler

@rittels look at that - ECMWF, GFS and ICON trajectories!

multimodel traj

Edit: KMZ file

mhaberler

GFS, ECMWF and ICON works very well
NEMS, AROME - no output

(IMO not an issue and I dont suggest putting energy into resolution)

mhaberler

@rittels we might have serious test material shortly

I am attending the Sagrantino Cup from July 26 to Aug 4th, and there should be 50+ hot air balloon teams there

there should be 2 flights daily, so that should yield hundreds of tracks in different altitudes

I will prepare and publish trajectories twice daily for each takeoff location and ask the teams to share their GPS tracks with me

rittels

@mhaberler Wow, that looks amazing.

rittels

@mhaberler said in anybody working on a trajectory plugin?:

append the model name

0.2.2

Gkikas LGPZ

@rittels
@ivo
Giving ideas!
I don't know if its possible to include sea currents in trajectories plugin.
It would be very helpful for tracking (lost) floating objects and oil spills
(in case of ship accident).
Of course, I understand that it will be an experimental product
as sea currents data are not updated very often.

Gkikas LGPZ

... for rubber ducks, also! 😊
https://community.windy.com/topic/7181/please-help-to-find-my-ducks

rittels

@Gkikas-LGPZ

Great idea, but don't think the plugin DataLoader contains current data. Possible with the interpolator though. Will try...

Rubber ducks!! 😂

Gkikas LGPZ

@rittels
They "pay 100 EUR/duck for the person who find it." 🤣

mhaberler

@Gkikas-LGPZ my ISP career has taught me to stop when done.. which I do here - I am all for single-feature-well-done tools and less so for feature creep

But I guess someone interested in sea currents could take traj as a an example and base to work from

mhaberler

@rittels works fine - all relevant info carried over!

thanks for jumping that many hoops so far!

mhaberler

@rittels

I just found an interesting feature - incidentally very useful:

do a trajectory for some future point in time and just let the window sit (do not clear)
hit 'Start' again once a new model run becomes available
since the old trajectory is not erased, both (or all) are shown together on one screen - i.e. you can immediately judge how the wind forecast changes over successive model runs

That is super useful for Alps crossings - we need something between 340 deg NW and 10 deg NE to make it across quickly enough and still hit the Po valley

since usually such a crossing is planned days in advance (like 5) the trend in forecast changes is essential even if things looked good initially

Bildschirmfoto 2019-07-06 um 12.11.42.jpg