There are several ways to create new Trips, depending on which Schedule View you are in and how much information should be pre-populated.
Option 1: Add a Trip Button
To start from scratch, or for brand new Schedules, use the Add a Trip button.
No values will be populated. See below for field descriptions.
Option 2: Insert a Trip into Schedule View: Timetable View
To add a Trip from the Timetable View, move the cursor to the desired start time and click the green Add Trip button that appears.
Start time, Calendar and Service Days will be auto-populated. See below for field descriptions.
Option 3: Insert a Trip into Schedule View: Timeline View
To add a Trip from the Timetable View, select the + icon that appears between any two existing Trips.
All values* will be auto-populated based on the preceding Trip. *Start Time will also be copied, and likely needs to be adjusted for the new Trip.
|Field||Best Practice||Required?||Learn More|
|Additional Options (click to expand)|
|Trip Short Name||
|Repeats with regular headways||
|In-seat transfers allowed||
GTFS operates on a scheduled, weekly basis. Therefore, a Trip is scheduled on one or more days of the week, called Service Days. In conjunction with Calendar Service Periods, Service Days determine whether a Trip will populate as an option for riders when searching for itineraries.
A Trip must have at least one Service Day defined, except in Exception Only Calendars. If a Trip happens less frequently than once per week (such as a 2nd and 4th Tuesday Shopping Shuttle) it must be scheduled on a semi-monthly Calendar.
If a Trip repeats more than once with an identical Stop Pattern and Timed Pattern, and does so at a regular headway, you can save the need to manually create each Trip by using the Repeats with regular headways function within the Trip edit menu:
- Regular headway: This is the interval, in HH:MM:SS that should exist between each repeated Trip start time. Default is one hour, but can be set to anything. Adjusting this will increase or decrease the Number of trips, depending on the Departure of last trip.
- Number of trips: You can manually adjust the number of trips, or allow this field to be updated by changes to the Regular headway or Departure of last trip.
- Departure of last trip: You can manually adjust the value of the last trip, which will update the Number of trips, or use Number of trips to increase or decrease this value.
Repeated Trips appear horizontally in the Timeline View.
In some scenarios, you may need to have your GTFS include the file frequencies.txt. If this is your use case, you can use Repeated Trips to populate this file and have your Trip(s) frequency-based instead of exact time-based.
This field is not by default public-facing. Email firstname.lastname@example.org for details about making this field visible in applications like Google Maps.
This field should only contain the text that appears in schedules and sign boards to identify the Trip to passengers. An example of its use is to refer to specific train numbers like those shown below (see 8453, 8458, 8456).
It should not be used for destination names or limited/express designations.
If an agency does request for this field to be displayed to the public, it will appear between the route name and headsign under the trip itinerary (see example below).