From kwthom at yahoo.com  Mon Jul  9 19:42:20 2018
From: kwthom at yahoo.com (Ken Thompson)
Date: Tue, 10 Jul 2018 02:42:20 +0000 (UTC)
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
Message-ID: <1042053213.1461874.1531190540181@mail.yahoo.com>

Playing with a multi-day route, I've created a single large route that spans multiple timezones.

In mucking about in the properties/Route Directions, etc. screen for a route, you can add in a 'layover' time that computes, well, non-traveling time during a journey.

I'm fairly certain that BC does *not* have a clue about time zones, and that's going to be a function of the GPS (which obviously does handle those changes well)

So, BC computes I'm arriving at 8pm, it's really 9pm, since I crossed a time zone line to my east.

True?

Thanks!

--Ken

From ldrider at imagesdesavions.com  Mon Jul  9 20:10:05 2018
From: ldrider at imagesdesavions.com (Stephen!)
Date: Mon, 09 Jul 2018 22:10:05 -0500
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <1042053213.1461874.1531190540181@mail.yahoo.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
Message-ID: <5D891578-2B78-43EC-AB29-D74EF2AD5A15@imagesdesavions.com>



>So, BC computes I'm arriving at 8pm, it's really 9pm, since I crossed a
>time zone line to my east.

In my experience, that is correct.


-- 
There is no need to tailgate me when I am doing 50 in a 35...  and those flashing lights on top of your car look ridiculous.

From armour783 at gmail.com  Tue Jul 17 04:02:45 2018
From: armour783 at gmail.com (Rick Armour)
Date: Tue, 17 Jul 2018 07:02:45 -0400
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <1042053213.1461874.1531190540181@mail.yahoo.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
Message-ID: <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>

Correct Basecamp does not compute time zones. Ask me how I found out...

- Rick Armour

> On Jul 9, 2018, at 10:42 PM, Ken Thompson <kwthom at yahoo.com> wrote:
> 
> Playing with a multi-day route, I've created a single large route that spans multiple timezones.
> 
> In mucking about in the properties/Route Directions, etc. screen for a route, you can add in a 'layover' time that computes, well, non-traveling time during a journey.
> 
> I'm fairly certain that BC does *not* have a clue about time zones, and that's going to be a function of the GPS (which obviously does handle those changes well)
> 
> So, BC computes I'm arriving at 8pm, it's really 9pm, since I crossed a time zone line to my east.
> 
> True?
> 
> Thanks!
> 
> --Ken
> 
> To make _ANY_ changes, including unsubscribing from this list, click ----->http://micapeak.com/mailman/listinfo/basecamp
> 

From becca37 at puckrat.com  Tue Jul 17 04:32:12 2018
From: becca37 at puckrat.com (Rebecca Rasmussen)
Date: Tue, 17 Jul 2018 05:32:12 -0600
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
Message-ID: <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>

And, conversely, at least on my RoadTech Zumo 660 and 665, the layover times that Basecamp *does* calculate *do not* carry over to the GPS unit. Very frustrating for me to have them flip and flop what they do and do not calculate for me. 
On 7/17/2018 5:02:55 AM, Rick Armour <armour783 at gmail.com> wrote:
Correct Basecamp does not compute time zones. Ask me how I found out...

- Rick Armour

> On Jul 9, 2018, at 10:42 PM, Ken Thompson wrote:
>
> Playing with a multi-day route, I've created a single large route that spans multiple timezones.
>
> In mucking about in the properties/Route Directions, etc. screen for a route, you can add in a 'layover' time that computes, well, non-traveling time during a journey.
>
> I'm fairly certain that BC does *not* have a clue about time zones, and that's going to be a function of the GPS (which obviously does handle those changes well)
>
> So, BC computes I'm arriving at 8pm, it's really 9pm, since I crossed a time zone line to my east.
>
> True?
>
> Thanks!
>
> --Ken
>
> 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


