Static and dynamic data

Static data

Static data describes the transport system as it is planned. It changes rarely, for example when a timetable period changes. Examples:

• Stops, stations and access points.
• Lines, routes and timetables.
• Fares and tariffs.
• Accessibility information.
• The road, walking and cycling network.

Typical formats: NeTEx and GTFS for public transport.

Dynamic data

Dynamic data describes what is happening now. It changes continuously and must be updated often. Examples:

• Delays, cancellations and platform changes.
• Disruptions and incidents.
• The real-time position of vehicles.
• The availability of shared bikes, scooters and cars.
• Current road traffic conditions.

Typical formats: SIRI and GTFS Realtime for public transport, GBFS for shared mobility and DATEX II for road traffic.

Metadata

Metadata is data about the data. For each dataset, it says who owns it, what area and modes it covers, which format it uses, how to access it, how often it is updated, and under what licence it can be reused. Good metadata is what makes a National Access Point useful as a catalogue.

Why both are needed

A journey planner uses static data to build the plan and dynamic data to keep it correct. Without delays, a plan can mislead. Without the timetable, there is nothing to compare the delays against. That is why the framework covers both, linked through common identifiers.

Levels of service

The regulation phases in requirements by level of detail and by how much of the network is covered. See the timeline and the regulation guide.

Frequently asked questions