Import favorites doesn't use the GPX metadata name

[JimmyS83]

It seems that Import favorites is ignoring tag within gpx.. At least for me it seems, that imported name became name of file instead. Can anyone confirm this?

[devemux86]

@JimmyS83 Can you explain with more details and a gpx example what you mean?

[JimmyS83]

In GPX file:

<metadata>
    <name>Ignored Name</name>
    <extensions>

When you export any favorites to file... then in exported gpx change name above, and import it, it has still the filename.gpx name in Cruiser, not name from metadata, at least for me it seems.

[devemux86]

@JimmyS83 You mean when importing a GPX file into favorites in my collection?

I think currently it uses the file name as group name during import.
We could change it so that the metadata name (if exists) has priority.

[JimmyS83]

Yes. Exactly, I updated post to not confuse anymore :) It doesnt matter much, but I think it would make a sence (when the name tag is there). If that wouldnt create another issues somwhere else of course..

[MotoUKRider]

I make use of this tag when importing my grouped Favorites into Cruiser.

For clarity, I export a ~1000 item GPX from BaseCamp and split it using my own Windoze app based (early example in that post) on each entries' name as a trigger, eg: "Photo, Nice Place", "Food, Pizza" etc. I then bundle the 9 GPX files it created into a ZIP and slipstream/import into Cruiser making use of each <name> tag in the GPX header.

Providing I don't move a Waypoint, no dupes are created. I haven't tested a name-change scenario. I sometimes "swipe-delete" all the Groups and re-import fresh just to keep things tidy.

 <metadata>
  <name>Ports</name>
   <extensions>
    <x:sym>directions_boat</x:sym>
    <x:color>#4363D8</x:color>
    <x:visible>true</x:visible>
    <x:zoom>11</x:zoom>
    <x:navigation>true</x:navigation>
   </extensions>
 </metadata>
 <wpt> etc

I've not installed 5.3.1 Beta 1 yet, so if anything different is happening since the last release then it may affect me, too.

I'm making use of this "under the hood" approach more by accident than design as I started naming my Waypoints in a methodical way about 5yrs ago, mainly to keep them in order - but the move (and advancements) to Cruiser have allowed me to make better use of my Favorites - no longer all just orange stars 👍

[devemux86]

@MotoUKRider

It currently uses the file name as group name during import (we could improve this with metadata name).
It works because the names are used as file names in export.

So you probably have files with names the metadata names?

[MotoUKRider]

@devemux86 Ah, yes - I do!
The same variable in my code determines both the GPX filename and the <name> tag.

[devemux86]

@JimmyS83 This should now first use the name in gpx in the latest:

• Cruiser 5.3.1 Beta 12 #765

Implemented for favorites, routes and tracks in my collection.

[devemux86]

@JimmyS83 Do you import a zip file with many gpx inside or a single gpx file?

You asked the group to get the name of the gpx.

If you import a gpx file and its name already exists then the group's name gets a suffix.

Important: Groups cannot have the same name.
Import of gpx is always done in the selected group that we used its menu.

[JimmyS83]

Single gpx. I dont know, that I could import multiple gpx via zip (if) :)
It would be good to have Update function then? Use case: External, automatically generated gpx, which needs to be updated time by time also in Cruiser (which I did via Import so far)?

[devemux86]

@JimmyS83 Do you press the menu of group A and expect to update the group B?

If you want to update group A, then select the menu of group A and press import.
Then group A will be updated with all the gpx data: favorites, name, icon, color, etc.

[JimmyS83]

Do you press the menu of group A and expect to update the group B?
Yes, it works that way so far, when filename was used instead a name.. I thought, Import is non group related, and when importing group, if exists, it wil Update, if not, it will create New group..

How then I could import new group? Import is available only after click to three dots of some group?

[devemux86]

How then I could import new group?

@JimmyS83 Create a new group and press import on it.

[devemux86]

The functions are designed to be simple without asking users too many confusing questions.

Everyone: if you find areas for improvement, please let me know so we can discuss them. 🙂

[devemux86]

• It should work in Cruiser 5.4.2 #776

[WolfgangZ42]

The desire to use TAG names when importing routes and tracks probably comes from using BaseCamp and/or Garmin devices. As I have never used either, I would like to be able to change this procedure.
Maybe we can have a setting under “Advanced” (Application or Navigation) for the naming preference (TAG name or filename)?
In my opinion, filename has the advantage that I can quickly create a copy with a new name, for example after a change in RouteConverter or GPS Track Editor without having to edit the TAG name. And the names in the Windows and Android directory would always be identical to the names in my collection.
At the moment I am helping myself by consistently deleting the TAG names.

[devemux86]

@WolfgangZ42 We can think about it.

There cannot be same names in a group (or same group names).
Because at the end they are translated to unique folders and files.

So even if 2 gpx files have the same metadata or track name,
during import a suffix is added automatically (similar to Firefox saving same file).

[devemux86]

@WolfgangZ42

More settings for every option complicates the app for new users.
We must try to reduce the existing settings and use sane defaults.

About this specific case, indeed the filename appears better.
When users import a gpx file, they only know the filename that always exist,
not a "possible" metadata / track name that may not exist and confuse them.

[WolfgangZ42]

About this specific case, indeed the filename appears better.

Just an example (my imported directory and the result):
. . .

More settings for every option complicates the app for new users.

I agree! Therefore my solution to delete via macro all TAG names. Even for .gpx files with several TRK sections it works for me:

Once in Cruiser renaming is possible because TAGname and filename are identical in export. Perfect!

[devemux86]

Once in Cruiser renaming is possible because TAGname and filename are identical in export. Perfect!

All apps should export gpx files this way. 🙂