BaseCamp 3.3.3.0 will not read Montana 8.gpx Tracks

You could post them here. Then someone with a little time to help might take a look at them for you. . .;)

Cheers,

Yes, please attach the gpx files and we can take a look.

Yay! Garmin is letting me stay logged in more than a few seconds now!

I am also having an issue, just this weekend, with a track I recorded with my Montana, opened with TopoFusionPro, edited out the sections of the track I did not want to save, and resaved the GPX file.

Now, when I import this GPX into BaseCamp, it only sees dozens of waypoints, and no longer a track.

But I can open the GPX in multiple other mapping software titles, and they all see it as a track.

Yay! Garmin is letting me stay logged in more than a few seconds now!

I am also having an issue, just this weekend, with a track I recorded with my Montana, opened with TopoFusionPro, edited out the sections of the track I did not want to save, and resaved the GPX file.

Now, when I import this GPX into BaseCamp, it only sees dozens of waypoints, and no longer a track.

But I can open the GPX in multiple other mapping software titles, and they all see it as a track.

The trimmed file is not valid XML, and thus isn't read at all. BaseCamp (and MapSource), or rather the XML parser we use, are very much unforgiving when it comes to invalid XML. TopoFusionPro probably has a bug if that's how you got the invalid file.

http://www.validome.org/xml/ should help you pin down what's wrong. In this case, a namespace wasn't declared in the header that was used further down (the one used to declare the track's color).

I attached the fixed version of the file (removed the color). You can set the color again in BaseCamp and it should fix the file for you.

Was it just the color?

I will look closely at the two files to see if I can determine all the differences.

Can you also please tell me why BaseCamp sees this file as only multiple waypoints, while my other mapping programs all see it as a track?

Yes, it was just the color (or rather the missing namespace for the color extensions, it was just easier for me to remove the color, than fixing the namespace).

It looks like the file contains nothing but tracks, and that is what BaseCamp displays. (BaseCamp displays tracks, not waypoints, even though a lot of the tracks only contain a single waypoint.)

Maybe the other programs read different extensions from that file contains and then somehow combine all the tracks into one? But from the raw data contained in that gpx file, it is several tracks.