NEW FEATURE PLS - Better Position List Headings

[Roger B]

I've noticed different formats use different names for the same data fields, so how about once the format of a loaded file is determined, the position list field name titles reflect the actual field names for that format.

I found the title "Description" for what is the GPX field "Name" a bit confusing.

[routeconverter]

I've noticed different formats use different names for the same data fields, so how about once the format of a loaded file is determined, the position list field name titles reflect the actual field names for that format.

I found the title "Description" for what is the GPX field "Name" a bit confusing.

Well, RouteConveter is not a GPX tool. In that case I would have choosen the GPX element names for the user interface.
RouteConverter is targetted at planning, conversion and simplified usage. This means it uses generic names for the data fields in the 75+ supported file formats. Switching to file format specific names would cause more confusion.

[Roger B]

I see your point.

I have to say out of the several tools I've tried this wins hands down except that GPXEditor scores on one point, ie being able to enter description and comment fields, as I mentioned in another feature request.

[routeconverter]

I could extend the semicolon magic to 2 semicolons:

<name> ; <description> ; <comment>

Actually only GPX has got this variety of fields that are hard to distinguish when it comes to what to store where.

[Roger B]

I'm not too sure.

When you load a GPX file that contains a description does it insert the ; automatically and then split the field into <name> & <desc> when you save it?

I suppose what I'm angling towards is how about adding Locus format to the list of formats? I'm sure a lot of users would appreciate that, Locus seems a very popular app.

If you think that may be a good idea I'm more than happy to help in any way I can.

[Roger B]

I could extend the semicolon magic to 2 semicolons:

<name> ; <description> ; <comment>

Actually only GPX has got this variety of fields that are hard to distinguish when it comes to what to store where.

That would be useful - I thought when you said RouteConverter had this bit of magic you meant it was peculiar to your program, but I guess it's a GPX feature, Locus supports it anyway.

I've found that when I add the <desc> field to <name> Locus displays them in different fields, which is what I was hoping for.

So I can now export GPX data to CSV using the Columbus V900 Professional format, load the CSV into Excel, do my edits and export the CSV back to RouteConverter and thence to Locus.

The awkward part of this is that there could be several fields in one spreadsheet column (<name>, <desc> and <cmt>), with a bit of messing about in a text editor finding ";" and replacing it with "," you can get a proper CSV file, but that only works if there are the same number of sub-fields in each name field, and of course ";" should not be used within any text.

What is needed is a CSV format that splits the GPX <name> field into <name>, <desc> and <cmt> to be used with spreadsheets, databases and so on that adhere to the traditional CSV format.

[routeconverter]

What is needed is a CSV format that splits the GPX <name> field into <name>, <desc> and <cmt> to be used with spreadsheets, databases and so on that adhere to the traditional CSV format.

I totally agree. It's on my todo list since 2011 or 2012.

[Roger B]

I'm well on with it using Excel.

I'm a bit slow because I've never used Excel before, I came up from Supercalc to Lotus123, but my QBASIC experience is coming in useful.

So far I can edit the <name>, <desc> and <cmt> fields and put them back into the VOX field (Columbus V900 Pro format), check the CSV file for formatting errors and delete selected records.

It's quite a project, I've written over 20 macros so far.

I'll keep you posted.

[routeconverter]

I could need the help of an experienced Java Programmer, who builds a generic "Excel (.csv)" format.