BaseCamp Beta crashes when...

It appears that BaseCamp is running out of memory while importing the file, there are a few possible solutions, but the easiest is to split the file in half using a text editor. We are working on making the import/export of .gpx files more efficient but there will always be limits. That is one reason we added the export of .gdb files in BaseCamp 3.2 beta. Because it is a binary file, its import and export is much more memory efficient. Sorry for the inconvenience.

Thanks for the feedback azdrmn. I did export the file in discussion as a GDB using BaseCamp Win-7. As noted above, the GPX file was 684KB and the exported GDB file is 709KB. When I imported the GDB file with beta-BC the waypoints were imported instantly (WOW!!!). That's some improvement in memory management over GPX files.

Now, I then did an export of the waypoints to a GPX file. The result was also very fast - but, the resulting file was 2.5MB.

I see why.

In my original GPX file the waypoints were structured as:

<wpt lat="48.25234" lon="-120.11282">
<name>&quot;CAMPGROUND&quot;</name>
<desc></desc>
</wpt>

*by the way, I removed the (&quot;) tags in the GPX file and it still crashed beta-BC.


In the exported GPX file the waypoints are structured as:

<wpt lat="47.600220004096627" lon="-120.640040002763271">
<name>"CAMPGROUND"1</name>
<sym>Campground</sym>
<extensions>
<gpxx:WaypointExtension xmlns:gpxx="www.garmin.com/.../v3">
<gpxx: DisplayMode>SymbolAndName</gpxx: DisplayMode>
</gpxx:WaypointExtension>
</extensions>
</wpt>

When I imported the beta-BC exported GPX file (2.5MB) it was also imported very quickly. So, this begs the question, why was the original GPX file so difficult to import for BC?

Cheers,

Sent the offending file as requested.

Cheers,

It turns out the problem is the 6000 waypoints all named the same thing. There is a memory inefficiency on the Mac side that is causing the crash. That should be fixed in time for the release.

Thanks for the feedback azdrmn.