Waypoint symbols

1. MapSource and BaseCamp support and interact with a WIDE variety of different GPS unit all of which have different capabilities and functions. Should they all support the same icons? Possibly. But some of these units go WAY, WAY back so they have different symbols.

2. Bad programming? Really I think that because the Favorites are constantly being indexed (based on the location) that it is automatically going to reindex from the the start. But I agree that it is aggravating.

1. Don't care how many different GPS units they make. These symbols exist in a main database somewhere. Why not at least make the waypoint symbols on the unit we are using available in Basecamp? The "pushpin" is a fine example of this not working when common sense would tell us it should.

2. But why not return me to the index for the one I just edited? Not return me to the top of the list again. I'm not moving, I'm sitting still. Location is not changing while I'm editing. So yes it's bad programming.

I had been a computer programmer beginning in 1974 with large mainframes in the USAF and then in the public sector with personal computer software, so I know a little about good & bad programming practices.

yes it's bad programming

Have you tried turning off the GPS antenna? It may then not default from your current location.

Antenna is internal. But even in simulation mode it still does it. Like I said bad programming.

And the thing with the Waypoint symbols is it not only bad programming it is short-sighted on how users would interface the GPS unit with Basecamp.

I honestly don't believe that Garmin software engineers actually use their own products. Either that, they think, that because they understand it, the average user should also understand it.

OR....They just don't give a darn.

KenSny wrote:

I transfer Mapsource waypoints, along with their symbols, to my 1490LMT for each trip. I've never had the problem that you experienced. The symbols display just fine on my unit.
Maybe you are missing a step somewhere.

346786

346814

Like KenSny, I think know a little about design and programming. I spent many years in systems, managing teams of application programmers. Even so, I find myself yelling at my computer when software does not respond as I think it should.

When this happens, I have to take a deep breath and say to myself, what might I have done if I were constructing the design for the software that offends me? Would I have known everything that a user might ever want the software to do 5 or 10 years down the road? Of course, I have to answer myself - No, that is unlikely. Might there be elements in the design that would have the effect of making it difficult to provide some feature in the future? Absolutely! Seen it many times in my career. Should you go back to the design stage and do a fresh design that would incorporate all the features the users want; and then reprogram the entire system and peripheral programs that interact with it?

Well, I don't know what KenSny would say, but starting from scratch was an option taken very seldom because the enormous cost of doing so would have to be borne by someone.

Let me insert a comment which I have often wanted to make when I see posters using words like "crap". Garmin did not force any of these posters to buy a Garmin versus a Magellan or a Tom Tom. The posters are the ones who either did no research or did not do enough research. Would they have been willing to pay an additional, say, $50, if the feature they want was there? If they are so concerned about the "crap", why don't they just say enough and switch to another manufacturer?

Now, if sticking in negative comments is their alternative to posting in the "Chit Chat" thread in order to get in their weekly post, I guess that is one way to do it.

I am almost certain that there does exist at Garmin a complete set of Waypoint Symbols, along with which devices use which "favorite" symbols internally. But does the fact that Garmin knows this automatically mean that software such as Basecamp or Mapsource should be redesigned to recognize which device is currently interacting with the program and then go through a reconciliation of which symbols should be available?

It would be nice if Garmin would add a lot of features (in the instant case symbols) to their software - such as Basecamp - and also change the firmware in all of the devices to take advantage of these features. Of course, Garmin would then be updating the firmware of discontinued models and this cost would have to be passed on to the purchasers of newer models.

I think the better course of action for us is to say - OK, that is the way it is. Don't like it, but there it is.

Then, are there ways that we can accomplish what we are after using the tools that we have?

1. @jgermann: Does your 765 display symbols created in Mapsource?
2. @ Ken: I see that you own a Nuvi 50. Garmin introduced this as a stripped down model. Another thread mentioned that you can not clear out the trip log either. I think buying a cheap model was a bad idea.

OK guys, I get it.
Everything is good in your world.
Thanks for your input.

And as far as "buying a cheap model was a bad idea". I use a GPS to get from point A to Point B. I don't need bluetooth, don't need it to play music, don't need it to view pictures, don't need traffic, etc. Since we all get the same map and updates, and we all can set POI/waypoints I would say that my cheap unit can get me from point A to Point B as good as the unit costing $200+ more. And yes it does not do multi-waypoint routes (Trip Planner), but IMHO that is not worth the extra cost.

And since Basecamp is supposed to be the one piece of software we are all "supposed" to use, it has flaws that need to be fixed. And if Garmin was serious about the user interface between the GPS unit and Basecamp they would get busy. Again IMHO.

You can criticize how my post was worded and take issue with my comments - so be it.

That's it. Finished with this thread. Thanks.

Just created a route in Mapsource with a Waypoint symbol on it. Sent to my 765. Imported the route from file. Previewed the route and the Waypoint symbol did appear.

The "cheap" comment was unwarranted and thus your anger in that regard is justified, however getting upset because other posters do not see the waypoints issue as being as severe as you paint it is not. Garmin is well aware that there are things in BaseCamp that need fixing, but they may not know about this one. You're not likely to read this, but perhaps letting Garmin know your thoughts and how they can fix the problem would work better than bitching on an enthusiast forum.

As if we as end users could fix the problem in the first place.

KenSny,
You asked "why does it do this" and "why doesn't it do that".

No one here can answer the "why". We can't. We don't know "why".

All we can do is tell you "how" it works. And ways to work within that system.

That's it.