What Does a Frequency-Based Transit Trip Mean?
From the earlier reference collection. Read the current software blog.
Frequency-based service describes departures through an interval or headway, which may not enumerate every individual departure time.
A pattern can replace a departure list
A timetable often lists specific departures: 8:00, 8:20, and 8:40. Frequency-based service describes a pattern instead, such as a vehicle arriving roughly every 20 minutes during a stated interval. The data may therefore communicate service spacing without spelling out every departure as a separate scheduled event.
This changes what a reader can infer. A headway is an interval between departures, not a promise that a particular vehicle will depart at each clock time a simple calculation generates.
Read the interval and the rule
Consider a service pattern covering 9:00 through 10:00 with a 15-minute headway. A basic illustration might suggest departures around 9:00, 9:15, 9:30, and 9:45, but the data’s exact interpretation depends on its fields and whether the service is exact or approximate. A display should preserve those semantics instead of turning every frequency record into invented precision.
GTFS includes a frequencies file as part of its schedule format. The presence of frequency information indicates that software should inspect the frequency definition rather than assume that a trip record represents every individual departure. [GTFS schedule reference](https://gtfs.org/documentation/schedule/reference/)
Do not imply more precision than supplied
If the source says vehicles run at approximate intervals, an interface should describe the pattern in those terms. Showing “Departs at 9:15” as a guaranteed exact time can mislead someone who interprets it as a fixed timetable entry. Clear wording such as “about every 15 minutes” communicates the level of detail available.
When exact departure instances are needed for a calculation, derive them only according to the specification and source fields. Keep the difference between a generated representation and a separately published fixed departure visible in the data model.
Help readers plan around the pattern
Present the start and end of the frequency window, the stated interval, and any relevant service-date context. A rider can then decide whether the service pattern fits a desired travel window without relying on a fabricated exact minute.
Frequency-based service is still useful schedule information; it simply answers a different question. It describes how often service is expected over a span, while a list of fixed departures identifies particular planned times.