Avoid duplicate waypoints

Hello,

I recently replaced my old Quest with a Zumo 350. This means also moving from Mapsource to Basecamp.

When I started creating a route in Mapsource, the first thing I did was add my home waypoint (starting point) to the Mapsource file and then started creating the route. When I then send the route to the Quest, the home waypoint still existed only once in the Quest, even if I send this multiple times, for multiple routes.

Now when I do this in Basecamp, the Home waypoint (or in fact any waypoint which is used in multiple downloaded routes) is duplicated in the Zumo (home1, home2 ,....).

How can I avoid this?

0 BTLAAKE over 11 years ago

My experience is that Garmin has made an effort over the last couple of years to get some form of synchronization between BaseCamp and devices. Unfortunately, the degree of success seems to vary from device to device.

If a solution has been implemented on your device, you will need to download the user data (waypoints, routes and tracks) to BaseCamp (do it to an empty list). Delete all the user data on the device and verify that it is gone. Make sure you have the latest firmware install on your device. Correct any problems on the download list in BaseCamp and then send it back to the device.

If you still have problems, complain to Garmin support for your device. Repeat with each firmware update and use the drag and drop solution if it works for your device between updates.

0 Fireblader666 over 11 years ago

Hmm, just tried the drag & drop method, but this gave the same result. Waypoint is being duplicated.

0 Fireblader666 over 11 years ago

Well it's unclear whether what you're describing is a bug or a feature. What other 'bugs' have you found? I've been using Basecamp for years and generally it's bug free although the odd one slips through.

Some other bugs or features:
- the toolbar arrangement gets lost when resizing the window to a smaller width then then the toolbars.
- extending a route with the insert tool doesn't always work. Sometime the black circle does not appear near the last via point. Deleting this last point seems to be the only solution.
- the name of a via point needs to be unique in the entire database. Why?
- help information seems to incorrect. Check out the preference help. Seems to be about another version.
- the are no via points in a route when using the create route from track option. The result is that this route can not be edited.

0 Former Member over 11 years ago

I will try to answer some of your questions.

- the toolbar arrangement gets lost when resizing the window to a smaller width then then the toolbars.

This is something we are aware of. Do you happen to have a Windows 8 machine? Or are you on Windows 7?

- extending a route with the insert tool doesn't always work. Sometime the black circle does not appear near the last via point. Deleting this last point seems to be the only solution.

I will try to reproduce this. We have some new route tools behavior but I have not seen this issue specifically. We have changed things such that if you have the "hand" tool selected, we now allow users to modify data by holding down the "ALT" key. Try this and let me know if this works for you.

- the name of a via point needs to be unique in the entire database. Why?

It is a database based application, and the names are the identifier for different types of data.

- help information seems to incorrect. Check out the preference help. Seems to be about another version.

We are working on updated help. The help is not too far off from the current version, but we are in the process of updating our help. This Forum is always the latest and greatest.

- the are no via points in a route when using the create route from track option. The result is that this route can not be edited.

Can you give me more information on this? The track to route feature takes the start point and end point of a track, and attempts to calculate a route based on that data, if it is a driving-type route. You will get a start point via, and an end point via for each of these. Inserting in between or editing this will throw up a warning that tells you that because the route was created from a track, you are altering that "shape." This is expected. Can you elaborate for me a little more about what it is you are seeing?

Thanks for all of the feedback. This is always very helpful to us in continuing to improve BaseCamp.

0 Fireblader666 over 11 years ago

I will try to answer some of your questions.

This is something we are aware of. Do you happen to have a Windows 8 machine? Or are you on Windows 7?

I'm using Windows7.

I will try to reproduce this. We have some new route tools behavior but I have not seen this issue specifically. We have changed things such that if you have the "hand" tool selected, we now allow users to modify data by holding down the "ALT" key. Try this and let me know if this works for you.

The 'ALT' key function has it's own problems. This works fine for small adjustments. But when you have to add several via points to the route, this method
often fails.
This is what sometimes happens: Say you have two via points, called A and B, and in between these points you have to add extra points to get the requested route.
When pressing 'ATL' the first extra point is correctly added between A and B, let's call this point AA (via points are then A - AA - B).
If you then have to add another extra point between AA and B to get the desired route, Basecamp incorrectly places this second extra point again between A and B messing up the route.
The only way to really get the desired route is use the insert tool.

It is a database based application, and the names are the identifier for different types of data.

I understand this, but the route name is allready a unique key in the database, so I don't see why a shaping point in a route also needs to be (again) unique in
the entire database. This way it's not possible to call the last via point always 'END' for example.
Not a big problem, but I don't understand why this is developed this way.

We are working on updated help. The help is not too far off from the current version, but we are in the process of updating our help. This Forum is always the latest and greatest.

OK.

Can you give me more information on this? The track to route feature takes the start point and end point of a track, and attempts to calculate a route based on that data, if it is a driving-type route. You will get a start point via, and an end point via for each of these. Inserting in between or editing this will throw up a warning that tells you that because the route was created from a track, you are altering that "shape." This is expected. Can you elaborate for me a little more about what it is you are seeing?

When I create a route from a track, using the motorcycle profile, the result is indeed 2 waypoint (start and end) and a route between these two waypoints.
When double clicking the route you see it has no other via points.
When zooming in, it's clear the route is not usable yet. But like you mentioned it is not possible to edit this route, because then the 'shape' is lost and
the result is useless.
This problem basicaly renders this function useless.

Thanks for all of the feedback. This is always very helpful to us in continuing to improve BaseCamp.

No problem. Any solution to the main problem I started this topic for (duplicate waypoints when downloading routes to my Zumo)?