BaseCamp 3.2.0.10 Beta posted

It's a zumo issue but look at the route in question. How many via points does it have in it? Over 250 and it can cause "issues".

Are you at v4.20 of the software? Hope that they deliver a "fix" rather than an "update" soon. v4.20 broke more than it fixed and reverting to an earlier version didn't fix a lot of what is broken (some of which you might not even be aware of unless you use Tracks).

Cheers,

Thanks Dan. Yes, I let it do the forced update to 4.20 when grabbing the latest map.

The route is actually fairly short and contains only six vias/shaping points. I created a new one in BC following the same roads and it imports just fine, so something got corrupted in the old file, I guess. I did a cursory look for broken (open) tags in the GPX file, but didn't spot anything obvious.

The zumo sure does seem fussy about route importing compared to my nuvi 760.

-dan

GPX Errors

I create my own GPX files. I do some of these manually, and some with software that I write.

Currently, if there is any error at all in the GPX file, it rejects the entire file and gives the following error:

xxxx.gpx is not a valid GPX file and could not be opened


It doesn't tell you anything about where the problem is. It would be nice if it could at least tell you the line number or show you the line(s) where it detected the error.

Thanks

Keith

It doesn't tell you anything about where the problem is. It would be nice if it could at least tell you the line number or show you the line(s) where it detected the error.

Thanks

Keith

Check the console. Typically BaseCamp will print the issue, line number and character on that line.

BaseCamp has a nice Custom Symbol organizer but it does not recognize my Montana as a "Compatible GPS". I know the Montana is since it has a \Garmin\Custom Symbols folder and I've manually added several which show up in the Symbols library.

Cheers,

We Have Problems

This is going to be a longish post, apologies in advance. I'm not happy.

I just returned from a motorcycle trip. As per my usual routine I downloaded and checked each days tracks, deleted the superfluous ones, and combined and renamed the result to reflect the date resulting in 9 tracklogs of ~ 1500 to 3000 points each. This was done on a MacBook air running the latest OS, all updates current with BaseCamp 3.2.0.10 Beta. Everything appeared to work as expected. The next step in my routine is to transfer the tracks to MapSource on my iMac to clean them up further using the available filter tools MapSource contains and archive them on a network drive.....

Problem #1

Every effort to export the tracks to a network drive or directly to another computer in .gdb format failed. Both MapSource 6.13.7 and whatever the current release is returned an "invalid MapSource file" error. BaseCamp had no problems importing the same file. All .gpx format exports worked fine, which leads to:

Problem #2

The .gpx and .gdb files appear to be randomly incomplete. Some tracks have the complete range of recorded data, some do not. A track contains the fields "Index", "Time", "Altitude", "Leg Length", "Leg Time", "Leg Speed", "Leg Course" and "Position". 3 of the 9 tracks have retained all of these fields. The other 6 contain only "Index", "Leg Course", "Leg Length", and "Position". :confused:

The first thing I did was check BaseCamp on the laptop and found the same thing. 3 of the 9 tracks were complete. The others missing data. :confused: :mad: Now it gets weird. ;)

Before I tried the export I copied the track files to a temp list, duplicated them, and combined the dupes into one track file comprising the entire trip. Roughly 11,000 points. I then deleted the duplicates. This track has complete data for every point..... Nothing missing.

I surmise from this that the tracks were indeed complete before I combined them and they somehow got edited in BaseCamp. I'm just thankful the combined track has all the data, I can split out individual days if I choose. This is not a new issue, I reported similar behavior in an earlier release.

The file issue is disconcerting as I prefer the .gdb format for archiving.

Files available on request.

This is going to be a longish post, apologies in advance. I'm not happy.

I just returned from a motorcycle trip. As per my usual routine I downloaded and checked each days tracks, deleted the superfluous ones, and combined and renamed the result to reflect the date resulting in 9 tracklogs of ~ 1500 to 3000 points each. This was done on a MacBook air running the latest OS, all updates current with BaseCamp 3.2.0.10 Beta. Everything appeared to work as expected. The next step in my routine is to transfer the tracks to MapSource on my iMac to clean them up further using the available filter tools MapSource contains and archive them on a network drive.....

