> Gesendet: Freitag, 20. März 2015 um 23:04 Uhr > Von: "Robert Norris" <rw_nor...@hotmail.com> > An: "viking devel" <viking-devel@lists.sourceforge.net> > Betreff: Re: [Viking-devel] [PATCH] Modify Time of GPX TP (GPS Track > Trackpoints) / Interpolate Timestamps between first and last TP > > Chistian, thanks again for your efforts but I fail so see how this is much > different to the time edit facility in the latest Viking source code. > (https://sourceforge.net/p/viking/code/) > > Also the type of timezone is now made a preference (Local, UTC or 'timezone > of the track's location'). > > * a tooltip has been added to explain unix epoch value > * both, unix epoch value and corresponding ISO Date may be selected for > clipboard transferal > > However these are useful. > > I realise with my timestamp edit facility you can not copy the full ISO date. > It should be straight-forward to manually add a right click menu with a copy > function.
The first patch I've submitted to the mailing list was against stable version 1.5.1(!) I've been reluctant to check whether the functionality I needed was available within trunk at that time. So please, simply ignore this first mail (or cherry pick the stuff you find useful, still). After I checked out trunk, built and tested the time picking functionality in place now within trunk, I decided it was superior to the attempt taken with the GPL3 tux-tv code. Hence, I stripped that code and submitted the remaining parts as a revised, second patch to this list with my last mail. Meanwhile you've taught me, that I do not need to modify the source to add links to the external tools menu. That's cool, but a) I still think these apps (geohack, osm, josm) are common enough (as common as stellarium/celestia the least) as to preship them, rather than make each potential user add these themselves (and potentially failing to find out about the modifiable xml file) b) The statements you've made about the usage of pass_along[MA_MISC] might be true and it's not a bug now, but this wizardry is coding style that might fall on your own feet with time to come :) If you want the code to be easily understood and extensible, you should straighten that out, *imho*. For reference: http://sourceforge.net/p/viking/code/ci/master/tree/src/viktrwlayer.c#l7792 As for the interpolating timestamps function: My use case is the same as the one already posted somewhere to this mailing list. * I usually run a gps tracker while cycling, and if I forget to resume it after a pause (or if the battery runs low), I'd like to be able to insert the missing segment, i.e. the segment not tracked. * The timespan this segment needs to cover is known: it needs to start at a time when the GPSr was put into suspend and needs to end when it resumed operation. * The track traveled is recalled from memory, I know where I've been and usually use JOSM or a similar software to point-and-click together the missing track segment. This segment itself may be saved as GPX, but this obviously will lack timestamps. * The average speed the missing segment was traveled with is given by (distance of track traveled / timespan). * The distances between single track points of (the artificially re-created) missing track vary a lot. I reconstruct timestamps such that the track is traveled at equal speed, because I want to minimize its influence on the stats for the rest of the (real) data. In particular it is very unlikely that it will influence top and minimum speed of the whole track. A nice side effect is that I will still be able to distinguish the artificial/made-up track part from the real parts. While I guess that it's possible to fake timestamps such that they will not be distinguishable (using an algorithm that mixes elevation data, randomization, etc.), you see that there are use cases where this is not desirable. If you think of viking as a swiss army knife for gpx track manipulation, you can only hope that people will make thoughtful use of it. As for the knife, it has functions I do not use at all, but then are useful for others. As for the knife, I do not know about all the different ways people use it in. Hoping to have satisfied your curiosity, Christian ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
