Using Multiple Time Zones

108 views
Skip to first unread message

NICTD

unread,
Feb 17, 2009, 2:54:31 PM2/17/09
to Google Transit Feed Spec Changes
I have one stop that is in eastern time and the rest of my stops are
on central time. Without stop_timezone, how would I accurately
display the departure/arrival times? I can just put everything on
central time zone but that would be confusing to those at the stop in
Eastern Time.

Thanks.

NICTD

Joe Hughes

unread,
Feb 17, 2009, 3:00:23 PM2/17/09
to Google Transit Feed Spec Changes
This question refers to the existing stop_timezone proposal mentioned
here:
http://groups.google.com/group/gtfs-changes/browse_thread/thread/2bb9026879bf10d9

In this proposal, stop_times are always given in the timezone
specified by agency_timezone, even if stop_timezone is present.
stop_timezone merely allows the feed consumer to know which timezone
the stop is in, so that it has enough information to present the time
to the user.

Consumers of the spec will generally expect stop_time values to
increase over the length of the trip, so it wouldn't work to alter the
stop_time value based on the timezone.

Joe

NICTD

unread,
Feb 17, 2009, 3:05:01 PM2/17/09
to Google Transit Feed Spec Changes
So, I should just put all times in the agency timezone (i.e. for an
arrival at 6PM EST, I would instead put that the arrival time is 5
pm)?

On Feb 17, 2:00 pm, Joe Hughes <joe.hughes.c...@gmail.com> wrote:
> This question refers to the existing stop_timezone proposal mentioned
> here:http://groups.google.com/group/gtfs-changes/browse_thread/thread/2bb9...

Jehiah Czebotar

unread,
Feb 17, 2009, 3:12:05 PM2/17/09
to gtfs-c...@googlegroups.com
correct. with an agency_timezone of CST(-6), a stop time at 6pm
EST(-5) would be listed as 5pm CST.

Joe Hughes

unread,
Feb 17, 2009, 3:15:01 PM2/17/09
to Google Transit Feed Spec Changes
If agency_timezone is "America/Chicago", then the arrival time would
be 17:00:00 in your example. (Remember, stop_times is given in time
elapsed since midnight in agency_timezone.) The stop_timezone would
be "America/Indiana/Indianapolis", and the feed consumer would be
responsible for formatting that arrival time in the appropriate
timezone for users.

Joe

Matt Weatherford

unread,
Feb 17, 2009, 3:09:51 PM2/17/09
to gtfs-c...@googlegroups.com
Hello,
I also have a long-route trip that covers two times zones and am
curious what solution is available to accurately present both zones to
the traveler.

Matt

Jehiah Czebotar

unread,
Feb 17, 2009, 3:19:11 PM2/17/09
to gtfs-c...@googlegroups.com
I think this is a pretty straight forward proposal.

It seems from the other thread that Yuriy is using this field, and
NICTD is now going to be publishing data with it. Are any feed
consumers using this so we can push this towards 'ready for inclusion'
status on this proposal?

--
Jehiah

Levi

unread,
Mar 21, 2009, 12:24:44 PM3/21/09
to Google Transit Feed Spec Changes
I was curious if this proposal was going to make it into the next feed
update as this would be greatly appreciated (and needed) for my
upcoming feed.

Thanks,

Levi

On Feb 17, 3:15 pm, Joe Hughes <joe.hughes.c...@gmail.com> wrote:
> If agency_timezone is "America/Chicago", then the arrivaltimewould
> be 17:00:00 in your example.  (Remember, stop_times is given intime
> elapsed since midnight in agency_timezone.)  The stop_timezone would
> be "America/Indiana/Indianapolis", and the feed consumer would be
> responsible for formatting that arrivaltimein the appropriate
> timezone for users.
>
> Joe
>
> On Feb 17, 12:05 pm, NICTD <emails4l...@mchsi.com> wrote:
>
> > So, I should just put all times in the agency timezone (i.e. for an
> > arrival at 6PM EST, I would instead put that the arrivaltimeis 5
> > pm)?
>
> > On Feb 17, 2:00 pm, Joe Hughes <joe.hughes.c...@gmail.com> wrote:
>
> > > This question refers to the existing stop_timezone proposal mentioned
> > > here:http://groups.google.com/group/gtfs-changes/browse_thread/thread/2bb9...
>
> > > In this proposal, stop_times are always given in the timezone
> > > specified by agency_timezone, even if stop_timezone is present.
> > > stop_timezone merely allows the feed consumer to know which timezone
> > > the stop is in, so that it has enough information to present thetime
> > > to the user.
>
> > > Consumers of the spec will generally expect stop_time values to
> > > increase over the length of thetrip, so it wouldn't work to alter the
> > > stop_time value based on the timezone.
>
> > > Joe
>
> > > On Feb 17, 11:54 am, NICTD <emails4l...@mchsi.com> wrote:
>
> > > > I have one stop that is in easterntimeand the rest of my stops are
> > > > on centraltime.  Without stop_timezone, how would I accurately
> > > > display the departure/arrival times?  I can just put everything on
> > > > centraltimezonebut that would be confusing to those at the stop in
> > > > EasternTime.
>
> > > > Thanks.
>
> > > > NICTD

Joe Hughes

unread,
Mar 31, 2009, 8:09:24 PM3/31/09
to gtfs-c...@googlegroups.com
Hi Levi,

The stop_timezone proposal still seems to be pending end-to-end
testing with real data and clients applications that do something
useful with the information. I'd encourage you to help test this
proposal by adding timezone information to the stops in your feed.

Thanks,
Joe
Reply all
Reply to author
Forward
0 new messages