railML.org issueshttps://development.railml.org/groups/railml/-/issues2024-03-19T16:59:04+01:00https://development.railml.org/railml/version3/-/issues/532Unification of relations in the UML model of RTM2024-03-19T16:59:04+01:00CO OntologyUnification of relations in the UML model of RTM## Description
the relationship between RTM_LinearLocation and associatedNetElement is modelled differently than RTM_AreaLocation. RTM_AreaLocation is modelled using an association arrow, while RTM_LinearLocation just included a member ...## Description
the relationship between RTM_LinearLocation and associatedNetElement is modelled differently than RTM_AreaLocation. RTM_AreaLocation is modelled using an association arrow, while RTM_LinearLocation just included a member field of the class. However both are annotated with the 1..* cardinality.
![image001](/uploads/12b14743086cf6bc3b777a727d1c69db/image001.png)
## Proposed solution railML 3.3
it could be remodeled so it uses the same UML procedure to define the relationship.3.3TT CoordinationTT Coordinationhttps://development.railml.org/railml/version3/-/issues/528Create wiki documentation for IS:etcsArea2024-01-11T14:43:02+01:00TT CoordinationCreate wiki documentation for IS:etcsAreaThe ETCS working group has created a draft documentation that can be used to create a wiki documentation for the railML 3 element etcsArea. The existing work includes a definition as well as example information.
This ticket is to create...The ETCS working group has created a draft documentation that can be used to create a wiki documentation for the railML 3 element etcsArea. The existing work includes a definition as well as example information.
This ticket is to create the wiki page from that documentation provided by the ETCS community.
ETCS document: https://cloud.railml.org/f/89860 <br>
Wiki page: https://wiki3.railml.org/wiki/IS:etcsArea3.3TT CoordinationTT Coordinationhttps://development.railml.org/railml/version3/-/issues/479Area in railML 3.x2023-12-08T10:52:22+01:00IS CoordinationArea 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 discus...## 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](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](https://www.railml.org/forum/index.php?t=msg&th=830&goto=2836&#msg_2836)
* Git issues:
* https://development.railml.org/railml/version2/-/issues/393 (railML 2.5)
* #479
* Wiki documentation:
* (railML 2.5) IS:genericArea: [https://wiki2.railml.org/wiki/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>`3.2TT CoordinationTT Coordinationhttps://development.railml.org/railml/version3/-/issues/103balise accuracy attribute2023-10-26T11:44:01+02:00Deleted Userbalise accuracy attributeMartin Lehmann suggested to rename the **balise** attribute **linkingAccuracy** to **locationAccuracy**.
see http://www.railml.org/forum/ro/index.php?group=1&id=56
That would really be a better term, see also "ETCS System Requirements ...Martin Lehmann suggested to rename the **balise** attribute **linkingAccuracy** to **locationAccuracy**.
see http://www.railml.org/forum/ro/index.php?group=1&id=56
That would really be a better term, see also "ETCS System Requirements Specification Chapter 7 (ERTMS/ETCS language)" (SUBSET-026-7 Issue 2.3.0):
"Q_LOCACC: Accuracy of the balise location"
Its value runs from "0" to "63m". Negative values were removed.3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/281Geographic coordinates 2D2023-10-26T11:42:18+02:00IS CoordinationGeographic coordinates 2DThe model shall support 2D geographic coordinates for locating railway infrastructure using a geodetic datum. The chosen geodetic datum shall be identified by its EPSG code.The model shall support 2D geographic coordinates for locating railway infrastructure using a geodetic datum. The chosen geodetic datum shall be identified by its EPSG code.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/297Asset 2D geographic location2023-10-26T11:42:15+02:00IS CoordinationAsset 2D geographic locationAn asset shall have a location on a 2D geographic earth surface representation based on a geodetic datum. The chosen geodetic datum shall be identified by its EPSG code.An asset shall have a location on a 2D geographic earth surface representation based on a geodetic datum. The chosen geodetic datum shall be identified by its EPSG code.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/282Geographic coordinates 3D2023-10-26T11:42:11+02:00IS CoordinationGeographic coordinates 3DThe model shall support 3D geographic coordinates for locating railway infrastructure using a geodetic datum. The chosen geodetic datum shall be identified by its EPSG code.The model shall support 3D geographic coordinates for locating railway infrastructure using a geodetic datum. The chosen geodetic datum shall be identified by its EPSG code.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/23Flatten 'trainDetector' and 'trainProtectionElement'2023-10-26T11:31:55+02:00Deleted UserFlatten 'trainDetector' and 'trainProtectionElement'# Leightweighting elements `trainDetector` and `trainProtectionElement`
## What to do?
Some common attributes are repeated inside every element instance. They could be sourced out into a "definition element" and used as reference.
Att...# Leightweighting elements `trainDetector` and `trainProtectionElement`
## What to do?
Some common attributes are repeated inside every element instance. They could be sourced out into a "definition element" and used as reference.
Attributes of element `trainDetector` for outsourcing:
* `detectionObject`
* `medium`
* `model`
* `axleCounting`
Attributes of element `trainProtectionElement` for outsourcing:
* `medium`
* `system`
* `model`
(Contribution by Thomas Albrecht at 16th meeting in Brunswick, October 6th, 2009)
## How to do?
Define new container element inside `infrastructure` for "trackEquipment".
Define new container element inside this for "trainDetectionSystems" and "trainProtectionSystems".
Define new elements inside these containers for "trainDetectionSystem" and "trainProtectionSystem" based on `tElementWithIdAndName` for attributes `id`, `name`, `description` and `anyAttribute`.
Change current definitions of `trainDetector` and `trainProtectionElement` to use `ref` attribute for references.
Harmonize definition and references with `rollingstock` and `timetable`.
## Library
railML could provide a library with "typical European train detection and train protection systems".
Their definition could be used with `xi:include` in XML instance files.
Contribution by users is needed.
This list should be extended with other systems, if required by railML users.
## Proposed solution railML 3.1
railML 3.1 provides both infrastructure components: <trainDetectionElement> and <trainProtectionElement>.
A <trainProtectionElement> can refer to the train protection system using the attribute @trainProtectionSystem that shall link to the codelist TrainProtectionSystems.xml, section trainProtectionSystemsAtTrack. Only if this list does not contain the specific train protection system to be modelled, it shall be described in its functionality using attributes @medium and @monitoring.
A <trainDetectionElement> can be specified via its attribute @type (e.g. "axleCounter" or "insulatedRailJoint" or "trackCircuit"). If the train detection element/system is not included in the list of @type, the specific installation can be described using attributes @detectedObject, @detectorMedium and @layout. If you want to define these parameters only once, do this for a "basic" train detection element and make use of the attribute @basedOnTemplate referencing to this train detection element from other (specific) train detection elements.
## Proposed solution railML 3.x
The railML 3.1 implementation shall be reviewed considering best practices and specific use case requirements.3.2IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/219Grouping of speed changes2023-10-26T11:03:52+02:00Deleted UserGrouping of speed changesThere are several speed change definitions at a certain position for several speed profiles.
I would be nice to group them, in order to have a single position (**pos**, **absPos**, **geoCoord**) and to address the speed change with a si...There are several speed change definitions at a certain position for several speed profiles.
I would be nice to group them, in order to have a single position (**pos**, **absPos**, **geoCoord**) and to address the speed change with a single **id** instead of several **id**s for each speed profile.
### Links
* Forum discussion
* Susanne Wunsch, 18.11.2011: [https://www.railml.org/forum/index.php?t=msg&th=120&goto=271&#msg_271]
* Trac tickets
* Wiki documentation
## Proposed solution railML 3.1
A `<speedSection>` can reference an arbitrary number of `<speedProfile>` instances using the optional and repeatable child element `<speedSection><validForSpeedProfile>` with attribute `@ref`.
## Proposed solution railML 3.x
The implementation from railML 3.1 need to be reviewed according best practices.3.2IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/459ETCS signal modeling update2023-10-26T10:58:37+02:00IS CoordinationETCS signal modeling update## Description
The attribute **`<signalIS / isEtcsSignal> @srsVersion`** seems to be not used or needed. Therefore, it is suggested to deprecate it.
Further, there are other specific types of ETCS signals, which cannot be modelled curr...## Description
The attribute **`<signalIS / isEtcsSignal> @srsVersion`** seems to be not used or needed. Therefore, it is suggested to deprecate it.
Further, there are other specific types of ETCS signals, which cannot be modelled currently.
_tbd: details to follow_
### Background
Discussion about ETCS signals was initiated at railML ETCS use case working group meeting on February 26, 2021 (see [https://www.railml.org/en/event-reader/railml-is-etcs-telco-2021-02-26.html].
### Links
* Forum discussion
* Christian Rahmig, 20.02.2022: [https://www.railml.org/forum/index.php?t=msg&th=857&goto=2913&#msg_2913]
* Trac ticket
* #459
* Wiki documentation
* IS:isEtcsSignal: [https://wiki3.railml.org/wiki/IS:isEtcsSignal]
## Proposed solution railML 3.2
It is suggested to deprecate **`<signalIS / isEtcsSignal> @srsVersion`**.3.2IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/460TrainProtectionElement vs ETCS2023-10-26T10:50:33+02:00IS CoordinationTrainProtectionElement vs ETCS## Description
It must be clarified how ETCS based systems shall be modelled. In particular, the usage of `<trainProtectionElement>` for ETCS based systems should be questioned.
### Background
The discussion was initiated at the railM...## Description
It must be clarified how ETCS based systems shall be modelled. In particular, the usage of `<trainProtectionElement>` for ETCS based systems should be questioned.
### Background
The discussion was initiated at the railML ETCS use case working group meeting on February 26, 2021 (see [https://www.railml.org/en/event-reader/railml-is-etcs-telco-2021-02-26.html]).
### Links
* Forum discussion
* Trac ticket
* #460
* Wiki documentation
* IS:trainProtectionElement: [https://wiki3.railml.org/wiki/IS:trainProtectionElement]
## Proposed solution railML 3.2
`<trainProtectionElement>` shall only be used for national and/or legacy train protection systems. ETCS based systems must not be modelled using `<trainProtectionElement>`.
This has to be clearly documented in the element annotations.3.2IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/194Logical constraint for speed profile characteristics2023-10-06T09:54:34+02:00Deleted UserLogical constraint for speed profile characteristicsAs stated in the forum by Dirk Bräuer (1) we may introduce an
attribute 'logicalConstraint' for the internal dependencies of
the characteristics given within one speed profile.
Are the characteristics AND or OR linked?
Does it strongly...As stated in the forum by Dirk Bräuer (1) we may introduce an
attribute 'logicalConstraint' for the internal dependencies of
the characteristics given within one speed profile.
Are the characteristics AND or OR linked?
Does it strongly depend on the 'influence' with the values
'decreasing' or 'increasing'?
May an 'increasing' speed profile be applied if __all__ characteristics
are met (logical AND)? Has an 'decreasing' speed profile to be applied
if at least __one__ of the given characteristics is met (logical OR)? If
so, we could clarify this issue in the documentation of the element
'speedProfile' rather than providing an attribute.
(1) http://www.railml.org/forum/ro/?group=1&id=1403.2IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/112Different codes for <ocp>2023-10-05T13:50:52+02:00Deleted UserDifferent codes for <ocp>## Description
Enhance <ocp> with an attribute for UIC country codes (UIC Leaflet 920-14).
```
<xs:attribute name="uicCountry" type="rail:tTwoDigits"/>
```
With railML version 2.2 the OCP child element <designator> has been introduced...## Description
Enhance <ocp> with an attribute for UIC country codes (UIC Leaflet 920-14).
```
<xs:attribute name="uicCountry" type="rail:tTwoDigits"/>
```
With railML version 2.2 the OCP child element <designator> has been introduced solving the issue with UIC country code and reference to infrastructure manager. This concept has been documented in the railML wiki. However, what is missing so far, is a real example station as best practice of an OCP.
### Links
* Forum discussion
* Trac ticket
* Wiki documentation (railML 2.x)
* OCP: [http://wiki.railml.org/index.php?title=IS:ocp]
* Designator: [http://wiki.railml.org/index.php?title=IS:designator]
* Dev:Registers.xml (Codelist): [http://wiki.railml.org/index.php?title=Dev:Registers]
## Proposed solution for railML 2.5
The OCP wiki page shall be enhanced with an example of an OCP having several designators. This example can be taken from Simple Example together with a figure.
Basically, solved with Best practice example of Pulsnitz on OCP wiki page
## Proposed solution for railML 3.x
Same to be done in the railML 3 wiki, page "Operational Point", section "Best practices"; example still missing3.2IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/293Asset mileage location2023-10-05T11:25:15+02:00IS CoordinationAsset mileage locationAn asset shall have a location within the railway network that is expressed using the classic, railway specific linear referencing system (mileage).An asset shall have a location within the railway network that is expressed using the classic, railway specific linear referencing system (mileage).IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/291Asset mesoscopic topology location2023-10-05T11:16:48+02:00IS CoordinationAsset mesoscopic topology locationAn asset shall have a location within the mesoscopic topology railway network.An asset shall have a location within the mesoscopic topology railway network.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/290Asset microscopic topology location2023-10-05T11:16:11+02:00IS CoordinationAsset microscopic topology locationAn asset shall have a location within the microscopic topology railway network.An asset shall have a location within the microscopic topology railway network.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/289Asset topology location2023-10-05T11:16:04+02:00IS CoordinationAsset topology locationAn asset shall have a location within the topology railway network.An asset shall have a location within the topology railway network.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/288Line geometry: gradient2023-10-05T11:08:01+02:00IS CoordinationLine geometry: gradientThe model shall support track alignment modelling in a macroscopic railway network considering its gradient profile by defining straight lines, valleys and crests.The model shall support track alignment modelling in a macroscopic railway network considering its gradient profile by defining straight lines, valleys and crests.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/286Track alignment: gradient2023-10-05T11:07:57+02:00IS CoordinationTrack alignment: gradientThe model shall support track alignment modelling in a microscopic railway network considering its gradient profile by defining straight lines, valleys and crests.The model shall support track alignment modelling in a microscopic railway network considering its gradient profile by defining straight lines, valleys and crests.IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/285Track alignment: radius2023-10-05T11:07:51+02:00IS CoordinationTrack alignment: radiusThe model shall support track alignment modelling in a microscopic railway network considering its curvature profile by defining straight lines, transition curves and curves.The model shall support track alignment modelling in a microscopic railway network considering its curvature profile by defining straight lines, transition curves and curves.IS CoordinationIS Coordination