Global element

DynamicStopAssignment

Defined in NeTEx/xsd/netex_part_2/part2_journeyTimes/netex_vehicleJourneyStopAssignment_version.xsd:299

Transmodel concept DYNAMIC STOP ASSIGNMENT

Change to a PASSENGER STOP ASSIGNMENT.

Type

DynamicStopAssignment_VersionStructure

Content model

Element structure

inherited from EntityInVersionStructure 3 items
- groupEntityInVersionGroup 0..1
  
  Common Properties of an ENTITY IN VERSION.
  - choice 0..1
    - validityConditions 1..1 validityConditions_RelStructure
      
      VALIDITY CONDITIONs conditioning entity.
    - ValidBetween 1..unbounded ValidBetween_VersionStructure
      
      OPTIMISATION. Simple version of a VALIDITY CONDITION. Comprises a simple period. NO UNIQUENESS CONSTRAINT.
  - alternativeTexts 0..1 alternativeTexts_RelStructure
    
    Additional Translations of text elements.
inherited from DataManagedObjectStructure 4 items
- groupDataManagedObjectGroup 1..1
  
  Common Properties of an object managed by a responsible ORGANISATION.
  - keyList 0..1 KeyListStructure
    
    A list of alternative Key values for an element.
  - privateCodes 0..1 PrivateCodesStructure
    
    A list of private codes that uniquely identifiy the element. May be used for inter-operating with other (legacy) systems. +v2.0
  - Extensions 0..1 ExtensionsStructure
    
    User defined Extensions to ENTITY in schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).
  - BrandingRef 0..1 BrandingRefStructure
    
    Reference to a BRANDING.
inherited from Assignment_VersionStructure_Dummy 2 items
- groupAssignmentGroup 1..1
  
  Elements for an ASSIGNMENT. An ASSIGNMENT assigns a property to an another element. It has a name and an order.
  - Name 0..1 MultilingualString
    
    Name of ASSIGNMENT.
  - Description 0..1 MultilingualString
    
    Description of ASSIGNMENT.
inherited from StopAssignment_VersionStructure 9 items
- groupStopAssignmentGroup 1..1
  
  Elements for a STOP ASSIGNMENT.
  - BoardingUse 0..1 xsd:booleandefault true
    
    Whether alignment is for boarding use. Default is 'true'.
  - AlightingUse 0..1 xsd:booleandefault true
    
    Whether alignment is for alighting use. Default is 'true'.
  - PrivateCode 0..1 PrivateCodeStructure
    
    DEPRECATED - use privateCodes. -v2.0
  - choice 0..1
    
    Reference or inline declaration of SCHEDULED STOP POINT which is being assigned.
    - ScheduledStopPointRef 1..1 ScheduledStopPointRefStructure
      
      Reference to a SCHEDULED STOP POINT.
    - ScheduledStopPoint 1..1 ScheduledStopPoint_VersionStructure
      
      A POINT where passengers can board or alight from vehicles. It is open, which hierarchical level such a point has. It can represent a single door (BoardingPosition) or a whole ZONE. The association to the physical model is done with STOP ASSIGNMENTs.
  - groupStopAssignmentDirectionGroup 1..1
    
    Directional elements for a STOP ASSIGNMENT. +v2.0
    - ArrivesForwards 0..1 xsd:booleandefault true
      
      Whether VEHICLE or TRAIN arrives at stop travelling in a forwards direction, i.e. operational orientation. Default is true. +v2.0
    - DepartsForwards 0..1 xsd:booleandefault true
      
      Whether VEHICLE or TRAIN departs from stop travelling in a forwards direction, i.e. operational orientation. Default is true.. Default is true. +v2.0
    - ArrivesFromLeft 0..1 xsd:booleandefault true
      
      Whether VEHICLE or TRAIN is expected to arrive at the QUAY from the left of a bystander facing the track edge of the platform. Default is true. +v2.0
    - DepartsToRight 0..1 xsd:booleandefault true
      
      Whether VEHICLE or TRAIN is expected to depart from the QUAY to the right of a bystander facing the track edge of the platform. Default is true. +v2.0
