NeTEX

NeTEx overview 🔍

What is NeTEx?

NeTEx (Network Exchange format) is a standard for exchanging public transport network, schedules, and related data. It is a general-purpose XML format designed for the efficient exchange of complex transport data among distributed systems.

It has been developed under the aegis of CEN (Comité Européen de Normalisation) and is the most recent development stage in over fifteen years work to systemise and harmonize European passenger information data.

NeTEx can be used to collect and integrate data from many different stakeholders, and to reintegrate it as it evolves through successive versions. It is used by public transport operators and IT providers across Europe to support a wide range of passenger information and operational applications.

Benefits of using NeTEx

NeTEx offers a number of benefits, including:

• Flexibility: NeTEx can be used to represent a wide range of public transport data, including networks, schedules, fares, and real-time information.
• Extensibility: NeTEx can be extended to support new types of data and functionality.
• Interoperability: NeTEx is a standard format, which means that data can be exchanged between different systems without the need for custom development.
• Support for modern web services architectures : NeTEx can be used to develop modern, web-based passenger information and operational applications.

Examples of NeTEx in use

NeTEx is used in a variety of ways across the public transport industry. For example:

• Passenger information: NeTEx can be used to provide real-time arrival and departure information to passengers, generate timetables and journey planners, and develop mobile apps for passengers.
• Operational applications: NeTEx can be used to manage fleet operations, integrate public transport data with other systems, such as traffic management systems and navigation apps, and support planning and analysis.

ℹ️ To find out more about the NeTEX data model, visit the NeTEX website.

⚙️ To verify your NeTEx data, use our free validation tool.

NeTEx European Passenger Information Profile 🇪🇺

	Description	Documentation
NeTEx EPIP	Ideally, all member states will provide NeTEx files according to the European Passenger Information Profile (EPIP) on their respective National Access Point. Data4PT provides some artefacts to simplify producing and quality assure such information. EPIP-adapted version of the full NeTEx XML schema has been produced.	Browse the graphic and interactive technical presentation and download the relevant artefacts and available example here.
NeTEx EPIP Light	The official NeTEx schema is too large and complex for C# code generation tools to handle, so a simplified version was created for application development. This schema has been reduced to only match the scope of the EPIP Profile (European Passenger Information Profile). It is compliant with the main NeTEx schema, but does not contain constraint checks and should not be used for validation.	The graphic interactive technical presentation and the technical artefacts are available here.

NeTEx national and EU minimum profiles inventory 🌐

A number of national and transnational profiles have already been defined for different European countries, while there are new profiles under development. In the following tables, DATA4PT provides an overview of the key characteristics of the national profiles per country, including the data categories that are currently covered. The tables will be continuously updated following new implementations.

Published profiles

Profile Name	NeTEx EPIP Based	NeTEx EPIP Compatible	Documentation
Austria (AT)	✅		Austrian profile
Denmark (DK)	✅		Denmark profile - NAP in Denmark
France (FR)		✅	French profile - Common profil - Stop Profile - Network Profil - Timetable profile - Fare Profile - Parking profile - Accessibility Profile
Italy (IT)	✅		Italian profile
Netherlands (NL)	✅		Netherlands profile - Bison Fares
Nordic (Norway, Sweden, Finland, Denmark)		✅	Nordic profile
Portugal (PT)			Portuguese profile
Slovenija (SI)		✅	Slovenian profile
UK (GB)		✅	UK profile - Introduction - Stop and Timetables - Fares
Irish (IRL)			Irish profile - Profile Elements - Profile Data Mappings

Data categories

Data categories are identified based on MMTIS EU Regulation 1926/2017

Data categories table.

