| [railML3|alpha] Modelling of track conditions [message #1433] |
Mon, 31 October 2016 13:57  |
Martin Karlsson
Messages: 14
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
EAPD/ECC
S-405 02 Göteborg, Sweden
Visiting address: Polhemsplatsen 5
Tel.: +46 70 6667615
martinkarlsson(at)railbombardiercom
[Updated on: Mon, 31 October 2016 14:20] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
