How to model a different departure than arrival platform?

Question

How to model a different departure than arrival platform?

Opened this issue 3 months ago · 13 comments

Answer 1 · 2024-06-03T08:55:27.000Z

With Calls no problem. What do you really want to know?

Answer 2 · 2024-06-03T08:57:51.000Z

show be doable in Arrival see 10.6: https://www.xn--v-info-vxa.ch/sites/default/files/2024-05/NeTEx_Core-Realisation_Guide_TP_Suisse-v1.00.pdf

Answer 3 · 2024-06-03T09:09:43.000Z

With Calls no problem. What do you really want to know?

I would argue that with a Call it is a problem too, because a Call has a ScheduledStopPointRef, not the individual Arrival or Departure. Hence if you want to do it by calls you also have to split it in two calls.

Answer 4 · 2024-06-03T11:05:12.000Z

You are right. We had the discussion with Laurent. And that's why he thinks HRDF is superior (one of the reasons). What I think is that in NeTEx. This should always be modeled as two calls as there is manoeuver (splitting or a DeadRun).
So I would really be interested, what @Aurige or @nick-knowles says.

Answer 5 · 2024-06-03T11:14:32.000Z

I think there is a difference between JourneyPlanner, Passenger, Driver and Vehicle views on the same dataset. But now we are talking HRDF; some magic *Something allows for this special case?

Answer 6 · 2024-06-03T11:17:58.000Z

HRDF is very bad for this. The GLEISE are originally texts. We had to implement an extension to be able to store the sloids.

Answer 7 · 2024-06-03T11:29:08.000Z

Then I don't see the superiority of HRDF :-)

Answer 8 · 2024-06-04T14:54:20.000Z

You would need a separate Assignment for arrival and for departures . CAn Specify whether lLighting or boarding is allowed

I just check and this appears to be okay in NeTEx

The reference is on CALL PART

Nioe that there are some changes in the latest TM model to support DECK PLANS
TranStopAssignment is renamed to BoardingPositonAssignment

Answer 9 · 2024-06-21T22:55:29.000Z

@Aurige @nick-knowles Sorry, it doesn't make sense to rename TRAIN STOP ASSIGNMENT to PASSENGER BOARDING POSITION ASSIGNMENT. Especially as it can also link only a STOP PLACE with a TRAIN COMPONENT. No BOARDING POSITION at all involved. Most will be on QUAY level and almost nobody uses BOARDING POSITION anywhere.

Also if one is doing EPIP, then there are no CALL or CALL PART. So where is the assignment done for the arrival and departure?

Answer 10 · 2024-06-24T14:00:57.000Z

The PassingTime is for ScheduledStopPoint, the Quay/StopPlace assignment is expected to be provided by PassengerStopAssignment/DynamicStopAssignment. These StopAssignment have a boardingUse/alightingUse, so you can specialise them and have boarding and alighting on 2 different Quays (and you can of course define multiple StopAssignment).

Answer 11 · 2024-06-24T14:11:10.000Z

@Aurige is your suggestion to extend the ServiceJourneyPattern?

Answer 12 · 2024-06-24T14:14:24.000Z

No, why ? I think that we already have something that works to assign a different Quay to arrival and departure

Answer 13 · 2024-06-24T14:18:20.000Z

No, why ? I think that we already have something that works to assign a different Quay to arrival and departure

Can you provide an XML-snippet for a single call?