Level of service (LOS)	Static data
Static data - Level of service 1 (LOS 1 )
LOS 1-1	Address identifiers (building number, street name, postcode)
LOS 1-2	Topographic places (city, town, village, suburb, administrative unit)
LOS 1-3	Points of interest (related to transport information) to which people may wish to travel
LOS 1-4	Operational Calendar, mapping day types to calendar dates
LOS 1-5	Identified access nodes (all scheduled modes)
LOS 1-6	Geometry/map layout structure of access nodes (all scheduled modes)
LOS 1-7	Connection links where interchanges may be made, default transfer times between modes at interchanges
LOS 1-8	Network topology and routes/lines (topology)
LOS 1-9	Transport operators
LOS 1-10	Timetables
LOS 1-11	Planned interchanges between guaranteed scheduled services
LOS 1-12	Hours of operation
LOS 1-13	Vehicles (low floor; wheelchair accessible.)
LOS 1-14	Accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators)
LOS 1-15	Existence of assistance services (such as existence of on-site assistance)
LOS 1-16	Road network
LOS 1-17	Cycle network (segregated cycle lanes, on-road shared with vehicles, on-path shared with pedestrians)
LOS 1-18	Pedestrian network and accessibility facilities
	Framework data
Static data - Level of service 2 (LOS 2)
LOS 2-1	Park & Ride stops
LOS 2-2	Bike sharing stations
LOS 2-3	Car-sharing stations
LOS 2-4	Publicly accessible refueling stations for petrol, diesel, CNG/LNG, hydrogen powered vehicles, charging stations for electric vehicles
LOS 2-5	Secure bike parking (such as locked bike garages)
LOS 2-6	Information service
LOS 2-7	Where and how to buy tickets for scheduled modes, demand responsive modes and car parking (all scheduled modes and demand-responsive incl. retail channels, fulfillment methods, payment methods)
LOS 2-8	Trip plans, auxiliary information, availability check
LOS 2-9	Basic common standard fares (all scheduled modes)
LOS 2-10	Fare network data (fare zones/stops and fare stages)
LOS 2-11	Standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares)
LOS 2-12	Vehicle facilities such as classes of carriage, on-board Wi-Fi.
Static data - Level of service 3 (LOS 3)
LOS 3-1	Passenger classes (classes of user such as adult, child, student, veteran, impaired access and qualifying conditions and classes of travel such as 1st, 2nd.)
LOS 3-2	Common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point to point fares prices for different point to point pairs including daily and weekly fares/zonal fare prices/flat fare prices)
LOS 3-3	Special Fare Products: offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products and add on products such as parking and travel, minimum stay
LOS 3-4	Basic commercial conditions such as refunding/replacing/exchanging/transferring and basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay.
LOS 3-5	How to pay tolls (incl. retail channels, fulfillment methods, payment methods)
LOS 3-6	How to book car sharing, taxis, cycle hire etc. (incl. retail channels, fulfillment methods, payment methods)
LOS 3-7	Where how to pay for car parking, public charging stations for electric vehicles and refueling points for CNG/LNG, hydrogen, petrol and diesel powered vehicles (incl. retail channels, fulfillment methods, payment methods)
LOS 3-8	Detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, ‘walk only’, turn or access restrictions (e.g. against flow of traffic)
LOS 3-9	Parameters needed to calculate an environmental factor such as carbon per vehicle type or passenger mile or per distance walked
LOS 3-10	Parameters such as fuel consumption needed to calculate cost
LOS 3-11	Estimated travel times by day type and time-band by transport mode/combination of transport modes

Static data - Level of service 1 (LOS 1)

Data Categories	EPIP	AT	DK	FR	IT	NL	Nordic (SE, NOR, DK, FIN)	PT	SI	GB
LOS 1-1				✅			✅		✅
LOS 1-2				✅			✅		✅	✅
LOS 1-3				✅			✅		✅
LOS 1-4		✅	✅	✅		✅	✅		✅	✅
LOS 1-5		✅	✅	✅		✅	✅		✅
LOS 1-6		✅		✅		✅	✅		✅
LOS 1-7		✅		✅			✅		✅	✅
LOS 1-8	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
LOS 1-9	✅	✅	✅	✅	✅	✅		✅	✅	✅
LOS 1-10	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
LOS 1-11		✅	not existent	✅		✅	For connection links we use journey planner based on OSM map data, road, cycle, and pedestrian network is based on OpenStreetMap		✅	✅
LOS 1-12		✅	✅	✅			✅		✅
LOS 1-13		✅	✅	✅		✅	✅		✅
LOS 1-14		✅	✅	✅			✅		✅
LOS 1-15			✅	✅			✅		✅
LOS 1-16				✅			✅		✅
LOS 1-17				✅			✅		✅
LOS 1-18				✅			✅		✅
Framework data								✅

