> > Any comments welcome.
>
> I started to review your work. I post some comments on GitHub. I also
> started to do some changes on my own topic branch:
> http://repo.or.cz/w/viking/guyou.git/shortlog/refs/heads/GpxRouteSupport
>
> Working on this topic, I think the best solution would be to add a
> "Route" sublayer.
Possibly, however I initially avoided this for a variety of reasons:
* It means the 'TrackWaypoint' Layer name is not so relevant
* I don't like having sublayers shown in the treeview when there is nothing in
them.
This seems to get in the way - I tend to have lots of TrackWaypoint layers, but
often only tracks in them.
If I were to rework this into being a Route sublayer, I would very much like to
make such that only when there are things in a sublayer that the sublayer is
shown on the treeview. Or at least one could make it a Viking preference: 'Show
Empty TrackWaypoint Sublayers'
* At the time of writing it last year, it was for primarily for speed and ease
of a working implementation. (I did it mainly on one rainy day IIRC)
However most operations on tracks should be available to a route. Eg, Split by
Number of Points, Export as GPX, etc...
These would all need reworking to operate on Routes.
Would need to add TrackWaypoint->Route properties copying many of the
TrackWaypoint->Track drawing type properties.
I would correspondingly then make gpspoint.c save as RTEPOINT type tags too,
rather than just a 'is_route' flag.
These changes could get rather large and a long time to write....
I quite like the method of considering a route a special type of track,
especially as no one else seems worried about the lack of this type of track
route support in Viking.
ATM I switch between using my implementation version, but as mainly doing other
Viking code tasks, my code has not got it in.
So I rely on some simple bash scripts which just take a gpx file change all
'trk' -> 'rte' and then upload to the GPS ensuring a '-r' in the gpsbabel
command line.
>Going further, the track creation tool should create
> a Route, not a Track (in my mind, track is logged by a device and a
> route is planned by user).
Agreed.
There still would be a function to convert a route to a track and a track to a
route.
> Sorry, no much more time to work/comment about this (real life).
>
Any one else have any thoughts on if / when / how / other issues - about route
support?
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
