Basecamp won't read averaged waypoint files

When you are using extensions, they have to be declared in the header. This file is missing them. I assume you created this file manually?
Also, in my experience mixing extensions doesn't work: you have to use either gpxx:WaypointExtension or wptx1:WaypointExtension

The Montana v4.60 firmware does still have an issue with Elevation of Averaged Waypoints. But, it no longer has issues with headers. If you didn't do as JaVaWa indicated then maybe you are using older Waypoints averaged by an older version of the Montana firmware(?).

Cheers,

DRTBYK and JaVaWa
Thanks for the info. It's been frustrating not getting any guidance on this problem until now.
Since I have waypoint files created with earlier firmware versions, is there a way to clean up a waypoint file that was created with an earlier version of the Montana firmware?
thanks for the help.
colemanjj

As I recall from earlier posts concerning averaged waypoints the problem is that BaseCamp is very picky about the order of the tags, right?
I'm working on a new version of MacGPX that handles all gpx extensions that I know of, and isn't picky about item order or mixing extensions. When saving data MacGPX will create a BaseCamp-compliant gpx file.
I'm thinking about a Windows version too (I'll have to come up with a new name for both versions...), but it isn't finished yet.
If you own a Mac, you can download a beta version of the new MacGPX here: http://www.javawa.nl/macgpx_en.html
If you don't, you'll have to wait... (or send me the files that need a clean up)

The sample you provided can be fixed by replacing the header. This may not work for all you files. I prefer to do this sort of thing with WordPad. After you make changes and save a file, make sure that it hasn’t added a “.txt” to the extension (e.g. MyFile.gpx.txt). If it does, edit the name and remove the .txt.

Export a waypoint from BaseCamp to a gpx file to get a valid header. Make a copy of the gpx file you want to fix – don’t work on the original in case this doesn’t work.

Open the BaseCamp gpx file with WordPad and copy the header. This is everything above <metadata>.

Open the copy of the file you want to fix and replace everything above <metadata> via select and paste.

If BaseCamp can import the altered file copy, you should be okay. You can delete the altered files, but keep the originals.

That wouldn't solve the problem with mixing extensions or item order problems...

I said that it might not work on all of his files, but it does with the one he supplied. The mixed extensions in his particular sample file don&#8217;t seem to cause a problem.

It&#8217;s a start on getting at least some of his data into BaseCamp for immediate use, nothing more.

I added a full header and eliminated the mixed extensions (converted all to wptx1) and the file works fine now.
The files with missing header info and mixed extensions worked with other software and with the GPS unit. Just seems like Basecamp is very picky.

Thanks for the help. I had been trying to fix the files by trial and error for months now. I thought of the header problem but never thought that mixed extensions might be a problem.
thanks a lot for the help. i can now finally use Basecamp with my waypoint files.

JaVaWa, I don't use a Mac but I'd switch to something other than Basecamp if I could find something that was compatible with the garmin extensions, including averaging, read multiple waypoint files simultaneously, and displayed more extension values (like the number of samples averaged). I'll keep checking your web site.

colemanjj

I'm afraid this is difficult to answer without seeing a sample gpx file. The issue could be in the header or construction of the Waypoint data.