route

A transport service that operates between places on a schedule. A route IS a schedule — it inherits recurrence fields and adds transport-specific structure: stops, direction, route identifiers.

Each occurrence of the route produces a trip (with legs).

Examples: Bus 29 Austin — route_type: bus, stops: [Congress, Riverside, …] UA 1234 LAX→JFK daily — route_type: flight, origin/destination airports Amtrak Acela NYC→DC — route_type: train Costco delivery (Sat 9:30a-7p) — route_type: delivery, store as origin

GTFS alignment: GTFS “route” = this shape. GTFS “trip” = our trip shape. GTFS “stop_times” = our leg origins/destinations.

Metadata	Value
Plural	`routes`
Subtitle field	`routeNumber`
Also	`schedule`

Fields

Field	Type
`routeType`	`string`
`routeNumber`	`string`
`direction`	`string`
`color`	`string`

Relations

Relation	Target
`stops`	`place[]`
`origin`	`place`
`destination`	`place`
`operator`	`organization`

Inherited

From schedule:

Field	Type
`cronExpression`	`string`
`durability`	`string`
`enabled`	`boolean`
`hours`	`json`
`lastFiredAt`	`datetime`
`nextFireAt`	`datetime`
`prompt`	`string`
`providerJobId`	`string`
`rrule`	`string`
`scheduleType`	`string`
`timezone`	`string`

Relation	Target
`produces`	`trip`
`provider`	`skill`

Prior art

External standards this shape draws from or aligns with. See Shape design principles for how prior art informs shape design.

GTFS routes.txt — Direct source. Our routeType maps to GTFS route_type (integer vocab); routeNumber = route_short_name; color = route_color.
schema.org/BusOrCoach + FlightRoute — Per-mode peers. Our stops[]/origin/destination are modeled separately per mode in schema.org.