3.0.2 Route Behavior Changes?

Former Member
Former Member
In 3.0.2 if I create new route that follows a road for say 20 miles and then the return route follows the same path back, as I am tracing the return route Basecamp is creating several individual waypoints listed in My Collection. This is different than in 3.0.1. Is there something that I can do to prevent this behavior.

Thanks
  • Former Member
    0 Former Member
    From the testing I've done I see the same behavior in BaseCamp 3.0.1.

    When BaseCamp makes stops in the route we try to name them based on other data at that location. When choosing the name we try to bias towards data that a user has created so that your route is named "Home to Work" instead of "123 Main St to 456 First Ave".

    I can see where a route folding back on itself could run into trouble. We'll take a case to look at ways to improve this.

    As an aside can you think of any case where you'd want to create a waypoint with a name based on a route or track underneath where you've clicked on?
  • Former Member
    0 Former Member
    I'm sorry I guess I didn't explain that very well. So here's a picture. I started this out by creating a new route on the right side of the map and then clicking on the far left side of the map. This created a route from the right to the left, now let say that I'd like to follow my return path along the same route, at every point I select along the return path Basecamp adds an individual waypoint on the left (circled portion of the image). 3.0.1 did not seem to have this behavior (or its a option that somehow I've turned on and I'd like to turn off)

    This of course is a over simplified example. Image a map that follows a route thru a city that has multiple turns in it. The "My Collection" folder now has hundreds of these individual waypoints listed in it.


    http://i85.photobucket.com/albums/k75/mwgoff72/Basecamp.jpg

  • Former Member
    0 Former Member
    I'm afraid I didn't explain very well either because we're on the same page :)

    That's the exact behavior I could reproduce in both BC 3.0.1 and 3.0.2. No matter which versions it shows up in this is something we'd like to change for the future.
  • Former Member
    0 Former Member
    That is very strange, On my laptop I have 3.0.1 and it does not exhibit this behavior. However, on my PC with 3.0.2 it does. Is there somewhere that I can download the older 3.0.1 version from?

    Thanks