GPSMAP 60CS screen cluttered by route point labels

For what it’s worth, I checked my registry and both MapSource and BaseCamp are using 12 00 00 00 for a Via Point. This corresponds to a Marker type(?) Waypoint (dot). I would be surprised if this wasn’t one of the oldest Garmin symbols, but you can make a waypoint on your GPSr and edit the symbol to see if it is there.

One other thing you can try is to set your points to don&#8217;t alert. If they are already set to don&#8217;t alert, they will be grayed out in the Properties tab and they won&#8217;t show under the Route Directions tab. Don&#8217;t Alert will change the trip extension from <trp:ViaPoint to <trp:ShapingPoint. It may not make a difference or your unit may ignore the trip extension, but it&#8217;s worth a try.

If your route is not a Direct Route, you should probably recalculate it to see if there are any changes.

I checked my registry and both MapSource and BaseCamp are using 12 00 00 00 for a Via Point. This corresponds to a Marker type(?) Waypoint (dot). I would be surprised if this wasn&#8217;t one of the oldest Garmin symbols...

Correct, symbol 12h is a small black square and it has been around for a very long time. That said some newer model units don't have it. I've no idea why but they don't.

I recommended using City, Small (code 45h) which is a small green circle which does exist in most units.

FYI: MapSource 6.16.3 Waypoint Symbols

PS: Only my 1490T unit (see my sig below) implements the small black square (12h) but all have City, Small (45h).

PPS: For symbol codes see this post.

https://forums.garmin.com/showthread.php?1165-via-points-in-MapSource&p=131057&highlight=ViaSymbol#post131057

BTW I use Flag, Green (8Eh) for my (default) waypoint symbol since all my units support that.

STUARTMW,

Thanks for the links and also where to set default waypoint and viapoint in the registry.

You could try using WindGDB3, from http://www.sackman.info/
It can do conversions for GDB files. One of the options is "make via points invisible".
So try exporting your route from BaseCamp as a GDB file, then running it through WinGDB3 with that option.

Wow, I haven't used WinGDB since version 1.x in Oct 2004. Simon Long was the original author. Think I'll play with the latest version a bit :)

Hi,
I have a similar problem with my eTrex 30.
When I create a route with Basecamp and import it in my GPS, the route is unusable on the tiny screen of the eTrex because cluttered with blue pins (no flags for me).

I tried to edit the window registry (replace 12 by 45) but the only change it did was to turn the tiny black dot symbols of the Via Points into small greendots. When I imported that route in my device, it didn't make any difference and I still had those damn blue pins cluttering my screen:mad:

I haven't tried the other solutions yet, but wouldn't it better that Garmin offers a proper solution. This problem, from what I've read, is affecting different devices and is not new at all, I can't understand why Garmin hasn't fixed that yet???

...cluttered with blue pins (no flags for me).

If you've read my previous posts on this subject you'll see that I said the "blue flag" is substituted for whatever symbol(s) a particular model doesn't support. Does the eTrex30 have a "blue flag' symbol? If not it might be using the "blue pin" instead.

The issue of different Garmin models only supporting some waypoint symbols is a long standing and common complaint. Currently BaseCamp supports 318 symbols but I don't know of any model that includes all of them.

In short you have to know what symbols your eTrex supports and only use those ones (unless you like blue pins).

OK i fixed the problem for my eTrex!

Stuart your post made think that it was weird that I had pins instead of flags if the symbols were missing.

On my eTrex I have 196 symbols (but some are duplicates), so I created a route with different symbols, some both available in Basecamp and the eTrex, and some only available in Basecamp.
As expected, the symbols that were both in Basecamp and the GPS were displayed properly, but the symbols that were only available in basecamp were displayed as blue flags, not blue pins.

So I thought if I could get rid of that damn blue pin symbol, it wouldn't cause a problem.
In order to do that I created a 32 pixels width square completly magenta (see explanations HERE), named it "Pin, Blue.bmp" and put it in the custom symbols folder of my GPS.

Now gone those damn blue pins that were cluttering my screen, the only drawback is I cant use that symbol anymore, I hope basecamp won't use it for something else.

Now I don't know if you can apply that technique to your device, because in my case the Via Points were displayed as blue pins (symbol available on my device), not as blue flags (displayed when a symbol is missing).

Well it sounds like BC is using the "blue pin" symbol for all via's. You said you modified the BC registry settings which should've fixed the issue (you did restart BC right?).

Your solution is quite elegant ("blue pin" is now blank as a custom symbol) so if that works for you then all is solved.