IS:propOperational

From railML 2 Wiki
Revision as of 09:57, 17 October 2017 by RailML Coord Governance (talk | contribs) (Description of Attributes corrected, detailed and translations added)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


propOperational
 


Scheme description / Schemenbeschreibung

Position of propOperational in the XML-Tree / Position von propOperational im XML-Baum

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

<propOperational> contains attributes which further refine the operational properties of an <ocp>.

Attributes of propOperational / Attribute von propOperational

  • operationalType: This is a keyword that defines the operational function of this ocp. Possible values are:
  • station Station: a usual station for beginning, ending, overtaking of trains with passing tracks, ...
    Bahnhof
  • stoppingPoint Stop: an ocp without signals, switches, addtional tracks where trains start, stop or end e. g. for passenger exchange
    Haltepunkt/Haltestelle (nicht bei DB Netz)
  • depot a train depot
  • crossover a connection between two tracks of a double-track line
    Überleitstelle
  • junction Junction: joining/splitting of two lines
    Abzweigstelle
  • blockPost Block post: a (mainly staffed) ocp with signals where the train spacing is monitored.
    Further Information: Article in Wikipedia
    Blockstelle: Eine (meist durch eine Betriebspersonal besetzte) Betriebsstelle (Zugfolgestelle), welche den Abstand der Züge beim Fahren im Raumabstand mit Signalen sichert.
    Weitere Informationen: Wikipedia-Artikel

  • blockSignal Block signal: an ocp consisting of a block signal for train spacing only, mainly unstaffed and automated operating
    Blocksignal/ggf. auch Zuglaufmeldestelle
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
  • trafficType: This is a keyword that defines the kind of traffic for this ocp. Possible values are:
  • passenger the prevailing traffic occuring at this ocp is passenger traffic
  • freight the prevailing traffic occuring at this ocp is freight traffic
  • shunting the prevailing traffic occuring at this ocp is shunting traffic, e. g. in a depot or a workshop
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
  • orderChangeable: if true, the ocp is capable of changing the train sequence on the open track. That means that the ocp has at least one point.
  • ensuresTrainSequence: if true, the ocp ensures and protects the train sequence on the open track. In other words: while the ocp is occupied by a train, a subsequent train may safely approach the ocp. The train sequence is protected. This is mostly implemented by a signal (e. g. a home signal or a block signal).

Syntactic Constraints / Syntaktische Beschränkungen

  • operationalType optional
  • trafficType optional
  • orderChangeable xs:boolean, default: false, optional
  • ensuresTrainSequence xs:boolean, default: true, optional

Not all combinations of operationalType and trafficType make sense. E. g. a stopping point with traffic type shunting is not plausible. Therefore, the following constraints apply:

  • if value of operationalType in (crossover, junction, blockPost, blockSignal) ==> trafficType not set
  • if value of trafficType == shunting ==> operationalType not equal to stoppingPoint

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.