From denniscodell at icloud.com  Tue Jul 17 06:04:13 2018
From: denniscodell at icloud.com (DENNIS O'DELL)
Date: Tue, 17 Jul 2018 15:04:13 +0200
Subject: [BaseCamp] Follow up regarding the BMW Navigator VI
Message-ID: <AD9E079A-966D-4376-8226-A6EB4B70935B@icloud.com>

A while back I believe I asked the question about screen brightness of the Navigator VI. I asked shortly after the Nav VI was released. So, now that some time has passed I am hoping there are more folks with more experience using the Nav VI.

How is the screen brightness in bright daylight as compared to the Nav IV and V? 

Any off putting characteristics or funny behavior?

I’m feed up with the dim and hazy screen brightness of the earlier versions, but hate to throw good money after bad if there isn’t a real improvement overall.

Thanks

Mit freundlichen Grüßen/With best regards,

Dennis C. O'Dell
denniscodell at icloud.com
Mobile: +49 (175) 855 6663
Home: +49 911 277 45370
Skype: diggertfu
Hochstrasse 19
Nürnberg 90429
Germany
 
"Laughter and Tears are both responses to frustration and exhaustion. I myself prefer to Laugh since there is less to do afterwards."
- Kurt Vonnegut

From ldrider at imagesdesavions.com  Tue Jul 17 08:07:06 2018
From: ldrider at imagesdesavions.com (Stephen!)
Date: Tue, 17 Jul 2018 10:07:06 -0500
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
Message-ID: <1824AB1F-98E2-45DB-B015-65A9C89EE8ED@imagesdesavions.com>



>Correct Basecamp does not compute time zones. Ask me how I found out...

Sounds like a sad story...


-- 
There is no need to tailgate me when I am doing 50 in a 35...  and those flashing lights on top of your car look ridiculous.

From kwthom at yahoo.com  Tue Jul 17 08:14:12 2018
From: kwthom at yahoo.com (Ken Thompson)
Date: Tue, 17 Jul 2018 15:14:12 +0000 (UTC)
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
Message-ID: <1863432426.5421353.1531840452981@mail.yahoo.com>

 Rick - Oooh...naah, I'll pass.  I don't need a scary story at this time of day.  Perhaps best to say I'm trying to learn from others and their omissions....   :)
 Rebecca - This seems to be more of a function for planning purposes.  The fact the GPS doesn't use this data may not be a bad thing.  If your 10 minute planned stop turns into an 8 minute stop, you just happen to be 2 minutes ahead at this stage of the trip...


Again, thanks for the confirmation!

--Ken

    On Tuesday, July 17, 2018, 4:32:19 AM MST, Rebecca Rasmussen <becca37 at puckrat.com> wrote:  
 
 And, conversely, at least on my RoadTech Zumo 660 and 665, the layover times that Basecamp *does* calculate *do not* carry over to the GPS unit. Very frustrating for me to have them flip and flop what they do and do not calculate for me. 
On 7/17/2018 5:02:55 AM, Rick Armour <armour783 at gmail.com> wrote:
Correct Basecamp does not compute time zones. Ask me how I found out...

- Rick Armour

> On Jul 9, 2018, at 10:42 PM, Ken Thompson wrote:
>
> Playing with a multi-day route, I've created a single large route that spans multiple timezones.
>
> In mucking about in the properties/Route Directions, etc. screen for a route, you can add in a 'layover' time that computes, well, non-traveling time during a journey.
>
> I'm fairly certain that BC does *not* have a clue about time zones, and that's going to be a function of the GPS (which obviously does handle those changes well)
>
> So, BC computes I'm arriving at 8pm, it's really 9pm, since I crossed a time zone line to my east.
>
> True?
>
> Thanks!
>
> --Ken
>
  

From jerrywhite518 at gmail.com  Tue Jul 17 08:46:37 2018
From: jerrywhite518 at gmail.com (Jerry White)
Date: Tue, 17 Jul 2018 08:46:37 -0700
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
Message-ID: <CAN_EBzrDybxjmFG1Ooakxi02uLuZDDYVKiZ9LN0cSbWksz4u1Q@mail.gmail.com>

I found out that the Nuvi 2797 keeps the layover times from Basecamp, but
the Zumo 550 doesn't. Fun having two vastly different ETAs on the same
route, side by side.

Jerry

On Tue, Jul 17, 2018 at 4:32 AM Rebecca Rasmussen <becca37 at puckrat.com>
wrote:

> And, conversely, at least on my RoadTech Zumo 660 and 665, the layover
> times that Basecamp *does* calculate *do not* carry over to the GPS unit.
> Very frustrating for me to have them flip and flop what they do and do not
> calculate for me.
> On 7/17/2018 5:02:55 AM, Rick Armour <armour783 at gmail.com> wrote:
> Correct Basecamp does not compute time zones. Ask me how I found out...
>
> - Rick Armour
>
> > On Jul 9, 2018, at 10:42 PM, Ken Thompson wrote:
> >
> > Playing with a multi-day route, I've created a single large route that
> spans multiple timezones.
> >
> > In mucking about in the properties/Route Directions, etc. screen for a
> route, you can add in a 'layover' time that computes, well, non-traveling
> time during a journey.
> >
> > I'm fairly certain that BC does *not* have a clue about time zones, and
> that's going to be a function of the GPS (which obviously does handle those
> changes well)
> >
> > So, BC computes I'm arriving at 8pm, it's really 9pm, since I crossed a
> time zone line to my east.
> >
> > True?
> >
> > Thanks!
> >
> > --Ken
> >
> > 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
>
>

