Strange case of "unroutable" waypoints

Former Member over 10 years ago

I have hundreds of waypoints. With them I create hundreds of routes which I then transfer to the nuvi, where they become trips. So far, so good, the process works fine.

But, for some unfathomable (to me) reason, some waypoints are omitted by the nuvi when creating the trip. Now, that could be just a nuvi software hiccup, but it's more confusing than that: the nuvi always omits the same waypoint(s), no matter what trip they belong to, so there's something different about these particular waypoints, something that makes them, for some reason, not acceptable by the nuvi as trip waypoints.

Note: the BaseCamp route is not the problem (all waypoints are there), it's only when the route is sent to the nuvi that some waypoints are dropped. Also, all waypoints are on roads.

Any clues as to why these waypoints, created in BaseCamp, are consistently rejected/omitted from any/all nuvi trips?

Thanks

0 SUSSAMB over 10 years ago

OK. I've done it again ensuring I see it exactly as you do, 120 not 122, and it still all shows up. Probably a device issue so you may want to try a master reset to see if that resolves it.

0 Former Member over 10 years ago

OK. I've done it again ensuring I see it exactly as you do, 120 not 122, and it still all shows up. Probably a device issue so you may want to try a master reset to see if that resolves it.

Thank you.

After a hard reset and everything new (waypoint, route and trip) this is the way it looks:

BaseCamp

Nuvi

I give up. :(

Thank you all for the kind assistance.

0 Former Member over 10 years ago

For this issue I would contact Garmin Support. http://www.garmin.com/support

0 Former Member over 10 years ago

Two different issues could exist:
1) Sequential automatic Waypoint numbering in B/C is subject to reordering of route points when routes containing more than 9 such points are sorted in B/C. This is due to the "Dewey Decimal System' integer sorting methods used in B/C.

Note: This problem should not occur with the Original Poster's stated waypoint naming.

2) Nuvis cannot create more than one (1) waypoint at any given geolocated Street Address. Therefore it is necessary to fake in an odd or even numbered address at least two digits away from the correct location to create additional waypoints in a current model Nuvi Essential with Trip Planner.

0 Former Member over 10 years ago

Thanks, 39_Steps

I think it's something different, because:

If I rename and move the McD's waypoint to a different street close by and strip all it address data the nuvi keeps on omitting the stop.
If I add another stop to the above trip the McD's stop magically shows up in the nuvi and all is well.

I'll accept it as a device hiccup and move on.

0 Former Member over 10 years ago

Upon further review, there seem to be several potential issues for locating this McDonalds waypoint:
1) It is Nevada. Zip codes may include very large geographical areas and "city" names. This POI may be called McDonalds of Lemmon Valley in other databases.
2) Garmin maps have drawn in an exit ramp that can be displayed closer to the POI than the named street vector on the Nuvi display. Original block numbers may have started at a different location.
3) Many other nearby business POIs, with addresses barely the minimum required two digits apart, are searchable.
4) Etc, etc, etc. Map vectors may vary by device map. Try Jack in the Box or create a different POi in the 200 block of Lemmon Drive.

(Perhaps other POIs/Waypoints with similar geolocation issues exist in the OP's large database.)

0 Former Member over 10 years ago

Jack in the Box works.

O'Reilly Auto Parts, Qdoba Mexican Grill and McD's, all of them right next to each other, don't work.

My device is trying to tell me something but either it's too subtle or I am too dense, 'cos I don't get it. :)

0 Former Member over 10 years ago

Thanks, 39_Steps

I think it's something different, because:

If I rename and move the McD's waypoint to a different street close by and strip all it address data the nuvi keeps on omitting the stop.
If I add another stop to the above trip the McD's stop magically shows up in the nuvi and all is well.

I'll accept it as a device hiccup and move on.

Well, I am having a hard time moving on and really don't want to learn BaseCamp because entering points directly into the Nuvi 56 suits my navigation needs. However let's take it from the top: Reno, Congested POIs on the 100 block of Lemmon Dr, Incorrect or at least inconsistent odd/even address number ranges on the map block in the vicinity of McDonalds, No via shape points used in routing - Stops only, Single waypoint is skipped inconsistently - but two intermediate waypoints route properly?

Hmm. Reno? nuances? OP is skilled Garmin user?

Try enabling U-turns to see if that changes the results.

0 SUSSAMB over 10 years ago

As you'll note from my posts I had no issue with using it, so I'm unsure what is happening here with tranquilo2. However I don't think he's that fussed and has moved on ...

0 Former Member over 10 years ago

Correct. I would still like to know why the nuvi ignores some waypoints but that is a nuvi issue, unrelated to BaseCamp, so there's no much point in flogging that dead horse in this particular forum.

Mod, I'm outta here, feel free to bury this one. :)