|
|
Line 10: |
Line 10: |
| {{importComment}} | | {{importComment}} |
| =={{examples}}== | | =={{examples}}== |
| {{importComment}} | | The structure of a railway track network is described by its topology. Topology defines how the tracks are connected with each other at switches and crossings and how the railway stations or operational points are connected via railway lines. Since all trains run on rails (tracks) and all relevant infrastructure elements are somehow situated in a defined relation on or next to the track, topology provides the basis for the location of static and dynamic elements in railways. Further, topology defines the possible ways of movement within the railway track network. The following figure shows how the railway track network is reduced to a microscopic and a more abstract mesoscopic topology model: |
| | <div class="res-img"> |
| | [[File:Topo_bild.pdf]] |
| | </div> |
| | <pdf>File:Topo_bild.pdf</pdf> |
| | ===Microscopic Topology=== |
| | The '''micro topology''' contains nine {{tag|IS|netElement}} objects, which are connected with each other by eleven {{tag|IS|netRelation}} objects. Altogether, the microscopic topology level network contains 20 {{tag|IS|networkResource}} objects. To better understand these concepts, the objects have human-readable IDs and references; it is strongly advised to use a generic number once applied to an actual project. The railML file shall look like this: |
| | |
| =={{Additional Information}}== | | =={{Additional Information}}== |
| ==={{Notes}}=== | | ==={{Notes}}=== |
| ==={{Open issues}}=== | | ==={{Open issues}}=== |
Revision as of 16:28, 7 May 2021
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:topology of railML ® version 3.2
|
Documentation
|
container element for topology model
|
Subschema
|
infrastructure
|
Parents*
|
infrastructure
|
Children
|
netElements (1..1), netRelations (0..1), netTravelPaths (0..1), networks (1..1)
|
Attributes: None
|
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Autoexport from the XML-Schema for element IS:topology of railML ® version 3.1
|
Documentation
|
container element for topology model
|
Subschema
|
infrastructure
|
Parents*
|
infrastructure
|
Children
|
netElements (1..1), netRelations (0..1), networks (1..1)
|
Attributes: None
|
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
The children have changed.
Semantics
Best Practice / Examples
The structure of a railway track network is described by its topology. Topology defines how the tracks are connected with each other at switches and crossings and how the railway stations or operational points are connected via railway lines. Since all trains run on rails (tracks) and all relevant infrastructure elements are somehow situated in a defined relation on or next to the track, topology provides the basis for the location of static and dynamic elements in railways. Further, topology defines the possible ways of movement within the railway track network. The following figure shows how the railway track network is reduced to a microscopic and a more abstract mesoscopic topology model:
<pdf>File:Topo_bild.pdf</pdf>
Microscopic Topology
The micro topology contains nine <netElement> objects, which are connected with each other by eleven <netRelation> objects. Altogether, the microscopic topology level network contains 20 <networkResource> objects. To better understand these concepts, the objects have human-readable IDs and references; it is strongly advised to use a generic number once applied to an actual project. The railML file shall look like this:
Additional Information
Notes
Open Issues