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