Home » railML newsgroups » railml.infrastructure » [railML3|alpha] Modelling of track conditions
[railML3|alpha] Modelling of track conditions [message #1433] Mon, 31 October 2016 13:57 Go to next message
Martin Karlsson is currently offline  Martin Karlsson
Messages: 8
Registered: October 2016
Junior Member
A number of track conditions (electrification, weightLimit, clearanceGauge etc.) are modelled in the "parameters" section of the infrastructure schema. A net element in the topology section (e.g. a track or a line) can then refer to the parameters which apply to it.

I would prefer if these track conditions were instead modelled in the "operation" section, as subclasses of OperationalEntity.

The most important reason for this is that almost all of these conditions can change anywhere, also in the middle of a track. As the OperationalEntity is derived from the LocatedNetEntity, it offers a much more flexible way of indicating the area where the condition applies, ranging from a small part of one track to the whole network. Since the ETCS language allows to communicate most of these conditions between arbitrary positions, I believe railML must support that too.

Another reason is that the direction of reference is inconsistent with the rest of the model. Assets and operational entities refer to their locations, but here it is the location which refers to its parameters. This also means that references to physical entities appear inside the topology section, which otherwise is a purely mathematical model.

Martin Karlsson
Bombardier Transportation
Rail Control Solutions
S-405 02 Göteborg, Sweden
Visiting address: Polhemsplatsen 5
Tel.: +46 70 6667615

[Updated on: Mon, 31 October 2016 14:20]

Report message to a moderator

Re: [railML3|alpha] Modelling of track conditions [message #1438 is a reply to message #1433] Tue, 08 November 2016 05:57 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 65
Registered: January 2016
Dear Martin,

Am 31.10.2016 um 13:57 schrieb Martin Karlsson:
> [...]
> I would prefer if these track conditions were instead
> modelled in the "operation" section, as subclasses of
> OperationalEntity.

Thank you for your feedback on this part of the model. Based on your
reasoning and the feedback I got in Paris from other users, I confirm
that the current approach of track parameter modelling is not very
useful although it is very similar to the "infraAttrGroups approach" of
current railML v2.x. Therefore, the parameter groups will be moved to
the asset and operational sections of the model an follow the generic
approach of location referencing provided by the RailTopoModel base.

Best regards

Christian Rahmig
railML.infrastructure coordinator
Previous Topic: [railML3|alpha] Linear coordinates
Next Topic: [railML3|alpha] Missing track conditions
Goto Forum:

Current Time: Sun Jan 21 07:32:45 CET 2018