Suggestion for Waypoint Symbols

I agree that would be nice.

We do have a case for this in our feature tracking database, but it hasn't made it yet. Hopefully we will get around doing something about waypoint symbols in a future release.

Thank for that! Of course I can live with it now, and if it will be implemented in one of the future versions, that would be fantastic :)

I too noticed that "Circle with X" in BaseCamp does not display properly, in my case, on the GPSMAP 62s.

Additionally, I've noted a problem with Custom Symbols compatibility which may be related. I created a custom symbol 001.bmp (16x16 pixel, RGB, 8 bits per channel). I placed the file in the Custom Symbols folder in the MyGarmin folder on my computer. A copy of the SAME file was also placed in the Custom Symbols folder on the 62s.

If I assign this custom symbol to a waypoint in the 62s it is displayed on the device. When I view the same waypoint on the device in BC, it does not display. If I assign this custom symbol to the waypoint with BC, it does not display on the 62s although it now displays in BC!

I had something similar with my Montana: if I design a route with route-via-points, in Basecamp I see little dots.
If the route is send to the Montana, I see pins with red ball cluttering the display.
In the received GPX it says <sym>Waypoint</sym>, So I designed a custom waypoint for it to replace this default pin. Unfortunally, the Montana itself refuses to use this replacement symbol. Even if I rename it to "MyWaypoint".

I emailed this as a feature on the wishlist for new firmware for the Montana: they would look into it.

Why do Garmin (Basecamp) and Garmin (Montana) use different symbols?

@Frensicpic:
As far as I remember it´s not enough to place the Custom Symbol on the device with the same name. They must not be named 001, 002 etc... they have another naming schema. Yesterday I stumbled upon a document with information about that. I´ll keep my eyes open if I find it again. I think it was something like cust001, cust002 etc... but I´m not sure anymore :confused:

Edit: Found it (on another Site, but it´s the same information) in the Oregon Wiki, #CM4: Oregon Wiki

@PBUEDI
Thanks...I've seen that page before although I missed the "renaming" part. I believe I saw elswhere that the files needed to be named 000 up to 063 for a total of 64. Interestingly, the "sample" files in MyGarmin are .png, not .bmp. They, along with the custom symbol .bmp file I created also appears in BaseCamp. A copy of this custom symbol also appears in my GPSMAP 62s under "custom".

The real issue is that if I assign this custom file via BC and send it to the GPS, it will not show on the GPS device although it appears in BC; If I assign this custom file via the 62s to the same waypoint, it shows on the 62s but not in BaseCamp

Did some "playing around" with one custom symbol file (001.bmp) and observed the following:
For BaseCamp, the file name must be numerical, 001.bmp in this case. This file with this name also works on the GPSMAP 62s.

For the 62s, the file name may either be numerical or a alpha (word(s)). The alpha named version of the same file will not appear in BaseCamp. I renamed 001.bmp to RR Xing.bmp for this test.

Back to 001.bmp, even though it works both on the device and in BaseCamp there is an incompatibility between the 62s and BC. If I select this particular symbol in BC and assign it to a waypoint, it displays properly in BC. When I disconnect the 62s and examine that waypont, the symbol defaults back to the "blue flag". If I assign the custom symbol to the waypont using the 62s, it does not display with the waypoint in BC!

Did you also try to rename the file like it´s mentioned in the Wiki?

So:
001.bmp for Basecamp and
Custom 1.bmp for the GPS?

Or:
000.bmp for Basecamp and
Custom 0.bmp for the GPS and so on.


It´s also important if you have a png, that you should not rename it to bmp. Some software can deal with wrong file extensions (for example realizing that there´s a png within that file with a bmp extension), but I´m not sure if BC and the Devices deal with it.

Yes, I did try "Custom 1", etc. as suggested in the Wiki. It does not make a difference in what I am experiencing. I can get custom symbols to show in BC or the GPSMAP 62s; the problem is the incompatibility between the two which is what I've been trying to express in my previous posts. The custom symbol I am working with was created as a bmp, not a renamed png.

The sample custom symbols in the MyGarmin folder are a series of 8 png's 000 - 007. They HAVE to be named in this manner to show in BC. Other names such as Custom 1 does not work! If I copy them to the CustomSymbol folder on the 62s, they do not show on the device regardless of the name.

The custom symbol bmp appears on the 62s regardless of its name (the same file named 002, Custom 2, or RR Xing, all work on the GPS).

Using the same symbol file, named one way for BC and another way for the 62s is un-satisfactory. If I assign a symbol via BC, it should appear on the GPS or vice-versa.

With this playing around I have also discovered that a symbol in the Marker category in BC called "Circle with X" does not display on the 62s. This symbol Note that this symbol is NOT in the Custom category. This particular symbol is not in the symbol library on the 62s.

If you do a search on this forum, you'll see that this I'm not alone with incompatibility of custom symbols between the GPS and BC. In the meantime, I'm not going to mess with symbols via BC unless they match the 62s. For my custom symbols, I'll place them in the GPS CustomSymbol folder via USB. The symbol on the device is more important than what BC is or not doing.

Thanks for your suggestions.
John