The short answer
Use NeTEx when you need the richness of the European standard, including fares and detailed network concepts, or when your National Access Point asks for it. Use GTFS when you need a simple format that almost every journey planner and map app understands. Many publishers offer both.
Side by side
| NeTEx | GTFS | |
|---|---|---|
| Origin | European standard (CEN) | Open, community-maintained format |
| Encoding | XML | Zip of CSV tables |
| Scope | Network, timetables, fares and more | Mainly stops, routes and timetables, with some fare support |
| Detail | Very detailed, many options | Simple, easy to produce |
| Real-time companion | SIRI | GTFS Realtime |
| Reference model | Transmodel | None formal |
| Typical effort | Higher | Lower |
When to choose NeTEx
- Your National Access Point requires or prefers it.
- You need fares, accessibility and network detail in one standard.
- You want a rich, vendor-neutral description that can be profiled nationally.
When to choose GTFS
- You want the widest tool support and quick adoption by apps.
- Your data model is simple.
- You need a format that small operators can produce easily.
Converting between them
Converting NeTEx to GTFS is common, but it is lossy: concepts that have no equivalent in GTFS are dropped or simplified. Converting GTFS to NeTEx can create valid data, but it cannot invent detail that was never in the source. Where possible, keep the richest format as the source of truth and generate the simpler one from it.
Next steps
See all data formats, how to publish transport data and SIRI vs GTFS Realtime.
Frequently asked questions
Is NeTEx better than GTFS?
Neither is better in general. NeTEx is richer and a European standard. GTFS is simpler and more widely supported by tools.
Can I publish both?
Yes, and many publishers do. Generate the simpler format from the richer one to keep them consistent.