| Re: Extra attributes on signal in RailML2.3 norwegian extention [message #1783 is a reply to message #1777] |
Thu, 03 May 2018 00:38  |
Tobias Bregulla
Messages: 20
Registered: June 2017
|
Junior Member |
|
|
Dear Morten, dear railML community!
Thanks for your posting, especially since we have a very similar problem
to solve right now. My colleague is currently developing a PlanPro[1] to
railML converter for the German infrastructure operator DB Netz.
In this project, the installation side of the signal in relation to the
track (right/left/above the track), the installation type
(upright/hanging) and also the mounting type (mast/gantry/...) must also
be transmitted. We planned to model our own extension of the railML 2.3
standard. If there were public documentation of the Norwegian railML 2.3
extension, we would base our modelling on it.
If there would be standardized modelling in railML 2.4, we could try to
suggest this - in the long run surely better - way to our client.
The topic of "number of lamps forming a signal" is not directly
comprehensible to us. Neither the practical relevance nor the concrete
implementation have we observed here in our projects so far. Can you
elaborate on this?
By the way: How many lamps does the signal 30ZU7 from the photo at
https://commons.wikimedia.org/wiki/File:Bad_Vilbel_Ks_2_Zs_3 _Zs_2.jpg
(installed in a new signal box of DB Netz in Hesse) have? 11 or 69? (SNCR)
Best regards,
Tobias Bregulla and the whole Bahnkonzept team
[1] Further information is available in German at
http://www.dbnetze.com/planpro/
Am 30.04.2018 um 13:48 schrieb Morten Johansen:
> Dear all
>
> The Norwegian ERTMS project have a need for holding some
> extra information when engineering our ETCS solution. This
> extra information is connected to signals and we have the
> idea that our need best can be fulfilled be adding tree
> attributes to the signal element as Norwegian extensions.
>
> What we have planned to do is to make these attributes as
> Norwegian extensions, all optional:
> - signal@nor:lamps (positive string), to hold the number of
> lamps at the current signals
> - signal@nor:side (enumeration: left/right/centre/other:),
> to hold the placement of the signal relative to the track
> and direction
> - signal@nor:mounted (enumeration: pole/gantry/other:), to
> hold where a signal is mounted.
> We in Norway have made et set of norwegian extensions to
> RailML2 based on the version RailML2.3, while waiting for
> the RailML3.1 to be released and sufficiently matured. Are
> any of the needs described above possible express by some,
> to us unknown, elements or attributes in standard RailML2.3?
> Or is it an acceptable way to handle these needs by making
> these attributes as suggested?
>
> Best regards
> Morten Johansen
> RailML coordinator in Bane NOR
|
|
|
|
Members
Search
Help
Login
Home
