Track color problem with GPSmap 62s

Score another one for the total lack of standardization at Garmin. :(

...ken...

Refer to my post "Errors in reading Oregon 550 files in Basecame" dated 12-21-2010

OK, I looked at that thread, but maybe I'm missing something; it still won't work.

I took a short track, imported it into basecamp, set the color to blue, and dropped it into the "All Data" folder on the GPSMAP 62s. So far, so good. It shows up as blue in basecamp's display of the 62s data and the DisplayColor extension tag for the track looks like the one in your post. But when I look at the track on the 62s, it's still red.

If use the track manager on the 62s to turn it blue and then plug the 62s back into the computer, I get a a dialog from Basecamp that says an error occured reading the file and it ignores the track.

Am I missing something?

I'll attach the track produced by basecamp and the version from the 62s after the color change below.

Repair bad GPX file.

First of all, I am no expert on editing XML. I only learned this to solve a problem that Garmin acknowledges they have, but after a year or so they have not fixed it. There is one of two problems; either the gps unit it not writing good language or Basecamp is not reading it correctly. I believe the former to be true. I have spent many many days and $70 to try to fix this issue. After a lot of searching, the XML Editor that has worked the best for me is both free, no spy ware and works very well is at this web site.
http://xml-copy-editor.sourceforge.net/
Try the following:
1. Down load and install the above XML editor, then launch it.
2. Open Basecamp.
3. Plug in your gps. Basecamp will give you an error message and tell you the name/s of the bad gpx tracks. Make a note of these.
4. In windows explorer click on your garmin unit or your garmin micro sd card; depending on where you are storing your tracks. These tracks are in the Garmin folder and then in the gpx sub folder.
5. After locating where to find the bad files, go to the XML editor and open that file or files.
6. You will notice that the track color is listed twice. There can only be one. The bad line will have a red squiggly line under it; this is the line that is causing you a problem. You will have to delete certain pieces of this line, if the red line does not go away the problem is not fixed. Any time you want test the language, just click on the 2 green check marks on the upper tool bar. The results will show on the bottom of the window and good language will result in no red lines under the XML lines.
7. When you are done with this track, save it back to your gps. It will ask if you what to replace the original file; say yes. Correct any additional tracks.
8. When you are all done, unplug your gps and then plug it back in again. Basecamp, if you were successful, will read all of your tracks.
I had to experiment to learn how do this, my reward is that I have learned a little more about the GPX world.
Good Luck

read this thread--- it sounds like the same problem.
https://forums.garmin.com/showthread.php?t=15490

A difference is the above thread is an Oregon 450, whereas yours is a 62. Did the previous software version of your 62 work ok? If it did, it's not the same problem and i wasted your time. The most recent beta for the the O450 caused this problem, and Garmin acknowledges it.

ron

That problem with the Oregon looks similar but different. My 62s is new, so I don't have any experience with the older firmware.

The bottom line seems to be that, for track colors, BaseCamp uses
<gpxx:TrackExtension xmlns:gpxx="www.garmin.com/.../v3">
and the 62s uses
<gpxtrx:TrackExtension>

The BaseCamp colors are ignored by the 62s, and the 62s colors are ignored by BaseCamp.

Thanks, everyone, for the pointers but I guess I'll just have to wait until the programmers at Garmin start working off the same page.

Thanks, everyone, for the pointers but I guess I'll just have to wait until the programmers at Garmin start working off the same page.

I hope you don't plan to hold your breath until that happens.

...ken...

I may have an answer. Not as good as what Garmin should have, but it will have to do for now. It is rather simple.

I had come to the conclusion that you cannot change color on the 62s with out errors when you connect to BaseCamp.

I know nothing about XML. I followed DRM4X4 instructions, I still had problems. It fixed the error, but you were stuck with the red color again. I really wanted different colors!

http://xml-copy-editor.sourceforge.net/
Try the following:
1. Down load and install the above XML editor, then launch it.
2. Open Basecamp.
3. Plug in your gps. Basecamp will give you an error message and tell you the name/s of the bad gpx tracks. Make a note of these.
4. In windows explorer click on your garmin unit or your garmin micro sd card; depending on where you are storing your tracks. These tracks are in the Garmin folder and then in the gpx sub folder.
5. After locating where to find the bad files, go to the XML editor and open that file or files.
6. This is were it is different. You do not need to delete.

Copy and add this: xmlns:gpxtrx="www.garmin.com/.../v3"

Example:
<trk>
<name>Dusy Ershim Trail</name>
<extensions><gpxtrx:TrackExtensionxmlns:gpxtrx="www.garmin.com/.../v3"><gpxtrx:DisplayColor>Magenta</gpxtrx:DisplayColor></gpxtrx:TrackExtension>
<gpxx:TrackExtension xmlns:gpxx="www.garmin.com/.../v3">
<gpxx:DisplayColor>Magenta</gpxx:DisplayColor>
</gpxx:TrackExtension>
</extensions>

*there is a space between TrackExtention and the part you add.
*This is a track that had the color changed on the 62s and was coming up with errors when connected to basecamp. It will have space for two colors. I believe one is for BaseCamp and the other is for the 62s.


click on the 2 green check marks on the upper tool bar. The results will show on the bottom of the window and good language will result in no red lines under the XML lines.
7. When you are done with this track, save it back to your gps. It will ask if you what to replace the original file; say yes. Correct any additional tracks.
8. When you are all done, unplug your gps and then plug it back in again. Basecamp, if you were successful, will read all of your tracks.
9. You will have to "Show on Map" on the 62s too.

I got lucky and figured this out. This seems to be the answer for now. Hopefully garmin will come up with a real solution. I hate having to "show on map" for all my tracks too. Whats up Garmin!!!!!

Thanks DRM4X4 I would not have gotten this far without your post.

You're very welcome!

Good job. Like myself, I knew very little about XML; I didn't think I should have too. With my 60CSx I have never had a problem, it's so simple to use. I can't understand why Garmin can't get this right. If I knew this error problem existed with the Oregon series I wouldn't have purchased it. I foolishly thought that Garmin would make a unit as good as the 60 series with much more to offer. However, in many ways it isn't as good the 60CSx and it is nothing but a headache! There are still two major problems with my Oregon 550: 1. It still makes incorrect tracks. The track will time to time swing wildly out from the actual track; my 60CSx has always been right on the money. 2. The read/write issue with the Oregon 550 and Basecamp.

@KD3131: Thanks!

FWIW:

This is still not fixed.
Note that the same problem exists in Mapsource: that Garmin software also refuses to open such GPX files...

...while a "simple" program like "GPS-utility" has no problem to open those files.

But what's more: when simply saving back... the file perfectly opens in BaseCamp AND Mapsource!!! No need to edit xml code.
One "problem" though: it opens in the Garmin softwares with "Standard" colour.
But at least it does not generate an error any more.

This is not a commercial for GPS-Utility... but it does a great job in exchanging file formats. It's freeware with reduced capacity or shareware at a moderate price for full capacity.
There may be others on the internet but I have not searched for them.

All that's needed:

• Connect the device
  
• Open the gpx-file in GPS-Utility.
  
• Save it back (if you don't trust it: don't overwrite but save under another file name).
  

May be helpful to some of us while waiting for a final fix by Garmin.