Shaping point feedback for 3.3.0.3 Beta

Looks Good.

I created 3 new routes in 3.3.0.3. A waypoint only route. A shaping point only route. A route with a mix of waypoints and shaping points. The were dragged to my Zumo 550 in the Device window and they import was finished on the Z550. These routes were identical to the routes I created in 3.3.0.2 which failed to download correctly to my Z550.

All 3 of these routes downloaded correctly from 3.3.0.3. The start and destination waypoints were transferred correctly and all waypoints and shaping points that determined the roads to be taken were correct. Recalculation using Faster Time on the Z550 did not change those routes I originally planned to ride.

I also Exported these routes and then Imported them using 3.2.2 to see if they would download correctly to my Z550. They do. I'll keep looking at 3.3.0.3 and see if the new logic continues to work and watch to see that all other good things continue to function after the change.

Looks good for me also on my Zumo 550

Actually, I am much lazier than Marc.

I just recalculated my original NY Rally route in the new 3.3.0.3 Beta version.

I did not recreate a new version of the route. My route had a few shaping points (unannounced) but mostly real waypoints.

However, after recalculating this route in the 3.3.0.3 beta, I dragged it to All Data on my Zumo 550.

I then did the routine on the Zumo after disconnecting, and then opened the route on the Zumo.

The Zumo screen before you select Go showed exactly the correct number of Via Points. (all but the start and end) The distance was slightly different from what was shown in BC. On the Zumo it showed 903 mile, in BC it showed 901 miles.

When I selected Go, and then previewed the route (I did not recalculate on the Zumo), it appeared to show all my waypoint flags where they should be. I zoomed in closer and went over the route and did not see any indication of any straight line segments, or other types of corruption.

My route went exactly the same places in the Zumo version as in the BC 3.3.0.3 beta version. As near as my zooming in would indicate.

I am completely confident that if I took this out to my bike to ride the route, it would make all the stops in all the exact right places.

I am happy so far!!

So then I recalculated, using Faster, on the Zumo. It did change the miles to 898. However, it still has the correct number of Via Points, and when I zoomed in to preview, I still do not see any evidence of straight line segments.

I don't understand why there are the discrepancies between the original miles on BC at 901, my Zumo before a recalculate which showed 903 miles, and now on the Zumo after a recalculate it shows as 898 miles.

I will admit, I did not zoom in to the lowest zoom level and exactly follow the route on the Zumo and BC at the same time.

Again, I am completely confident I could use this route as it sits on the Zumo to ride the route.

Later on I will open other routes I've previously created in BC, in the new 3.3.0.3 beta version, and then upload them to the Zumo 550, and see what happens.

If there are any discrepancies, I will report on them.

Thanks Garmin for apparently solving the problem with sending routes to the Zumo 550!!

Don

More routes sent to Zumo 550 worked as they should

I just wanted to add, I've sent at least a half dozen more routes to my
Zumo 550, from BC Beta 3.3.0.3, and all apear to be just fine for riding, using the Zumo.

Most of the routes are 300-500 miles long, with numerous via/way points.

Unfortunately, I cannot give you the exact creation history of the routes. I am next thing to positive though, that they have all seen older versions of the maps, and the non-beta version of BC.

However, now I am using map version 2012.3 in both BC and on my Zumo.

All of the routes have some combination of shaping points (some announced, some not) and "real" announced waypoints.

Some of the waypoints were known to BC (gas stations, motels, restaraunts, etc) and some are just points on roads that I want to stop at.

In every case, the first thing I did when opening these routes in BC beta 3.3.0.3 was to recalculate the route. Then I usually added a few more waypoints (New Waypoint Tool), or shaping points (Insert Tool) to the route.

When I had the route the way I wanted it to be for my actual riding, I connected my Zumo to the computer, and then dragged the route to All Data on the Zumo.

I then disconnected the Zumo and waited till it said the new data was available. At which time I imported the route into the Zumo.

When the Zumo was done with the process, I selected the route. In every single case, the number of via points shown was exactly as it should have been. The mileage shown was usually a little off from what was shown in BC.

For the first couple routes I did a preview, and all my waypoints had the orange flags. (plus green Start and checkered End) Then I did a preview of the routing itself (at about 2 miles zoom) and did not find any indication of straight line segments.

