Robin Thomas

`TractiveElementType` and `TrailingElementType` already have an `equipments` property. So it almost feels inconsistent that `VehicleType` doesn't. Also a `DeckPlan` is referenced from a `VehicleType` but its elements can contain equipments...

Just want to give a short comparison of the current status quo vs the proposal. Consider the use case of depicting that a vehicle type has 3 steps in its...

This sounds like equipment is considered to be something unique that can only exist once in reality. This makes sense when thinking e.g. about an elevator that shall be monitored....

> Not sure if the answer for DeckPlan is that every equipment is wrapped in an ActualVehicleEquipment. To answer my own question: If I interpret the documentation correctly then `ActualVehicleEquipment`...

This was discussed at the 2025-08-26 meeting. It was mentioned that: - `VehicleType` is supposed to be something of a lower level of detail like "this is a low floor...

Actually it is already possible to assign `Equipments` to a `VehicleType`. It's just the other way around than what we expected. If this is allowed, does it rely hurt to...

@Aurige If adding `equipments` to `VehicleType` is not an option, what about one of the following changes: - Add properties from `VehicleType` like `DeckPlanRef`, `Width`, `PropulsionType`, `capacities` etc. to `VehicleModel`....

Hi and thanks for the detailed report. We don't really like the idea of having a separate setting for this as we want to keep the app as simple as...

At the time we didn't really know what the process for contributing to NeTEx was. So we first created the proposals as issues and waited for feedback. Now knowing more...

Hi thanks for the feature request. What you propose is exactly what we planned back then. We just didn't find the time yet 🙂