Missing property: operational length of platform

[MathiasVDA]

I see a structural property "length" that can be used in combination with a platform entity. But I don't see the "operational length". This is the length of the platform that a train can use to load/unload passengers.

This length is always smaller than the structural length and is influenced by:

• the location of the light signals
• the location of the panels indicating the end of the platform to passengers
• the arrival direction of the train (train needs to stop in front of the lightsignal)
• the departing direction of the train (train needs to be completely on the applicable side of the light signal the applies for the departing direction)

I would propose to add the semantic property but not as a value to be supplied by the infrastructure manager but for which the values will be infered from the position of a platform and the relevant signals (both lightsignals and the signals that indicate the end of the platform for passengers).

[Certiman]

We have added in comments of era:length (added marking):

Length of an infrastructure object which can be 
- a section of line (For operational length, use era:lengthOfSectionOfLine), 
- a tunnel (For operational length, use era:lengthOfTunnel), 
- a platform (**For its usable length, use era:lengthOfPlatform**), 
- a siding (For its usable length, use era:lengthOfSiding), and 
- length of other areas such as 
  - a non-stopping area (accuracy +- 10m), 
  - a walkway, 
  - an evacuation and rescue point.

Vehicle length.

It would allow to use era:lengthOfPlatform in the above cases, if at least some directionality is combined with that parameter, using era:Orientation. However, would not solve the 4 cases, as you would have to model a 2x2 directions matrix...

[Interoperable-data]

Dear @MathiasVDA , the current release has different sub-properties for length, see here https://data-interop.era.europa.eu/era-vocabulary/#length. Could you please have a look and see if those solve your issue?

[MathiasVDA]

Dear @MathiasVDA , the current release has different sub-properties for length, see here https://data-interop.era.europa.eu/era-vocabulary/#length. Could you please have a look and see if those solve your issue?

It depends on the use case. I see a sub property https://data-interop.era.europa.eu/era-vocabulary/#lengthOfPlatform with definition:

The maximum continuous length (expressed in metres) of that part of platform in front of which a train is intended to remain stationary in normal operating conditions for passengers to board and alight from the train, making appropriate allowance for stopping tolerances.

This would not be suitable for an operator to compose a train that is capable for all routes to unload passengers over the entire length of the train. For this the minimum continuous length should be used.

[nicolasgatez]

as @MathiasVDA said, the length of a platform is a combination of three factors :

• the physical platform itself (including the signalling elements such as signals, balises and panels (for trains) and panels(for passengers))
• The rules of the operator concerning the visibility of signals
• the route that the train follows. Some platforms have switches allowing a number of different routes, each one with its own operational length. (In Belgium up to 4 combinations physical/routes are managed).

The rules factor is not managed by the IM and thus cannot be provided.

If the routes are not managed in the RINF a meaningful length cannot be provided through this mean, only the position of the limiting elements, such as switches, signals and passenger panels.

If routes are managed in the RINF, then the length is not a property of the platform, but of the combination Route/Platfom.