IS:propOperational

From railML 2 Wiki
Jump to navigation Jump to search


propOperational
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

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

Attributes of propOperational / Attribute von propOperational

  • operationalType: a keyword that defines the operational function of this OCP (xs:string, optional); possible values:
    • station: a regular passenger station
    • stoppingPoint: an ocp without tracks where trains start, stop or end e. g. for passenger exchange (German: Haltepunkt)
    • depot: a train depot
    • crossover: a connection between two tracks of a double-track line (German: "Überleitstelle")
    • junction: joining/splitting of two lines (German: "Abzweigstelle")
    • blockPost: an ocp without block signale where the train sequence is monitored (German: "Zuglaufmeldestelle")
    • blockSignal: an ocp consisting of a block signal only (German: "Zugfolgestelle" / "Blockstelle")
  • trafficType: a keyword that defines the kind of traffic for this OCP (xs:string, optional); possible values:
    • 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
  • 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. (xs:boolean, optional)
  • 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). (xs:boolean, optional)

Syntactic Constraints / Syntaktische Beschränkungen

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.