NationalProfiles - nick-knowles/NeTEx GitHub Wiki

A NeTEx profile specifies how NeTEx should be used for a specific purpose with a specific data set.

Profiles are needed for three main reasons:

• NeTEx is a large general-purpose standard that can be used for many different use cases; a profile selects just the subset of elements needed for a particular business requirement, simplifying the task of implementation.
• NETEx allows for different workflows between data users, with different partitioning of data sets between files (e.g. should there be a separate timetable document per operator, per network, per line, etc?). The profile sets out the desired aggregations, again simplifying implementation and validation.
• NeTEx is intended to support the distributed, peer-to-peer exchange of data between many different organisations in many different countries. Typically many different coding systems will be in use in such a context. A profile clarifies which systems of identifiers are being used are being used.

---

A number of National and international profiles have already been defined for different European countries and more are under development.

• ch : Swiss profile - Work In progress.
• de : German Profile.
  • VDV462.
• dk : Denmark - Nordic Profile.
• eu : Europe - Passenger Information Profile (Timetables).
• fi : Finland - Nordic Profile .
• fr : FrenchProfile.
  • Common Profile specification.
  • Stop Profile specification.
  • Network Profile specification.
  • Timetable Profile specification.
• ie : Irish Profile.
  • Profile Elements.
  • Profile Data Mappings.
• nl : Netherlands profile.
  • Profile specification.
  • Bison Fares.
• no : Norway - Nordic Profile.
• se : Sweden - Nordic Profile.
• uk : UK Profile (FareExchange.
  • Introduction.
  • Stops and Timetables.
  • Fares.