This object is in archive! 

Track file name change after importing in Locus

sl91 shared this problem 8 years ago
Not a Problem

Hi


I have decided to store all my tracks in a dropbox folder. I made a test on Locus and what I have observed is after importing a set of these files the displayed names in Locus Pro 391 have changed. Why ? Is this issue related to the initial length of the file names. Some of these file were recorded using Locus. I use the following filename structure:


Year_month_day_country_starting city name_used software_remark


This file name is manually entered in dropbox using the file rename function.


Best regards


sl91

Replies (4)

photo
1

Hello sl91,


what means "displayed names changed"?


1) It is important to understand, that file is just a container for some data. One track, two tracks, five points, doesn't matter. All may be included in one file. But every track or point has it's own name. So if you import such file, tracks and points will use it's names defined inside of this file. Name of file is not important here.


2) if you still think there is some problem, it's is as usually import to allow me simulate this problem. In this case, easier is to share one file with me. Thanks

photo
1

Well, I mean the files displayed under data\tracks\mytracks. I can share one of these files in dropbox. How to proceed (sharing email adress ?)


regards


sl91

photo
1

send it on locus@asamm.com

photo
1

OK I do it for one file immediately

photo
1

Fine, file probably received.


Quick look ...


In file is one track named "SEP-16-12 14:33:36". So I assume, that you import this track to Locus and this track is always named "SEP-16-12 14:33:36". Which is correct. As i wrote, name of file has no influence on imported track.

photo
1

This is crazy ! the file name in Dropbox is:


2012-09-16_France_PR_D091_5_Circuit_Ertechy_Hiking.gpx


I really don't understand...

photo
1

Open your file in any text editor and you will see this:

ab51fbc26b287c2c3ad810cc81d9871a

where you may see line "<name>SEP-16-12 14:33:36</name>", which define name of imported track.

photo
1

Ok. So as far as I understand, the displayed file name in any file manager (or Dropbox) is not considered. Locus takes into account the file name encapsulated within the gpx. Am I right ?


Regards


sl91

photo
1

yes, as I wrote ... except rare cases, name of files is not important.

photo
1

Ok, So I will have to edit each file in order to apply my naming system. This is much work...


Thanks


sl91

photo
1

sl91 - you may find it simpler to edit the track name once imported into Locus rather than editing the <name>@@@</name> inside the GPX file.


Menion maybe an advanced track import tickbox could be "Use filename for track name"? If there are multiple tracks in the imported file then append _<N> to each track name.

photo
1

Please no extra settings ... it make no sense as this is first complain on this topic, after five years of Locus existence. Thanks

photo
1

Hi Menion,


I understand your point of view but I am sure that the question concerning file naming will be more and more important in the future. Thanks for your support.


sl91

photo
1

I discovered the same problem with .gpx-files, which I got on top for a bought book with route suggestions.

I opened the .gpx files using a text editor and the problem was the same Menion mentioned above:

<rte>

<name>001 bis 055</name>

The file name is 001_D-Sued.gpx and it appears in Locus as an imported track 001 bis 055.

Of course you can import such files one by one and change every name manually, or you change the name with a computer using a text editor, but I would very welcome such an import feature where the name is choosable as there are 100 route suggestions to import and name changing for every single track is very time consuming.

photo
2

Hello, understand. Anyway I'm still not convinced.


Why should I create some workaround, usable for 1 people from 1000, just because creator of GPX tracks made a mistake and incorrectly generated invalid names for it's tracks?


Sorry, but I see best solution here, contact of author of book, with suggestion how to improve naming of these routes.

Replies have been locked on this page!