From 43222a775451e3efb1aadd34a56901b25ce18541 Mon Sep 17 00:00:00 2001 From: Thomas Kling Date: Thu, 29 Sep 2022 09:14:09 +0200 Subject: [PATCH 1/9] Extensions of LineInformation, StopInformation and TripInformation Structure plus Number of Error Messages in DMS reduced from 10 to 0. --- IBIS-IP_CustomerInformationService_V2.4.xsd | 239 +++++ IBIS-IP_DeviceManagementService_V2.3.xsd | 463 ++++++++ IBIS-IP_common_V2.4.xsd | 1061 +++++++++++++++++++ 3 files changed, 1763 insertions(+) create mode 100644 IBIS-IP_CustomerInformationService_V2.4.xsd create mode 100644 IBIS-IP_DeviceManagementService_V2.3.xsd create mode 100644 IBIS-IP_common_V2.4.xsd diff --git a/IBIS-IP_CustomerInformationService_V2.4.xsd b/IBIS-IP_CustomerInformationService_V2.4.xsd new file mode 100644 index 0000000..e44f89c --- /dev/null +++ b/IBIS-IP_CustomerInformationService_V2.4.xsd @@ -0,0 +1,239 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + if vehicle is not on a trip and no tripinformation is available occurrence typically is 0 + if vehicle is on a trip or knows the next trip to run occurrence typically is 1 + if vehicle is on a trip and also knows the subsequent trip that info can be provided in the second TripInformation so occurrence is 2 + + + + + Index of the Stoppoint in the Stopsequence, which is the next Stop + + + + + + Global display content - this content should be used if no stop specific display content is available + please make sure that the global display content and the stop specific content are provided for the same DisplayContentRefs. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Index of the Stoppoint in the Stopsequence, which is the next Stop in the first trip + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Contains the information about route deviation + + + + + Information on DoorState + + + + + Is the Emergency-Button pressed? + + + + + Is the Stop-Button inside the vehicle pressed? + + + + + Defines the exit side + + + + + Gives information, if the vehicle is moving forward, default value is "true" + + + + + DEPRECATED, is of type VehicleModeEnumeration. MyOwnVehicleMode SHOULD BE USED INSTEAD + + + + + Mode- and Submode information vehicle I am in - in accordance with Netex + + + + + Gives information, if the loud speaker is activated for a passenger announcement + + + + + Gives information, if the stopInformation inside the vehicle is in active or in passiv state (intentionally, e.g. due to "route left) + + + + + + diff --git a/IBIS-IP_DeviceManagementService_V2.3.xsd b/IBIS-IP_DeviceManagementService_V2.3.xsd new file mode 100644 index 0000000..5fe444c --- /dev/null +++ b/IBIS-IP_DeviceManagementService_V2.3.xsd @@ -0,0 +1,463 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warnings and errors only, no state messages + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unique id generated by the controller to identify an update job + + + Timestamp used for GetUpdateHistory and RetrieveUpdateState responses and for logging + + + URL from which the device shall download the update file + + + Optional checksum of update file + + + Optional size of update file + + + + + + + + + + + + + + + + + + + + + + + + + + Timestamp given by operation InstallUpdate + + + Current status of update + + + Optional device specific update log + + + + + + + + + + + + + + Minimum requirement for any device allowing updates is an update history depth of 1, + i.e. history shall contain at least the last update performed (regardless of its result), if there was any. + + + + + + + + Timestamp given by operation InstallUpdate + + + URL from which the device downloaded the update file + + + Status of update. Typically final status (InstallationSuccessfull or InstallationFailed) + + + Optional list of updated components + + + Optional device specific update log + + + + + + + + + + + + + Status of update on its finalization + + + + + + + + + + Types of checksum + + + Cyclic redundancy check, 32-bit + Message digest algorithm 5, 128-bit + Secure hash algorithm, 256-bit + + + + + Information about the result of InstallUpdate + + + Update will be performed + URL type has been rejected, e.g. FTP may not supported by some devices + No updates are possible + Update has to be postponed + + + + + Information about the current status of update + + + Update in progress + Device has to be restarted by operation RestartDevice + Specified update file could not be downloaded from URL + Specified update file is not usable + State of device firmware already as required + Update failed e.g. due to memory write error + Update successfully completed + + + + + + Information on named subdevice + + + + + Used to identify subdevice + + + + + Information on subdevice + + + + + + + + + + + + + + + + + + + + + + + + + + + Status information of named subdevice + + + + + Used to identify subdevice + + + + + Status information of subdevice + + + + + + + Error messages of named subdevice + + + + + Used to identify subdevice + + + + + Warnings and errors only, no state messages + + + + + + + + + + + diff --git a/IBIS-IP_common_V2.4.xsd b/IBIS-IP_common_V2.4.xsd new file mode 100644 index 0000000..c76badc --- /dev/null +++ b/IBIS-IP_common_V2.4.xsd @@ -0,0 +1,1061 @@ + + + + + + + + + Structure for decscribing the informations for an additional announcement + + + + + Reference to the Announcement in the schedule data + + + + + Text of the Announcement + + + + + Text of the Announcement for a text-to-speech-system + + + + + + true, if the additional annoucement should be pronounced immiditaley + + + + + period in which the addional announcement should be played + + + + + describes a specific point, where the addional announcement should be played + + + + + + + + Structure for decscribing the informations for an regular announcement + + + + + Reference to the Announcement in the schedule data + + + + + Text of the Announcement + + + + + Text of the Announcement for a text-to-speech-system + + + + + + + Structure for describing an area at the stop point for detecting the right stop position + + + + + Distance before the defined Stoppoint, where the detection area begins, value in [m] + + + + + Distance behind the defined Stoppoint, where the detection area begins, value in [m] + + + + + + + Structure for describing a beacon point + + + + + Reference to the beacon point in the schedule data + + + + + Code of the beacon point + + + + + Shortname of the beaon point + + + + + Text, which gives some additional information on the beacon point + + + + + + + + + Length of the bytearray of applikationdata + + + + + Applikationdata from Card as Byte-Array + + + + + + + + + + Length of the bytearray of ticketdata + + + + + Ticketdata from Card as Byte-Array + + + + + + + + + + + + + + Structure for describing a connection + + + + + StopPoint, where the connection should take place (from planning system) + + + + + StopPoint-referenced connection-reference + + + + + Describes the kind of connection + + + + + Structure for desccribing the information which is shown on a head- or sidesign + + + + + Platform, on which the connection should take place + + + + + Describes the status of the connection + + + + + Describes the mode of the pick-up vehicle, DEPRECATED !, THE ConnectionMode SHOULD BE USED INSTEAD + + + + + Mode- and Submode information of the pick-up vehicle in accordance with Netex + + + + + Information, at which time the leaving vehicle will depart based on realtime information + + + + + Information, at which time the leaving vehicle is planned to depart + + + + + + + Structure for describing data-versions + + + + + Kind of data + + + + + Versionreference of the data + + + + + + + + + + + + Structure for describing destination information + + + + + Reference to the destination-information in the schedule-data + + + + + Text of the destination + + + + + Shorttext of the destination if there is limited space + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Structure for describing the information for a headsign or a sidesign + + + + + Reference to the display content information in the schedule data + + + + + Information on the line, which should be displayed + + + + + Information on the destination, which should be displayed + + + + + Information on the via points which should be displayed + + + + + Additional Information Text, which could be displayed, e.g. "Extra Ride", "Express", ... + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + The run number (Kurs-Nummer) the trip is operated + + + + + Group for Display-Information if there is more than one content at the same time + + + + + + + + + unique ID for the farezone + + + + + + + + + + + + code according EN 1545 + + + + + text according EN 1545 + + + + + + + Structure for describing a GNSS-Point + + + + + Reference to the point in schedule data + + + + + + + + + + Structure for describing a GNSS-Point + + + + + + + + + + + Reference to the stoppoint from the planning system + + + + + + + + + + + + Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation + + + + + + + + + + + + + + + + identifier of a symbol number , which is used by displays see LINIEN_CODE in VDV 452 chapter 9.7.2 REC_LID + + + + + + + + + + + + Name of the Service or Device, which sends the message, which has to be logged + + + + + + + + + + + ... of the ErrorMessage + + + + + + + + + + + + + + + + + + aus REC-SEL bzw. REC_SEL_ZP der VDV 452 + + + + + + + + + In Analogie zu REC_ORT aus VDV 452 + + + + + + Point, where specific GNSS-Information is provided, "GNSS-Solution" for the Beacon-Points, analogue to REC_OM from VDV 452 + + + + + + Point, where Information for TrafficSignalPriorisation is provided + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + StopIndex on current trip + + + + + Reference to the stoppoint from the planning system + + + + + + + + + + This Value is needed for the demonstration at the SSB + + + + + Soll-Abstand zwischen den Haltestellen + + + + + Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation + + + + + + + + + + StopIndex on current trip + + + + + Reference to the stoppoint from the planning system + + + + + + + + + + + A resolution of 30s is recommended, for the display it is recommended to show the arrival time in minutes. + + + + + + + This Value is needed for the demonstration at the SSB + + + + + Soll-Abstand zwischen den Haltestellen + + + + + Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + List of StopPoints; with additional information + + + + + Information of the location state + + + + + Delay in seconds. Early times are shown as negative values. + + tbd: what happens, if this value isn't set + + + + + + + + + + + + + + + + not StopPointAnnouncements; additional announcements; e.g. of the operator or dispatcher + + + + + The direction of the route, 1->forward 2->backwards and 0->UNDEFINED + + + + + The run number (Kurs-Nummer) the trip is operated + + + + + The pattern number (Linienfahrweg-Nummer) the trip is operated + + + + + The path destination number (RoutenZiel-Nummer) the trip is operated + + + + + + + + + + + + + Time, at which the trip is starting + + + + + + + In Analogie zu LID-Verlauf aus VDV 452 + + + + + + + + + + + + + + + + + + + + + Structure for describing a via point on journey. + + + + + + The identifier of the via place in the journey; used to help identify the vehicle journey on arrival boards. + + + + + The name of the via place in the journey; used to help identify the vehicle to the public. + + + + + The short name of the via place in the journey; used to help identify the vehicle to the public. + + + + + Value, which defines a priority to select a number of via points, if not all via points can be shown + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + For compatibility reasons, this structure is now a sequence of members, all of which are optional - of course, at least one member should be included in meaningful data. + + + + + + If the service returns a heartbeat value and it is not 0, the subscriber can expect that the service will send data at least every heartbeat seconds. This heartbeat can be used to monitor the connection quality by the client. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Value, which allows to decide which Information is shown, if there is not enough time to show all + + + + + If more than one Sign-Information is given, you need to know + + + + + Time-Value, which defines the part of the Periodtime in which this Sign-Information should be shown + + + + + + + a combined Mode and SubMode information in accordance with Netex "netex_submode_version.xsd" + + + + + + + + + + + + + From 80024780e7fc6b661801a25258e6c0d92322e51c Mon Sep 17 00:00:00 2001 From: ThomasKling <54571682+ThomasKling@users.noreply.github.com> Date: Mon, 7 Nov 2022 12:50:57 +0100 Subject: [PATCH 2/9] Update IBIS-IP_common_V2.4.xsd --- IBIS-IP_common_V2.4.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/IBIS-IP_common_V2.4.xsd b/IBIS-IP_common_V2.4.xsd index c76badc..b893a1a 100644 --- a/IBIS-IP_common_V2.4.xsd +++ b/IBIS-IP_common_V2.4.xsd @@ -448,7 +448,7 @@ - + From d04ca8f62f7a78a17cb23c081242f6842ef3991a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dirk=20Wei=C3=9Fer?= Date: Thu, 5 Jan 2023 08:06:58 +0100 Subject: [PATCH 3/9] Add files via upload --- IBIS-IP_AnalogRadioService_V2.4.xsd | 42 +++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 IBIS-IP_AnalogRadioService_V2.4.xsd diff --git a/IBIS-IP_AnalogRadioService_V2.4.xsd b/IBIS-IP_AnalogRadioService_V2.4.xsd new file mode 100644 index 0000000..48fb303 --- /dev/null +++ b/IBIS-IP_AnalogRadioService_V2.4.xsd @@ -0,0 +1,42 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From 57c17bc4e1191cd49d3a9139ca02cd5de04d56ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dirk=20Wei=C3=9Fer?= Date: Thu, 5 Jan 2023 08:07:34 +0100 Subject: [PATCH 4/9] Add files via upload --- IBIS-IP_VideoRecordingService_V2.4.xsd | 68 ++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 IBIS-IP_VideoRecordingService_V2.4.xsd diff --git a/IBIS-IP_VideoRecordingService_V2.4.xsd b/IBIS-IP_VideoRecordingService_V2.4.xsd new file mode 100644 index 0000000..07ff2c4 --- /dev/null +++ b/IBIS-IP_VideoRecordingService_V2.4.xsd @@ -0,0 +1,68 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file From dcdd74b3af655384614e38b6da5d028913e93308 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dirk=20Wei=C3=9Fer?= Date: Fri, 6 Jan 2023 08:06:23 +0100 Subject: [PATCH 5/9] Commons and Enums updated Changes in Common and Enumerations due to AnalogRadioService --- IBIS-IP_Enumerations_V2.4.xsd | 679 +++++++++++++++++++++ IBIS-IP_common_V2.4.xsd | 1051 +++++++++++++++++++++++++++++++++ 2 files changed, 1730 insertions(+) create mode 100644 IBIS-IP_Enumerations_V2.4.xsd create mode 100644 IBIS-IP_common_V2.4.xsd diff --git a/IBIS-IP_Enumerations_V2.4.xsd b/IBIS-IP_Enumerations_V2.4.xsd new file mode 100644 index 0000000..654093b --- /dev/null +++ b/IBIS-IP_Enumerations_V2.4.xsd @@ -0,0 +1,679 @@ + + + + + + + + + Information whether a connection will rest protected + + + + + + + + + + Value, which is necessary for distinction between an Interchange and a Connection + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information on the state of the doors in a vehicle + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information on the ExitSide (sic!) + + + + + + + + + + + Information on the GNSS-Coordinate-System + + + + + + + + + + + + + + + + Information on the GNSS-Quality + + + + + + + + + + + + Information on the type of GNSS + + + + + + + + + + + + + + + Information on the kind of a trip + + + + + + + + + + Information on the location in a very general way + + + + + + + + + + + + + + + + + + Information whether the vehicle is onroute or offroute + + + + + + + + + + Information on the general direction of a route + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the result of ticket validation + + + + + + + + + + + + + + + + + + + + + + Information about trip state, + EmptyRun: trips is selected but has not yet started ( e.g. drive from depot to first stop point ) + OnTrip: on trip , + OffTrip: trip has ended there is no next trip yet, ( e.g. drive to the depot ) + TripBreak: trip has already started but there is a break now it will be continued ( e.g. driver break), + OffDuty: no trip, bus parked ( e.g. driver has logged of, OBU still running ) + + + + + + + + + + + + + + compliant with NETEX + + + + + + + + + + + + + + + + + + compliant with NETEX + + + + + + + + + + + PT Transport Sub Modes. + + + + + + + + + + + + + + + + Non PT Road Submodes. + + + + + + + + + + TPEG pti02 Rail submodes loc13. + See also See ERA B.4.7009 - Name: Item description code. + + + + + Values for Rail MODEs of TRANSPORT: TPEG pti_table_02, train link loc_table_13. + + + + + + + See ERA B.4.7009 - Name: Item description code: (8 high speed train). Long distance train formed by a unit capable for high speed running on high speed or normal lines most modern train unit + + + + + See ERA B.4.7009 - Name: Item description code: . (12 suburban) Regional train organised by the regional government public transport in and around cities, running on its own freeways underground or overground, operational running with signals + + + + + See ERA B.4.7009 - Name: Item description code. (11 Regional) Regional train organised by the regional government even if formed by a unit capable for high speed running on high speed lines + + + + + See ERA B.4.7009 - Name: Item description code: (10 Interregional) Regional train running in more than one region. + + + + + See ERA B.4.7009 - Name: Item description code: (9 Intercity). Long distance train formed by a unit capable for high speed or not running on high speed or normal lines modern train unit high quality service restricted stopping pattern + + + + + + + + See ERA B.4.7009 - Name: Item description code: (14 Motor rail) Service transporting passenger's motor vehicle passengers are admitted either with vehicle only or with or without vehicle Service mode + + + + + See ERA B.4.7009 - Name: Item description code: (16 Historic train). + + + + + + + + + + See ERA B.4.7009 - Name: Item description code: (15 Mountain train) Local train adapted for running in mountain railway lines. + + + + + + + + TPEG pti03 Coach submodes. + + + + + Values for Coach MODEs of TRANSPORT: TPEG pti_table_03. + + + + + + + + + + + + + + + + + + + TPEG pti04 Metro submodes. + + + + + Values for Metro MODEs of TRANSPORT: TPEG pti_table_04. + + + + + + + + + + + + + TPEG pti05 Bus submodes. + + + + + Values for Bus MODEs of TRANSPORT: TPEG pti_table_05, col_table_10. + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti06 Tram submodes. + + + + + Values for Tram MODEs of TRANSPORT: TPEG pti_table_06, col_table_12. + + + + + + + + + + + + + + + + TPEG pti07 Water submodes. + + + + + Values for Water MODEs of TRANSPORT: TPEG pti_table_07. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti08 Air submodes. + + + + + Values for Air MODEs of TRANSPORT: TPEG pti_table_08. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TPEG pti09 Telecabin submodes. + + + + + Values for Telecabin MODEs of TRANSPORT: TPEG pti_table_09, col_table_14. + + + + + + + + + + + + + + + + TPEG pti10 Funicular submodes. + + + + + Values for Funicular MODEs of TRANSPORT: TPEG pti_table_10. + + + + + + + + + + + + + TPEG pti11 Taxi submodes. + + + + + Values for Taxi MODEs of TRANSPORT: TPEG pti_table_11. + + + + + + + + + + + + + + + + + + TPEG pti12 SelfDrive submodes. + + + + + Values for SelfDrive MODEs of TRANSPORT: TPEG pti_table_12. + + + + + + + + + + + + + \ No newline at end of file diff --git a/IBIS-IP_common_V2.4.xsd b/IBIS-IP_common_V2.4.xsd new file mode 100644 index 0000000..62d1206 --- /dev/null +++ b/IBIS-IP_common_V2.4.xsd @@ -0,0 +1,1051 @@ + + + + + + + + + Structure for decscribing the informations for an additional announcement + + + + + Reference to the Announcement in the schedule data + + + + + Text of the Announcement + + + + + Text of the Announcement for a text-to-speech-system + + + + + + true, if the additional annoucement should be pronounced immiditaley + + + + + period in which the addional announcement should be played + + + + + describes a specific point, where the addional announcement should be played + + + + + + + + Structure for decscribing the informations for an regular announcement + + + + + Reference to the Announcement in the schedule data + + + + + Text of the Announcement + + + + + Text of the Announcement for a text-to-speech-system + + + + + + + Structure for describing an area at the stop point for detecting the right stop position + + + + + Distance before the defined Stoppoint, where the detection area begins, value in [m] + + + + + Distance behind the defined Stoppoint, where the detection area begins, value in [m] + + + + + + + Structure for describing a beacon point + + + + + Reference to the beacon point in the schedule data + + + + + Code of the beacon point + + + + + Shortname of the beaon point + + + + + Text, which gives some additional information on the beacon point + + + + + + + + + Length of the bytearray of applikationdata + + + + + Applikationdata from Card as Byte-Array + + + + + + + + + + Length of the bytearray of ticketdata + + + + + Ticketdata from Card as Byte-Array + + + + + + + + + + + + + + Structure for describing a connection + + + + + StopPoint, where the connection should take place (from planning system) + + + + + StopPoint-referenced connection-reference + + + + + Describes the kind of connection + + + + + Structure for desccribing the information which is shown on a head- or sidesign + + + + + Platform, on which the connection should take place + + + + + Describes the status of the connection + + + + + Describes the mode of the pick-up vehicle, DEPRECATED !, THE ConnectionMode SHOULD BE USED INSTEAD + + + + + Mode- and Submode information of the pick-up vehicle in accordance with Netex + + + + + Information, at which time the leaving vehicle will depart based on realtime information + + + + + Information, at which time the leaving vehicle is planned to depart + + + + + + + Structure for describing data-versions + + + + + Kind of data + + + + + Versionreference of the data + + + + + + + + + + + + Structure for describing destination information + + + + + Reference to the destination-information in the schedule-data + + + + + Text of the destination + + + + + Shorttext of the destination if there is limited space + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Structure for describing the information for a headsign or a sidesign + + + + + Reference to the display content information in the schedule data + + + + + Information on the line, which should be displayed + + + + + Information on the destination, which should be displayed + + + + + Information on the via points which should be displayed + + + + + Additional Information Text, which could be displayed, e.g. "Extra Ride", "Express", ... + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + Additional Information Text, which is assigned project-specific + + + + + The run number (Kurs-Nummer) the trip is operated + + + + + Group for Display-Information if there is more than one content at the same time + + + + + + + + + unique ID for the farezone + + + + + + + + + + + + code according EN 1545 + + + + + text according EN 1545 + + + + + + + Structure for describing a GNSS-Point + + + + + Reference to the point in schedule data + + + + + + + + + + Structure for describing a GNSS-Point + + + + + + + + + + + Reference to the stoppoint from the planning system + + + + + + + + + + + + Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation + + + + + + + + + + + + + + + + identifier of a symbol number , which is used by displays see LINIEN_CODE in VDV 452 chapter 9.7.2 REC_LID + + + + + + + + + Name of the Service or Device, which sends the message, which has to be logged + + + + + + + + + + + ... of the ErrorMessage + + + + + + + + + + + + + + + + + + aus REC-SEL bzw. REC_SEL_ZP der VDV 452 + + + + + + + + + In Analogie zu REC_ORT aus VDV 452 + + + + + + Point, where specific GNSS-Information is provided, "GNSS-Solution" for the Beacon-Points, analogue to REC_OM from VDV 452 + + + + + + Point, where Information for TrafficSignalPriorisation is provided + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + StopIndex on current trip + + + + + Reference to the stoppoint from the planning system + + + + + + + + + + This Value is needed for the demonstration at the SSB + + + + + Soll-Abstand zwischen den Haltestellen + + + + + Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation + + + + + + + + + + StopIndex on current trip + + + + + Reference to the stoppoint from the planning system + + + + + + + + + + + A resolution of 30s is recommended, for the display it is recommended to show the arrival time in minutes. + + + + + + + This Value is needed for the demonstration at the SSB + + + + + Soll-Abstand zwischen den Haltestellen + + + + + Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + List of StopPoints; with additional information + + + + + Information of the location state + + + + + Delay in seconds. Early times are shown as negative values. + + tbd: what happens, if this value isn't set + + + + + + + + + + + + + + + + not StopPointAnnouncements; additional announcements; e.g. of the operator or dispatcher + + + + + The direction of the route, 1->forward 2->backwards and 0->UNDEFINED + + + + + The run number (Kurs-Nummer) the trip is operated + + + + + The pattern number (Linienfahrweg-Nummer) the trip is operated + + + + + The path destination number (RoutenZiel-Nummer) the trip is operated + + + + + + + + + + + Time, at which the trip is starting + + + + + + + In Analogie zu LID-Verlauf aus VDV 452 + + + + + + + + + + + + + + + + + + + + + Structure for describing a via point on journey. + + + + + + The identifier of the via place in the journey; used to help identify the vehicle journey on arrival boards. + + + + + The name of the via place in the journey; used to help identify the vehicle to the public. + + + + + The short name of the via place in the journey; used to help identify the vehicle to the public. + + + + + Value, which defines a priority to select a number of via points, if not all via points can be shown + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + For compatibility reasons, this structure is now a sequence of members, all of which are optional - of course, at least one member should be included in meaningful data. + + + + + + If the service returns a heartbeat value and it is not 0, the subscriber can expect that the service will send data at least every heartbeat seconds. This heartbeat can be used to monitor the connection quality by the client. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Value, which allows to decide which Information is shown, if there is not enough time to show all + + + + + If more than one Sign-Information is given, you need to know + + + + + Time-Value, which defines the part of the Periodtime in which this Sign-Information should be shown + + + + + + + a combined Mode and SubMode information in accordance with Netex "netex_submode_version.xsd" + + + + + + + + + + + + + From 0860c858d43012e9a22454b9a5ae428101d8c7bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dirk=20Wei=C3=9Fer?= Date: Thu, 1 Feb 2024 11:09:25 +0100 Subject: [PATCH 6/9] Update IBIS-IP_common_V2.4.xsd --- IBIS-IP_common_V2.4.xsd | 42 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/IBIS-IP_common_V2.4.xsd b/IBIS-IP_common_V2.4.xsd index 62d1206..752fd00 100644 --- a/IBIS-IP_common_V2.4.xsd +++ b/IBIS-IP_common_V2.4.xsd @@ -447,6 +447,21 @@ identifier of a symbol number , which is used by displays see LINIEN_CODE in VDV 452 chapter 9.7.2 REC_LID + + + Published line identification for the passenger. For displaying the line on all media such as line network maps, timetable printouts, passenger information on the internet, on signs, the stop displays, on the exterior and interior displays of the vehicles. + + + + + Specification of a xml formatted text to reference an symbol for special lines. Used as alternative to the LineSymbolCode. For example for displaying an airport symbol the following string could be used: airport + + + + + International line ID e.g. in Germany according to VDV433 DLID, internationally according to NeTEx. + + @@ -597,7 +612,9 @@ + + This Value is needed for the demonstration at the SSB @@ -657,6 +674,31 @@ + + + Short name of the stop in the planning program and ITCS. To identify a stop on media with limited display length, e.g. older interior displays, on-board computer or ticket printer terminal. + + + + + Stop number that is used throughout the transport association (PTA) for activation of ticket printers and ticket validators. This number is not necessarily unique and is only used for stops that are used productively. This number is not required for non-productive stops (e.g. depots, parking facilities, car parks). + + + + + Transport company-wide internal unique number of a stopping point in the network. + + + + + International stop ID e.g. in Germany according to VDV432 (DHID), internationally according to NeTEx, NAPTAN. + + + + + International stopping point ID e.g. in Germany according to VDV432 (DHID), internationally according to NeTEx, NAPTAN. + + From c2ff90731d1b51cf7d7b779497d1fd3a03929442 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dirk=20Wei=C3=9Fer?= Date: Thu, 1 Feb 2024 11:12:36 +0100 Subject: [PATCH 7/9] Update IBIS-IP_common_V2.4.xsd --- IBIS-IP_common_V2.4.xsd | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/IBIS-IP_common_V2.4.xsd b/IBIS-IP_common_V2.4.xsd index 752fd00..1946fd3 100644 --- a/IBIS-IP_common_V2.4.xsd +++ b/IBIS-IP_common_V2.4.xsd @@ -774,7 +774,17 @@ The path destination number (RoutenZiel-Nummer) the trip is operated - + + + + Unique block number per day of operational day. Used for logon on the vehicle in block operation. + + + + + International trip ID e.g. in Germany according to VDV433 (DFID), internationally according to NeTEx. + + From 0aa728aab47a7f13b6f36da415581d51592c4ca7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dirk=20Wei=C3=9Fer?= Date: Thu, 1 Feb 2024 11:16:27 +0100 Subject: [PATCH 8/9] Update IBIS-IP_Enumerations_V2.4.xsd Fixing Typo --- IBIS-IP_Enumerations_V2.4.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/IBIS-IP_Enumerations_V2.4.xsd b/IBIS-IP_Enumerations_V2.4.xsd index 654093b..2afed8c 100644 --- a/IBIS-IP_Enumerations_V2.4.xsd +++ b/IBIS-IP_Enumerations_V2.4.xsd @@ -72,7 +72,7 @@ - + @@ -676,4 +676,4 @@ - \ No newline at end of file + From 1be43b9209df5b6a5ee25a3bed2528977b06103e Mon Sep 17 00:00:00 2001 From: Tobias Huber Date: Mon, 2 Sep 2024 09:56:52 +0200 Subject: [PATCH 9/9] TicketValidationServce 2.4 should use enums 2.4 --- IBIS-IP_TicketValidationService_V2.4.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/IBIS-IP_TicketValidationService_V2.4.xsd b/IBIS-IP_TicketValidationService_V2.4.xsd index 291f415..34b18b8 100644 --- a/IBIS-IP_TicketValidationService_V2.4.xsd +++ b/IBIS-IP_TicketValidationService_V2.4.xsd @@ -1,7 +1,7 @@ - +