Hello railML world! [message #1631] |
Thu, 31 August 2017 11:19 |
Jörgen Strandberg
Messages: 15 Registered: August 2017
|
Junior Member |
|
|
Hi,
This is my first posting and I would just like to introduce myself.
I'm Jörgen Strandberg, a software developer from a background of an electronics engineer. I've been with Bombardier Transportation a 15+ years, working with railway signaling from the viewpoint of a software toolmaker, with focus on configuring the products we sell.
Ich bin Jörgen Strandberg, ein Softwareentwickler aus dem Hintergrund eines Elektronik-Ingenieurs. Ich bin mit Bombardier Transportation eine 15 + Jahre gewesen. Und ich habe mit Eisenbahn-Signalisierung aus der Sicht eines Software-Toolmaker, mit Fokus auf die Konfiguration der Produkte, die wir verkaufen, gearbeitet.
Lazy as I am, ever since I started to use one, I've been on a mission to let the computer do as much work as possible. For some years now that means rather do data exchange than entering data more than once.
I'm looking forward to learn and discuss railML modeling techniques with you all.
Regards
Jörgen
|
|
|
Re: Hello railML world! [message #1636 is a reply to message #1631] |
Fri, 01 September 2017 15:12 |
christian.rahmig
Messages: 458 Registered: January 2016
|
Senior Member |
|
|
Dear Jörgen,
thank you for your introduction and welcome to the railML community!
I am Christian, the railML infrastructure scheme coordinator and
together with the other active modellers and users I am looking forward
to discussing with you about railML infrastructure modelling issues
here. Is there any special topic that you are interested in?
Best regards
Christian
Am 31.08.2017 um 11:19 schrieb Jörgen Strandberg:
> Hi,
>
> This is my first posting and I would just like to introduce
> myself.
>
> I'm Jörgen Strandberg, a software developer from a
> background of an electronics engineer. I've been with
> Bombardier Transportation a 15+ years, working with railway
> signaling from the viewpoint of a software toolmaker, with
> focus on configuring the products we sell.
> Ich bin Jörgen Strandberg, ein Softwareentwickler aus dem
> Hintergrund eines Elektronik-Ingenieurs. Ich bin mit
> Bombardier Transportation eine 15 + Jahre gewesen. Und ich
> habe mit Eisenbahn-Signalisierung aus der Sicht eines
> Software-Toolmaker, mit Fokus auf die Konfiguration der
> Produkte, die wir verkaufen, gearbeitet.
>
>
> Lazy as I am, ever since I started to use one, I've been on
> a mission to let the computer do as much work as possible.
> For some years now that means rather do data exchange than
> entering data more than once.
>
> I'm looking forward to learn and discuss railML modeling
> techniques with you all.
>
> Regards
> Jörgen
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Re: Hello railML world! - speed restrictions in railML 2.x [message #1651 is a reply to message #1645] |
Mon, 09 October 2017 11:28 |
Dirk Bräuer
Messages: 313 Registered: August 2008
|
Senior Member |
|
|
Hi Jörgen,
I follow the speed restrictions discussions since several years and so I feel competent to answer some of your questions:
> And as a type of train category based on axle load cannot be directly specified in an IS::speedChange, an additional IS:speedProfile with an appropriate maxAxleLoad value could be created and referenced.
This was the intention. A <speedChange> shall not directly specify an axle load nor any other restriction. Instead, the corresponding <speedProfile> shall include all restrictions which apply for that profile.
> - Should speedProfile instances additionally specify maxAxleLoad, and if so what values are relevant in the example?
Yes, that is the intention of the attribute <speedProfile>.maxAxleLoad.
> - How can the end of speed restrictions be modeled, e.g. the one for trains with axle load above 17.5 tons in the example should end at 500 m?
Up to railML 2.2 (including): with vMax='999' as a tentativeness
<speedChange vMax='999'/>
From railML 2.3 (including): with vMax='end':
<speedChange vMax='end'/>
both with pos= location of end of speed restriction.
Please be aware that the end of a speed restriction can apply either to the train head or end of train. So, the attribute <speedChange>.trainRelation may be of interest, too. That's why there is no "length" of a speed restriction.
See also
http://www.wiki.railml.org/index.php?title=IS:speedChange
With best regards,
Dirk Bräuer.
|
|
|
|