Hundreds of waypoints in Device Favorites?

Hello I've created a custom route (or at least I think I did) by importing a saved gpx file from a map created thru Tyre. (creating custom routes inside BaseCamp is horrible, so I use Tyre).

The route comes in to BaseCamp fine, then I send it to my Nuvi 1100LM device. The map shows up on the Nuvi but in my Favorites is not just the route name, but "ALL" of the hundreds of waypoints. It takes me forever to cycle down to the actual route destination name.

Is there any way to get rid of the waypoints showing in my favorites, once the route is established? I tried deleting them in BaseCamp and it did delete them, but when I send it to the device they are still there?

I'm wondering if the ones still there are from my first send, and (heaven forbid) I have to manually cycle thru and delete them one at a time on the device itself.

Appreciate any input on this.

0 SUSSAMB over 11 years ago

I agree with most of that ...

However Basecamp will send just the route to a nuvi, without sending any other associated points. Simply right click the route and select Send to ...

I've certainly found no need to delete waypoints/POIs from the database prior to sending the route :confused:

There's a further explanation here https://forums.garmin.com/showthread.php?21640-POIs-Waypoints-Via-Points-Shaping-Points-101

0 RW_G over 11 years ago

You’ll find many answers to your question, partly because Garmin has changed terminology over the years. Here is my understanding:

The base part of a Route is made up of Via Points. A Via Point can be a Waypoint, a POI (Point of Interest) or a Location. A Location is created by clicking on the Map with either the Route Creation tool or the Insert tool. If the Route is an Automated Route (any profile except Direct), it will be supplemented with additional points that follow routable features on the Map. A few of them will show up under the Route Directions tab.
< . . . . . . . . . . . cut . . . . . . . . . . . . . . . . . . .>
There is an exception to the above. If you delete the Waypoints/POIs from the BaseCamp database after creating the Route, it will not send the Waypoints/POIs as separate objects (Waypoints) in addition to the Route. Nor will they be exported as separate objects. Perhaps this what SUSSAMB does?

Thank you for the excellent detailed info to my question on purchasing choice on a newer NUVI.
From experimentation I've found my current NUVI does not acknowledge the route at all when it gets it back after I deleted the Waypoints from it in BaseCamp. Say like if I save the 1st (source) and 2nd (destination) point only, that's all that goes back to the Nuvi and it then creates it's own map when selecting the destination (as before I ever edited it in BaseCamp).

(in response to BTLAAKE) -I agree with most of that ...

However Basecamp will send just the route to a nuvi, without sending any other associated points. Simply right click the route and select Send to ...

I've certainly found no need to delete waypoints/POIs from the database prior to sending the route :confused:

There's a further explanation here https://forums.garmin.com/showthread.php?21640-POIs-Waypoints-Via-Points-Shaping-Points-101