Static data - Level of service 2 (LOS 2)

Data Categories	EPIP	AT	DK	FR	IT	NL	Nordic (SE, NOR, DK, FIN)	PT	SI	GB
LOS 2-1			✅	✅			✅		✅
LOS 2-2			✅	✅			✅		✅
LOS 2-3			✅	✅			✅		✅
LOS 2-4							Only charging stations for electric vehicles		✅
LOS 2-5			✅	✅			✅		✅
LOS 2-6			✅	✅			✅		✅
LOS 2-7				✅			✅		✅
LOS 2-8				✅			✅		✅
LOS 2-9				✅		✅	✅		✅	✅
LOS 2-10				✅			✅		✅	✅
LOS 2-11				✅			✅		✅	✅
LOS 2-12			✅	✅			✅		✅	✅

Static data - Level of service 3 (LOS 3)

Data Categories	EPIP	AT	DK	FR	IT	NL	Nordic (SE, NOR, DK, FIN)	PT	SI	GB
LOS 3-1				✅			✅			✅
LOS 3-2				✅			✅			✅
LOS 3-3				✅			✅			✅
LOS 3-4				✅			✅
LOS 3-5				✅
LOS 3-6
LOS 3-7				✅
LOS 3-8							✅
LOS 3-9							✅
LOS 3-10							✅
LOS 3-11							✅

⚠️ If you believe that your use cases are resolved in an existing profile, it is highly recommended to adopt an existing solutionand cooperate with the corresponding entity. You will save resources while you will ensure that your profile is interoperable.

📄 You can also find contact details for some of the entities responsible for the profiles in the documentation list. Otherwise you can contact us in DATA4PT.

Software & tools 🧰

An ecosystem of NeTEx XML tools is under development, including both open-source and commercial products.

The following list of software is known to support NeTEx. We distinguish between different categories that may later receive a list of key performance indicators.

XML tools

General purpose XML tools can be used to work with the NeTEx XML schema and XML documents that conform to it.

XML tools	Description
XML SPY	commercial
Oxygen	commercial
List of tools	open-source

Conversion tools

Name	Availability	|Description	Profile	colspan="1" |License
netex-protobuf	✅	NeTEx to protobuf converter	All	EUPL
gtfs2netexfr	✅	Export GTFS data to NeTEx.	French
hastus	✅	Giro Hastus OIG script to export NeTEx from a system, in addition can export crew operations.	Dutch, Nordic(?)	AGPL-3.0
josm-plugin-netex-converter	✅	Export OpenStreetMap pedestrian routing information into NeTEx.		GPL 2.0
netex-gtfs-converter-java	✅	Export NeTEx data to GTFS	Nordic	EUPL
Chimera	✅	Chimera is a framework for semantic data transformation pipelines. A converter between GTFS and NeTEx has been implemented adopting an intermediate Transmodel representation.	Nordic (ready), EPIP/Italian (ongoing)	Framework – Apache License 2.0, Mapping GTFS-NeTEx – Proprietary license
OpenMove ATLAS	✅	The management platform OpenMove ATLAS allows import and editing of data in GTFS format and export also in GTFS or NeTEx format (currently the Italian Profile is supported, other profiles can be implemented on request).	EPIP Italian	Proprietary license
GTFS2NeTEx-converter	✅	Converts GTFS data in NeTEx Italian Profile.	EPIP Italian	Proprietary License

Data validation tools

Name	Availability	Description	Profile	License
XMLlint	✅	XML syntax validation, XSD schema validation and constraint checking.	All	MIT
Greenlight - The Data4PT Validation tool	✅	Validating NeTEx data.	All
NeTEx validator java	✅	Validation library for NeTEx data, analyzing and reporting schema compliance.	Nordic
Antu	✅	Validate NeTEx datasets against the Nordic NeTEx Profile.	Nordic

Language bindings

Name	Availability	Description	Profile	License
netex-java-model	✅	NeTEx XML bindings for Java, with additions to map temporal types to native objects.	All	EUPL
netex-csharp-model	❌	NeTEx XML bindings for C#. Currently being researched with a variety of tools. Contact DATA4PT if you have questions or have found the golden egg.	All
netex-parser-java	✅	Parse NeTEx files and lookup entities in an index	Nordic	EUPL

