Which format for which data?
The reference model: Transmodel
Transmodel is the European reference data model for public transport information (EN 12896). NeTEx and SIRI build on it, which is why their concepts line up, for example stops, lines, journeys and vehicles.
Quick comparison
- NeTEx: XML, rich and detailed, covers timetables, networks and fares, CEN standard.
- SIRI: XML, real-time exchange of departures, delays and situations, CEN standard.
- GTFS / GTFS Realtime: CSV files in a zip, and Protocol Buffers for real-time; simple and widely supported; stewarded by MobilityData.
- GBFS: JSON feeds for shared mobility; stewarded by MobilityData.
- DATEX II: XML, for road traffic and travel data; CEN standard.
Profiles
Broad standards leave many options open. A profile is an agreement on how to use a standard in a country or region so that data from different producers looks the same. Check your National Access Point for the profile it expects.
Where the formats are used
The formats are published through National Access Points and consumed by journey planners and other services. For terminology, see the dictionary.
Frequently asked questions
Do I have to use NeTEx and SIRI?
They are the main European standards and the regulation points to them. National requirements and profiles vary, so check what your National Access Point expects.
Is GTFS part of MMTIS?
GTFS is not a CEN standard, but it is very widely used for timetables and is often accepted alongside NeTEx. National rules decide what is accepted.
Which format is easiest to start with?
GTFS and GBFS are generally considered easy to start with. NeTEx and SIRI are more detailed and take more effort.