> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bayareatransit.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Static data

> The scheduled network model: operators, lines, stops, patterns, timetables, holidays, and shapes.

## Core hierarchy

The static part of the transit API describes the network in layers:

* **Operators** identify transit agencies
* **Lines** identify public routes within an operator
* **Stops** identify scheduled boarding and alighting points
* **StopPlaces** represent the physical station or stop context around those points

```mermaid theme={null}
classDiagram
  class Operator {
    id
    privateCode
  }
  class Line {
    operatorRef
    publicCode
    siriLineRef
  }
  class ServiceJourneyPattern {
    lineRef
  }
  class StopPointInJourneyPattern {
    scheduledStopPointRef
    order
  }
  class ScheduledStopPoint {
    id
    name
    parentStation
  }
  class StopPlace {
    id
    name
  }
  Operator "1" --> "*" Line
  Line "1" --> "*" ServiceJourneyPattern
  ServiceJourneyPattern "1" --> "*" StopPointInJourneyPattern
  StopPointInJourneyPattern "*" --> "1" ScheduledStopPoint
  StopPlace "1" --> "*" ScheduledStopPoint
```

## Patterns

Patterns describe the ordered stop sequence followed by a line. A single line can have multiple patterns, and a pattern may pass through the same stop more than once.

## Timetables

Timetables describe scheduled service for a given line, direction, and day type. The transit specification also notes that timetable responses include supporting structures such as routes, day types, and optionally day assignments.

```mermaid theme={null}
classDiagram
  class TimetableFrame {
    vehicleJourneys[]
  }
  class ServiceJourney {
    id
    dayTypeRef
    privateCode
  }
  class TimetabledPassingTime {
    stopPointInJourneyPatternRef
    arrivalTime
    departureTime
  }
  class LinkSequenceProjection {
    id
  }
  class LineString {
    pos[]
  }
  TimetableFrame "1" --> "*" ServiceJourney
  ServiceJourney "1" --> "*" TimetabledPassingTime
  ServiceJourney "1" --> "0..1" LinkSequenceProjection
  LinkSequenceProjection "1" --> "1" LineString
```

## Holidays and service exceptions

The holidays endpoint exposes service exceptions defined by an operator or agency. The transit specification treats these as part of the service calendar model rather than as a standalone alerting system.

## Shapes

Shapes describe the geometric path traveled by a vehicle for a trip. The shapes endpoint requires an operator and trip id, and the trip id comes from the timetable data.

## Examples and appendices

The transit specification includes both XML and JSON examples for the static resources. Those appendices are useful because they show the actual nested envelope structure, not just the top-level field names mentioned in the prose sections.