IS:propOperational: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(added link to documentaiton of types of ocps) |
No edit summary |
||
Line 21: | Line 21: | ||
:* {{Enum|siding}} {{Intro|2.4}} an ocp to collect and deliver of cargo wagons to build trains, but not for train operation | :* {{Enum|siding}} {{Intro|2.4}} an ocp to collect and deliver of cargo wagons to build trains, but not for train operation | ||
:* {{OtherEnum | :* {{OtherEnum | ||
|notes_en = | |notes_en = | ||
|notes_de = | |notes_de = | ||
}} | }} | ||
Line 52: | Line 52: | ||
* if value of {{Attr|operationalType}} in ({{Enum|crossover}}, {{Enum|junction}}, {{Enum|blockPost}}, {{Enum|blockSignal}}) ==> {{Attr|trafficType}} not set | * if value of {{Attr|operationalType}} in ({{Enum|crossover}}, {{Enum|junction}}, {{Enum|blockPost}}, {{Enum|blockSignal}}) ==> {{Attr|trafficType}} not set | ||
* if value of {{Attr|trafficType}} == {{Enum|shunting}} ==> {{Attr|operationalType}} not equal to {{Enum|stoppingPoint}}|proposed=2020-02-25|status=proposed|id=IS:007}} | * if value of {{Attr|trafficType}} == {{Enum|shunting}} ==> {{Attr|operationalType}} not equal to {{Enum|stoppingPoint}}|proposed=2020-02-25|status=proposed|id=IS:007}} | ||
|example=Examples of the usage of {{IS:Tag|propOperational}} can be found here: [[Dev:Types_of_ocps]] | |||
}} | }} |
Revision as of 17:02, 22 February 2023
propOperational
Scheme description / Schemenbeschreibung
Position of propOperational in the XML-Tree / Position von propOperational im XML-Baum
Multiplicity / Anzahl
Semantics / Bedeutung
<propOperational> contains attributes which further refine the operational properties of an <ocp>.
Please, be aware of the semantic constraint(s)!
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 (external link)
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 (externer Link, 🇩🇪) - blockSignal Block signal: an ocp consisting of a block signal for train spacing only, mainly unstaffed and automated operating
Blocksignal/ggf. auch Zuglaufmeldestelle - siding (introduced with version 2.4) an ocp to collect and deliver of cargo wagons to build trains, but not for train operation
- 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.
- 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
- operational (introduced with version 2.4) the prevailing traffic occuring at this ocp is operational traffic (no passengers, no goods, just staff)
- 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).
- remoteControlled: (introduced with version 2.5) specify whether the <ocp> is remotely controlled by a TMS[1] or CTC[2].
- simultaneousEntry: (introduced with version 2.5) describes the pattern for a simultaneous entry into the <ocp>. Possible values are:
- yes
- no
- partial
- 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.
Syntactic Constraints / Syntaktische Beschränkungen
- operationalType: tOcpOperationalType (union of (restriction of xs:string, tOtherEnumerationValue)); optional
- trafficType: tOcpTrafficType (union of (restriction of xs:string, tOtherEnumerationValue)); optional
- orderChangeable: xs:boolean; default: false; optional
- ensuresTrainSequence: xs:boolean; default: true; optional
- remoteControlled: xs:boolean; default: false; optional
- simultaneousEntry: tSimultaneousEntry (union of (restriction of xs:string, tOtherEnumerationValue)); optional
Semantic Constraints / Semantische Beschränkungen
|
Best practice & Examples / Empfohlene Anwendung & Beispiele
Examples of the usage of <propOperational> can be found here: Dev:Types_of_ocps
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.