Module Info
- Reference
RailTicketData- Numeric OID
1.3.6.1.4.1.17218.1.0.2.3.7
Elements included as String and as Numeric values: Some elements are included in different formats to reduce the data size. These elements must be included only once. These elements are named with the same name and appendix Num (numeric values) IA5 (String values according to ASN IA5String (7Bit)) Example: trainNum - in case of a numeric train number trainIA5 - in case of a alphanumeric train Id
As Kosovo does not have an official ISO Country Code the following codes are used:
926 for Kosovo as numeric ISO Country CodeXK for Kosovo as alphanumeric 2-character ISO Country CodeRICS codes must be used to encode companies (issuer, product owner, ...) where available other codes are possible based on bilateral agreements the format is kept more flexible to cover upcoming extensions of the RICS code by ERA
Stations can be coded using the UIC and upcoming ERA code lists. Proprietary codes are possible based on bilateral agreements. Format: 1..9999999 or alphanumeric without special character (IA5String)
INTEGERS must not exceed the value of 9,223,372,036,854,775,807 (64 bit) even in case they are unrestricted!!! Some elements like ReferenceNum or cardIdNum are defined as an unrestricted integer. Unlike other numerical values the cardIdNum and referenceNum can be larger than a usual 32 bit Integer Some ASN.1 implementation tools are limited to 32 bit integers which is too small. Please ensure to use a tool capable of dealing with larger numbers.
Optional BOOLEANs have three values: "true", "false", "unknown" = the Boolean is absent from the data.
time is encoded as the number of minutes of the day 0 = 00:00, 1439 = 23:59, time data elements end with "time" in their name
The issuing date is given in UTC, but some other date values are given in local time where the exact time zone is not known.
For local dates the date is associated with the corresponding location: e.g.: valid from date -> location where the journey starts valid until date -> location where the journey covered by the ticket ends
there could be rare cases where this does not provide a unique interpretation: e.g. open ticket or pass without start and end location for a collection of zones or countries with different time zones. in these cases the fare conditions must clarify the rules for these cases (e.g. by allowing to use the ticket a few hours after the end of validity).
The difference in days is calculated from dates only, ignoring the time and time zone information.
Example 1: (31.12.2017 23:05 UTC == 01.01.2018 00:05 CET) :
issuing date (UTC): 31.12.2017 23:05 == 01.01.2018 00:05 CET
issuingYear = 2017
issuingDay = 365
issuingTime = 1385
local departure date (CET): 01.01.2018 00:15 == 31.12.2017 23:15 UTC
departureDate = 1 (= 01.01.2018 - 31.12.2017)
departureTime = 15
departureUTCOffset = -4 (UTC = local + offset * 15 Minutes)
Example 2: (01.01.2018 00:05 UTC == 31.12.2017 20:05 AST)
issuing date (UTC): 01.01.2018 00:05 UTC == 31.12.2017 20:05 AST
issuingYear = 2018
issuingDay = 1
issuingTime = 5
local departure date (AST): 31.12.2017 22:05 AST == 1.1.2018 02:05 UTC
departureDate = -1 (= 31.12.2017 - 01.01.2018)
departureTime = 1325
departureUTCOffset = 16 (UTC = local + offset * 15 Minutes)
departureDate can become -1 with a departure west of the GMT zone only
Tickets might cover multiple time zones where valid from and until is not linked to a specific time zone (e.g. Eurail Pass valid for whole Europe). In this case the date times are to be interpreted as local at the actual place where the traveler is and the ticket is checked. The utcOffset must not be provided for these local date times.
!! In general the issuing date and time is always UTC whereas the other dates and times are always local. !!
It is RECOMMENDED not to use the utcOffset until there is a need to do so.
The specification makes use of extension (",..."). These extensions might be defined in future versions of the UIC specification Implementations must support the extension feature of ASN.1, at least they must be able to ignore extensions while decoding the data ASN.1 extensions will be defined by UIC. It is not allowed to define bilateral extensions.
Bilateral extensions can be included in the data element "ExtensionData".
RailTicketData1.3.6.1.4.1.17218.1.0.2.3.7This module explicitly exports the following symbols:
UicRailTicketData uicRailTicketDataThe basic entry point of the data structure. The data includes:
This sequence contains the following fields:
Data specific to the issuer.
Data on the travelers.
Data of the transport document.
Data specific to support the ticket control process.
Proprietary data defined bilaterally.
This is an object of the class: DATA-ELEMENT
This object has the following field values:
FCB3
the choice on the different transport documents that can be included in the bar code data:
This sequence contains the following fields:
specific id to be exchanged with the ticket (e.g. id of the phone in case of tickets linked to a phone)
choice of the ticket
The value of this choice may be one of the following:
Reservation (without car carriage) (IRT and RES)
Reservation of car carriage
open ticket specification (NRT)
pass specification (RPT) including Eurail and Interrail
voucher
customer card either to identify a customer and / or to provide reductions
countermark to accompany a group ticket
car parking slot
FIP duty ticket
ticket to pass the gates at a station
proprietary data defined bilaterally In the specific case of a pure Account Based Ticketing barcode, in which no ticket must be present, as it is impossible with the existing definition to completely remove the ticket from the DocumentData, a specific "minimal" extension with extensionId = "_3011+0" and extensionData = ''H is used.
delay confirmation
confirmation of the delay of a train
This sequence contains the following fields:
reference of the delay confirmation, reference is optional, in case it is given it must be given in num or IA5
train number of the delayed train - numeric or alphanumeric
planned departure date of the delayed train in local time at the station where delay became relevant (see below)
This type is constrained in the following way:
The value must be greater than or equal to:
2016
The value must be less than or equal to:
2269
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
366
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC. (UTC = local + offset * 15 Minutes)
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
station where the delay became relevant
This field, when unset, defaults to the following value: stationUIC
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
delay in minutes at the mentioned station
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
indication that the train was cancelled
type of confirmation provided
This field, when unset, defaults to the following value: travelerDelayConfirmation
affected original ticket(s)
info text
proprietary data defined bilaterally
The value of this enumeration may have one of the following values:
Value:
0
confirmation of train delay, whether the traveler was on board in unconfirmed
Value:
1
confirmation that the traveler was on board of the delayed train
Value:
2
confirmation that a ticket linked to the delayed train was issued
Details of the issuer and the issue of the ticket
This sequence contains the following fields:
provider of the signature (RICS code)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
issuer of the transport document if the issuer is different from the security provider (RICS code).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
issuing time stamp in UTC
This type is constrained in the following way:
The value must be greater than or equal to:
2016
The value must be less than or equal to:
2269
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
366
The number of the minutes of issue might be used in case of account based ticketing with a delay of n minutes for the replication of central booking data to the control devices (e.g. at SBB) The time can be compared with the last synchronization time of the control device.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
name of the issuer (E.g. short name mentioned in RICS code table)
specimen indicates a test specimen not valid for traveling
secure paper indicates that this barcode is issued with a secure paper ticket to ensure the uniqueness of the ticket. This allows to use the same control procedure as for e-tickets also for anonymous tickets the double use of the ticket is in this case excluded by the secure paper.
indicates that the ticket is valid for traveling or still needs activation
currency of the price: ISO4217 currency codes
This type is constrained in the following way:
The length of the value must exactly:
3
This field, when unset, defaults to the following value:
EUR
fraction of the prices included
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
3
This field, when unset, defaults to the following value:
2
PNR used by the issuer to identify the document. ID to uniquely identify this barcode within the context of the issuer and an appropriate time range. This can be used to query the ticket in the eTCD. issuerPNR must be provided except for rare special cases like a pure token.
proprietary data defined bilaterally
location of sale in case of a sale on board of a train numeric train number or alphanumeric id of the train where the ticket was sold
line number
point of sale
data supporting the control process
This sequence contains the following fields:
cards that can be used to identify the ticket holder
id-card id must be checked to identify the traveler
passport id must be checked to identify the traveler
other items which could be used to identify the ticket holder (for future use, code list to be defined)
validation of the passport is required (e.g. in case of Eurail)
online validation of the ticket required
percentage of the tickets to be validated in more detail (i.e. via online check or detailed checks later-on)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
manual validation of the traveler age required (in case of reductions)
manual validation of the travelers reduction card required (in case of reductions)
controller info text
additional tickets that should be controlled
proprietary data defined bilaterally
Traveler data these data do not include tariff details of the booked tariffs, tariff data are included in the transport document details and might have a reference to the traveler defined here.
This sequence contains the following fields:
traveler list
ISO 639-1 coding of the language preferred for the traveler / ticket holder
This type is constrained in the following way:
The length of the value must exactly:
2
name of the group in case of a group ticket
reservations of seats , couchettes and berths included are the data defined in:
This sequence contains the following fields:
train number - numeric or alphanumeric
departure date in local time at the departure station number of the days calculated from the issuing date
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
reference is optional, it is given it must be given in num or IA5.
organization responsible for the product definition (RICS Code to be used as standard)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product codelist defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
32000
service code list from 918.1 (seat couchette,..)
This field, when unset, defaults to the following value: seat
code table used to encode stations
This field, when unset, defaults to the following value: stationUICReservation
origin station code
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
destination station code
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
origin station name
destination station name
departure time in local time at the departure station
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel. if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory times to be shown on a ticket should always be the local times.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
arrival date and time in local time at the arrival station. number of days counted from the departure date.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
20
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). should be omitted in case it is the same as for departure. the UTC offset can be used to calculate the duration of the travel times to be shown on a ticket should always be the local times.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
responsible carriers on the route
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
travel class
This field, when unset, defaults to the following value: second
service level code list from 918.1
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
2
places
additional places in a second coach
compartment details (open space, wheelchair,..)
number of persons on the ticket without place numbers (on IRT)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
200
This field, when unset, defaults to the following value:
0
description of berths
tariffs included (Adult, Children,... )
type of the price (supplement,... )
This field, when unset, defaults to the following value: travelPrice
type of supplement - code list from 918.1
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
9
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
200
This field, when unset, defaults to the following value:
0
luggage restrictions and registered luggage. in case the luggage restrictions are general and do not depend on the ticket type they should not be included
bilaterally agreed proprietary extension
details on the VAT included to be used in after sale processes
This sequence contains the following fields:
ISO 3166 numeric country code
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
1/10th of a percent
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
999
amount of VAT, the currency and the currency fraction is included in the issuing data
european tax id of the company paying VAT
reservations of car carriage included are the data defined in:
This sequence contains the following fields:
loading of the car in local date and time at the loading station. number of the days calculated from the issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). times to be shown on a ticket should always be the local times.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
reference is optional, in case it is given it must be given in num or IA5.
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product codelist defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This field, when unset, defaults to the following value: stationUICReservation
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
description of the car
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
9
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
6
This field, when unset, defaults to the following value: norack
height of a roof rack in cm
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
number of boats on a rack
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
2
number of biycles on a rack
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
4
number of surf boards on a rack
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
5
reference to an entry on the loading list
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
999
This field, when unset, defaults to the following value: upper
responsible carriers on the route (RICS codes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This field, when unset, defaults to the following value: travelPrice
data for open tickets (NRT and group tickets) included are the data defined in:
This sequence contains the following fields:
reference to this openticketdata document. reference must be given either in numeric or alphanumeric format
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product codelist defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
to support other ticket content (e.g. VDV, UTPF, VöV, CALYPSO). issuer code using the default code table of the product owner
authorization id provided to the issuer by the product owner
ticket includes the return trip - should be set to false if it is not relevant (e.g. zones)
for tickets valid in regions without from or to stations no station is provided
This field, when unset, defaults to the following value: stationUIC
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
for tickets valid in regions without from or to stations no station is provided
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
description for manual evaluation in case structured data are not available
specification of the ordered sequence of valid regions
return route description. the return route description can be omitted if it is identical to the inversed outbound validRegion sequence
date/time validity in local time of the location where the journey starts. number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel. if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory. times to be shown on a ticket should always be the local times.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
date/time validity in local time of the location where the journey ends. number of days from valid-from date, 0 = valid until day is equal to the first day of validity.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel . if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory. times to be shown on a ticket should always be the local times. should be omitted in case it is the same as for departure.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
here it is possible to list the activated days of the ticket: day the ticket is activated. The activation is valid from 00:00 to 23:59 in the time zone of the current location of the traveler thereby the activation might include more or less that 24 hours in case time zone borders are crossed travel days of a ticket might be subject to a separate activation to be valid for traveling list of activated days in case the entire ticket is not activated the day is given by the number of days from the first day of validity 0 = first day of validity
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
This field, when unset, defaults to the following value: second
servicelevel code according to leaflet 918.1 to encode other products (e.g. PREMIUM, ...)
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
2
carriers involved in the transport (RICS codes) the indication of carriers is mandatory on international routes, they can be listed here but can also be included in viaDetails
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
list of service brands for which the ticket is valid in case the included service brands are listed all other brands are excluded service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
list of service brands for which the ticket is not valid service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
additional included open tickets e.g. to include local city traffic on parts of a the route
in case the luggage restrictions are general and do not depend on the ticket type they should not be included
included or excluded transport modes code list: EN 1545-1 (transport type code)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
31
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
31
data for passes included are the data defined in:
This sequence contains the following fields:
reference to this passdata. reference is optional, in case it is given it must be given in numeric or alphanumeric format
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product code list defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
type of the pass, code list provided by the product owner in case of Eurail:
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
250
literal name of the pass
This field, when unset, defaults to the following value: second
begin of validity (local time). number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes).
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
end of validity (local time). number of days from valid from day, 0 = valid on valid-from-date
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
in case the valid until time is not provided the valid until time is 23.59 (local time)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler. offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). should be omitted in case it is the same as for departure.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
additional validity periods and excluded time ranges
max number of days of validity in case the valid from day is open
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
max number of possible trips to be activated
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
250
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
250
here it is possible to list the activated days of the ticket: day the ticket is activated. The activation is valid from 00:00 to 23:59 in the time zone of the current location of the traveler. thereby the activation might include more or less that 24 hours in case time zone borders are crossed. travel days of a ticket might be subject to a separate activation to be valid for traveling. list of activated days in case the entire ticket is not activated. the day is given by the number of days from the first day of validity. 0 = first day of validity
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
included countries, code table according to UIC leaflet 918.9
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
250
included carriers (RICS codes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
excluded carriers (RICS codes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
region description to cover local zones
This sequence contains the following fields:
begin of time range (local time). number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes).
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
end of time range (local time). number of days from valid from day, 0 = valid on valid-from-date.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
in case the valid until time is not provided the valid until time is 23.59 (local time)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler. offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). should be omitted in case it is the same as for departure.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
included carriers (RICS codes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
excluded carriers (RICS codes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brand: code list uic.org/service-brand-code-list.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This field, when unset, defaults to the following value: boarding
This sequence contains the following fields:
This sequence contains the following fields:
number of days from issuing date (local date)
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
local time. in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes).
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
number of days from valid from day, 0 = valid on valid from date
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler. offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). should be omitted in case it is the same as for departure.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
This sequence contains the following fields:
local time
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
local time
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
data for vouchers. included are quite basic further study is required.
This sequence contains the following fields:
reference to this voucher data, reference is optional, in case it is given it must be given in numeric or alphanumeric format
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product code list defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
begin / end of validity in local date wherever the traveler is located.
This type is constrained in the following way:
The value must be greater than or equal to:
2016
The value must be less than or equal to:
2269
number of the day in the year (1.1. = 1)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
number of year
This type is constrained in the following way:
The value must be greater than or equal to:
2016
The value must be less than or equal to:
2269
number of the day in the year (1.1. = 1)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
type of the voucher, code list defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
data for FIP tickets. included are data from the FIP ticket layout.
This sequence contains the following fields:
reference to this fip ticket, reference is optional, in case it is given it must be given in numeric or alphanumeric format
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product code list defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
begin / end of validity in local date time wherever the traveler is located. number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
last day of validity. number of days from valid from day, 0 = first day of validity
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
activated days: list of days for which the ticket is valid in local date wherever the traveler is located. the day is given by the number of days from the first day of validity. 0 = first day of validity.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
included carriers
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
number of travel days allowed
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
200
travel class
This field, when unset, defaults to the following value: second
data station passage and access. ticket used to enter, exit or pass a station without traveling by train. E.g. for staff working in a station.
This sequence contains the following fields:
reference to this station data, reference is optional, in case it is given it must be given in numeric or alphanumeric format
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product code list defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
code table used to encode he stations
This field, when unset, defaults to the following value: stationUIC
list of station where the passage is allowed
station names
list of areas in a station where the access is allowed
area names
begin of validity in local date and time of the station. number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes).
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
number of days from valid from day, 0 = first day of validity
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). should be omitted in case it is the same as for begin of validity (might be different in case of changes to summer time)
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
number of days for station passage in case the number of days is limited and less that the validity period.
data for customer cards included are data from:
note: customer data are included in the traveler data structure
This sequence contains the following fields:
customer details. optional, as there might be an anonymous cards.
card id might be numerical or alphanumerical
begin / end of validity in local date wherever the traveler is located. begin of validity time is 00:00
This type is constrained in the following way:
The value must be greater than or equal to:
2016
The value must be less than or equal to:
2269
number of the day in the year (1.1. = 1)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
number of year from valid from year onwards
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
250
This field, when unset, defaults to the following value:
0
number of the day in the year (1.1. = 1)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
code of the card type code list defined by the issuer
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
1000
readable description of the card type
customer status code
50 - code table of the card issuer
readable customer status "e.g. gold",
list of included services,
50 code list of the issuer
data for customer cards included are data from:
This sequence contains the following fields:
booking reference to this parking booking, reference is optional, in case it is given it must be given in num or IA5
parking date in time zone of the parking. validity is the whole day depending on opening hours of the parking facility. number of days from the issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
370
number of days from the from parking date in case it is different from that date.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product code list defined by the product owner.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
code needed to access the parking lot
This field, when unset, defaults to the following value: stationUIC
in case the parking ground is associated with a station
data for countermarks issued with group tickets included are data from:
This sequence contains the following fields:
reference to this countermark, reference is optional, in case it is given it must be given in num or IA5.
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product codelist defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
reference of the group ticket
sequential number of the countermark
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
200
total number of countermarks
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
200
name of the group
This field, when unset, defaults to the following value: stationUIC
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
description for manual evaluation in case structured data are not available
specification of the ordered sequence of valid regions
ticket includes the return trip
retrun route description. can be omitted if it is identical to the inversed outbound validRegion sequence.
date/time validity in local time of the location where the journey starts. number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel. if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory. times to be shown on a ticket should always be the local times.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
date/time validity in local time of the location where the journey ends. number of days from valid-from date, 0 = valid until day is equal to the first day of validity.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel. if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory. times to be shown on a ticket should always be the local times. should be omitted in case it is the same as for departure.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
This field, when unset, defaults to the following value: second
valid carriers
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brands where the ticket is valid in case this list is provided the ticket is invalid on all other service brands service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brands where the ticket is not valid in case this list is provided the ticket is valid on all other service brands
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
Generic extension element.
The value of 'extensionId' describes how 'extensionData' is encoded:
Others values are reserved for future UIC use and shall not be used.
This sequence contains the following fields:
included open ticke for a part of the travel (e.g. local city trafic)
This sequence contains the following fields:
organization responsible for the product definition. (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
product id to identify the issued product codelist defined by the product owner
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
65535
issuer code using the default code table of the product owner (today used e.g. by VDV)
authorization id provided to the issuer by the poroduct owner (today used e.g. by VDV)
regional validity data
This field, when unset, defaults to the following value: stationUIC
specification of the ordered sequence of valid regions, ordered in the direction of travel
date/time validity in local time of the location where the journey starts. number of days from issuing date.
This type is constrained in the following way:
The value must be greater than or equal to:
-367
The value must be less than or equal to:
700
This field, when unset, defaults to the following value:
0
in case the valid from time is not provided the valid from time is 00.00 (local time). in case UTC offset is provided (NOT RECOMMENDED) the local date time in the time zone of validity region. The region where the ticket is valid must not cover more than one time zone. in case no UTC offset is provided (RECOMMENDED) the local date time in the time zone of the current location of the traveler.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel. if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory. times to be shown on a ticket should always be the local times.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
date/time validity in local time of the location where the journey ends. number of days from valid-from date, 0 = valid until day is equal to the first day of validity.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
This field, when unset, defaults to the following value:
0
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes). the UTC offset can be used to calculate the duration of the travel. if UTC offset is used in control devices the usage of UTC offset has to be agreed bilateral to be mandatory. times to be shown on a ticket should always be the local times. should be omitted in case it is the same as for departure.
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
travel class to be given in case it differs from the class of the main ticket
servicelevel code according to leaflet 918.1 to encode other products (e.g. PREMIUM, ...) to be provided in case it differs from the main ticket
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
2
valid carriers (RICS codes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brands where the ticket is valid. in case this list is provided the ticket is invalid on all other service brands. service brand: code list uic.org/service-brand-code-list.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brands where the ticket is not valid. in case this list is provided the ticket is valid on all other service brands.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
included or excluded transport modes code list: EN 1545-1 (transport type code)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
31
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
31
tariff data for open tickets information included are:
This sequence contains the following fields:
number of passengers using the tariff
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
200
This field, when unset, defaults to the following value:
1
type indication youth, adult, senior,..
age restrictions of the tariff
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
64
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
128
named traveler list. link to the traveler in case the travelers have to be named (e.g. Eurail passes) the number indicates the position in the traveler list starting from 1
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
254
restriction on country of residence. this tariff is restricted by the country of residence given in the traveler data (e.g. Eurail tickets are not valid in the contry of residence).
section in case the tariff applies to a part of the route only
details on series according to leaflet 108.1
tariff code
tariff description
reduction cards applied (incl. discount cards, loyalty cards relevant for the tariff)
This sequence contains the following fields:
data related to tariffs based on series according UIC leaflet 108.1. supplying carrier according to UIC leaflet 108.1 (RICS code).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
offer identifier of the carrier according to UIC leaflet 108.1
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
99
series of the carrier according to UIC leaflet 108.1
This sequence contains the following fields:
This field, when unset, defaults to the following value: stationUIC
IA5 or Num not both.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
IA5 or Num not both.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
customer card reference
This sequence contains the following fields:
issuer of the card. (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
Name of the card e.g. "VISA-CARD"
type of the card, code list defined by the issuer
in case only the leading part of the card number is provided
in case only the trailing part of the card number is provided
This sequence contains the following fields:
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
3
customer id might be numerical or alphanumerical
date of birth
This type is constrained in the following way:
The value must be greater than or equal to:
1901
The value must be less than or equal to:
2155
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
12
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
31
indicates the ticket holder/group leader in case of groups
country of residence (numeric ISO country code). to be used in case there product restrictions on the country of residence (e.g. Eurail passes)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
This sequence contains the following fields:
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
customer status "gold"
This sequence contains the following fields:
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
description for manual evaluation in case structured data are not available
specification of the ordered sequence of valid regions for the return trip
regional validity of an open ticket specification of the regional validity.
The value of this choice may be one of the following:
train link data includes a restriction of an open ticket valid only on a specific train and date on a part of the route
This sequence contains the following fields:
local date at the station where the train link starts (fromStation). days from the issuing date onwards.
This type is constrained in the following way:
The value must be greater than or equal to:
-1
The value must be less than or equal to:
500
time in minutes, local time at the station where the train link starts
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
offset in units of 15 minutes from local time to UTC (UTC = local + offset * 15 Minutes).
This type is constrained in the following way:
The value must be greater than or equal to:
-60
The value must be less than or equal to:
60
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
regional validity using a set of lines
This sequence contains the following fields:
local service provider / carrier within the zone (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
ids of the valid lines known by the local carriers on that line
This field, when unset, defaults to the following value: stationUIC
in case the line must be entered via a specific station (e.g. local city traffic at the end of a journey starting from the main train station)
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
code of the local city in case the line is part of regional city transport. code list of the local carrier.
regional validity in a zone
This sequence contains the following fields:
local service provider / carrier within the zone (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This field, when unset, defaults to the following value: stationUIC
in case the zone must be entered via a specific station (e.g. local city traffic at the end of a journey starting from the main train station).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
in case the zone must be left via a specific station (e.g. local city traffic at the beginning of a journey terminating at the main train station).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
code of the local city in case the zone is part of regional city transport code list of the local carrier.
ids of the valid zones known by the local carriers in that zone
binary encoding of zones, encoding specification provided by the local service provider.
EU NUTS code for a region.
via station includes a description of of the route by via stations. Via stations follow the description in leaflet 108.1: via stations can e mandatory to pass (but there does not need to be a train stop at this stations): visible route description: "station" there can be a list of alternative routes: visible route description: "(station1/station2)" there can also be alternative routes: "(station1station2/station3station4)" although the definition in 108.2 is not very precise on this option
This sequence contains the following fields:
This field, when unset, defaults to the following value: stationUIC
mandatory via station
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
9999999
list of alternative routes, one of these has to be taken
list of stations along the route
carrier responsible for the transport starting at this station (RICS-Code). in case the carrier is included here it might be omitted in the carrier list of the region data.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
the route id as series number as defined in 108.1 data
route id of the route code list defined by the carrier on that route
service brands valid for the route in case this list is provided the ticket is invalid on all other service brands service brand: code list uic.org/service-brand-code-list
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
service brands valid for the route in case this list is provided the ticket is valid on all other service brands
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
This sequence contains the following fields:
TokenType provides an additional identifier known use cases
This sequence contains the following fields:
provider of the token
in case the provider has multiple tokens
TicketLinkType is used to define a link from the ticket in the bar code to another ticket (requirement from Eurail) use cases
This sequence contains the following fields:
data to reference the external ticket. reference must be given in numeric or alphanumeric format.
in case the ticket can also be identified via the issuer PNR (= Ticket Reference Number).
organization responsible for the product definition (RICS Code / proprietary code in case no RICS code is defined, proprietary codes must ensure to be unique).
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
32000
type of linked ticket
This field, when unset, defaults to the following value: openTicket
type of link
This field, when unset, defaults to the following value: issuedTogether
code table used fort station codes defines the code table used e.g. to define station code
The value of this enumeration may have one of the following values:
Value:
0
standard UIC station code from MERITS (UIC country code + 5 digit local code)
Value:
1
standard UIC station code for reservation
Value:
2
future standard ERA station code
Value:
3
local carrier code list. e.g. in case of stations / stops of non-railways stops (city traffic)
Value:
4
non standard code to be used within the issuer eco system only not applicable for multi carrier travel documents or in case issuer and carrier are different
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
Value:
4
Value:
5
Value:
6
Value:
7
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
place data corresponding to leaflet 918.1 placeString = place number ranges in case of groups
This sequence contains the following fields:
printable place string ("15-18, 21, 22" )
printable place description
individual places
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
254
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
Value:
4
Value:
5
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
Value:
4
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
Value:
4
Value:
5
Value:
6
Value:
7
Value:
8
Value:
9
Value:
10
Value:
11
sleeper compartment types corresponding to leaflet 918.1
This sequence contains the following fields:
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
This field, when unset, defaults to the following value: family
compartment details corresponding to leaflet 918.1
This sequence contains the following fields:
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
99
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
99
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
99
This field, when unset, defaults to the following value: unspecified
luggage restrictions the basis for these data is week: SCIC mentions a maximum of three pieces of hand luggage but does not includes a definition of hand luggage SCIC refers to special conditions on registered luggage, but SCIC NRT does not contain definitions on that and UIC 108.1 does not contain data structures for luggage
This sequence contains the following fields:
allowed hand luggage pieces on this ticket (3 = default in current NRT tariff)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
This field, when unset, defaults to the following value:
3
allowed hand luggage pieces on this ticket (3 = default in current NRT tariff)
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
This field, when unset, defaults to the following value:
1
This sequence contains the following fields:
id of the additional registered luggage
maximum weight in kg
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
99
sum of length with and height in cm
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
300
generic type for geo coordinates
This sequence contains the following fields:
This field, when unset, defaults to the following value: milliDegree
This field, when unset, defaults to the following value: wgs84
separate hemishpere flag reduces the data size
This field, when unset, defaults to the following value: east
separate hemishpere flag reduces the data size
This field, when unset, defaults to the following value: north
This sequence contains the following fields:
logitude difference to a reference point
latitude difference to a reference point
The value of this enumeration may have one of the following values:
Value:
0
WGS 84 standard system.
Value:
1
(outdated) GRS 80 coordinate system
The value of this enumeration may have one of the following values:
Value:
0
approx. 11 cm on earth surface
Value:
1
1 / 10000 degree is approx. 11 meter on earth surface
Value:
2
approx 110 meter on earth surface
Value:
3
Value:
4
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
The value of this enumeration may have one of the following values:
Value:
0
Value:
1
Value:
2
Value:
3
Value:
4
Value:
5
Value:
6
Value:
7
Value:
8
The value of this enumeration may have one of the following values:
Value:
0
Value:
1