Waypoint averaging corrupts the userdata.gpx for Basecamp

Thanks for reporting. Would you mind attaching the gpx file in total?

Thanks for replying so fast. Is there a way to send you the GPX without publishing it here? Maybe you can PM me an E-Mail address for that?

You can send a PM to me.

This is a device software issue. It has been fixed on the Montana/Astro320/Rino6xx/GPSMAP62stc/eTrexX0 devices so far, fixes for other devices should follow.

They don't have an ETA on it yet.

This is a device software issue.

Couldn't Basecamp/Mapsource simply ignore unknown tags in GPX files? That way 3rd party (not just Garmin) GPX files could be imported without getting the

"This is not a valid GPX file"

error when they have custom, but valid, extensions.

Couldn't Basecamp/Mapsource simply ignore unknown tags in GPX files? That way 3rd party (not just Garmin) GPX files could be imported without getting the

"This is not a valid GPX file"

error when they have custom, but valid, extensions.

They are not valid extensions if the gpx file in question doesn't declare them.

I believe we ignore custom extensions as long as the file itself is valid.

In this case, there is a Garmin extension that uses the 'Samples' tag, it it however not referenced in the gpx file. Which makes the gpx file fail validation.

I´m not too familiar with GPX / XML too, but maybe this helps Stuartmw a little bit to understand what Falagar means.
And please correct me if I´m wrong.

Basically a GPX is just a XML file which contains Data between XML Tags. Additionally you can point to a Schema within the XML file. The Schema itself contains information about which Tags are allowed in this XML file and which Data is valid for a specific Tag.

AFAIR you can describe that a Tag which contains a Date, may only contain a Date and not Coordinates. When opening a GPX in Basecamp (or in an XML Editor which supports Schemas), the XMl is validated against the Schema. If there´s a mismatch, the validation fails and that´s it.

So even if a Tag might look valid to you (because it´s written correctly and opened / closed correctly) it may not be contained in the Schema, which makes it invalid. So either the creator of the XML file also has to make sure it is included in the Schema or he should not create the Tag in the XML file.

....but maybe this helps Stuartmw a little bit to understand what Falagar means.

Yes it works as you describe. However the Schema is obtained via a URL so you must be connected to the internet and the file must be downloadable.

This model doesn't work well when one is traveling, doesn't have a permanent internet connection or when there are backbone/server issues.

In short if the Schema, for whatever reason, cannot be obtained Basecamp/Mapsource will throw an error without importing any data. The same happens if the Schema isn't up-to-date/correct as Falgar explained.

Falgar is correct in saying that a GPX file is technically invalid if the Schema doesn't match. My point is that this strict interpretation can result in problems.with perfectly valid files.

Corrupted GPX files, such as the ones (current.gpx) sometimes produced by my 1490T, are another issue. Basecamp/Mapsource will fail to read anything yet ExpertGPS will read what it can.

Yes it works as you describe. However the Schema is obtained via a URL so you must be connected to the internet and the file must be downloadable.
This model doesn't work well when one is traveling, doesn't have a permanent internet connection or when there are backbone/server issues.

In short if the Schema, for whatever reason, cannot be obtained Basecamp/Mapsource will throw an error without importing any data. The same happens if the Schema isn't up-to-date/correct as Falgar explained.

All schemas that BaseCamp supports are built into the application, so it needs no Internet connection to read and validate XML files.

I'm having a similar problem with my Montana 650 firmware v 4.20
After I average an existing waypoint Basecamp will no longer read the .gpx file.
I see that the elevation associated with the averaged waypoint becomes corrupt, see below:
[PHP] <wpt lat="39.200754" lon="-79.609911">
<ele>4999999781011763100000000.000000</ele><time>2012-08-09T22:55:15Z</time>
<name>32-87D2</name>
<sym>Controlled Area</sym>
<extensions>
<wptx1:WaypointExtension><wptx1:Samples>2</wptx1:Samples>
<wptx1:Depth>0.3048</wptx1:Depth>
<wptx1:DisplayMode>SymbolAndName</wptx1:DisplayMode>
<wptx1:Categories>
<wptx1:Category>20120804-205450</wptx1:Category>
</wptx1:Categories>
</wptx1:WaypointExtension>
</extensions>
</wpt>[/PHP]