Editing /Management & visualisation tools

Name	Availability	Description	Profile	License	URL
Nplan	✅	Java backend / TypeScript frontend for create/edit/export of NeTEx data (Support both Timetable based and On-demand polygon based services)	Nordic	EUPL	backend - https://github.com/entur/uttu frontend - https://github.com/entur/enki
NSR	✅	Java backend / JavaScript frontend for import/creation/edit/export for NeTEx stops data. (Act as a National Stops Register for the whole of Norway)	Nordic	EUPL	backend - https://github.com/entur/tiamat frontend - https://github.com/entur/abzu
Chouette	✅	Java backend / Ruby frontend for import/validation/edit/export of NeTEx data. Highly modified version of the old AFIMB version of Chouette. NOTE: Legacy software not recommended for new implemetations	Nordic	CeCILL-B	backend - https://github.com/entur/chouette frontend - https://github.com/entur/chouette2
Chouette	✅	Java based NeTEx tools, transforms between profiles and standards (NeTEx, GTFS, Neptune).	EPIP	Apache 2.0
mobilitx	✅
mobiref	✅
NeTEx Reader	⏳	C# based XML tool based on Giro Hastus XSD	Dutch		https://www.youtube.com/watch?v=mpb_1Y9uR5k
netexconv2	⏳	Java based NeTEx tools, transforms between profiles and standards (NeTEx, DINO, HAFAS, KV1, GTFS).	Dutch, EPIP, Nordic, VDV462
IVU.cloud	✅		EPIP
Motus	✅	4Motus is the Fleet Scheduling Management System provided by Pluservice. The application is designed by independent and integrated modules which can be activated according to specific operational needs. One of the latest module created and already available is the generation of NeTEx datasets starting from the operational data collected by public transport operators. For this purpose, Motus receives the input data starting from a GTFS and it is able to enrich these data with further relevant information such as contracts, vehicles. Then Motus transforms these data into the NeTEx Italian profile. Data model: the database is designed according to Transmodel specifications, European reference standard (EN12896) for public transport.	Italian

Journey planning engine

Name	Availability	Description	Profile	License
OpenTripPlanner	✅	Timetable and shortest path journey planner supporting reading various input formats including GTFS and NeTEx.	Nordic	Apache 2.0
OpenMove	✅	Multimodal, intermodal trip planner with real-time capabilities, step-by-step instructions, fare system, and compatibility with market standards.

Planning system supporting native NeTEx export

Name	Availability	Planning system from	Profile
Hastus	✅	Giro for public transport	Nordic
Trapeze	✅	Trapeze for public transport	Nordic
DG Buss	✅	Datagrafikk for public transport	Nordic
Train Plan	✅	Trapeze for railway	Nordic
IVU	⏳	IVU for public transport	Nordic
IVU	⏳	IVU for railway	Nordic
Turnit	✅	Turnit for public transport	Nordic
Nplan	✅	Entur for public transport	Nordic
TPSI	✅	HaCon for railway	Nordic

NeTEx part 5 for 🆕 modes

NeTEx Part 5 is an extension to the NeTEx data exchange format that is specifically designed for publishing data about "alternative modes" of transportation, such as car sharing, cycle sharing, carpooling, and car/cycle rental. It is primarily oriented towards static data, such as the service that is offered and the associated infrastructure.

NeTEx Part 5 is now available as CEN/TS 16614-5:2022 (E)

	Description
Technical artefacts	The XML schema (XSD) for NeTEx Part 5 New Modes. Examples are also provided, along with other useful documentation.
Canonical mapping with GBFS	The EU-funded project DATA4PT and MobilityData experts have released a high-level mapping between the General Bikeshare Feed Specification (GBFS) and Transmodel to support better interoperability of shared mobility data feeds.

References

Name	Description
NeTEx-CEN GitHub	Find xsd, examples and relevant documentation on NeTEx schema
NeTEx EPIP profile GitHub	Find xsd and relevant documentation dedicated on NeTEx EPIP schema
NeTEx Website	Find general information on NeTEx project