Track color problem with GPSmap 62s

Thanks to the clues from KD3131 and DRM4X4, I've been able to make track files that display in the right color in both BaseCamp and the 62s. After importing a track into BaseCamp and setting the color there, I tell BaseCamp to upload it to the 62s and then I add the extra bit of XML that the 62s needs. I ended up writing a little Perl script that goes through all the track files on the 62s and adds the needed <gpxtrx:TrackExtension> tags automatically.

Here's how that part of the the file ends up looking:
<extensions>

<gpxx:TrackExtension xmlns:gpxx="www.garmin.com/.../v3">
<gpxx:DisplayColor>Blue</gpxx:DisplayColor>
</gpxx:TrackExtension>

<gpxtrx:TrackExtension xmlns:gpxtrx="www.garmin.com/.../v3">
<gpxtrx:DisplayColor>Blue</gpxtrx:DisplayColor>
</gpxtrx:TrackExtension>

</extensions>

Of course, if I use BaseCamp to change anything later, I have to redo the fix but at least this works and the tracks all end up with the color I want.

Now if only someone could come up with a way to tell the 62s not to hide the track every time I touch its track file.

And I agree with MARCVANIMPE's endorsement of the program called GPS Utility. It's a great little program that I use a lot.

I made it more complicated than I needed in the above post yesterday. There doesn't seem to be any need to have both the gpxx and gpxtrx versions of the tags. The gpxtrx version appears to be sufficient.

To summarize:

If I use the 62s track manager to assign a color to a track that hasn't previously had a color assigned, it adds xml to the track file that looks like this (line breaks added for clarity):
<extensions>
<gpxtrx:TrackExtension>
<gpxtrx:DisplayColor>Magenta</gpxtrx:DisplayColor>
</gpxtrx:TrackExtension>
</extensions>

BaseCamp chokes on that version when it tries to read the file from the 62s because it's not proper xml.

If I start with BaseCamp and color the track there, It adds xml to the track file that looks like this:
<extensions>
<gpxx:TrackExtension xmlns:gpxx="www.garmin.com/.../v3">
<gpxx:DisplayColor>Magenta</gpxx:DisplayColor>
</gpxx:TrackExtension>
</extensions>
The 62s ignores that version because it uses a gpxx prefix where the 62s wants a gpxtrx prefix.

If change the gpxx prefix to gpxtrx in the track files that BaseCamp put in the 62s gpx folder, it looks like this:
<extensions>
<gpxtrx:TrackExtension xmlns:gpxtrx="www.garmin.com/.../v3">
<gpxtrx:DisplayColor>Magenta</gpxtrx:DisplayColor>
</gpxtrx:TrackExtension>
</extensions>

That version works for both BaseCamp and the 62s.

I uploaded the latest version of BaseCamp (3.2.0.2 beta) and firmware for the GPSmap 62s (3.00).

The good news is that BaseCamp no longer produces errors for tracks that have had their color set on the 62s -- it isn't as picky about correct XML as it was before. The 62s and BaseCamp both seem to work well with track files colored on the 62s; they have track color sections that look like this:
<extensions>
<gpxtrx:TrackExtension>
<gpxtrx:DisplayColor>LightGray</gpxtrx:DisplayColor>
</gpxtrx:TrackExtension>
</extensions>

The bad news is that tracks that I upload from BaseCamp to the 62s still have the gpxx prefix in their XML and are still ignored by the 62s. I still need to edit the track files to change gpxx to gpxtrx. The files uploaded by BaseCamp now have track color sections that, before I edit them, look like this:
<extensions>
<gpxx:TrackExtension>
<gpxx:DisplayColor>LightGray</gpxx:DisplayColor>
</gpxx:TrackExtension>
</extensions>