railML 3 issueshttps://development.railml.org/railml/version3/-/issues2023-12-08T10:53:03+01:00https://development.railml.org/railml/version3/-/issues/522Fixing genericArea location2023-12-08T10:53:03+01:00IS CoordinationFixing genericArea location## Description
The `<genericArea>` element has a mandatory child element `<location>`. This does not make sense for generic areas that do not have a circular or polygon location, but refer to area limits (child element `<isLimitedBy>`)....## Description
The `<genericArea>` element has a mandatory child element `<location>`. This does not make sense for generic areas that do not have a circular or polygon location, but refer to area limits (child element `<isLimitedBy>`). For railML 3.3 it is foreseen to set the mandatory element `<location>` to optional. For railML 3.2 a work-around based on zero-entries shall be applied.
### Background
### Links
* Forum discussion:
* Torben Brand, 10.10.2023: https://www.railml.org/forum/index.php?t=msg&th=925&start=0&
* Git issues:
* #479
* #522
* Wiki documentation:
* IS:genericArea: https://wiki3.railml.org/wiki/IS:genericArea
## Proposed solution railML 3
In railML 3.2: Workaround based on zero entries as documented in the wiki.
In railML 3.3: Setting child element `<location>` to optional.3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/387Update Simple Example to Version 3.22023-11-28T10:06:37+01:00IS CoordinationUpdate Simple Example to Version 3.2## Description
The following issues have been found so far:
* The switch "69W04" is located on netElement "ne_b02". It "functions" as switch (with choice of way) for trains that pass this netElement in reverse direction. Therefore, **a...## Description
The following issues have been found so far:
* The switch "69W04" is located on netElement "ne_b02". It "functions" as switch (with choice of way) for trains that pass this netElement in reverse direction. Therefore, **applicationDirection of the switch element "69W04" need to be corrected from "normal" to "reverse"**.
* The switches "69W03" and "60W04" have linear coordinates given in kilometer values ("4.500"). The used linearPositioningSystem defines the units to be meters. Therefore, **the location measure values of switches "69W03" and "69W04" need to be corrected from km to m ("4.500" --> "4500.0").**
### Background
Simple Example can be downloaded from railML Website: [https://www.railml.org/en/user/exampledata.html]
### Links
* Forum discussion
* Peter Vancsa, 26.06.2020: [https://www.railml.org/forum/index.php?t=msg&th=738&start=0&]
* Trac tickets
* Wiki documentation
## Proposed solution
Attribute @applicationDirection of the switch element "69W04" need to be corrected from "normal" to "reverse" in Simple Example railML 3.1 export file.
Attribute @measure of the switch element "69W03" need to be corrected from "4.500" to "4500.0". Attribute @measure of the switch element "69W04" need to be corrected from "4.550" to "4550.0".3.2CoordinationCoordinationhttps://development.railml.org/railml/version3/-/issues/314Remove empty sequences schema (de: Leere Schemensequenzen entfernen)2022-05-09T17:36:28+02:00IS CoordinationRemove empty sequences schema (de: Leere Schemensequenzen entfernen)## Description
Current railML v3.1 beta version contains a number of empty sequences in elements, e.g. in <netRelation>, <platformEdge> or <horizontalCurve>. Although the schema is still syntactically valid with the empty sequences, it i...## Description
Current railML v3.1 beta version contains a number of empty sequences in elements, e.g. in <netRelation>, <platformEdge> or <horizontalCurve>. Although the schema is still syntactically valid with the empty sequences, it is our aim to remove them from the schema. The origin of the empty sequences is presumably to be found in the automatic generation process.
### Background
Currently, railML v3 schema files are exported from UML modelling tool "Enterprise Architect". It seems that every complexType is exported together with a complexContent requiring a sequence.
### Links
* Forum post 1: [https://www.railml.org/forum/index.php?t=msg&th=539&goto=1660&#msg_1660]
* Forum thread 2: [https://www.railml.org/forum/index.php?t=msg&th=633&start=0&]
## Proposed solution for railML 3.1
If the automatic XSD generation in Enterprise Architect does not allow complexType with simpleContent, empty sequences will be part of the automatic XSD export. In that case, only a post-processing script may help to remove the empty sequences.3.3CO CoordinationCO Coordinationhttps://development.railml.org/railml/version3/-/issues/254Unit for <tunnel>@crossSection (de: Einheit für <tunnel>@crossSection)2022-05-09T17:03:24+02:00CoordinationUnit for <tunnel>@crossSection (de: Einheit für <tunnel>@crossSection)The unit for the cross section of an Tunnel is metre (tLengthM), but must be square metre, as the area of the cross section is meant. Typical values for railways are 80 m² or 100 m², see http://commons.wikimedia.org/wiki/File:4-05m_Tunne...The unit for the cross section of an Tunnel is metre (tLengthM), but must be square metre, as the area of the cross section is meant. Typical values for railways are 80 m² or 100 m², see http://commons.wikimedia.org/wiki/File:4-05m_Tunnelquerschnitt.png for more details.
### Links
* Forum discussion
* Trac tickets
* #54 crossSection: ocp vs. tunnel
* Wiki documentation
## Proposed solution railML 3.1
railML 3.1 does not implement tunnel cross section.
## Proposed solution railML 3.x
When a use case requires the implementation of a tunnel cross section, the resulting model has to consider this issue.3.3IS CoordinationIS Coordination