Skip to content

Conversation

@Robbendebiene
Copy link
Contributor

@Robbendebiene Robbendebiene commented Aug 6, 2025

Resolves #873

In general the proposal follows the idea of place equipments like LiftEquipment or RampEquipment which all derive from an abstract AccessEquipment.

This slightly deviates from the original proposal in the following ways:

  • Dropped MinimumEquipmentLength and MaximumEquipmentLength to avoid choice element in favour of IsAdjustableLength. Also the minimum length for sliding steps and ramps would usually be close to 0 which isn't very valuable.
  • Added HoistOperatingRadius to HoistVehicleEquipment for feature parity with AccessVehicleEquipment
  • Added NumberOfTreads to RetractableStepVehicleEquipment to clarify some scenarios (see aa7c6e3)
  • Modified AccessVehicleEquipment & WheelchairVehicleEquipment to reuse PassengerEquipmentGroup in order to avoid code duplication (see 563fdab)
  • Dropped KneelingBoardingHeight in favour of a more flexible modelling way
  • Added real ramp length to reliably calculate the ramps slope because the external length can differ from the ramps length (example)
  • Used "External" instead of "Equipment" to describe outer equipment dimensions

This addresses:
- How to model an entrance that has retractable steps complementing built-in steps? What should be NumberOfSteps in this case? (see ICE)
- How to detect that something is a sliding step offering level access. It is somehow a step but doesn't introduce any relevant stepping height for passengers.
Only have a single kneeling property that indicates whether other measurements where taken when kneeling is active/inactive.
@TuThoThai TuThoThai added this to the netex_2.1 milestone Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants