-
Notifications
You must be signed in to change notification settings - Fork 50
Journey #80
Copy link
Copy link
Closed
Labels
change-requestRequest for an additional feature -- Must be discussed with the groupRequest for an additional feature -- Must be discussed with the groupdocument has been updatedNeTEx Document already updatedNeTEx Document already updated
Milestone
Metadata
Metadata
Assignees
Labels
change-requestRequest for an additional feature -- Must be discussed with the groupRequest for an additional feature -- Must be discussed with the groupdocument has been updatedNeTEx Document already updatedNeTEx Document already updated
Type
Fields
Give feedbackNo fields configured for issues without a type.
The TransportMode defined in Journey is currently of the AllVehicleModeOfTransportEnumeration type. This is not consistent with the TransportSubmode member because the list may contain a value that does not have TransportSubmode. There may be some type of anomaly here, or SelfDriveSubmode and TaxiSubmode may not be used as a TransportSubmode member.
In ValidityParameterAssignment, you can specify the vehicleMode and transportSubmode elements in the validityParameters member. These are in harmony with each other. It is noticeable that there are several modes of transport lists defined in NETEX (e.g.: AllVehicleModesOfTransportEnumeration, VehicleModeEnumeration, AllModesEnumeration etc.) , but as if they were used mixed in each entity and I do not understand why, so I think they may be due to a misspelling.