Create your data feed


Time zone fields specify the time zone for the transit agency and stops.

Agency Timezone

The agency_timezone field in file agency.txt sets the time zone for your transit agency. This required field also serves as a reference for the departure and arrival times shown in your GTFS feed. All agencies in a feed must have the same agency_timezone.

Stop Timezone

If a feed covers multiple time zones, provide time zone information for stops outside the agency_timezone in the stop_timezone field. Set this optional field in file stops.txt. If you omit stop_timezone, our system assumes the stop is located in the timezone specified by field agency_timezone in the agency.txt file. Ensure that trip travel times remain accurate and consistent by providing departure and arrival times based on the agency_timezone for stops that are out of that time zone.

Routing results show calculated departure and arrival times in the local time zone of each stop.

Daylight Saving Time

Some trips may operate during the switch from or to Daylight Saving time and then continue to operate as normal. Model such trips as belonging to the previous day and having departure times consistent with vehicle travel time. Our algorithm automatically calculates correct times for user display.

If services follow a special schedule during the switch from or to Daylight Saving time (for example, wait for an hour at one stop), then disable normal trips for this date and model this trip as an additional, exceptional trip.


A bus that starts at 1:59am on the night the switch happens is modeled as following:

Displayed departure time
         [Google Maps]
        25:59:00                01:59 am
        26:01:00                03:01 am

Time-related validation warnings

Feed validation may return warnings on time field settings.

Fast Travel Between Stops

Fast travel warnings are caused when the computed velocity of a trip is higher than the maximum velocity defined for that route_type.

If times in stop_times.txt are provided in the local time of the corresponding stop and not in the time defined in agency_timezone, the system may return a Fast Travel warning. More importantly, the system will return incorrect routing results. The routing algorithm assumes that times in stop_times.txt are provided in the time zone defined in agency_timezone.

Fix this situation by defining stop times in stop_times.txt that use the time zone defined in agency_timezone.

Even if you set stop_timezone values in stops.txt, it is best practice to specify times in stop_times.txt as time since midnight in the timezone specified by agency_timezone in agency.txt. This setting ensures that the time values in a trip always increase over the course of a trip, regardless of which timezones the trip crosses. Also, note that times in stop_times.txt should always be provided in the time defined in agency_timezone (NOT the local time of the corresponding stop).

This warning normally indicates a data problem. Check for the following:

  • stop locations: a stop too far away from the correct location would trigger this warning
  • Stop times are accurate
  • If the warning is due to daylight saving changes, refer to Daylight Saving Time above for details.
Was this helpful?
How can we improve it?