Difference between revisions of "User:Milan Wölke"

From wiki.railML.org
Jump to: navigation, search
Line 140: Line 140:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/categories/category
+
[[TT:timetable|<timetable>]]/[[TT:categories|<categories>]]/[[TT:category|<category>]]
  
 
|
 
|
Line 150: Line 150:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/annotations/annotation
+
[[TT:timetable|<timetable>]]/[[TT:annotations|<annotations>]]/[[TT:annotation|<annotation>]]
  
 
|
 
|
Line 160: Line 160:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/formationTT
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/formationTT
  
 
|
 
|
Line 170: Line 170:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/operatingPeriodRef
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/operatingPeriodRef
  
 
|
 
|
Line 180: Line 180:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT
  
 
|
 
|
Line 190: Line 190:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/times
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/times
  
 
|
 
|
Line 200: Line 200:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/connections
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/connections
  
 
|
 
|
Line 210: Line 210:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/connections/connection
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/connections/connection
  
 
|
 
|
Line 220: Line 220:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/connections/connection/annotationRef
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/connections/connection/annotationRef
  
 
|
 
|
Line 230: Line 230:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/statistics
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/statistics
  
 
|
 
|
Line 240: Line 240:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/sectionTT/runTimes
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/sectionTT/runTimes
  
 
|
 
|
Line 250: Line 250:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/stopDescription
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/stopDescription
  
 
|
 
|
Line 260: Line 260:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/stopDescription/stopTimes
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/stopDescription/stopTimes
  
 
|
 
|
Line 270: Line 270:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/ocpsTT/stopDescription/annotationRef
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/ocpsTT/stopDescription/annotationRef
  
 
|
 
|
Line 280: Line 280:
 
|-
 
|-
 
|
 
|
[[TT:timetable|<timetable>]]/trainParts/trainPart/annotationRef
+
[[TT:timetable|<timetable>]]/[[TT:trainParts|<trainParts>]]/[[TT:trainPart|<trainPart>]]/annotationRef
  
 
|
 
|

Revision as of 09:07, 17 March 2015

  1. railML® 3 use cases im Timetable-Schema


Use case / Anwendungsfall / Scénario d’utilisation:


Passenger information at stations/Fahrgastinformation am Bahnhof


Description / Beschreibung / Description


This use case describes the exchange of data between a system for providing passenger information at a railway station and a timetable planning system. The PIS allows for display of the current schedule including information about the current state of operation such as delays, cancelation or additional trains. In order to do so the schedule as published to the passenger for the current day of operation is necessary. The completeness of this timetable information limits the accuracy of the information available to the passenger by means of the PIS. The mandatory data can be limited to the services run on the current operation day, including all stops of a train with the according arrival and departure times. Additional information for can be provided to model blocks of services (can be used to increase accuracy of forecast information), planned interconnection with other services, planned construction sites with impact on the services, etc.


Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces


A PIS is a pure railML consumer.


Mandatory information imported from timetable system includes:

  • <train>
  • <trainPart>
  • <category>
  • <ocp>



Optionally imported information includes:

  • <track>
  • <formation>
  • <annotation>/<annotationRef>
  • <rostering>
  • <connection> (in order to provide and manage connection information for internal or external services)
  • <statistics>


If the topology is not imported from railML it is assumed that it is imported from a different source including an appropriate mapping to the ocp’s imported from railML.


Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML®

Mandatory: infrastructure

Optionally: rolling stock


Characterizing Data / Charakterisierung der Daten / Caractérisation des données


This section serves to specify the required data regarding certain aspects.


How often do the data change (update)?

yearly

regular changes

daily


How big are the data fragments to be exchanged (complexity)?

Huge - whole data set


Which views are represented by the data (focus)?

Mid term planning (eg. for yearly timetable disposition)

Short term planning (eg. for trackworks)

Passenger information


Which specific timetable data do you expect to receive/send (elements)?

Element

Mandatory

Remarks

Infrastructure/operationControlPoints/ocp

X

Used for referencing with the PIS topology

<timetable>/<timetablePeriods>/<timetablePeriod>

X


<timetable>/<operatingPeriods>/<operatingPeriod>

X


<timetable>/<categories>/<category>



<timetable>/<annotations>/<annotation>



<timetable>/<trainParts>/<trainPart>/formationTT



<timetable>/<trainParts>/<trainPart>/operatingPeriodRef

X


<timetable>/<trainParts>/<trainPart>/ocpsTT

X


<timetable>/<trainParts>/<trainPart>/ocpsTT/times

X


<timetable>/<trainParts>/<trainPart>/ocpsTT/connections



<timetable>/<trainParts>/<trainPart>/ocpsTT/connections/connection



<timetable>/<trainParts>/<trainPart>/ocpsTT/connections/connection/annotationRef



<timetable>/<trainParts>/<trainPart>/ocpsTT/statistics



<timetable>/<trainParts>/<trainPart>/ocpsTT/sectionTT/runTimes



<timetable>/<trainParts>/<trainPart>/ocpsTT/stopDescription



<timetable>/<trainParts>/<trainPart>/ocpsTT/stopDescription/stopTimes



<timetable>/<trainParts>/<trainPart>/ocpsTT/stopDescription/annotationRef



<timetable>/<trainParts>/<trainPart>/annotationRef



<timetable>/trains/train

X


<timetable>/trains/train/trainPartSequence

X


<timetable>/trains/train/trainPartSequence/trainPartRef

X


<timetable>/rosterings/rostering/blockParts/blockPart



<timetable>/rosterings/rostering/blocks/block



<timetable>/rosterings/rostering/blocks/block/blockPartSequence/blockPartRef




Mit Blick auf den Usecase Fahrgastinformation im Fahrzeug sollte <annotation> u. U. erweitert werden, um das Zielsystem der Sonderinformation zu bestimmen. Ausserdem sollte m. E. nach im rostering der Übergangstyp hinterlegt werden. Das hat Einfluss auf die Prognoseberechnung, sowie die berechnung von Via Zieltexten.