One of the most important steps towards regulatory compliance is aligning your ticketing platform with common data standards. Two that frequently come up in discussions around Mobility-as-a-Service (MaaS) are GTFS and NeTEx. Both aim to standardise transport data, but each has its own structure and areas of focus. In addition, there is also SIRI (not the Apple product). Let’s figure out what they are and how they can benefit ticketing companies and MaaS platforms alike.
What is GTFS?
General Transit Feed Specification (GTFS) is a widely used data format that originated in North America. It’s designed to provide static schedule and route information for public transport systems, covering elements such as:
- Routes and trips (bus, rail, ferry, etc.)
- Timetables and frequencies
- Stop locations and stop times
- Basic fare information
GTFS is relatively straightforward to implement and is supported by many existing tools and platforms, making it an excellent starting point for many ticketing providers. Although GTFS is primarily focused on timetable data, extensions like GTFS-RT (Real-Time) allow it to handle live service disruptions, vehicle locations and more dynamic updates.
What is NeTEx?
Network Timetable Exchange (NeTEx) is a European standard that builds on a broader scope than GTFS. While GTFS is quite streamlined, NeTEx is more complex and adaptable. It aims to cover a wider range of operational details, such as:
- Multi-level fare structures and ticketing rules
- Comprehensive stop and station definitions
- Complex relationships between different transport networks
- Support for longer-distance and inter-regional services
NeTEx’s flexibility and depth make it particularly suitable for large or intricate transit networks. As MaaS continues to expand across regions, NeTEx can be beneficial for services that require detailed modelling of routes, fares and organisational structures.
What is SIRI (not Apple’s)?
Service Interface for Real-time Information (SIRI) is a European standard designed to complement NeTEx by enabling the exchange of live, operational data. Where NeTEx focuses on detailed, static information such as timetables and complex fares, SIRI deals with real-time updates like service disruptions, vehicle locations and arrival times.
By integrating SIRI into a ticketing or journey planning platform, operators can provide passengers with accurate, up-to-the-minute travel details. This not only increases user satisfaction—by giving them reliable information to manage delays or plan alternative routes—but also strengthens compliance with regional requirements that emphasise transparency and punctuality in public transport services.
Key differences between GTFS and NeTEx
- Depth and detail
- GTFS: Best for straightforward static data, widely adopted in North America and beyond for buses, subways and other public transport modes.
- NeTEx: Provides a more comprehensive framework, covering complex fare rules, longer-distance services and multi-operator networks.
- Complexity
- GTFS: Simpler to implement, making it easier for smaller operators or services.
- NeTEx: More flexible and powerful but can be time-consuming to adopt due to its detailed structure.
- Regional usage
- GTFS: Established as a de facto standard worldwide, particularly strong in the United States and other English-speaking regions.
- NeTEx: More common in Europe, with official support from European Union standards bodies.
- Use cases
- GTFS: Ideal for city-level or regional services where standard timetables and basic fares are sufficient.
- NeTEx: Suitable for operators who need to integrate more complex data (e.g. varying fare policies, multiple transport authorities) or for those operating across national borders.
Which standard should you use?
For ticketing providers integrating with MaaS platforms, the choice often comes down to the scope of your services, regulatory requirements, and regional focus. If you’re working primarily with smaller or simpler networks, GTFS may be the best place to start. However, if you plan to expand into European markets with multiple operators and more complex fare rules, NeTEx could be a better fit—or you may even end up using both.
Ultimately, staying flexible and open to multiple standards can offer the broadest reach and regulatory compliance. Many MaaS solutions are built to accommodate data feeds in multiple formats, bridging gaps between operators and regions. By ensuring your ticketing platform aligns with these standards, you’ll not only simplify your compliance efforts but also position your business to thrive in an increasingly interconnected mobility ecosystem.
Get in touch with us today to discuss data standards and integrations.