| Attribute "trainNumberField@elementNumber" Datatype [message #3656] |
Thu, 19 June 2025 13:22  |
Silvan Gruber
Messages: 9
Registered: July 2024
|
Junior Member |
|
|
Dear IL-community,
According to railml-schema (railML3.3), the data type of the attribute "trainNumberField@elementNumber" must be a "non-negative Integer". In Switzerland, we use train number fields labeled "2A" / "2B" when, for example, two trains are to be dispatched to the same track (see picture below). Therefore, the data type of the attribute would probably be "String."
Question to the community: Is there a need to label trainNumberFields with values other than "non-negative integer"?
Best regards
Silvan
[Updated on: Thu, 19 June 2025 13:26] Report message to a moderator |
|
|
|
|
|
| Re: Attribute "trainNumberField@elementNumber" Datatype [message #3659 is a reply to message #3658] |
Mon, 23 June 2025 08:17  |
Silvan Gruber
Messages: 9
Registered: July 2024
|
Junior Member |
|
|
Hi Joerg,
Thank you for your quick response ; )
We use the "designator" element exclusively to reference external data. Elements are primarily labeled with the "name" element (in the "infrastructure" subschema) and the "assetName" element (in the "interlocking" subschema).From my perspective, the "assetName" element in the interlocking subschema already provides the ability to label an element that only exists in the interlocking part. For example, we use this element for "IL:tvdSections" or "IL:trackIL." Since the "trainNumberField@elementNumber" attribute cannot be used as a label, we would suggest introducing an "assetName" element for the train number field.
Best regards
Silvan
[Updated on: Tue, 24 June 2025 12:05] Report message to a moderator |
|
|
|
|
|
Members
Search
Help
Login
Home
