Area in railML 3.x

Description

Areas are needed for several applications. There exists a modelling solution in railML 2.5. For ETCS use case and other use cases, too, an implementation in railML 3.x is needed.

Background

Links

• Forum discussion:
  • Thomas Langkamm, 21.09.2021: https://www.railml.org/forum/index.php?t=msg&th=830&goto=2832&#msg_2832
  • Christian Rahmig, 11.10.2021: https://www.railml.org/forum/index.php?t=msg&th=830&goto=2836&#msg_2836
• Git issues:
  • version2#393 (railML 2.5)
  • #479 (closed)
• Wiki documentation:
  • (railML 2.5) IS:genericArea: https://wiki2.railml.org/wiki/IS:genericArea

Proposed solution railML 3.2

Proposal mentioned in the forum:

• a new "view" is added to <infrastructure>: it is named <genericLocations>
• within <genericLocations> an arbitrary number of <genericArea> elements may exist
• a <genericArea> has an ID, name and designator attributes / child elements
• a <genericArea> contains child elements for specifying a location, e.g. as <circle> or <polygon>
• like any functional infrastructure element, the <genericArea> shall have child elements to be located within the topology network using <spotLocation>, <linearLocation> and/or <areaLocation>
• the <genericArea> may reference bounding elements using <isLimitedBy> references pointing to functional infrastructure elements
• the specific purpose of the generic area comes from outside via the specific elements pointing to the <genericArea>, e.g. an <etcsArea>