Define semantic rules for using <speedChange> elements
Define semantic rules for using <speedChange> elements
Description
In order to define continuous speed profiles along the whole track network, it is mandatory, that oriented elements are placed at every track begin and every track end leaving no gaps.
Background
This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
is a sub-element of .
In addition to the speedProfile@name attribute, the speed profile is also indicated in the attribute @etcsTrainCategory of the element. The values of the speedChange@etcsTrainCategory are railML2.4nor specific and a mapping of the values of the international train category numbers, adapted accordingly to the definition of the attribute in the railML wiki.
In railML2.4nor the speed information modelled via elements must be defined along the full extent of all tracks. Thus, it is mandatory to place a in the beginning of a model with a @dir="up" and on the end of a model with a @dir="down" value or at a mileage direction change once for each direction (see also 3.10.2 of document linked below).
For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.7 (page 42).
Links
- Forum discussion:
- [...]
- Trac tickets:
- #424
- #425
- Wiki documentation:
- IS:speedChange: [https://wiki2.railml.org/wiki/IS:speedChange]
- IS:speedProfile: [https://wiki2.railml.org/wiki/IS:speedProfile]
Proposed solution in railML 2.5
The element is already implemented in railML 2.x.
The action resulting from this ticket is a clarification in the wiki. The following new semantic rules must be defined:
- Every line track has to have at least one
<speedChange>at the track begin with parameters@pos="0"and@dir="up". - Every line track has to have at least one
<speedChange>at the track end with parameters@pos="{value equal to trackEnd@pos}"and@dir="down".
Semantic rules need to be added in the railML 2 wiki.
Activity
- Description changed
== Description == + + In order to define continuous speed profiles along the whole track network, it is mandatory, that oriented <speedProfile> elements are placed at every track begin and every track end leaving no gaps. + + === Background === This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future. <speedChange> is a sub-element of <trackElements>. In addition to the speedProfile@name attribute, the speed profile is also indicated in the attribute @etcsTrainCategory of the <speedChange> element. The values of the speedChange@etcsTrainCategory are railML2.4nor specific and a mapping of the values of the international train category numbers, adapted accordingly to the definition of the attribute in the railML wiki. In railML2.4nor the speed information modelled via <speedChange> elements must be defined along the full extent of all tracks. Thus, it is mandatory to place a <speedChange> in the beginning of a model with a @dir="up" and on the end of a model with a @dir="down" value or at a mileage direction change once for each direction (see also 3.10.2 of document linked below). For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.7 (page 42). - Which of the existing elements can be used? - - * <speedChange> - - === Background === - - […] - === Links === * Forum discussion: - * […] + * [...] * Trac tickets: * #425 * Wiki documentation: - * none + * IS:speedChange: + * IS:speedProfile: == Proposed solution in railML 2.5 == - tbd + The element <speedChange> is already implemented in railML 2.x. + + The action resulting from this ticket is a clarification in the wiki. The following new semantic rules must be defined: + * Every line track has to have at least **one <speedChange>** at the track begin **with parameters @pos="0" and @dir="up"**. + * Every line track has to have at least **one <speedChange>** at the track end **with parameters @pos="{value equal to trackEnd@pos}" and @dir="down"**.- Status changed from new to accepted
- Summary changed from Extend definition of and add values to Define semantic rules for using elements
restructuring; adding solution proposal (semantic rules)
-
- Description changed
== Description == In order to define continuous speed profiles along the whole track network, it is mandatory, that oriented <speedProfile> elements are placed at every track begin and every track end leaving no gaps. === Background === This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future. <speedChange> is a sub-element of <trackElements>. In addition to the speedProfile@name attribute, the speed profile is also indicated in the attribute @etcsTrainCategory of the <speedChange> element. The values of the speedChange@etcsTrainCategory are railML2.4nor specific and a mapping of the values of the international train category numbers, adapted accordingly to the definition of the attribute in the railML wiki. In railML2.4nor the speed information modelled via <speedChange> elements must be defined along the full extent of all tracks. Thus, it is mandatory to place a <speedChange> in the beginning of a model with a @dir="up" and on the end of a model with a @dir="down" value or at a mileage direction change once for each direction (see also 3.10.2 of document linked below). For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.7 (page 42). === Links === * Forum discussion: * [...] * Trac tickets: + * #424 * #425 * Wiki documentation: - * IS:speedChange: - * IS:speedProfile: + * IS:speedChange: [https://wiki2.railml.org/wiki/IS:speedChange] + * IS:speedProfile: [https://wiki2.railml.org/wiki/IS:speedProfile] == Proposed solution in railML 2.5 == The element <speedChange> is already implemented in railML 2.x. The action resulting from this ticket is a clarification in the wiki. The following new semantic rules must be defined: * Every line track has to have at least **one <speedChange>** at the track begin **with parameters @pos="0" and @dir="up"**. * Every line track has to have at least **one <speedChange>** at the track end **with parameters @pos="{value equal to trackEnd@pos}" and @dir="down"**.adding links to Wiki
-
- Cc added @coordination.IS
- Description changed
== Description == In order to define continuous speed profiles along the whole track network, it is mandatory, that oriented <speedProfile> elements are placed at every track begin and every track end leaving no gaps. === Background === This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future. <speedChange> is a sub-element of <trackElements>. In addition to the speedProfile@name attribute, the speed profile is also indicated in the attribute @etcsTrainCategory of the <speedChange> element. The values of the speedChange@etcsTrainCategory are railML2.4nor specific and a mapping of the values of the international train category numbers, adapted accordingly to the definition of the attribute in the railML wiki. In railML2.4nor the speed information modelled via <speedChange> elements must be defined along the full extent of all tracks. Thus, it is mandatory to place a <speedChange> in the beginning of a model with a @dir="up" and on the end of a model with a @dir="down" value or at a mileage direction change once for each direction (see also 3.10.2 of document linked below). For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.7 (page 42). === Links === * Forum discussion: * [...] * Trac tickets: * #424 * #425 * Wiki documentation: * IS:speedChange: [https://wiki2.railml.org/wiki/IS:speedChange] * IS:speedProfile: [https://wiki2.railml.org/wiki/IS:speedProfile] == Proposed solution in railML 2.5 == The element <speedChange> is already implemented in railML 2.x. The action resulting from this ticket is a clarification in the wiki. The following new semantic rules must be defined: * Every line track has to have at least **one <speedChange>** at the track begin **with parameters @pos="0" and @dir="up"**. * Every line track has to have at least **one <speedChange>** at the track end **with parameters @pos="{value equal to trackEnd@pos}" and @dir="down"**. + + Semantic rules need to be added in the railML 2 wiki.- Owner set to @documentation.GOV
- Status changed from accepted to assigned
Semantic rules need to be added in wiki;
ticket has been re-assigned to Mr. Leberl who is responsible for railML wiki documentation
mentioned in issue #424
The Semcon has been introduced under
https://wiki2.railml.org/wiki/IS:speedChange#semconIS:011
and the change has been listed under
@coordination.IS please check the changes.
assigned to @coordination.IS and unassigned @documentation.GOV
changed milestone to %2.5
removed 2.5 label