From becca37 at puckrat.com  Tue Jul 17 10:11:36 2018
From: becca37 at puckrat.com (Rebecca Rasmussen)
Date: Tue, 17 Jul 2018 11:11:36 -0600
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <1863432426.5421353.1531840452981@mail.yahoo.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
 <1863432426.5421353.1531840452981@mail.yahoo.com>
Message-ID: <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>

Ken .. " If your 10 minute planned stop turns into an 8 minute stop, you just happen to be 2 minutes ahead at this stage of the trip..." ... hehheh yes and no. At that point I might well be 2 minutes ahead of whatever overall ETA Basecamp had told me when it was accounting for layovers, but now I'd be 8 minutes BEHIND what my particular GPS thinks my ETA should be. And since my GPS ETA is the one I see for, say,1,000 miles on the motorcycle during an Iron Butt Saddle Sore, with each and every stop I get further and further "behind" schedule. Then have to mentally kick myself and remind myself that it will all work out fine because I accounted for all that during planning in Basecamp. :P 

From kwthom at yahoo.com  Tue Jul 17 11:02:02 2018
From: kwthom at yahoo.com (Ken Thompson)
Date: Tue, 17 Jul 2018 18:02:02 +0000 (UTC)
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
 <1863432426.5421353.1531840452981@mail.yahoo.com>
 <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>
Message-ID: <1902439247.5545143.1531850522216@mail.yahoo.com>

 Right-o!

"Plan the Ride, then Ride the Plan!"

Understand completely!

--Ken
    On Tuesday, July 17, 2018, 10:11:48 AM MST, Rebecca Rasmussen <becca37 at puckrat.com> wrote:  
 <...snip!>
 > Then have to mentally kick myself and remind myself that it will all work out fine because I accounted for all that during planning in Basecamp. :P 




  

From crasmussen at carolina.rr.com  Tue Jul 17 14:54:28 2018
From: crasmussen at carolina.rr.com (Chris Rasmussen)
Date: Tue, 17 Jul 2018 17:54:28 -0400
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
 <1863432426.5421353.1531840452981@mail.yahoo.com>
 <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>
Message-ID: <011b01d41e18$be0eb3f0$3a2c1bd0$@carolina.rr.com>

