Home » railML newsgroups » railml.infrastructure » Level crossing default parameters / Standardwerte bei Bahnübergängen
Level crossing default parameters / Standardwerte bei Bahnübergängen [message #1716] Mon, 12 March 2018 13:10 Go to next message
Tobias Bregulla is currently offline  Tobias Bregulla
Messages: 15
Registered: June 2017
Junior Member
Dear Community,

when modelling level crossings for exports from our program GPSinfradat
more detailed we encountered a problem with standard values in railML 2.3:

After the documentation in the schema and on the wiki page
(http://wiki.railml.org/index.php?title=IS:levelCrossing), there are the
following default values:
- Length: 0,000 metres (length)
- Crossing angle: 90 degrees (angle)
- Level crossing protection: none (protection)
All values are optional.

Thus we would express (from our interpretation) by omitting the optional
values that the level crossing crosses right-hand and has a width of 0
meters. This can be wrong on the one hand (e. g. we do not have a
crossing angle because it could not be detected) and on the other hand
it is not technically correct (width of the level crossing is 0 meters).
Or are the defaults only valid if the attribute exists but is not filled?

Can the default values be removed from railML 2.4 on, so that an
"UNKNOWN" value can be transferred?
For railML 2.3 (and before that, if necessary), can you please add a
note to the wiki saying that missing the values does not necessarily
mean the above mentioned values?

Best regards,

Tobias Bregulla
Bahnkonzept Dresden/Germany
***************************
Liebe Community,

bei der verfeinerten Modellierung von Bahnübergängen für Exporte aus
unserem Programm GPSinfradat sind wir auf ein Problem mit Standardwerten
in railML 2.3 gestoßen:

Nach der Dokumentation im Schema und auf der Wiki-Seite
(http://wiki.railml.org/index.php?title=IS:levelCrossing) gibt es
Standardwerte für folgende Attribute:
- Länge: 0,000 Meter (length)
- Kreuzungswinkel: 90 Grad (angle)
- Sicherungsart: keine (protection)
Beide Werte sind optional.

Damit würden wir (aus unserer Interpretation) schon alleine durch ein
Weglassen der optionalen Werte ausdrücken, daß der Bahnübergang
rechtwinkling kreuzt und eine Breite von 0 Metern hat. Dies kann
einerseits falsch sein (z.B. Kreuzungswinkel liegt uns nicht vor, da er
nicht erfasst werden konnte) und ist andererseits fachlich nicht
zutreffen (Breite des Bahnübergangs ist 0 Meter). Oder gelten die
Vorgaben nur, wenn das Attribut zwar vorhanden, aber nicht gefüllt ist?

Können bitte ab railML 2.4 die Standardwerte entfernt werden, so daß
auch sinnvoll ein "UNBEKANNT"-Wert übertragen werden kann?
Kann bitte für railML 2.3 (und ggf. davor) ein entsprechender Hinweis im
Wiki angebracht werden, daß ein Fehlen der Werte nicht zwingend oben
genannte Werte bedeutet?

Beste Grüße,

Tobias Bregulla
Bahnkonzept Dresden
Re: Level crossing default parameters / Standardwerte bei Bahnübergängen [message #1720 is a reply to message #1716] Mon, 12 March 2018 16:45 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 179
Registered: January 2016
Senior Member
Dear Tobias,
dear all,

thank you for your input and remarks on current level crossing
implementation!

Am 12.03.2018 um 13:10 schrieb Tobias Bregulla:
> [...]
> After the documentation in the schema and on the wiki page
> (http://wiki.railml.org/index.php?title=IS:levelCrossing), there are the
> following default values:
> - Length: 0,000 metres (length)
> - Crossing angle: 90 degrees (angle)
> - Level crossing protection: none (protection)

Let's have a look at the default values one by one:

@length="0"
You are right, this makes no sense. A better default value will be
"unknown" resulting from removing the explicit default value.

@angle="90"
You are right, "unknown" will be the better default value. Therefore, it
is better to remove the current default value.

@protection="none"
I am not sure about this default value. Therefore, I would like to ask
the community: do you need to exchange data about level crossings where
you do not know about the technical protection equipment of the level
crossing?

Any feedback is highly appreciated...

I created a Trac ticket [1] for the topic to be solved until release of
railML 2.4.

[1] https://trac.railml.org/ticket/323

Best regards
Christian

--
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
Re: Level crossing default parameters / Standardwerte bei Bahnübergängen [message #1724 is a reply to message #1720] Tue, 13 March 2018 10:57 Go to previous messageGo to next message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 253
Registered: August 2008
Senior Member
Dear Christian,

> @protection="none"
> I am not sure about this default value. Therefore, I would like to ask the community: do you need to exchange data about level crossings where you do not know about the technical protection equipment of the level crossing?

Yes. I want to opt for this usage, i. e. opt for allowing to express a level crossing with unknown kind of protection, therefore deleting the default value.

In timetables, you may have a speed restriction because of a level crossing (a speed restriction starting several hundred metres before the level crossing and ending at the level crossing, labelled "BÜ km 12,34" or such in the timetable). To place the label for the timetable into the railML file, it may be preferable to use a <levelCrossing> element. But, from the pure timetable, one cannot see whether the speed restriction is e. g. because of a reduced sight at a non-technical protected level crossing or e. g. because of a too short switch-on distance of a level crossing with technical protection.

With best regards,
Dirk.
Re: Level crossing default parameters / Standardwerte bei Bahnübergängen [message #1727 is a reply to message #1720] Fri, 16 March 2018 08:42 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 179
Registered: January 2016
Senior Member
Dear all,

Am 12.03.2018 um 16:45 schrieb Christian Rahmig:
> [...]
> @length="0"
>
> @angle="90"
>
> @protection="none"
>
> I created a Trac ticket [1] for the topic to be solved until release of
> railML 2.4.
>
> [1] https://trac.railml.org/ticket/323

All three default values have been removed. The ticket has been closed.

Best regards
Christian

--
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
Previous Topic: loading gauge
Next Topic: [railML 3.1] level crossing parameters
Goto Forum:
  


Current Time: Sat Nov 17 16:32:07 CET 2018