Standard timetable dataset operations
Upload NeTEx dataset
This endpoint allows for uploading a NeTEx dataset into Entur import and validation pipeline. It provides the same feature as a manual upload from the Operator Portal application.
path Parameters
codespaceLowercase codespace attributed to the data provider. Examples: rut, sky, vyg, …
Headers
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Upload NeTEx dataset › Responses
OK - the dataset has been received successfully (this is only a technical acknowledgement, before applying any validation rule. The dataset may be rejected further down in the validation pipeline)
correlationIdDownload filtered NeTEx dataset
This endpoint gives access to private NeTEx datasets not available on Entur open data portal. These datasets include, in addition to the data available on the open data portal, the following private data:
- NeTEx Block data
- DeadRuns
- Lines and Service Journeys with restricted publication
This dataset is time-filtered (past trips are removed) and content-filtered (unknown NeTEx entities are filtered out). Datasets that failed validation are not published on this endpoint. To access the original NeTEx dataset sent by the data provider, without any alteration, use instead Latest original dataset download endpoint.
path Parameters
codespaceCodespace of the NeTEx dataset
query Parameters
dsjcompatibilityStructure of DatedServiceJourney in the returned dataset, during the transition to NeTEx 1.16:
legacy (the default) returns the NeTEx 1.15 structure, in which replaced journeys are repeated
DatedServiceJourneyRef elements; new returns the NeTEx 1.16 structure, in which they are held in a
replacedJourneys container. Only datasets that contain replacement information differ between the
two; the others are returned unchanged and declare the NeTEx version the pipeline exported.
Headers
ET-Client-NameEntur Client Header.
It is required that all consumers identify themselves by using this header.
Entur will deploy strict rate-limiting policies on API-consumers who do not identify with a header and reserves the right to block unidentified consumers.
The structure of ET-Client-Name should be: <company>-<application>.
X-Correlation-IdCorrelation id
Download filtered NeTEx dataset › Responses
NeTEx dataset ZIP archive with private data. Expired data and unsupported NeTEx entities are filtered out.