I was wondering why basecamp always adds a 30 min. stop when ever I make a route or edit a route by adding a waypoint not only to the new waypoint but to all the other waypoints that were there and correct with no stop times? It is annoying that every time I add a waypoint I get a 30 min stop time, then I need to go into max zoom and click on the waypoint list and then move the waypoint slightly to remove the 30 min stop for all the wave points in my list/route. Also it would be nice if the wave points default to be on the road instead of having to do the same "max zoom" step to move them to the road from off of the road, and to be able to add a waypoint between to others without having to move it up the list to where it goes. (recalculate day plays havoc with round trip day rides) I have basecamp set for motorcycles and curvy roads. Or am I doing something wrong?
This is so absolutely annoying!!. While the stop-over time might be a nice feature for car drivers, who tend to let the stat nav do most of the work and are happy following whatever route the software plots, it's a really annoying feature for any motorcycle rider.
This is because our routes tend to be substantially more complicated, we usually have a very good idea of which roads we want to hit and will add waypoints simply to force the route to go where we want it to. As an example, when you have 4 or 5 waypoints that are merely a few kilometres away (like 1-5km) that have been set to force the route through them, and the software adds a 30 minute stop to each of them, your arrival times at the end of the day or to the next waypoint where you really want to stop become completely bogus.
Currently, the only workaround I have found for this issue is to manually edit each of those waypoints, and set the departure time to be the same as the arrival time. This of course creates another issue; if at some point you decide to add say a 1hr stop for lunch before those waypoints, because the departure time has been manually set, when you hit recalculate day they wont be included in the calculation, and instead you'll get a red exclamation mark next to them, kindly letting you know that your departure time cannot be before your arrival time, as it has now shifted 1hr forward due to the stop you added earlier.
The solution is easy, the default stop-over time for waypoints should be configurable.
I have been planning complex motorcycle routes for years using BC and I have never seen this. Is this because I never use Trip Planner? I always create "real" routes, not trips, in part because earlier testing of Trip Planner on various nuvi GPSes produced horrible results and also because I'm already familiar with how to do routes.
I have been planning complex motorcycle routes for years using BC and I have never seen this. Is this because I never use Trip Planner? I always create "real" routes, not trips, in part because earlier testing of Trip Planner on various nuvi GPSes produced horrible results and also because I'm already familiar with how to do routes.
-dan
I believe it is indeed a feature of Trip Planner. I haven't designed "real" routes yet, but I presume they don't have options to specify things like amount of riding hours per day, setting arrive and leave times per waypoint and so on, am I right?.
You are correct that using routes, BC will not calculate arrival and stop times etc. for you. But if this "math atheist" can look at the route info window and do the calculations himself, anybody can. ;-)
Seriously, it is easy. The info window gives you columns showing at each routing direction (not just waypoint), distance and time for that leg, and cumulative distance and time for the ride to that point. If your route turns out to be too much for one day, it is not all that hard to split it into two or more routes, using the total distance or time columns to decide where to make the splits.
Can't you just use "shaping points" instead of Waypoints. The former, of course are not announced while the latter are because they are places one expects to stop.
