search

NeTEx-CEN / NeTEx

NeTEx is a CEN Technical Standard for exchanging Public Transport schedules and related data.
http://netex-cen.eu
GNU General Public License v3.0
78 stars 40 forks source link

How to model a different departure than arrival platform? #738

Open skinkie opened 1 month ago

ue71603 commented 1 month ago

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

ue71603 commented 1 month ago

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

skinkie commented 1 month ago

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.

ue71603 commented 1 month ago

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.

skinkie commented 1 month ago

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?

ue71603 commented 1 month ago

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

skinkie commented 1 month ago

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

nick-knowles commented 1 month ago

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

image

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 image

ue71603 commented 2 weeks ago

@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?

Aurige commented 1 week ago

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).

skinkie commented 1 week ago

@Aurige is your suggestion to extend the ServiceJourneyPattern?

Aurige commented 1 week ago

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

skinkie commented 1 week ago

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?