This is why I keep a separate list of arrival/departure times and route point to point  Really only important during rallying.  If your just going somewhere your either gonna be early or late,  Doesn't really matter so long as you get there.  If you have a deadline, the ETA will show you if you have time to stop.  ETA says 10:00am and you don't need to be there until 11:00 you have some time to kill.  If it says ETA 11:00 and you are supposed to be there at 10:00 you best not dilly dally and once in motion, twist the wrist.  

For Rallies, a SECOND GPS set to the Checkpoint lets you know if your early or late.

M2C, YMMV.

Ride Smart(ly)
Chris
crasmussen at carolina.rr.com
IBA 60711
I travel not to go anywhere, but to go. I travel for travel's sake. The great affair is to move. 
                                                                                                               Robert Louis Stevenson




-----Original Message-----
From: Basecamp <basecamp-bounces at lists.micapeak.com> On Behalf Of Rebecca Rasmussen
Sent: Tuesday, July 17, 2018 1:12 PM
To: basecamp at lists.micapeak.com
Subject: Re: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)

Ken .. " If your 10 minute planned stop turns into an 8 minute stop, you just happen to be 2 minutes ahead at this stage of the trip..." ... hehheh yes and no. At that point I might well be 2 minutes ahead of whatever overall ETA Basecamp had told me when it was accounting for layovers, but now I'd be 8 minutes BEHIND what my particular GPS thinks my ETA should be. And since my GPS ETA is the one I see for, say,1,000 miles on the motorcycle during an Iron Butt Saddle Sore, with each and every stop I get further and further "behind" schedule. Then have to mentally kick myself and remind myself that it will all work out fine because I accounted for all that during planning in Basecamp. :P 

To make _ANY_ changes, including unsubscribing from this list, click ----->http://micapeak.com/mailman/listinfo/basecamp



From moteramaura at gmail.com  Wed Jul 18 07:19:09 2018
From: moteramaura at gmail.com (Maura)
Date: Wed, 18 Jul 2018 09:19:09 -0500
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <011b01d41e18$be0eb3f0$3a2c1bd0$@carolina.rr.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
 <1863432426.5421353.1531840452981@mail.yahoo.com>
 <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>
 <011b01d41e18$be0eb3f0$3a2c1bd0$@carolina.rr.com>
Message-ID: <CAP-_d7_XsQ9UGgiFt4BF=vAHFY_yRL2x=v3317XJeXcbDM1Qjw@mail.gmail.com>

Basecamp is a route planning program. It does not have the same function as
the GPS device.
For route planning, the hours of travel is important. Is this route 18
hours or riding or 19? Makes a difference. Basecamp is also tied in your
computer to your computer clock.IF it is set to your home time zone , then
your basecamp arrival time will be off if you are in another time zone.

Basecamp does not distort the travel time by switching time zones. This is
a good thing.

In my zumo, the time zone switches from the initial input. So if you are
going on a one hour trip over a time zone, it can show it taking like 2
minutes to go 70 miles. Not good for time/fatigue management.
In my Montana, the time zone switch does not occur until you cross over
into the time zone itself. So the two units are often out of sync by an
hour. Older 376c and 478s do not make time zone adjustments.

You need to understand how your particular unit handles time zones. It is
easy to make a critical error that can leave you an hour late if you rely
on GPS time zone switch .

Hope this helps

Maura

On Tue, Jul 17, 2018 at 4:54 PM Chris Rasmussen <crasmussen at carolina.rr.com>
wrote:

