IS:propOperational
From wiki.railML.org
Revision as of 09:57, 17 October 2017 by Coordination (Talk | contribs) (Description of Attributes corrected, detailed and translations added)
propOperational
Contents
- 1 Scheme description / Schemenbeschreibung / Description du schéma
- 1.1 Position of propOperational in the XML-Tree / Position von propOperational im XML-Baum / position de propOperational dans l’aborescence XML
- 1.2 Multiplicity / Anzahl / Multiplicité
- 1.3 Semantics / Bedeutung / Sémantique
- 1.4 Attributes of propOperational / Attribute von propOperational / Attributs de propOperational
- 1.5 Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques
- 2 Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples
- 3 Notes / Anmerkungen / Notes
- 4 Open issues / Offene Punkte/Pedenzen / Questions ouvertes
Scheme description / Schemenbeschreibung / Description du schéma
Position of propOperational in the XML-Tree / Position von propOperational im XML-Baum / position de propOperational dans l’aborescence XML
- Parent: <ocp>
- Children: <uptime>
Multiplicity / Anzahl / Multiplicité
Semantics / Bedeutung / Sémantique
<propOperational> contains attributes which further refine the operational properties of an <ocp>.
Attributes of propOperational / Attribute von propOperational / Attributs de 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
Gare - 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)
Point d'arrêt - depot a train depot
- crossover a connection between two tracks of a double-track line
Überleitstelle - junction Junction: joining/splitting of two lines
Abzweigstelle
Bifurcation - 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
Poste de Block Manuel - blockSignal Block signal: an ocp consisting of a block signal for train spacing only, mainly unstaffed and automated operating
Blocksignal/ggf. auch Zuglaufmeldestelle
Signal de Block Automatique - 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.
- station Station: a usual station for beginning, ending, overtaking of trains with passing tracks, ...
- 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.
- 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 / Contraintes syntactiques
- 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 / Bonnes pratiques & exemples
Not yet described. / Noch nicht beschrieben. / Pas encore décrit.
Notes / Anmerkungen / Notes
Not yet described. / Noch nicht beschrieben. / Pas encore décrit.
Open issues / Offene Punkte/Pedenzen / Questions ouvertes
Not yet described. / Noch nicht beschrieben. / Pas encore décrit.