Robert Norris <rw_nor...@hotmail.com> writes: >> Hello, >> I step in the translation of viking after some time and I'm not sure >> how to distinguish translation of >> Track and Route. > > Thank you very much for the translation efforts. > >> I expect that basic difference is that Track comes from device (and >> have timestamps), while Route I create in viking and later save to >> device? > > Generally yes. > > I think of a Track as a path I've already been on, whereas a Route is > a path I'm planning to take.
I can see the point in that distinction, but I see it as Track is a sequence of points that is perhaps a record of where a device has been. It will typically but not always have elevations and timestamps. A route is a sequence of points that defines a way to get from here to there. It's more of a recipe for getting somewhere So I've pretty much agreed with Robert, but I find the have-been/planning secondary to the kind of data it is. One could generate a track object from a route, with timestamps, to be the track object that might be created from a person following the route. You can think of a track as maybe having thousands of points, whereas a route will typically have less than 10.
pgp7zVAkdqn55.pgp
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
