IS:macroscopicNode trackBegin: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Created using IS:macrocopicNode contents) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{ElementDocu| | ||
| | elementName = macroscopicNode | ||
| | |||
| | |parent = {{IS:Tag|trackBegin}} | ||
|ownAttributes = | |||
{{InheritRef | |||
|attributeName = ocpRef | |||
|contextLink = {{IS:Tag|ocp}} | |||
|notes_en = {{Ann| }} | |||
}} | |||
* {{Attr|flowDirection}}: This specifies how trains can pass the node. Possible values are: | |||
:* {{Enum|in}} only into the node (track --> node) | |||
:* {{Enum|out}} only out of the node (track <-- node) | |||
:* {{Enum|both}} into and out of node (track <--> node) | |||
:* {{Enum|unknown}} | |||
:* {{OtherEnum | |||
|notes_en = | |notes_en = | ||
| | |notes_de = | ||
|ocpRef | }} {{AddAnn|| }} | ||
|flowDirection | |||
|semantics = | |||
A {{IS:Tag|macroscopicNode|trackBegin}} represents a logical connection of (multiple) {{IS:Doc|track}}s without respect to the physical layout of their {{IS:Doc|connections}}. {{AddAnn|| }} | |||
|notes = | |||
Many simulation programs, especially in the simulation domain for complete networks, have no knowledge about the physical {{IS:Doc|track}} layout of a station. They model a station as a "zero-dimensional vertex" in a "graph" with {{TT:Doc|train}}s being able to switch to every "edge" (here: {{IS:Doc|track}}) that is connected to that "vertex". The {{IS:Tag|macroscopicNode|trackBegin}} provides means to represent this simplified infrastructure model in RailML. | |||
Simulation programs that depend on precise "microscopic" modelling of stations (including {{IS:Doc|switch}}es, lengths, {{IS:Doc|signal}}s, ...) are likely to be troubled by {{IS:Tag|macroscopicNode|trackBegin}}. Possible solutions can be: | |||
* refuse the import of XML-files containing {{IS:Tag|macroscopicNode|trackBegin}} | |||
* convert the {{IS:Tag|macroscopicNode|trackBegin}} internally into a set of {{IS:Doc|switch}}es and thus allowing all travel directions as the {{IS:Tag|macroscopicNode|trackBegin}} does. This might severely mess up the {{IS:Doc|infrastructure}} model in case of {{IS:Tag|macroscopicNode|trackBegin}}s with many connected {{IS:Doc|track}}s. | |||
* convert the {{IS:Tag|macroscopicNode|trackBegin}} internally into {{IS:Doc|openEnd}}s and thus allowing {{TT:Doc|train}}s to enter and leave the simulation in that point. "Warping" {{TT:Doc|train}}s from one {{IS:Doc|track}} of the node to another via "virtual open ends" is a semantically identical behaviour compared with a macroscopic node. {{AddAnn|| }} | |||
|constraints = | |||
* {{Attr|ocpRef}} {{RailMLType|tGenericRef}}, mandatory | |||
* {{Attr|flowDirection}} default: {{Enum|both}}, optional | |||
All {{IS:Doc|track}}s connected to this {{IS:Doc|macroscopicNode}} shall refer to the same {{IS:Doc|ocp}}. | |||
The associated {{IS:Doc|ocp}} shall have suitable operational attributes set (e. g. as a station). {{AddAnn|| }} | |||
}} | }} | ||
Revision as of 13:31, 8 April 2016
macroscopicNode
Scheme description / Schemenbeschreibung
Position of macroscopicNode in the XML-Tree / Position von macroscopicNode im XML-Baum
- Parent: <trackBegin>
- Children: Not yet described. / Noch nicht beschrieben.
Multiplicity / Anzahl
Semantics / Bedeutung
A <macroscopicNode> represents a logical connection of (multiple) tracks without respect to the physical layout of their connections.
Attributes of macroscopicNode / Attribute von macroscopicNode
- ocpRef: This refers to the id attribute of the associated <ocp> element.
' '
- flowDirection: This specifies how trains can pass the node. Possible values are:
- in only into the node (track --> node)
- out only out of the node (track <-- node)
- both into and out of node (track <--> node)
- unknown
- 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
- ocpRef xs:IDREF, mandatory
- flowDirection default: both, optional
All tracks connected to this macroscopicNode shall refer to the same ocp.
The associated ocp shall have suitable operational attributes set (e. g. as a station).
Best practice & Examples / Empfohlene Anwendung & Beispiele
Not yet described. / Noch nicht beschrieben.
Notes / Anmerkungen
Many simulation programs, especially in the simulation domain for complete networks, have no knowledge about the physical track layout of a station. They model a station as a "zero-dimensional vertex" in a "graph" with trains being able to switch to every "edge" (here: track) that is connected to that "vertex". The <macroscopicNode> provides means to represent this simplified infrastructure model in RailML.
Simulation programs that depend on precise "microscopic" modelling of stations (including switches, lengths, signals, ...) are likely to be troubled by <macroscopicNode>. Possible solutions can be:
- refuse the import of XML-files containing <macroscopicNode>
- convert the <macroscopicNode> internally into a set of switches and thus allowing all travel directions as the <macroscopicNode> does. This might severely mess up the infrastructure model in case of <macroscopicNode>s with many connected tracks.
- convert the <macroscopicNode> internally into openEnds and thus allowing trains to enter and leave the simulation in that point. "Warping" trains from one track of the node to another via "virtual open ends" is a semantically identical behaviour compared with a macroscopic node.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.