COMO CREAR UN CONJUNTO CON TRACKS Y WP
Si de cero creo un nuevo track, un nuevo archivo de wp y un nuevo conjunto y arrastro el track y los wp al nuevo conjunto, consigo que se cree un conjunto en el que permanecen el track y los wp.
Pero si creo un nuevo conjunto y arrastro a él un track ya existente y un archivo de wp existente, automáticamente Land me convierte los WP en puntos del roadbook. Y eso no lo quiero.
Cómo conseguir en el segundo casoque Land haga un conjunto en el que tracks y WP permanezcan y no me los convierta en puntos de roadbook.
-
Hello,
It is related to the file format, two things are to be distinguished the visual aspect and the file itself.
Import or Merge of "GPX" including a track and a list of WPTs:
- If all the WPTs are perfectly placed on the track the notion of "ENSEMBLE" disappears from the Land visualization, both are incorporated into a single GPX. But this gpx separates the two entities, tracks and WPTs by different tags and different locations of the file, they are two different blocks.
- In the same way the association of a GPX track and list of WPTs (Expected an ENSEMBLE) is merged into a single gpx, if the WPTs are ALL perfectly superimposed on the track. The trick to keep the notion of "ENSEMBLE" is to add a WPT outside the track (Far from the Track), and it will remain a "ENSEMBLE"
The merger when everything overlaps seems quite logical they are no longer distinct entities.
A set (ENSEMBLE) (a gpx track and a list of gpx WPTs) is in *.gpx format, if they are combined in the common GPX they are two very different entities (different tags) even if on the screen the appearance is that of a Road Book, since the old "RTE" has been abandoned for more than two years. There has been a fairly recent evolution of Land to find the "RTE" function again through the "ROAD BOOK" possibility of joining your WPTs by a straight line (Bird Fly).
If this same set (ENSEMBLE) is saved in *.trk format the WPTs are then incorporated into the track, it is therefore a real Road Book.
The difference is as follows, for a loop route or with common round trip segments, in the case of the real Road Book in *.trk format all the "WayPoints" will be chained in the defined order, in the case of the "ghost Road Book" the *GPX file, the route tracking will choose the WPT on a proximity criterion, so it can at an intersection switch from one loop to another or jump directly from the starting branch to the return branch if a section is common (which happens often).
Takes the list of Land and GPS developments this development is less than a year old.
This is one of the strong points of TwoNav which allows you to stay on the itinerary in the case of nested loops or common reverse routes (This does not exist elsewhere in this case it jumps). This avoids suddenly finding yourself totally lost or going in the wrong direction for loop routes or with intersections.
If you want to keep the trace on one side and the list of WPTs on the other it is a simple question of organization (which is what I do), it is enough that the whole thing is a third file (a different name).
Best Regards
Iniciar sesión para dejar un comentario.
Comentarios
1 comentario