[BaseCamp] Breaking up a route

Tue Apr 14 14:47:37 PDT 2015

On my Mac, I can "hover" over any point along a route (there doesn't need to be a waypoint there) and a little box pops up that tells me what time I'll be at that point.
Isn't that what you're looking for?

John Z
Molino, FL
Sent from my iPad

> On Apr 14, 2015, at 2:16 PM, Tim Bowman <tk.bowman at comcast.net> wrote:
> 
> I just went into BC and used one of my recent routes to refresh my memory
> about routing and timing of waypoints.
> 
> To use this feature, one needs to set up at a minimum the Beginning waypoint
> with a departure time.  The remaining waypoints will then have an arrival
> time computed based upon your BC preferences and it's knowledge of roadway
> speeds.  If you want to add layover times to a given Waypoint, BC will then
> recalculate the subsequent Waypoints' arrival times.
> 
> If you click on a Waypoint in your route on the map, it will display the
> arrival and departure times.  But as I described above, it's far easier for
> me to evaluate my route with the list of waypoints and the arrival/departure
> times listed.
> 
> HTH,
> 
> Tim
> 
> 
> -----Original Message-----
> From: Basecamp [mailto:basecamp-bounces at micapeak.com] On Behalf Of Maura
> Sent: Tuesday, April 14, 2015 11:22 AM
> To: BaseCamp
> Subject: Re: [BaseCamp] Breaking up a route
> 
> I do not have BaseCamp available to me at the moment to test and tell you
> exactly how, but BC allows you to set the start time of a route, or the
> finish time, or add stopovers. You can use this to achieve what you are
> talking about in S and T. Not the same, I know, BC better IMHO for my
> purposes, YMMV.  Open the route and it is in there. On long routes with no
> turns , does it kill you to just add a one click waypoint at the approximate
> location :)?  Maybe some one who has BC open can chime in and explain how
> you can get info at any point in the route with the mouse. I forget.
> 
> Sorry for such a low-content churlish post. Suffering withdrawal cuz I can't
> play with BC.
> 
> Maura
> in
> Vancouver, Canada
> 
> On Tue, Apr 14, 2015 at 10:54 AM, Jerry White <jerrywhite518 at gmail.com>
> wrote:
> 
>> I liked that functionality in S&T, and wish BC had it. I do what you 
>> do, SWAG it based on the route directions, the measuring tool, and 
>> trial and error. You might want to try using a proximity circle, 
>> though I don't know if it lets you set it to 1000 miles. :)
>> 
>> Jerry
>> 
>> On Tue, Apr 14, 2015 at 10:37 AM, Greg Horodeck <greghoro at gmail.com>
>> wrote:
>> 
>>> Not sure if I used the proper term in the subject. Looking for a 
>>> better solution to a problem I have than the one(s) I am using.
>>> 
>>> 
>>> 
>>> On a long route, say from Chicago to Albuquerque, I want to break it 
>>> into three rather equal daily segments. Either by mileage or by 
>>> time. Since
>> most
>>> of my travel will  be  on Interstate, either time or mileage based 
>>> should be relatively synonymous.
>>> 
>>> 
>>> 
>>> While it is very simple to plan the route to determine the total 
>>> mileage/time and divide by the number of segments, the problem I'm 
>>> having is determining just where on the route the segment break 
>>> point(s) are.
>>> 
>>> 
>>> 
>>> I've looked at the Route Directions, which can help to SWAG an
>> approximate
>>> location. However, on long stretches where the road does not change,  
>>> I still end up with a bit of trial and error. Using the Measure tool 
>>> is
>> also
>>> helpful, more so on a relatively straight route.
>>> 
>>> 
>>> 
>>> Another technique I've used is time based, using Streets & Trips. 
>>> One can specify the number of hours one drives per day in planning 
>>> the route and let S&T show where the stopover is.  Divide the total 
>>> route travel time by
>> the
>>> number of desired segments  to determine the daily driving time.  I 
>>> am
>> not
>>> aware of an analog to this within BaseCamp. Other problems with this 
>>> technique is that BaseCamp and S&T have different routing algorithms.
>> While
>>> using two different software solutions adds complexity to the 
>>> solution,
>> it
>>> is not a deal breaker.
>>> 
>>> 
>>> 
>>> I can see this being useful for planning a long point to point ride 
>>> such
>> as
>>> a Four Corners or Ultimate Coast to Coast. Or even figuring out 
>>> potential gas stops for a Certification ride based on fuel range.
>>> 
>>> 
>>> 
>>> Thoughts?
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Greg
>>> 
>>> 
>>> To make _ANY_ changes, including unsubscribing from this list, click
>> ----->
>>> http://micapeak.com/mailman/listinfo/basecamp
>> 
>> To make _ANY_ changes, including unsubscribing from this list, click 
>> -----> http://micapeak.com/mailman/listinfo/basecamp
> 
> To make _ANY_ changes, including unsubscribing from this list, click
> ----->http://micapeak.com/mailman/listinfo/basecamp
> 
> 
> To make _ANY_ changes, including unsubscribing from this list, click ----->http://micapeak.com/mailman/listinfo/basecamp
> 