Compatible Waypoint Symbols

You must be new here. ;) Welcome! :D
Sadly, there is no solution. The problem exists with mapsource too.
And every device, not just our Vista HCx's, suffer it to varying degrees.
It is IMHO, the #1 most annoying issue with garmin.... :(

Hi. Thanks. Yup, I'm new here. Been reading for a while, but just signed up to post that question.

That is what I was afraid of. I just wanted to be sure there wasn't something I overlooked.

It seems like the software is developed by people who don't use it. Its a shame too.

The problem isn't with the Basecamp software developers in this case. It's the complete lack of standardization on the device development side of the company. Basecamp developers just try to provide a set of icons that catch most of what's out there. With the complete lack of standards (in more than just this case) on the device development side, it's pretty much impossible for Basecamp to perfectly match the devices.

...ken...

The problem isn't with the Basecamp software developers in this case. It's the complete lack of standardization on the device development side of the company. Basecamp developers just try to provide a set of icons that catch most of what's out there. With the complete lack of standards (in more than just this case) on the device development side, it's pretty much impossible for Basecamp to perfectly match the devices.

...ken...

Yeah, I've had an aviation flight control system engineer friend tell me that Garmin makes great stuff, but as a company they are too compartmentalized.... that some great feature in item X simply isnt available in item Y and vice versa. Both items X and Y being equally great, either hardware or software, and in any segment (consumer, mil, commercial).

But hey, when you are top of the heap, you don't really see a need to improve your operational structure. :D

At the risk of turning this thread into yet another witch hunt against Base Camp:

Actually it is the developer's problem. Where is why.

1) The geocache application GSAK supports a wide number of GPS devices (from multiple manufacturers) yet maintains specific flexibility for a user to customize which icons are compatible or not. If an individual has the foresight to develop his software to the specific needs of the user, it is expected that a developer such as Garmin would have the foresight.

2) Basecamp does not have to be compatible with every GPS out there, but it should know what icons are specific to those in the Garmin line. It is unacceptable that a software developed by Garmin can't filter out icons for Garmin devices. Standardization between manufacturers is one thing (and difficult to control) but, standardization within a single manufacturer model line should be.

The problem isn't with the Basecamp software developers in this case. It's the complete lack of standardization on the device development side of the company. Basecamp developers just try to provide a set of icons that catch most of what's out there. With the complete lack of standards (in more than just this case) on the device development side, it's pretty much impossible for Basecamp to perfectly match the devices.

...ken...

Phizy, I agree with you. I am not a developer, but much of my work involves taking users and operations staff suggestions and turning them into actionable work for developers. Software can solve many problems, if it is made a priority. Elsewhere on this forum, I have suggested several ways of achieving at least SOME way for the user to get a level of compatibility. But it also seems that even if the developers WANTED it, the device people would be unwilling to share the icon images with them.

Yes. Understandable. Garmin should not, and may not have the ability to link correctly with other GPS manufacturers (although GPS Babel seems to) but should be within itself. Herein lies the issue.

By the mere fact that there are 3rd party applications able to handle the cluster of icons provides direct evidence that Garmin is not focused on the customer in terms of its Base Camp application.

BC has a couple of symbols I like which are not supported by my 62s. Thought a nice feature would be that BC symbols could be installed in the device or vice versa. I'm referring to existing symbols here, not custom symbols.

BC has a couple of symbols I like which are not supported by my 62s. Thought a nice feature would be that BC symbols could be installed in the device or vice versa. I'm referring to existing symbols here, not custom symbols.

That truly WOULD be nice! Even if it were a matter of installing them as custom symbols, that would be hella better than what there is now.

2) Basecamp does not have to be compatible with every GPS out there, but it should know what icons are specific to those in the Garmin line. It is unacceptable that a software developed by Garmin can't filter out icons for Garmin devices. Standardization between manufacturers is one thing (and difficult to control) but, standardization within a single manufacturer model line should be.

That's my point. At Garmin there is no standardization of icons and software features even within the Nuvi model line. Even where two Nuvi models have the same or similar software features they may work quite differently. And the differences only get larger as you cross model lines, say from Nuvi to Montana or eTrex or .... etc.

So the Basecamp developers -- and the Mapsource developers before them -- just do the best they can. In the end, some Basecamp icons are not found on some Garmin devices and some Garmin device icons are not found in Basecamp.

I agree with the suggestion that it would be nice if icons that are in Basecamp could be installed on a device that does not have them. But that, first, requires the feature be added to the device before the Basecamp developers would be able to take advantage of it.

Not much point in Basecamp being able to do something that none of the devices know how to do.

...ken...