Hi Cédric,

routes are the widows of the GPS world :) What you picture is usually done with 
tracks and waypoints. You follow a track and if you get close to a waypoint you 
get some information. Routes usually are created by simply selecting waypoints 
as start, intermediate and end point. And then the device does some magic and 
guides you. 

In the dominant Garmin world you can calculate whatever route you want and 
transfer it to the device. The device will ignore it and calculate it's own. 
That is the reason for the primary route (only the few points to define a 
route) and the secondary route (the calculation on the PC). If you transfer a 
secondary route on a Garmin the thing goes berserk. 

As Garmin is dominant, their point of view influenced the definition of the GPX 
format. GPX lacks structure to store a calculated route. In fact the track 
structure would make a much better container for high sophisticated routes.

In QLGT you can place waypoints close to trackpoints and QLGT will attach these 
points with the track and create what is commonly called a roadbook. This is a 
loose coupling just by distance. If a device, like the Sportiva, supports close 
coupling of waypoints and tracks the export handler should convert the data in 
what ever format is needed. 

Now for routes. I do not think that a routpoint should be derived from CWpt. 
CWpt is huge. A waypoint can store geocaches, pictures, epic poems. Whatever! I 
wouldn't want to deal with that on routes. And I want to change CWpt without 
caring about routes. Imho the simple GPX representation of a waypoint should be 
enough for a routepoint. 

Concerning backward compatibility: It's enough to read older versions. I do not 
want to carry the burden to save data readable for old and new versions of 
QLGT. This is free software. Users must update frequently. Thus you can 
restructure the writing part of serialization completely and append the reading 
part. 

Export mode ore not: there is already CGpx::exportMode that flags that controls 
the amount of data stored in a GPX file. Device export is eCleanExport. 

Oliver

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users

Reply via email to