Problem #1

Every effort to export the tracks to a network drive or directly to another computer in .gdb format failed. Both MapSource 6.13.7 and whatever the current release is returned an "invalid MapSource file" error. BaseCamp had no problems importing the same file. All .gpx format exports worked fine, which leads to:

Problem #2

The .gpx and .gdb files appear to be randomly incomplete. Some tracks have the complete range of recorded data, some do not. A track contains the fields "Index", "Time", "Altitude", "Leg Length", "Leg Time", "Leg Speed", "Leg Course" and "Position". 3 of the 9 tracks have retained all of these fields. The other 6 contain only "Index", "Leg Course", "Leg Length", and "Position". :confused:

The first thing I did was check BaseCamp on the laptop and found the same thing. 3 of the 9 tracks were complete. The others missing data. :confused: :mad: Now it gets weird. ;)

Before I tried the export I copied the track files to a temp list, duplicated them, and combined the dupes into one track file comprising the entire trip. Roughly 11,000 points. I then deleted the duplicates. This track has complete data for every point..... Nothing missing.

I surmise from this that the tracks were indeed complete before I combined them and they somehow got edited in BaseCamp. I'm just thankful the combined track has all the data, I can split out individual days if I choose. This is not a new issue, I reported similar behavior in an earlier release.

The file issue is disconcerting as I prefer the .gdb format for archiving.

Files available on request.

Please do send the files to [email][email protected][/email] referring to this forum post in the subject. We have had reports of .gdb files not being importable by MapSource, but we have not been able to recreate it.

As for the missing data, we will need file with no fields missing and the ones with it missing.

Thanks for the feedback and sorry for the inconvenience.

If I create a route in the Motorcycle Activity, then change my mind and want it to be recalculated as an Automotive route (I have very different routing prefs set for each), BC 3.2.0.10 will not acknowledge the change.

Selecting recalc does not change the route. I have to delete it and start over with BC already in Automotive mode to get the desired result.

Similar behavior with "method" ie: car or bike.

Also, when deleting waypoints in the via list, if I do a manual recalc, the focus shifts way from that window and to the route, though the next waypoint appears to be selected. If I hit the delete key at that point, it deletes the entire route. Oops. Speaking of which, how many steps back will Undo take me?

-dan

To change a route's activity are you changing the app's default profile or the individual route's? Once you have created a route, you will need to change its profile using the route dialog's activity picker.

Sorry for the confusing behavior when recalculating. We will look into this.

Undo should take you all the way back to the beginning of your current BaseCamp run.

Please do send the files to [email][email protected][/email] referring to this forum post in the subject. We have had reports of .gdb files not being importable by MapSource, but we have not been able to recreate it.

This may be an issue with my original BaseCamp instal on the MacBook. When I tried to open BaseCamp and select a track just now, the app would crash. After a re-installation, exported .gdb files (so far) are acting as they should. I really hate problems like this. ;) I'll keep an eye on the new instal.

As for the missing data, we will need file with no fields missing and the ones with it missing.

Thanks for the feedback and sorry for the inconvenience.

All of the tracks were in a single list and were duped as such before joining. The track resulting from the joining was included in the same list, and that list was exported/archived. I'll forward the file containing all of the tracks as per instructions.

BaseCamp has a nice Custom Symbol organizer but it does not recognize my Montana as a "Compatible GPS". I know the Montana is since it has a \Garmin\Custom Symbols folder and I've manually added several which show up in the Symbols library.

Cheers,

Currently BaseCamp only supports the legacy unit's custom waypoint symbols. We have updating to support the newer mass storage unit's custom waypoint symbols on our ToDo list.

In the meantime, if you really, really want them in BaseCamp, you can copy them into your ~/Library/Application Support/Garmin/Custom Waypoint Symbols directory and name them 0.<format> - 63.<format> where <format> can be .png, .bmp, or .tiff.