Home » railML newsgroups » railML.infrastructure » [railML2] adding new element <area> for the mapping of track sections
Re: [railML2] adding new element <area> for the mapping of track sections [message #2785 is a reply to message #2783] Thu, 08 July 2021 06:34 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Dear all,

I updated the railML 2.5 solution proposal in Trac ticket #393 [1] according to all received feedback. This is how it looks like:

A new element <areas> shall be added in <infrastructure>. This shall be the container for an arbitrary number of <area> elements.

The element <area> shall have the common attributes: @id, @pos, @absPos, @code, @name, @description.

The element <area> shall have an attribute @type with the following enumeration values:
* "trackSection" - a track section area (track vacancy detection)
* "project" - an area used for a certain project (e.g. construction)
* "local" - a locally operated area in interlocking
* "work" - a work area in interlocking
* "information" - an area used for passenger information systems
* "other" - any other type of area...

The element <area> shall have an optional attribute @controllerRef to reference the controller that belongs to the area. This attribute is not relevant for project areas.

The element <area> shall have an optional, but repeatable child element <limitedBy> to reference the borders of the area marked by different infrastructure elements.
* The borders of a track section can consist of the following elements: <trainDetector>, <trackCircuitBorder>, <bufferStop> or <openEnd>.
* For local and work areas preferably, interlocking elements shall be referenced.
* The project area is limited by elements of type <border>

The element <area> shall have an optional child element <state> that can be used to define the (operational) state of the area.

The element <area> shall have different options for specifying its location (and thus, its shape) summarized in an optional child element <location>. It contains a choice of:
* a <circle> given by center point <center> (tGeoCoord) and @radius (tLengthM)
* a <polygon> given by at least 4 points <point> (tGeoCoord) where the first and last point are identical to close the area.
* a <trackLocation> with repeatable child elements <trackRef> with attributes @ref (required), @fromPos and @toPos (tLengthM)


This is your chance for final comments on the proposed solution before it goes live with railML 2.5...

[1] https://trac.railml.org/ticket/393

Thank you very much and best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML2] Adding a new element <turningResistance> to <ocp>
Next Topic: [railML2] Adding a new element informationArea to ocp
Goto Forum:
  


Current Time: Tue Jul 23 01:13:26 CEST 2024