I then did a recalculate (always Faster) on the Zumo, and in most cases the mileage was at, or closer to, that shown in BC. And when I looked closer on the Zumo, it had chosen slightly different roads than BC in a few places. But it still went to every single waypoint, and shaping point, set up in my route.

After the first couple routes, I just automatically did the recalculate on the Zumo (like I always did with MS) and found the route to be completely usable for riding on the Zumo.

I do not use any of the fancier tasks in BC other than creating and editing routes.

For me, it appears BC beta 3.3.0.3 will work perfectly for creating, and then sending routes to the Zumo, to be ridden. Which is all I need.

Thanks Falagar, and Garmin, for listening, and then fixing, the problems we were having with doing this. (hopefully this is fixed for everyone)

Don

I imported two routes made with Mapsource and an older version of maps into BC. They are a short trip to and back from a Breakfast location. 39 miles each way. Each route has a start, finish and 3 points in between, to shape the route. One of the points is at an intersection and the other two are on the hwy. All were used to shape the route, but as everyone knows, the one at the intersection was not announced and the other two were.

First thing I did was delete all routes and favorites from my Z660, connect it to the computer and delete the current.gpx and temp.gpx files.

Next I did a recaclulate of each route with BC 3.3.0.3. This changed the distance to 34 miles. I can see where the change was made. I left this change because I am just testing the shaping/waypoints.

I looked at the properties of each route, and the point at the intersection shows "039 (won't alert)" in grey. Other points show in black. All is well so far. I then changed the other two points in one of the routes by right clicking it in properties and picking "Don't Alert on Arrival (shaping point)".

I then dragged both to All Data on the Z660, unmounted the Z660 from Windows and put the batter cover back on. I gave the Zumo time to boot and import the routes. I then went to custom routes and they were both there.

Now for the part that doesn't seem to be working. In the preview mode on the Z660, both routes show 4 point (flags); start (green flag), finish (checkered flag), and the two points on the hwy (orange flags). The point at the intersction, that was changed by BC, did not show in the preview (this seems to work as designed). I expected the other two points not to show on the one route where I changed them in the properties, to not alert on arrival.

Now for the part that doesn't seem to be working. In the preview mode on the Z660, both routes show 4 point (flags); start (green flag), finish (checkered flag), and the two points on the hwy (orange flags). The point at the intersction, that was changed by BC, did not show in the preview (this seems to work as designed). I expected the other two points not to show on the one route where I changed them in the properties, to not alert on arrival.

This is working as expected. We try to do the best we can to tell the device to honor the shaping points. But full device support for the new shaping point format will come at a later date.

What about the Zumo 550?

I just did a test by using the oldest maps and Mapsource versions I still have kicking around. CNNA2009 and MS 6.13.7. I created a route with 10 shaping points not located on intersections.

Imported the route into BaseCamp Beta 3.3.0.3 which has CNNA2012 maps. I selected all of the 10 shaping points in the Route properties box and set them to Won't Alert.

After sending to my Zumo and importing, the display showed orange flags for all of the 10 shaping points. I didn't expect that. Did you expect that?

It currently all depends on how you set the shaping points.

Remember, the devices haven't changed at all yet, full support for the shaping point extension that BaseCamp 3.3 writes out will come later (if for a new generation of Zumos, or by a firmware update I am not sure).

So what the devices currently should recognize as shaping points are route points set on an intersection or an address. It won't work if you set a waypoint as shaping point, or if you set a via-point on a POI.

Orange Flags

So what the devices currently should currently recognize as shaping points are route points set on an intersection or an address.

Thanks. That's what I'm seeing recently.

This is working as expected. We try to do the best we can to tell the device to honor the shaping points. But full device support for the new shaping point format will come at a later date.

Falagar,
Thank you for your reply. I hope this feature is made functional with a FW update.

From your rply to MKROUSE:

Remember, the devices haven't changed at all yet, full support for the shaping point extension that BaseCamp 3.3 writes out will come later (if for a new generation of Zumos, or by a firmware update I am not sure).

Point name balloons during insert point.

The Select Tool displays a point name balloon while hovering at a specific location on the map.

It would be very helpful if the Insert Tool also displayed a point name balloon when the rubberband is active and allowed the user to select one of the list of possible names displayed in that balloon. This would allow the user to more certainly select a map intersection point for a shaping point.