FlexibleServiceProperties (Subcomponent of SERVICE JOURNEY)
FLEXIBLE SERVICE PROPERTIES describe additional properties of a FLEXIBLE or demand responsive (DRT) service. They can be attached to a SERVICE JOURNEY to make it flexible.
In NeTEx, A SERVICE JOURNEY may either embed its own FLEXIBLE SERVICE PROPERTIES, or reference a shared instance. EPIP requires each SERVICE JOURNEY to embed its own instance.
FlexibleServiceProperties – XML Element
Classification | Name | Type | Cardinality | Description |
::> | ::> | DataManagedObject | ::> | FLEXIBLE SERVICE PROPERTIES inherits from DATA MANAGED OBJECT. |
«PK» | id | FlexibleServicePropertiesIdType | 1:1 | Identifier of FLEXIBLE SERVICE PROPERTIES. |
«FK» | TypeOfFlexibleServiceRef | TypeOfFlexibleServiceRef | 1:1 | TYPE OF FLEXIBLE SERVICE for which these are the properties. |
«cntd» | BookingArrangements | BookingArrangements | 0:1 | Booking contact for FLEXIBLE SERVICE. Currently not in use in the Austrian NeTEx Profile |
«enum» | FlexibleServiceType | FlexibleServiceEnum | 0:1 | Flexible service type. One of the following: · fixedPassingTimes · dynamicPassingTimes · fixedHeadwayFrequency · notFlexible Currently not in use in the Austrian NeTEx Profile |
| CancellationPossible | xsd:boolean | 0:1 | Whether cancellation is always possible (meaning the Operator can decide to cancel a journey, usually because there are not enough passengers, or they are too busy to run the service.) Currently not in use in the Austrian NeTEx Profile |
| ChangeOfTimePossible | xsd:boolean | 0:1 | Flag saying that it may be moved (usually passing time update to optimise the service). Currently not in use in the Austrian NeTEx Profile |
Example from the Austrian NeTEx Profile:
