Combining with static DII data
- Bert
- Dick Zetterberg
Real-time data can only be provided to Samtrafiken if static data with matching ids is delivered as well. Static data should, according to the SIRI standard, be delivered as NeTEx when delivering SIRI data. However, if you are currently delivering static data in the DII format, Samtrafiken also accepts SIRI data which refers to the static DII data. In the static DII data (as well as in other Noptis standards), GIDs are used to refer to objects. GIDs have a fixed length of 16 digits and are constructed according to a specific format, depending on the referenced object. If a value does not use all the available space for a field, it is left-padded with zeroes.
- 1 SIRI > DII References
- 2 GID format
- 2.1 Line
- 2.2 ServiceJourney
- 2.3 StopArea
- 2.4 JourneyPatternPoint
SIRI > DII References
In this case, references should reference DII data through GID values as described in the table below.
SIRI | Example reference | Meaning | Example from DII |
|---|---|---|---|
LineRef |
| Transport authority 25, Line 28 |
|
DatedVehicleJourneyRef |
| Transport authority 25, Line 10, Journey number 11 |
|
StopPointRef AimedQuayRef ActualQuayRef |
| Transport authority 25, JourneyPatternPoint 97101 Note! A JourneyPatternPoint GID should be delivered, not a StopPoint |
|
StopPlaceRef |
| Transport authority 25, StopArea 971 |
|
GID format
Line
A line GID is constructed by joining a fixed prefix (4 digits), the transport authority number (3 digits), the line number (4 digits), and trailing zeroes (5 digits) as can be seen below.
A line number must be between 1 and 9998. If alphanumeric characters are used in the public identification of the line, it is necessary to define a numeric counterpart for use in GID, which can be considered as an internal alternative identification of the line. This should be taken care of while producing the DII files, and the SIRI data should just use the numeric line number as the DII data uses.
GID type (constant) | Transport Authority | Line Number | Unused | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9 | 0 | 1 | 1 | 0 | 2 | 5 | 0 | 0 | 2 | 8 | 0 | 0 | 0 | 0 | 0 |
ServiceJourney
A servicejourney GID is constructed by joining a fixed prefix (4 digits), the transport authority number (3 digits), the line number (4 digits), and the journey number (5 digits) as can be seen below.
GID type (constant) | Transport Authority | Line Number | Journey Number | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9 | 0 | 1 | 5 | 0 | 2 | 5 | 0 | 0 | 2 | 8 | 0 | 0 | 0 | 1 | 1 |
StopArea
A stoparea GID is constructed by joining a fixed prefix (4 digits), the transport authority number (3 digits), the stop area number (6 digits), and three trailing zeroes (3 digits) as can be seen below.
A stop area number must be between 1 and 999998.
GID type (constant) | Transport Authority | Stop Area Number | Unused | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9 | 0 | 2 | 1 | 0 | 2 | 5 | 0 | 0 | 0 | 0 | 9 | 7 | 0 | 0 | 0 |
JourneyPatternPoint
A journeypatternpoint GID is constructed by joining a fixed prefix (4 digits), the transport authority number (3 digits) and the journey pattern point number (9 digits) as can be seen below.
A journey pattern point number must be between 1 and 999 999 998.
GID type (constant) | Transport Authority | Journey pattern point number | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9 | 0 | 2 | 5 | 0 | 2 | 5 | 0 | 0 | 0 | 0 | 9 | 7 | 1 | 0 | 1 |
Â
Â