BC 3.3.1 (won't alert) to all inserted via points

Former Member
Former Member
I'm looking at a route and nearby waypoints. I decide to add one to my route. I select the Insert tool, select the route and get the rubberband. I select the waypoint and it is added to my route as expected.

Every waypoint added this way ends up with the Shaping Point (won't alert) property. Is this expected behavior or am I missing a selection process to determine the alert/won't alert property of that point.

Do you prefer a New Thread for each issue or should I post under the 3.3.1 thread?
  • Look at this thread https://forums.garmin.com/showthread.php?t=25557

    above that explains how to set alerts (or not)

    If you go to the route properties and pull up the list of points simply right click and select as necessary
  • Former Member
    0 Former Member over 13 years ago
    I'm aware of how to fix it. I don't care to do double effort for each inserted waypoint while using the insert tool. When I'm inserting waypoints, it seems logical that I want those announced. When I'm inserting a Map Point, Map LIne or Map Intersection, those probably should have the property of (Don't Alert).
  • Might be to you, to me I'd prefer it the other way :)

    However not sure if there's a way to make it default to what you prefer ;)
  • It appears that the developers still have a bit to learn about basic use cases. Notification should not be based on whether a point is a waypoint or shaping point or whatever.

    There are two times when a person wants notification.

    1. When you are approaching a direction change.

    2. When you are approaching a "Stop".

    Unfortunately no Garmin device or software has the ability to define "stops". So instead we try to fiddle with notification properties of various types of points as a workaround.

    Microsoft Streets&Trips has the opposite problem. It has the concept of "stops". But it treats every point you put in a route as a stop and announces it as such. That has its own set of issues.

    ...ken...
  • Former Member
    0 Former Member over 13 years ago
    The only time you want a flagged, announced via point is if it is a waypoint, q.v. a "stop". Every other via point is a shaping point and does not need to be flagged or announced. Normal navigation instructions will tell you when to turn regardless of a via point or not. Where I use shaping points is where I don't want the waypoint announcements which are repeated at more intervals than navigation instructions.
  • Former Member
    0 Former Member over 13 years ago
    I am ok with posting issues in the 3.3.1 thread, but I definitely prefer a new thread for each issue, as it's easier to follow.

    That behavior is currently working as intended. We decided that when inserting a point with the tool, or when drawing a route on the map the user would most likely not want those announced. Maybe that was a wrong assumption.

    What we are planning to do is have a way to distinguish setting shaping vs. via points when inserting a point, most likely with the Ctrl key. So if you were to create a route point and hold down Ctrl, it would not be a shaping point.

    That feature didn't make it into 3.3, but we'd like to add it in a future feature release.
  • Former Member
    0 Former Member over 13 years ago
    I personally love that non-stops are (won't alert). My issue is I can't seem to get this to work on gpx files that I received from a fellow rider. I'm assuming they had to create waypoints to deviate from the given route (we bikers never take the straight route).

    Even when I seem to get BaseCamp to tag it as (won't alert) it still does when I run the route on my zumo.

    Am I missing something?
  • Former Member
    0 Former Member over 13 years ago
    The Zumos don't have full support for this.

    Shaping points (via points that won't be announced) only work if you create them on an address, or intersection on the map.

    You can also try to recalculate the route on your computer after you received it from someone else, that *might also fix the issue.

    Future devices will have full shaping point support and should properly skip announcing a via point if BaseCamp shows them as a shaping point.