IS:operationalPoint: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
(Created page with "{{subst:docBase |element=operationalPoint |subschema=IS}}")
 
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
<!--Element '''{{{element}}}'''-->
<!--Element '''{{{element}}}'''-->
[[File:Alvaro-sanchez-2D7Q7AlVIA4-unsplash.jpg|thumb|500px|{{unsplash|2D7Q7AlVIA4|heyapricot|name=Alvaro Sanchez}}]]
=={{introduction}}==
=={{introduction}}==
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
Line 10: Line 12:
{{importComment}}
{{importComment}}
=={{examples}}==
=={{examples}}==
<syntaxhighlight lang=xml>
            <operationalPoint id="_7D41696E-2373-420D-9625-D0BC090C31DD">
              <name name="Bevern (Bremervoerde)" language="en"/>
              <spotLocation id="a2b5634a-d560-403e-88b0-957a8f433865"
                              netElementRef="b2c25c81-a49d-44ce-8d3e-409668b95278"
                              pos="4889.0">
                  <geometricCoordinate positioningSystemRef="xxx"
                                        x="11.111"
                                        y="22.222"
                                        z="33.333"/>
              </spotLocation>
              <designator register="RL100" entry="ABEV"/>
              <designator register="UOPID" entry="DE-ABEV"/>
            </operationalPoint>
</syntaxhighlight>
{{importComment}}
{{importComment}}
=={{Additional Information}}==
=={{Additional Information}}==
==={{Notes}}===
==={{Notes}}===
==={{Open issues}}===
==={{Open issues}}===

Latest revision as of 12:49, 13 May 2024

© Alvaro Sanchez (Source; Unsplash License)

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:operationalPoint of railML® version 3.2
Documentation

The OperationalPoint defines a point in the railway network that is essential for railway operation. Typical examples for railway operational points are stations, block signals or stopping points. Operational points allow an interaction between the railway operator and the train driver.

Subschema

infrastructure

Parents*
Children

areaLocation (0..*), connectedToLine (0..*), designator (0..*), external (0..*), gmlLocations (0..*), infrastructureManagerRef (0..*), isValid (0..*), limitedByBorder (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), opEquipment (0..1), opOperations (0..1), spotLocation (0..*), typeDesignator (0..*)

Attributes:

  • basedOnTemplate: references a generic operational point (optional; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),

  • belongsToParent: references the one and only parent operational point of this operational point

    - if some information exists in parent and child, then information in child overwrites it in child

    - if some information exists only in parent, then child inherits this information from parent (optional; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),

  • timezone: the timezone of the operational point as defined in the tz database, e.g. "Europe/Berlin" (optional; xs:string),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
*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:operationalPoint of railML® version 3.1
Documentation

The OperationalPoint defines a point in the railway network that is essential for railway operation. Typical examples for railway operational points are stations, block signals or stopping points. Operational points allow an interaction between the railway operator and the train driver.

Subschema

infrastructure

Parents*
Children

any (0..*), areaLocation (0..*), connectedToLine (0..*), designator (0..*), external (0..*), gmlLocations (0..*), infrastructureManagerRef (0..*), isValid (0..*), limitedByBorder (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), opEquipment (0..1), opOperations (0..1), spotLocation (0..*)

Attributes:

  • belongsToParent: references the one and only parent operational point of this operational point (optional; xs:IDREF; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),

  • basedOnTemplate: references a generic operational point (optional; xs:IDREF; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),

  • timezone: the timezone of the operational point as defined in the tz database, e.g. "Europe/Berlin" (optional; xs:string),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
*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.

The attributes have been changed.

Semantics

Best Practice / Examples

            <operationalPoint id="_7D41696E-2373-420D-9625-D0BC090C31DD">
               <name name="Bevern (Bremervoerde)" language="en"/>
               <spotLocation id="a2b5634a-d560-403e-88b0-957a8f433865"
                              netElementRef="b2c25c81-a49d-44ce-8d3e-409668b95278"
                              pos="4889.0">
                  <geometricCoordinate positioningSystemRef="xxx"
                                        x="11.111"
                                        y="22.222"
                                        z="33.333"/>
               </spotLocation>
               <designator register="RL100" entry="ABEV"/>
               <designator register="UOPID" entry="DE-ABEV"/>
            </operationalPoint>

Additional Information

Notes

Open Issues

Retrieved from "https://wiki3.railml.org/index.php?title=IS:operationalPoint&oldid=8987"