Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #393
Closed
Open
Issue created Oct 05, 2020 by Organisation@organisation.GOVOwner

Add area description

Description

There are several examples / scenarios where an area element would be beneficial. Area elements don't exist so far.

Which of the existing elements can be used?

  • with nor-extensions. See ticket #394 for more details on this element.

Sub-elements:

  • , for more information see trac ticket #396 (closed).

For description of sub-elements see document, point 4.9.3.

The sub-element has the following optional sub-elements:

For description see document, point 4.14 and trac ticket #395.

Background

This ticket was raised by Norway as part of the standardization in Norway and shall be used commonly in the future.

This element is a new high-level grouping element introduced in raiLML2.4nor.

The element describes several different types of areas, e.g. specification of specially controlled areas within the network.

Different kinds of areas are:

  • Track section
  • Work area
  • Project area
  • Local area
  • Overlapping or gapping track section borders

For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.4, 17.12.2020, point 4.9.

Links

  • Forum discussion:
  • Torben Brand, 12.03.2021: [https://www.railml.org/forum/index.php?t=msg&th=804&goto=2681&#msg_2681]
  • Torben Brand, 20.12.2018: [https://www.railml.org/forum/index.php?t=msg&goto=2051&#msg_2051]
  • Torben Brand, 14.07.2018: https://www.railml.org/forum/index.php?t=msg&goto=1882&&srch=track+section#msg_1882
  • Trac tickets:
  • #393
  • #395
  • #473
  • Wiki documentation:
  • none

Proposed solution in railML 2.5

A new element shall be added in . This shall be the container for an arbitrary number of elements.

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

~~The element 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 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 shall have an optional, but repeatable child element to reference the borders of the area marked by different infrastructure elements.

  • The borders of a track section can consist of the following elements: , , or .
  • For local and work areas preferably, interlocking elements shall be referenced.
  • The project area is limited by elements of type

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

The element shall have different options for specifying its location (and thus, its shape) summarized in an optional child element . It contains a choice of:

  • a given by center point (tGeoCoord) and @radius (tLengthM)
  • a given by at least 3 points (tGeoCoord) where the first and last point are assumed to be connected to close the area.
  • a with repeatable child elements with attributes @ref (required), @fromPos and @toPos (tLengthM)

In order to specify the purpose of an area, the element referencing the area need to be considered. The following areas are intended:

  • OCPs may be linked with an "information area" that defines a region where position-fencing is used to generate specific passenger information
  • element shall link with repeatable, but optional child element to the generic area element
  • there can exist "sections with impairments" on a track or a railway line
  • element shall link with repeatable, but optional child element to the generic area element
  • The impairment affects railway operation, which can result in longer running times for trains. Therefore, an additional running time shall be defined (see #395)
  • tracks contain "track sections" that are relevant for the interlocking control
  • element shall link with repeatable, but optional child element to the generic area element
  • there are "local operation areas" that are controlled by an interlocking
  • element shall link with repeatable, but optional child element to the generic area element
  • there are "work zones" that are integrated into interlocking control
  • element shall link with repeatable, but optional child element to the generic area element
  • projects may be spatially linked with "project areas"
  • element shall link with repeatable, but optional child element to the generic area element
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany