Problem with Basecamp making routes with existing Waypoints...

I have what I think is a problem with Basecamp when making routes.

I have gone into Basecamp and made a folder called states and in that folder I make a list all the states and put campgrounds in each list.

I make a seperate list called All Routes. I don't need to keep all the routes I make just some that are repeated ever so often.

Now when I make a route I select the All Routes list. Click on the toolbar to make a route. I go to the campgound I am leaving and the one I am going too. Basecamp makes a route.

Now when I look at the route the campground waypoints in the route have a 1 added to the end of the waypoint name. It also makes new waypoints in the list named All Routes of the same name.

This to me is not good. I don't like the duplication, the change of the names of the wayponts and Route.

I have no problem going to Basecamp but this is just causing clutter. If I have a waypoint in a list and make a route that I keep in a seperate list I don't need it to be duplicated.

Falgar, what is your take on this. Can you change this so the list stays where ever I place it and the waypoints stay in the original folder. When I travel from one state to another, ie Texas to Oklahoma I don't want waypoints duplicated and put in some other list.

BC

  • Try this. Create the route in the folder containing the waypoints . Then move the route to where you want it.
  • Try this. Create the route in the folder containing the waypoints . Then move the route to where you want it.


    That would work as long as I stay in Texas, what happens when I go from a campground in one state to another campground in a different state.

    Now I am not trying to be difficult and beat up Basecamp. I am trying to learn how to use it in a way that works for me. Maybe someone else has a similar problem.

    I see no logical reason the waypoints have to be duplicated, name changed, and stay an any list in the database. As said before they all are in My Collection but being viewed in a different way. I do understand not having duplicate names (like Home or whatever) but it is all in one database they should be able to be used from anywhere.

    Still looking for a possible answer or solution..

    BC
  • Former Member
    0 Former Member
    I also have a list for each state that has my camping and places in each state that I might want to visit...

    When I start my trip planning, I go to each state list, right click and send each place I want to travel to my "Trip Planning" folder list. This makes a copy in my Trip Planning list.

    I then use control "A" to select all waypoints in the list then right click and select create route from selected waypoints... I then delete all wayspoints from the Trip Planning folder list...

    I select the new route and start arranging the waypoints in the sequence I want to visit...
  • As Hardwire posts, the trick is to assemble your waypoints in a list and then create the routes.
  • Former Member
    0 Former Member
    I have found it easier to create the route in "My Collection" where you have access to all waypoints. When you send the route to a list it automatically creates references in the list for all the waypoints that were used.

    Alternatively you can create the route in a list of waypoints and then send that route to another list. Again, references (or pointers) are created in the second list to all the waypoints that are used.

    Once you get your head around that lists only contain bookmarks, or pointers, or references to the items in My Collection, then things get easier. Think of a list in the same way as the desktop on your PC. It generally only contains shortcuts to programs that are stored elsewhere on your disk. You can have as many shortcuts as you like to a particular program, but they all refer to just one item.

    Basecamp requires that each data item has a unique name. Hence, when duplicates are made they need to have a different name to the original, even if references appear in different lists or folders.
  • I just tried what you described (creating route in new list from waypoints in different lists) with v4.1.2 and I get slightly different results. I get a new route with 1 appended to the waypoint names in the route properties, but new waypoints are not created – either in the list or in My Collections.

    The route that is created has inserted the waypoints as via points. If I send the waypoints to the new list and then make a route, the waypoints are inserted as waypoints and I do not get the 1 appendage. This difference is probably why the 1 has been added – it tells the user a waypoint has been used as a via point in the route.

    The choice of waypoints or via point makes a difference in how Garmin packages routes when exporting or sending to a device. Routes created with waypoints will contain the route and the waypoints. Routes created with via points will only contain the route.

    Whether this is by design or not I do not know. Perhaps FALAGAR can comment.
  • You get a 1 appended because you're not doing what I suggested. You need to make sure the waypoints are in the same list as the route you're creating. If you do that you won't get the 1 appended as BC is not creating new waypoints.
  • You get a 1 appended because you're not doing what I suggested. You need to make sure the waypoints are in the same list as the route you're creating. If you do that you won't get the 1 appended as BC is not creating new waypoints.


    I do not get a new waypoint by either method. I was not trying give a suggestion to the OP on how to make a route that will avoid the "1", you and others have already done a fine job of this.

    I am pointing out that the waypoint is inserted into the route differently (a via point vs. a waypoint) and how it will affect the exported/sent route. Whether this is by design or not, I do not know.
  • Apologies ... Misread your post. But it is why you get the 1 appended to your via points.
  • You need to make sure the waypoints are in the same list as the route you're creating. If you do that you won't get the 1 appended as BC is not creating new waypoints.


    I get a new route with 1 appended to the waypoint names in the route properties, but new waypoints are not created – either in the list or in My Collections.
    The route that is created has inserted the waypoints as via points. If I send the waypoints to the new list and then make a route, the waypoints are inserted as waypoints and I do not get the 1 appendage. This difference is probably why the 1 has been added – it tells the user a waypoint has been used as a via point in the route.
    FALAGAR can comment.


    Great post SUSSAMB. I tried sending the waypoints I want to us to start and end a route to my All Routes List. Then went into the list, selected the waypoints and made a route with them. When the route was completed I deleted the waypoints from the All Routes list. Worked great.

    I also had BC add a 1 to the waypoints in the route. I found if I inserted the actual waypoint and deleed the one with the added 1 it worked fine once done.

    Also something else I found out. If I make a route in the All Routes list and then want to add another waypoint I can't click on the + symbol and navigate to the proper list other than the one it is in. But using the method you suggested I can send the waypoint to the list the route is in and then insert it into the route. It would be nice to be able to move to other lists to select a waypoint. You fixed my problem but we are not able to use methods of using programs as we have over the years.

    Thanks for your ideas.

    BC