Latest BC version
4.32 fw on Oregon
symptom - connecting to BC and see file type not recognized error on this track and others.
To recreate (from oregon wiki thread http://garminoregon.wikispaces.com/message/view/home/32437782):
re: 4.32 track issues
I guess it is more complex yet. It seems I need to export or create the track with BC which has the header with the gpx property very short compared to a track created on the 450 (BC created one):
<gpx xmlns="www.topografix.com/.../1"
creator="BaseCamp 3.1.2" version="1.1"
xmlns:xsi="www.w3.org/.../XMLSchema-instance"
xsi:schemaLocation="www.topografix.com/.../1 www.topografix.com/.../gpx.xsd">
I can copy this onto the 450 and reboot and connect to BC and all is well. If I go into the unit and change the track color and then connect to BC, it fails the file type not recognized error.
The 450 leaves the above gpx refs the same but adds the color attribute to the trk section:
<extensions>
<gpxtrx:TrackExtension>
<gpxtrx:DisplayColor>Red
</gpxtrx:DisplayColor>
</gpxtrx:TrackExtension>
</extensions>
If I delete this from the file BC reads it fine.
If I add the more extensive gpx section below that a track created on the 450 makes and leave the DisplayColor extention, it also works.
I would conclude that the extentions require more include paths in the gpx section.
Here is the gpx section that the 450 makes:
<gpx xmlns="www.topografix.com/.../1"
xmlns:gpxx="www.garmin.com/.../v1"
xmlns:gpxtrx="www.garmin.com/.../v3"
xmlns:gpxtpx="www.garmin.com/.../v1"
creator="Oregon 450t"
version="1.1"
xmlns:xsi="www.w3.org/.../XMLSchema-instance"
xsi:schemaLocation="www.topografix.com/.../1
http://www.topografix.com/GPX/1/1/gpx.xsd
http://www.garmin.com/xmlschemas/WaypointExtension/v1
http://www8.garmin.com/xmlschemas/WaypointExtensionv1.xsd
http://www.garmin.com/xmlschemas/TrackPointExtension/v1
www.garmin.com/.../TrackPointExtensionv1.xsd">