> This is why I keep a separate list of arrival/departure times and route
> point to point  Really only important during rallying.  If your just going
> somewhere your either gonna be early or late,  Doesn't really matter so
> long as you get there.  If you have a deadline, the ETA will show you if
> you have time to stop.  ETA says 10:00am and you don't need to be there
> until 11:00 you have some time to kill.  If it says ETA 11:00 and you are
> supposed to be there at 10:00 you best not dilly dally and once in motion,
> twist the wrist.
>
> For Rallies, a SECOND GPS set to the Checkpoint lets you know if your
> early or late.
>
> M2C, YMMV.
>
> Ride Smart(ly)
> Chris
> crasmussen at carolina.rr.com
> IBA 60711
> I travel not to go anywhere, but to go. I travel for travel's sake. The
> great affair is to move.
>
>                                      Robert Louis Stevenson
>
>
>
>
> -----Original Message-----
> From: Basecamp <basecamp-bounces at lists.micapeak.com> On Behalf Of Rebecca
> Rasmussen
> Sent: Tuesday, July 17, 2018 1:12 PM
> To: basecamp at lists.micapeak.com
> Subject: Re: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
>
> Ken .. " If your 10 minute planned stop turns into an 8 minute stop, you
> just happen to be 2 minutes ahead at this stage of the trip..." ... hehheh
> yes and no. At that point I might well be 2 minutes ahead of whatever
> overall ETA Basecamp had told me when it was accounting for layovers, but
> now I'd be 8 minutes BEHIND what my particular GPS thinks my ETA should be.
> And since my GPS ETA is the one I see for, say,1,000 miles on the
> motorcycle during an Iron Butt Saddle Sore, with each and every stop I get
> further and further "behind" schedule. Then have to mentally kick myself
> and remind myself that it will all work out fine because I accounted for
> all that during planning in Basecamp. :P
>
> 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
>
>

From ldrider at imagesdesavions.com  Wed Jul 18 08:03:52 2018
From: ldrider at imagesdesavions.com (Stephen!)
Date: Wed, 18 Jul 2018 10:03:52 -0500
Subject: [BaseCamp] Verify My Sanity (BC Feature Confirmation...)
In-Reply-To: <CAP-_d7_XsQ9UGgiFt4BF=vAHFY_yRL2x=v3317XJeXcbDM1Qjw@mail.gmail.com>
References: <1042053213.1461874.1531190540181.ref@mail.yahoo.com>
 <1042053213.1461874.1531190540181@mail.yahoo.com>
 <F911D22E-E741-43AF-A862-FD28A0928CCE@gmail.com>
 <3019f357-e084-4dc6-b37a-47b39694ee61@getmailbird.com>
 <1863432426.5421353.1531840452981@mail.yahoo.com>
 <e29c638c-33a0-4dbb-aa22-be25547ec44d@getmailbird.com>
 <011b01d41e18$be0eb3f0$3a2c1bd0$@carolina.rr.com>
 <CAP-_d7_XsQ9UGgiFt4BF=vAHFY_yRL2x=v3317XJeXcbDM1Qjw@mail.gmail.com>
Message-ID: <49196A99-060E-499F-8A12-8BC0857D1F27@imagesdesavions.com>



>In my Montana, the time zone switch does not occur until you cross over
>into the time zone itself. So the two units are often out of sync by an
>hour. Older 376c and 478s do not make time zone adjustments.

Having used either a 376c or a 478 for long distance or rally riding since 2006 (and a GPS II+ before that) I simply convert ALL time restrictions to Rally HQ time before I even start planning.  I run the entire ride based on Rally Time and ignore time zones.  It takes a little more work on the front end during planning but makes the ride a lot easier and less stressful.


-- 
There is no need to tailgate me when I am doing 50 in a 35...  and those flashing lights on top of your car look ridiculous.

From carrollwalker at cox.net  Sat Jul 28 07:05:56 2018
From: carrollwalker at cox.net (Carroll Walker)
Date: Sat, 28 Jul 2018 07:05:56 -0700 (PDT)
Subject: [BaseCamp] Explain RENDERING as it is used in BaseCamp Options
Message-ID: <2092806510.4862.1532786756549@myemail.cox.net>

I have an idea what this BaseCamp option is but I'm not sure.  If anyone can enlighten me,  I would very much appreciate it.

Thanks very much in advance

Carroll Walker