Thanks for another excellent explanation link for future purchases. However I'm still a little confused as to knowing what attributes are included in a Newer Nuvis the do have "MULTI-POINT ROUTING" capability. Does this mean I will have access to "shaping" points in BaseCamp
OR
does that not matter to my original delimna of wanting to have a "route" with a custom shape (or whatever description thereof) without having all the Points (whatever they're type) sent to my Favorites list. Having to sort thru hundreds of Whatever Points in my Favorites to select a route or destination is just not functional.
Hopefully I am making myself clear on my desires here.

0 SUSSAMB over 11 years ago

From 2013 models onwards nuvis accept shaping points from Basecamp, prior to that shaping points were simply treated like normal waypoints/via points.

0 BTLAAKE over 11 years ago

Thank you for the excellent detailed info to my question on purchasing choice on a newer NUVI.
From experimentation I've found my current NUVI does not acknowledge the route at all when it gets it back after I deleted the Waypoints from it in BaseCamp. Say like if I save the 1st (source) and 2nd (destination) point only, that's all that goes back to the Nuvi and it then creates it's own map when selecting the destination (as before I ever edited it in BaseCamp).

SUSSAMB owns a Nuvi and I do not, so I cannot say how I Nuvi will behave while SUSSAMB can.

With regards to what I wrote, the Waypoints are not deleted from the Route, but from the BaseCamp database. That is, you should see a Route and separate Waypoints. You delete the Waypoints and leave the Route alone. I mean delete and not delete from list. They should be not show up when looking at My Collection.

I've certainly found no need to delete waypoints/POIs from the database prior to sending the route :confused:

As I wrote, what is sent is not necessarily what is used. A device is free to ignore any information it chooses.

My outdoor device receives data in the form of a .gpx file(s). It also stores information in the same format. My device (NOT a Nuvi) will receive the information in separate files based on object type (Waypoint, Track or Route). That is, if I send just a selected route containing Waypoints to my device, BaseCamp will send two .gpx files – one for the Route and one for all Waypoints in the Route.

If I export the same selected route as a .gpx file, BaseCamp will export a single file and that file will contain the Route and any Waypoints in the route as separate Waypoint objects.

Perhaps BaseCamp now sends different information based on device/device type, but it would be easier to send all the information any device might use and let the device choose which information to use or discard. I know that how information is sent to my device by BaseCamp has varied during the development of the application.

I was merely seeking clarification on how a Nuvi behaves, I don’t own one.

The trick of deleting the Waypoints from the BaseCamp database is the only way to send just a route to my device (NOT a Nuvi). After sending the route, one has the option of undoing the delete to restore the Waypoints. The other alternatives are to manually delete the correct Waypoint file on the device, turn on the device and delete from there or delete them by accessing my device thru BaseCamp. The trick also works with exporting a route as a .gpx file. Give it a try and check what is in the file with a text editor like Notepad.

0 SUSSAMB over 11 years ago

Thanks for that. If I can find some time I'll have a play tomorrow and see what exactly is happening when I send just a route to my nuvi.

0 Former Member over 11 years ago

I was merely seeking clarification on how a Nuvi behaves...

I'm not sure that a definitive statement can be made about "how a nuvi behaves".

Different models do different things and that may even change according to firmware version.

Also the whole waypoint/via/shaping point along with POI's discussion is so confusing since, as has already been noted, the terminology has changed. The way I look at it there are

Waypoints, that is user created locations.
Via's, locations that do NOT appear in the Waypoint list but that are included in the route to make it follow a certain path. Via's can be POI's (map or custom), road junctions, or arbitrary points on a map. They can be announced or unannounced (assuming a device supports that). In BaseCamp Via's are referred to as "Shaping Points".
Routing points, that are automatically created by computer software to define the route but are ignored by most devices. These points do NOT appear in the route properties.

Now to my knowledge Waypoints are transferred to devices when a route is transferred. Via's are not BUT their names are included in the route and the device includes, or not, their location in the route if they can match the name. Routing points are also included but have no names just coordinates.

I don't know what BaseCamp does when Waypoints, that are part of a route, are deleted but I suspect they become Via's.

Here some snippets from a route GPX file to illustrate the above

Waypoints included in the route

<wpt lat="38.870959281921387" lon="-97.873141765594482">
        <time>2014-03-05T17:49:05Z</time>
        <name>End</name>
        <sym>Number 2, Red</sym>
        <extensions>
            <gpxx:WaypointExtension xmlns:gpxx="www.garmin.com/.../v3">
                <gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode>
            </gpxx:WaypointExtension>
        </extensions>
    </wpt>

    <wpt lat="38.879130212590098" lon="-97.878014082089067">
        <time>2014-03-05T17:48:47Z</time>
        <name>Start</name>
        <sym>Number 1, Red</sym>
        <extensions>
            <gpxx:WaypointExtension xmlns:gpxx="www.garmin.com/.../v3">
                <gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode>
            </gpxx:WaypointExtension>
        </extensions>
    </wpt>

Route

<rte>
        <name>Start to End</name>
        <extensions>
            <gpxx:RouteExtension xmlns:gpxx="www.garmin.com/.../v3">
                <gpxx:IsAutoNamed>true</gpxx:IsAutoNamed>
                <gpxx:DisplayColor>Magenta</gpxx:DisplayColor>
            </gpxx:RouteExtension>
        </extensions>
        <rtept lat="38.879130212590098" lon="-97.878014082089067">
            <time>2014-03-05T17:48:47Z</time>
            <name>Start</name>
            <sym>Number 1, Red</sym>
            <extensions>
                <gpxx:RoutePointExtension xmlns:gpxx="www.garmin.com/.../v3">
                    <gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
                    <gpxx:rpt lat="38.87913029640913" lon="-97.87801424972713">
                        <gpxx:Subclass>010092D617015FE91000211600002C2B2900</gpxx:Subclass>
                    </gpxx:rpt>
                    <gpxx:rpt lat="38.879070281982422" lon="-97.876875400543213">
                        <gpxx:Subclass>090092D61701116E0E001F8A2C001F2A8F00</gpxx:Subclass>
                    </gpxx:rpt>
                    <gpxx:rpt lat="38.878898620605469" lon="-97.875716686248779"/>
                    <gpxx:rpt lat="38.87836217880249" lon="-97.87320613861084"/>
                    <gpxx:rpt lat="38.87836217880249" lon="-97.873055934906006">
                        <gpxx:Subclass>050092D61701206D4E001F182C002C2A0000</gpxx:Subclass>
                    </gpxx:rpt>
                    <gpxx:rpt lat="38.87836217880249" lon="-97.873055934906006">
                        <gpxx:Subclass>050092D61701206D0E00211700009B060000</gpxx:Subclass>
                    </gpxx:rpt>
                </gpxx:RoutePointExtension>
            </extensions>
        </rtept>
        <rtept lat="38.87836217880249" lon="-97.873055934906006">
            <time>2014-03-05T17:49:51Z</time>
            <name>N Brookville Rd and 238 and Ramp</name>
            <cmt>N Brookville Rd and 238 and Ramp</cmt>
            <desc>N Brookville Rd and 238 and Ramp</desc>
            <sym>Waypoint</sym>
            <extensions>
                <gpxx:RoutePointExtension xmlns:gpxx="www.garmin.com/.../v3">
                    <gpxx:Subclass>050092D6170128205B100F1BBA0097A5C166</gpxx:Subclass>
                    <gpxx:rpt lat="38.87836217880249" lon="-97.873055934906006">
                        <gpxx:Subclass>050092D61701206D0E00211600009B060000</gpxx:Subclass>
                    </gpxx:rpt>
                    <gpxx:rpt lat="38.87836217880249" lon="-97.873055934906006">
                        <gpxx:Subclass>050092D61701206D0E001F022C002C2A5901</gpxx:Subclass>
                    </gpxx:rpt>
                    <gpxx:rpt lat="38.870959281921387" lon="-97.873141765594482">
                        <gpxx:Subclass>0A0092D61701873206001F00170037500000</gpxx:Subclass>
                    </gpxx:rpt>
                    <gpxx:rpt lat="38.870959281921387" lon="-97.873141765594482">
                        <gpxx:Subclass>0A0092D617018732060021170000B5240000</gpxx:Subclass>
                    </gpxx:rpt>
                </gpxx:RoutePointExtension>
            </extensions>
        </rtept>
        <rtept lat="38.870959281921387" lon="-97.873141765594482">
            <time>2014-03-05T17:49:05Z</time>
            <name>End</name>
            <sym>Number 2, Red</sym>
            <extensions>
                <gpxx:RoutePointExtension xmlns:gpxx="www.garmin.com/.../v3">
                    <gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
                </gpxx:RoutePointExtension>
            </extensions>
        </rtept>
    </rte>

Note that a Via (not Waypoint) is included by name "N Brookville Rd and 238 and Ramp". That is a road junction.

One can also see many Routing points. For example

<gpxx:rpt lat="38.87913029640913" lon="-97.87801424972713">
                        <gpxx:Subclass>010092D617015FE91000211600002C2B2900</gpxx:Subclass>

0 SUSSAMB over 11 years ago

I don’t own a Nuvi, but contrary to what SUSSAMB has written, Garmin typically will send both the Route and all Waypoints/POIs added to the Route. Locations in Routes created by clicking on the Map are not sent as separate points. It is not possible to export just a Route without it including the Waypoints/POIs, but that doesn’t mean a particular device will make use of all of the information sent to it (a Shaping Point in an example, it will be interrupted as an Alerting Via Point). This may well be the case with a Nuvi, but it will not be the case with all devices.

There is an exception to the above. If you delete the Waypoints/POIs from the BaseCamp database after creating the Route, it will not send the Waypoints/POIs as separate objects (Waypoints) in addition to the Route. Nor will they be exported as separate objects. Perhaps this what SUSSAMB does?

Having done some checks today I have to agree that what BTBLAKE says is absolutely correct. Waypoints that exist in the folder that contains the route will also be sent to the nuvi provided they are also in the route. If those waypoints are deleted first they are not sent.

I've not seen this behaviour before, maybe it's just the way I use Basecamp for planning, in that I tend to do all my waypoint and route planning in Basecamp for a trip and then send the whole lot to my nuvi. Or maybe it's a change to how Basecamp works. Either way it does seem nonsense that if you select just a route that associated waypoints that have been used to create that route are also sent individually to the GPS. Perhaps the Basecamp developers can look at this to see if an option could be included that says something along the lines of 'Do you want the associated waypoints also sent to your GPS'.

Equally as Stuart mentions, it may be a nuvi issue rather than a Basecamp one :confused:

0 Former Member over 11 years ago

Waypoints that exist in the folder that contains the route will also be sent to the nuvi provided they are also in the route.

Yep. MapSource does the same (unless you untick Waypoints in the transfer dialog).

If those waypoints are deleted first they are not sent.

Or use MapSource and simply untilck Waypoints :p

Now the route you get in your device depends on what's already in it. If the Waypoints already exist then your route includes those Waypoinst as though they'd been sent. If not your route consists of Via's. One can have a route consisting of nothing but Via's (i.e. consuming no Waypoint memory). Been there, done that.

0 SUSSAMB over 11 years ago

Well I would have sworn Basecamp didn't use to send waypoints (or at least they didn't appear in the nuvi favourites list) so either it's changed the way it works or my nuvi has. I'm not sure I remember how to use Mapsource now (:p) so I'll have to hope the Basecamp team add some sort of choice as existed in Mapsource, assuming it's a Basecamp issue and not the nuvi at fault.

In the meantime I'll have to ensure I move routes to an empty folder prior to sending them to my nuvi :)

0 Former Member over 11 years ago

Well I would have sworn Basecamp didn't use to send waypoints (or at least they didn't appear in the nuvi favourites list) so either it's changed the way it works or my nuvi has.

Depends on what a device does when a duplicate Waypoint is sent to it. Does it ignore it or create another copy with '1' on the end of the name? If the former it may appear as though Waypoints aren't sent. If the later you'll see the duplicate Waypoints.

In MapSource I usually untick Waypoints when trasferring routes to avoid getting duplicates (which I only have to go delete).