Home » railML newsgroups » railML.infrastructure » [raillML3] Mounting information of signals (Proposal for new attribute in <signalConstruction>)
[raillML3] Mounting information of signals [message #3177] Mon, 18 December 2023 11:14 Go to next message
Georg Boasson is currently offline  Georg Boasson
Messages: 18
Registered: October 2020
Junior Member
For information and compatibility with railML2, a new attribute @mountedOn (railML2.4nor is using the name @mounted) is wanted in the <signalConstruction> element. The main issue for this attribute will be information about how the signal is physical mounted. The attribute may be optional. Proposed enumeration values as in railML2.5:

MountedOn: The way the signal is physical mounted (optional; xs:string; patterns: other:w{2,})

• pole: The signal is mounted on a pole along the track
• gantry: The signal is mounted above the track
• wall: The signal is mounted on a wall
• ground: The signal is mounted on the ground
Re: [raillML3] Mounting information of signals [message #3183 is a reply to message #3177] Fri, 05 January 2024 13:35 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Dear Georg,

thank you very much for your input / modeling request and Happy New Year!

As your modeling proposal is already very detailed, it will be easy to put it into a Git issue for upcoming railML version 3.3.
Are there other members in the railML community that need this information about the signal mounting, too?

Thank you very much and best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [raillML3] Mounting information of signals [message #3186 is a reply to message #3183] Wed, 17 January 2024 17:15 Go to previous messageGo to next message
Martin Zien is currently offline  Martin Zien
Messages: 14
Registered: December 2021
Junior Member
Hello Christian, hello Georg,

yes, I can agree that such an extension makes sense and would be a useful completion of the set of information provided in railML 3.x.
If such information would be provided as machine readable input from an Infrastructure Manager, it's not necessary to collect it addtionally from documents like Basic Design Specifications or by Site Surveys.
Having it as optional element, would still allow the way of working in the conventional way, if necessary.

Would be interesting to read, what other members think in this matter.


Best regards
Martin Zien
(Siemens Mobility)

[Updated on: Wed, 17 January 2024 17:17]

Report message to a moderator

Re: [raillML3] Mounting information of signals [message #3227 is a reply to message #3186] Fri, 19 April 2024 11:58 Go to previous messageGo to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 38
Registered: November 2022
Member
Dear all

This topic is now concluded with a ticket in the GitLab repository [1]. Please let us know if it does not meet your expectations.

[1] https://development.railml.org/railml/version3/-/issues/533

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [raillML3] Mounting information of signals [message #3229 is a reply to message #3227] Tue, 23 April 2024 12:10 Go to previous messageGo to next message
Francesca Iannaccone is currently offline  Francesca Iannaccone
Messages: 3
Registered: October 2023
Junior Member
Dear all,

sorry for the late reply. I think that the attribute is useful and I agree on the proposed values!

Kind regards,
Francesca Iannaccone (NEAT)
Re: [raillML3] Mounting information of signals [message #3240 is a reply to message #3229] Fri, 03 May 2024 15:44 Go to previous messageGo to next message
Martin Zien is currently offline  Martin Zien
Messages: 14
Registered: December 2021
Junior Member
Dear all,


I would like to add one more option to the discussion:

From experience in daily business in relation to Marker Boards, I would recommend to introduce a further option (see also attachment):

bufferStop: The signal (typically a board like ETCS- Stop Marker borad) is mounted on a Bufferstop that terminates a dead end track.


I agree to the other options presented in the discussion above.


Best regards
Martin Zien
(Siemens Mobility)
Re: [raillML3] Mounting information of signals [message #3241 is a reply to message #3240] Fri, 03 May 2024 16:43 Go to previous messageGo to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 38
Registered: November 2022
Member
Dear all

We have now two proposals on the representation of a signal at buffer stop. Do you see them as alternative, complementary etc.? Please provide your comments.

Proposed solutions:

- signalIS/signalConstruction/@type="virtual". A similar issue documented in the Wiki [1] of railML3 after the meeting of Schematic track plan working group.

- signalIS/signalConstruction/mountedOn="bufferStop". Solution coming from this forum thread.

[1] https://wiki3.railml.org/wiki/IS:signalConstruction

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Mon, 13 May 2024 16:22]

Report message to a moderator

Re: [raillML3] Mounting information of signals [message #3245 is a reply to message #3240] Mon, 13 May 2024 16:28 Go to previous messageGo to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 38
Registered: November 2022
Member
Dear Mr Zien

Please see the issue / ticket for the railML 3.3 development [1] changed according to your request i.e. new enumeration value added "bufferStop" to the attribute @mountedOn.

[1] https://development.railml.org/railml/version3/-/issues/533

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [raillML3] Mounting information of signals [message #3256 is a reply to message #3245] Fri, 21 June 2024 12:35 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Dear all,

in case you have any further comments and ideas for modelling the mounting of signals apart from the ones already mentioned in ticket #533 [1] please let us know. The ticket will be the base for implemented solution in railML 3.3.

[1] https://development.railml.org/railml/version3/-/issues/533

Thank you very much and best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Usage of //network/networkResource
Next Topic: Balise group values for IS:functionalType
Goto Forum:
  


Current Time: Mon Jul 15 10:55:13 CEST 2024