Time Zone Changes

Not sure what you're asking.

GPS units will change timezones as you cross timezones so if you create a route in BC and send it to your device then yes the time will automatically change.

I don't know about BC (don't use it to make routes) but MapSource (old PC software) only shows the (estimated) elapsed time of routes so timezones are irrelevant.

Yes, it does. I created a short, 14 min. route from somewhere in Spain to somewhere in Portugal (they have different time zones), and BaseCamp shows a departure time of 16:36 and an arrival time of 15:50.

No. Time zones have no affect on the amount of time it takes to travel a route.

Correct.

If you want your arrival times to match the time for the zone you are in you will have to correct the zone setting on your gps and reset your watch.

The question was whether BaseCamp takes time zones into account or not, and it does.

Everything the gps does is based on GCT Time Zone 0.

Incorrect. It is based on UTC. This is neccessarily not the same as Time Zone 0, because that zone is UTC+1 in the summer because of daylight saving time (not everywhere though)

Correct.

The question was whether BaseCamp takes time zones into account or not, and it does.

Incorrect. It is based on UTC. This is neccessarily not the same as Time Zone 0, because that zone is UTC+1 in the summer because of daylight saving time (not everywhere though)

Even if BaseCamp adjusts arrival times for different time zones....so what?
Do you keep changing your watch every time you cross a time zone in the middle of a ride?
When you load that route into a gps does it adjust arrival times for different time zones?
None of mine do but they are old so maybe new ones do.

GCT was the wrong acronym but time zone 0 = UTC is correct. I had half of it correct :).
GCT Greenwich Civil Time is what we used to use for astronomy with an ephemeris. Now called ephemeris time which is within a few seconds of UTC.

I repeat....GPS units do not adjust their recorded data for time zones or daylight savings time. Everything is recorded in time zone 0=UTC. Open up any FIT(with the Fit File Repair Tool) TCX GPX track in notepad and look at the date and time. Then open that track in BaseCamp and look at the date and time. You will see that BaseCamp, MapSource, Connect, TrainingCenter, have all started with 0=UTC and applied the time zone and DLST per whatever the computer time settings are.

None of mine do but they are old so maybe new ones do.

I know my 1490T does because it did it on a long trip some years ago. It took me a while to figure out that the ETA was for the destination timezone (-1 hour from where I started). Also the unit time changed when I crossed the timezone. In fact that happened almost exactly on the border.

Now my 76CSx probably doesn't do that (don't recall ever crossing a timezone with it) and I don't know if my Oregon 450 does (probably).

Now as I said in my first reply I don't use BC for routes. I think the PC version of BC shows elapsed time just like MapSource but I could be wrong. PC/Mac software would need to know the start time to calculate an ETA (with/without timezone or DST changes).

Even if BaseCamp adjusts arrival times for different time zones....so what?

Well, that was what the topic starter wanted to know...

Do you keep changing your watch every time you cross a time zone in the middle of a ride?

The clock on most GPSses does (when the time zone is set to automatic); my watch does that too (it's a fenix).

GCT was the wrong acronym but time zone 0 = UTC is correct. I had half of it correct :).

I know that the GPS stores the time stamps in UTC. What I meant is that UTC is not a time zone; it's just "Coordinated Universal Time". Time zones are offsets from UTC. In certain places the offset is 0, depending on what individual countries see fit (there is no real relation with the longitude; only at sea outside territorial waters), and on the time of year.

Now my 76CSx probably doesn't do that (don't recall ever crossing a timezone with it) and I don't know if my Oregon 450 does (probably).

Your 76CSx doesn't have the ability to adjust the clock automatically depending on the time zone; your Oregon does.

I think the PC version of BC shows elapsed time just like MapSource but I could be wrong. PC/Mac software would need to know the start time to calculate an ETA (with/without timezone or DST changes).

It shows the elapsed time (the real one; not adjusted for the time zone difference). The start time is the time you created the route, but you can change it afterwards in BC.

As of BaseCamp 4.2, we adjust the arrival/departure time of points in a route based on time zone changes. Previously we did not.

In the trip planner you can hover over the "time zone changed" icon to see how many hours difference there is between points. See my screenshot...

As of BaseCamp 4.2, we adjust the arrival/departure time of points in a route based on time zone changes. Previously we did not.

In the trip planner you can hover over the "time zone changed" icon to see how many hours difference there is between points. See my screenshot...

I can see that Trip Planner seems to take time zones into account, but I can't see where standard routes are time zone aware. Am I missing something?

I think they are if you edit the route properties to create a start date and time for the route. Open the properties window and click on the clock icon adjacent to the departure waypoint.