BaseCamp 3.3.0.2 Beta is available

0: Can you attach a gpx file of the track that get filtered down to just 2 points? I haven't been able to reproduce this issue?

2: Currently we do not calculate ascent/descent for direct routes. That will be in 3.3 final (or the next Beta, if there is one). Ascent/Descent will be displayed in the statistics on the route's properties page. For auto-routes, we already do this in the Beta.

3: It's not just about route settings for different profiles, it's about activities. A mountain-biker might prefer very different routes than a tour biker, and will get different routes once the maps and devices support it. We are just a little ahead.

0. here you go gpx attached. However read my text more carefully, then I think you would be able to replicate. It happens to any track, that got created using the "autoroute to track conversion". Actually even via points set in the route before, will be dropped. That shouldn't be the actual behavior though. Just for reference I attach such a track (no via points). I think the filter should not drop previous via points, and filter reasonably. All other filter modes do work - so it doesn't matter that much however.....

2. Well I just retested using a map with DEM. For them it works. It doesn't work however for maps with contourlines only without a DEM. Please enable it also for maps without DEM but with contourlines.

3. okay, well I though something in this direction already, but thanks for confirmation...

0. here you go gpx attached. However read my text more carefully, then I think you would be able to replicate. It happens to any track, that got created using the "autoroute to track conversion". Actually even via points set in the route before, will be dropped. That shouldn't be the actual behavior though. Just for reference I attach such a track (no via points). I think the filter should not drop previous via points, and filter reasonably. All other filter modes do work - so it doesn't matter that much however.....

2. Well I just retested using a map with DEM. For them it works. It doesn't work however for maps with contourlines only without a DEM. Please enable it also for maps without DEM but with contourlines.

3. okay, well I though something in this direction already, but thanks for confirmation...

Thanks for the track. I can definitely reproduce the issue with that track.

All modern Garmin Topo maps have DEM. At this point I doubt we will add support for contour-line-only maps.

Regarding the issue with maps corrupting routes, does Garmin really think it's acceptable behavior on the part of it's software that users will have to throw out all routes created in one version of the maps, and totally re-create them every time there's a map update?

Not tryijng to bash, but I think this is an issue if that's Garmin's position.

Thanks for the route.

No, that is certainly not acceptable behavior. We are working on some changes that will alleviate the issue. You'll still have to re-calculate each route when a new map comes out, but you won't have to re-build it.

Backup Restore problem:
I added some tracks in BC 3.3 beta and tried to transfer the overall result back to BC 3.2.2. Therefore I produced a backup in BC 3.3 and restored it in BC 3.2 . It seemed to work (no messages), but the tracks added in BC 3.3 are not available in BC 3.2.
The workaround, to export the new tracks in BC 3.3 and import them in BC 3.2 I did not try until now. I will try this probably in january, coming back from a travel.

That is working as intended.

3.2 cannot read data from 3.3.

3.2's database is stored in %APPDATA%\Garmin\BaseCamp\Database\3.2.
3.3's database is stored in %APPDATA%\Garmin\BaseCamp\Database\3.3.

When you do a Backup, all you do is zip up the %APPDATA%\Garmin\BaseCamp directory (which contains both databases). So backing up in 3.3 and restoring with 3.2 will cause you to end up with the exact same directory contents, it's just that 3.2 and 3.3 read from different databases.

So exporting should be the way to go.

A couple of things on waypoints.

Can you make it accept cords with degree and minute symbols? Its always a pain to have to edit them out when you are cutting and pasting.

I wanted to set a promity for 500 feet around a waypoint. I entered 500 FT and it said invalid format. So I entered .01 mi and it accepted it and converted to 51 FT. I then changed 51 to 500 and it accepted 500 feet.

gpx send to Zumo device may not be complete.

One of the users over on zumoforums provided a route that was acting strange on his Z550. Each time he sent it from BC and imported it, the end point and possibly all 4 intermediate waypoints were not present in the route, though the distance and map of the route looked good.

I had difficulty repeating it, but discovered that if I changed the 4 waypoints to shaping points, the imported route looked like his. But then in BC, I changed the 4 waypoints back to display as normal. The Z550 imported route would still not display them or the endpoint.

Finally I exported the list to a gpx and opened it with MapSource, sent it to the Z550 and the import of the route showed the 4 waypoints and endpoint as it should.

My theory is that the route <extensions> starts by resetting the subclass with
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
that may be a requirement on certain devices, but missing from the BC gpx.

The attached Waypoint Route.gpx is an export from BC. The attached Waypoint Route_MS.gpx is a Save As from MapSource after opening the BC Waypoint Route.gpx. Both files in the attached zip. Compare the two gpx files and you'll see the differences between one that works (MS) and one that doesn't (BC) for the same route.

Update:
I edited in the above XML expression to the BC gpx file that doesn't work right to the <rtept> <extensions> for each of the 6 total waypoints in the <rte> and the BC gpx now displays the flags and edit of the add/remove for the route in my Z550 shows them again as should be.

Summary:
While switching a waypoint to a shaping point and back to not a shaping point seems to have caused this behavior, possibly by a software switch not being reset, this is probably a glitch when using the insert route point ends up on an intersection and the user resets the automatic set to a shaping point.

BaseCamp Beta Routes

Dave, thank you! for following through on this critical component [for some of us] of sending custom routes to our Zumo devices.

Dave, thank you! for following through on this critical component [for some of us] of sending custom routes to our Zumo devices.

Dave, I second Marc's thanks. Thank you.

Being able to send routes to the Zumo 550, and having Waypoint flags be shown, and announced, on the Zumo, is a basic function of a GPS.

I hope Garmin is giving it more attention than some of the arcane problem requests I've seen posted here.

Don