inherited from PassengerStopAssignment_VersionStructure 11 items
- groupPassengerStopAssignmentGroup 1..1
  
  Elements for a PASSENGER STOP ASSIGNMENT. Either StopPlace(Ref) or Quay(Ref) must at least be present. Best practice is to always have at least the StopPlace(Ref). It is also prefered that the Ref are used and the Quay/StopPlace are defined on their own in the appropriate Frame.
  - choice 0..1
    
    STOP PLACE to which SCHEDULED STOP POINT is to be assigned.
    - StopPlaceRef 1..1 StopPlaceRefStructure
      
      Reference to a STOP PLACE.
    - StopPlace 1..1 StopPlace_VersionStructure
      
      Version of a named place where public transport may be accessed. May be a building complex (e.g. a station) or an on-street location. Can be a STOP PLACE, VEHICLE MEETING POINT, TAXI RANK. Note: If a master id exists for a StopPlace (must be stable and globally unique), then it is best used in the id. Optimally it would be built according IFOPT. It can also be put into one of the privateCodes in addition. If it is stored in KeyValue, then it should be documented well, so that importing systems know, which id is the relevant one.
  - choice 0..1
    
    QUAY to which SCHEDULED STOP POINT is to be assigned.
    - QuayRef 1..1 QuayRefStructure
      
      Reference to a QUAY.
    - Quay 1..1 Quay_VersionStructure
      
      A place such as platform, stance, or quayside where passengers have access to PT vehicles, Taxi cars or other means of transportation. A QUAY may contain other sub QUAYs. A child QUAY must be physically contained within its parent QUAY.
  - choice 0..1
    
    BOARDING POSITION to which SCHEDULED STOP POINT is to be assigned.
    - BoardingPositionRef 1..1 BoardingPositionRefStructure
      
      Reference to a BOARDING POSITION.
    - BoardingPosition 1..1 BoardingPosition_VersionStructure
      
      A location within a QUAY from which passengers may directly board, or onto which passengers may directly alight from, a VEHICLE.
  - choice 0..1
    - passengerBoardingPositionAssignments 0..unbounded passengerBoardingPositionAssignments_RelStructure
      
      Train stop assignments elements to use for which SCHEDULED STOP POINT is to be assigned. +v2.0
      
      inherited from passengerBoardingPositionAssignments_RelStructure 3 items
      
      choice 1..unbounded
      
      PassengerBoardingPositionAssignmentRef 1..1 PassengerBoardingPositionAssignmentRefStructure
      
      Reference to a PASSENGER BOARDING POSITION ASSIGNMENT.
      
      PassengerBoardingPositionAssignment 1..1 PassengerBoardingPositionAssignment_VersionStructure
      
      The default allocation of a SCHEDULED STOP POINT to a specific STOP PLACE, and also possibly a QUAY and BOARDING POSITION. NB Rebmed from TRAIN STOP ASSIGNMENT in v2.
      
      PassengerBoardingPositionAssignment_Dummy 1..1 PassengerBoardingPositionAssignment_VersionStructureabstract
      
      Assignment of a SCHEDULED STOP POINT to a STOP PLACE and QUAY, etc.
    - trainElements 0..unbounded trainStopAssignments_RelStructure
      
      Train elements to which SCHEDULED STOP POINT is to be assigned. DEPRECATED -v2.0
inherited from VehicleJourneyStopAssignment_VersionStructure 2 items
- groupVehicleJourneyStopAssignmentGroup 1..1
  
  Elements for a VEHICLE JOURNEY STOP ASSIGNMENT. Original PASSENGER STOP ASSIGNMENT for which this is a change.
  - VehicleJourneyRef 0..unbounded VehicleJourneyRefStructure
    
    Reference to a VEHICLE JOURNEY. If given by context does not need to be repeated.
  - PassengerStopAssignmentRef 0..1 PassengerStopAssignmentRefStructure
    
    Reference to a PASSENGER STOP ASSIGNMENT.
Defined here
groupDynamicStopAssignmentGroup 1..1

Elements for a DYNAMIC PASSENGER STOP ASSIGNMENT.
- JourneyPatternRef 0..1 JourneyPatternRefStructure
  
  Reference to a JOURNEY PATTERN.
- DatedVehicleJourneyRef 0..1 VehicleJourneyRefStructure
  
  Reference to a DATED VEHICLE JOURNEY.

Properties

Attributes

Attribute	Type	Use	Documentation	Source
`id`	`DynamicStopAssignmentIdType`	required	—

inherited 12 attributes from base types

Attribute	Type	Use	Documentation	Inherited from
`nameOfClass`	`NameOfClass`	optional	Name of Class of the ENTITY. Allows reflection. Fixed for each ENTITY type.	`EntityStructure`
`dataSourceRef`	`DataSourceIdType`	optional	Name of source of the data.	`EntityInVersionStructure`
`created`	`xsd:dateTime`	optional	Date ENTITY was first created.	`EntityInVersionStructure`
`changed`	`xsd:dateTime`	optional	Date ENTITY or version was last changed.	`EntityInVersionStructure`
`modification`	`ModificationEnumeration`	optional default: `new`	Nature of last modification: new, revise, delete, unchanged, delta. Default is "new".	`EntityInVersionStructure`
`version`	`VersionIdType`	optional	Version number of entity. The value may be "any" or a VERSION number adhering to agreed-upon formatting and interpretation rules (representing, e.g., a number or a date). Consecutive VERSION numbers should be strictly increasing.	`EntityInVersionStructure`
`status`	`StatusEnumeration`	optional default: `active`	Whether ENTITY is currently in use. Default is "active".	`EntityInVersionStructure`
`derivedFromVersionRef`	`VersionIdType`	optional	Version of this object from which this version of ENTITY was derived.	`EntityInVersionStructure`
`compatibleWithVersionFrameVersionRef`	`VersionIdType`	optional	Version of frame from with which this version of ENTITY is compatible. Assumes Frame of the same Id as current frame.	`EntityInVersionStructure`
`derivedFromObjectRef`	`ObjectIdType`	optional	Identity of object from which this object of ENTITY was derived. Normally the same.	`EntityInVersionStructure`
`responsibilitySetRef`	`ResponsibilitySetIdType`	optional	Reference to RESPONSIBILITY SET for managing the object. If absent, then responsibility is same as for containing context of this object.	`DataManagedObjectStructure`
`order`	`xsd:positiveInteger`	optional	Order in which to show an ASSIGNMENT. In some rare cases order makes no sense. The convention should be that order="1" is set then for all elements. -v2.0	`Assignment_VersionStructure`

DynamicStopAssignment

Type

Related elements

Element structure

Attributes