[go: nahoru, domu]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Estimated delay in timetables #749

Open
ue71603 opened this issue Jul 4, 2024 · 6 comments
Open

Estimated delay in timetables #749

ue71603 opened this issue Jul 4, 2024 · 6 comments
Assignees
@Aurige
Labels
question
Milestone
netex_2.0

Comments

@ue71603
Copy link
Contributor
ue71603 commented Jul 4, 2024 •
edited by skinkie
Loading

In some timetables with already know that there will be a probable delay (e.g. due to construction). We would prefer not to change the arrival and departure time (Arrival/Time and Departure/Time). We were thinking about using CheckConstraints also for that.

However, it seems we don't a CheckProcess or CheckService that reflects that.

<Call id="ch:1:Call:ch:1:ServiceJourney:33-15365-1-1_1_2" version="any" order="2">
    <ScheduledStopPointRef ref="ch:1:ScheduledStopPoint:8504416:3" version="any"/>
    <Arrival>
        <Time>17:30:00</Time>
        <ForAlighting>true</ForAlighting>
        <IsFlexible>false</IsFlexible>
        <CheckConstraint id="ch:1:CheckConstraint:2" version="any" order="1">
            <delays id="ch:1:delays:1">
                <CheckConstraintDelay id="ch:1:CheckConstraintDelay:1" version="any" order="1">
                    <alternativeTexts>
                        <AlternativeText attributeName="Name">
                            <Text lang="it">Ritardo stimato</Text>
                        </AlternativeText>
                        <AlternativeText attributeName="Name">
                            <Text lang="en">Estimated delay</Text>
                        </AlternativeText>
                        <AlternativeText attributeName="Name">
                            <Text lang="fr">Retard prévu</Text>
                        </AlternativeText>
                    </alternativeTexts>
                    <Name>Voraussichtliche Verspätung</Name>
                    <MinimumLikelyDelay>PT4M</MinimumLikelyDelay>
                </CheckConstraintDelay>
            </delays>
        </CheckConstraint>
    </Arrival>

We could use CheckProcess=none or other.

Questions:

  1. Is this something to be stored in CheckConstraints
  2. If yes, how to model the CheckProcess? New value?
@ue71603 ue71603 added this to the netex_2.0 milestone Jul 4, 2024
@Aurige
Copy link
Contributor
Aurige commented Jul 4, 2024 •
edited
Loading

is it a delay for all ServiceJourneys of the calendar, or just on a specific (operational) day ?

The CheckConstraint does not really express a delay, but it's usually indicating that you need to be at the stop in advance in order to have sufficient time to cross the check

@ue71603
Copy link
Contributor Author
ue71603 commented Jul 8, 2024

It is a delay on a ServiceJourney (for the given Availabilitycondition). E.g. the we have a TRAIN NUMBER 1234. During July thereis construction, so we get two SERVICE JOURNEY:

  • SJ1 Not July with no planned delay
  • SJ1.1 July with such a planned delay

It is clear that this is not the idea of CheckConstraint. But there is no other mechanism in NeTEx. How would you do it?

@Aurige
Copy link
Contributor
Aurige commented Jul 8, 2024

I recognise that it is not obvious
I would create a SJ1.1 for the dedicated period, and add a dedicated Description and maybe an assigned Notice (where you can mention and explain the delay) and of course updated passing times.
SJ1.1 can also be linked to SJ1 using derivedFromObjectRef, and a version o SJ1 can have a ServiceAlteration=replaced

I guess that, even if in your example it is a delay, it is more a service reorganisation due to the construction/works and it may also be early, or cancelled stops, etc. or a mix of all

@ue71603
Copy link
Contributor Author
ue71603 commented Jul 8, 2024 •
edited
Loading 
<ServiceJourney id="444" version="1">
   <AvailabilityCondition id="allYear"/>
    < TrainNumber>444</TrainNumber>
</ServieJourney>

planned delay for July 

<ServiceJourney id="444-1" version="1">
   <AvailabilityCondition id="allYearexceptJuly"/>
    < TrainNumber>444</TrainNumber>
</ServieJourney>

<ServiceJourney id="444-2" version="1">
   <AvailabilityCondition id="July"/>
    < TrainNumber>444</TrainNumber>
   <ServiceAlteration>replaced</ServiceAlteration>
</ServieJourney>

<ServiceJourney id="444-2a" version="2">
   <AvailabilityCondition id="July"/>
    < TrainNumber>444</TrainNumber>
    <derivedFromObjectRef  ref="444-2" version="1"/>
</ServieJourney>

@Aurige
Copy link
Contributor
Aurige commented Jul 9, 2024 •
edited
Loading

yes, something like that (note that derivedFromObjectRef is an attribute) ... I guess the the Description/Notice is also important for passenger information
Also I see a risk that a journey planner dos not managed the replaced ... and use it in July. It may be nice to be explicit and set isAvailable=false in 444-2 AvailabilityCondition

@BredeD
Copy link
BredeD commented Jul 10, 2024

I think your use case are sinilar to what we use datedServiceJourney for, where we also can manage the links between multippel replacement buses to a previous planned train.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Aurige Aurige

Labels
question
Projects
None yet
Milestone
netex_2.0
Development

No branches or pull requests
3 participants
@Aurige @ue71603 @BredeD