BaseCamp 3.01 won't import Dakota 20 waypoints that were Waypoint Averaged

Former Member over 15 years ago

BaseCamp 3.01 was giving me a communication error with my Dakota 20, and only downloading a few of my waypoints. I discovered that the missing ones in a file on the GPS, and importing it gave:

"/Volumes/GARMIN/Garmin/GPX/MBC_Wpts.GPX" is not a valid GPX file and could not be opened."

By experimentation, I found out that MapSource declared any waypoints where I had used the GPS feature to position average were thought to be invalid. the XML file for these contains:

<extensions>
<gpxx:WaypointExtension xmlns:gpxx="www.garmin.com/.../gpxx:Samples>

It's the <gpxx:Samples> key that seems to throw it off.

0 azdrmn over 15 years ago

Firstly, I'm not quite sure which application you are talking about. BaseCamp for the Mac (my first assumption given the forum), MapSource for the PC (given the original title of this thread) or BaseCamp for the PC. However, it doesn't matter because there is an issue with the device that causes it to write invalid GPX files when the waypoint is averaged. We are trying to work with the device team to fix the issue.

BTW, to speed up the process of figuring out why a GPX file isn't opening, the actual error is printed to the console. It will give the file name, line and character numbers that the parser considers in error.

0 Former Member over 15 years ago

I posted it in Garmin Forums > Mac & Windows Software > Mac Software > BaseCamp .

Yep, it's BaseCamp for the Mac. I'm guessing that's the tag saying that the waypoint is averaged, and the number is the number of points that went into averaging the waypoint so far so it knows how much weight to give any new recording of that same point to the average.

0 Former Member over 15 years ago

Problem solved and explained

The latest Dakota 20 firmware upgrade does the right thing, in fact now it seems to create a new xml file for each waypoint... however, it doesn't correct the point-averaging of any waypoints created before that. I fixed it by removing the offending tags from the xml file.