Entur's implementation documentation for Nordic public transport data
Timetables · Stops · Vehicles · Fares · Operations
⚠️ Release Candidate — This documentation is under active development. Not yet the official source.
NeTEx is the common standard that Nordic public transport integrates toward — covering timetables, stops, vehicle assignments, and fare products in a shared XML format. The Nordic NeTEx Profile constrains the full standard into a practical subset.
This repository is Entur's implementation guide: clear explanations, validated examples, and machine-readable rules for how to produce and consume NeTEx data in the Nordic context.
flowchart LR
A["🏁 Get Started"] --> B["📐 Conventions"]
B --> C["🚌 Build a Timetable"]
C --> D["🚏 Stops"]
D --> E["📅 Calendar"]
E --> F["📦 Full Dataset"]
| # | Guide | You'll learn |
|---|---|---|
| 1 | Get Started | What NeTEx is, document anatomy, frames and objects |
| 2 | NeTEx Conventions | ID patterns, versioning, codespace rules |
| 3 | How to Build a Timetable | Line → Route → JourneyPattern → ServiceJourney → Departure |
| 4 | Stop Infrastructure | Logical stops, physical platforms, the assignment bridge |
| 5 | Calendar | DayTypes, OperatingPeriods, exceptions, date-based scheduling |
Beyond the core reading path, these guides cover specific domains:
| Domain | Guide |
|---|---|
| 🔄 Interchanges & connections | Interchange |
| 📢 Passenger information & booking | Passenger Information |
| 🚌 Vehicle assignment & blocks | Vehicle Scheduling |
| 🚆 Rolling stock & train composition | Rolling Stock |
| Extended Sales & Deviations | |
| 🛠️ Tooling & debugging | Tools |
Every NeTEx concept follows three layers:
objects/<Name>/
├── Description_<Name>.md → What it is, when to use it, how it connects
├── Table_<Name>.md → Every element, type, and cardinality per profile
└── Example_<Name>.xml → Minimal valid XML you can copy-paste
| Folder | Content |
|---|---|
| frames/ | Frame-level containers (Description, Table, Example per frame) |
| objects/ | Object-level building blocks (one folder per NeTEx class) |
| guides/ | Topic guides explaining how to model specific scenarios |
| ontology/ | Machine-readable knowledge graph (Turtle/OWL) |
| assets/ | Images and support files |
💡 Need to look up a specific element? Browse objects/ directly or check the Glossary.
The ontology/ folder contains a layered knowledge graph sourced from entur-netex-ontology (git submodule). To fetch the ontology files locally, clone with --recurse-submodules (or run git submodule update --init --recursive).
netex:base — Base NeTEx schema (classes, properties, cardinality), generated from the NeTEx XSD and owned externally (CEN). Imported viaowl:imports; not stored in this repo.- ontology/entur-netex-ontology/nordic-netex-ontology/netex-nordic.ttl — Nordic Profile:
nordic:Xprofile nodes and fields, constraints and element ordering - ontology/entur-netex-ontology/nordic-netex-ontology/netex-nordic-vocab.ttl — Shared profile vocabulary (
profile:) and Nordic terms (nordic:) not derived from the XSD - ontology/entur-netex-ontology/nordic-netex-ontology/netex-nordic-model.ttl — Curated frame containment between profile nodes
- ontology/entur-netex-ontology/nordic-netex-ontology/netex-transmodel-alignment.ttl — NeTEx ⇄ Transmodel mapping
- ontology/entur-netex-ontology/nordic-netex-ontology/netex-siri-bridge.ttl — NeTEx ⇄ SIRI real-time bridges
- ontology/entur-netex-ontology/netex-entur.ttl — Entur profile:
entur:Xprofile nodes for Entur-only classes, governance (codespaces, data ownership) - ontology/entur-netex-ontology/netex-entur-nsr.ttl — Entur NSR sub-profile (stop places)
- ontology/entur-netex-ontology/netex-rolling-stock.ttl — Rolling stock sub-profile
- ontology/netex-nordic-documentation.ttl — Documentation paths on the profile nodes, and guides with the classes they cover (local to this repo). Generated from
objects/,frames/andguides/— runpython scripts/generate_documentation_ttl.pyafter adding or renaming documentation files
This repository uses Docsify for local preview:
npx docsify-cli serve .Contributions welcome — especially validated examples, corrections to element tables, and new topic guides. See the existing patterns in objects/ and guides/ for conventions.
Documentation: CC BY 4.0