| |
ServiceJourneyPattern |
mandatory |
1..1 |
unknown |
|
|
| + |
Name |
optional |
1..1 |
unknown |
|
|
| + |
RouteView |
mandatory |
1..1 |
unknown |
|
|
| ++ |
LineRef |
mandatory |
1..1 |
unknown |
|
|
| + |
DirectionType |
mandatory |
1..1 |
unknown |
|
|
| + |
pointsInSequence |
mandatory |
1..1 |
unknown |
|
|
| ++ |
StopPointInJourneyPattern |
mandatory |
1..1 |
unknown |
|
|
| +++ |
ScheduledStopPointRef |
mandatory |
1..1 |
unknown |
|
|
| +++ |
ForAlighting |
mandatory |
1..1 |
unknown |
|
|
| +++ |
ForBoarding |
mandatory |
1..1 |
unknown |
|
|
| +++ |
DestinationDisplayRef |
optional |
1..1 |
unknown |
|
Indicates that the destination has changed. Superseeds Line or ServiceJourney |
| +++ |
RequestStop |
optional |
1..1 |
unknown |
|
|
| +++ |
StopUse |
optional |
1..1 |
unknown |
|
All values possible |
| +++ |
bookingArrangements |
optional |
1..1 |
unknown |
|
|
| ++++ |
BookingArrangementRef |
optional |
1..1 |
unknown |
|
Specially we use bookingArrangementRef here to model the information that a stop is flexible. From the HRDF conversion only a BookingNote can be passed at the moment. With native NeTEx handling we can transfer more information. |
| ++++ |
BookingArrangement |
we expect a BookingArrangementRef. We use this here to show how native NeTEx handling could improve transfering information here |
1..1 |
unknown |
|
|
| + |
ServiceJourneyPatternType |
expected |
1..1 |
unknown |
|
|