VDVde / OJP

Open API for distributed journey planning. CEN/TS 17118:2017.
https://www.vdv.de/open-journey-planner.aspx
22 stars 12 forks source link

Undefined delay on a leg and the information that the connection can't be guaranteed #382

Closed ue71603 closed 1 year ago

ue71603 commented 1 year ago

From Andreas Schlapbach I got asked,

  1. whether we can inform about an undefined delay on a leg
  2. whether we can provide the information that a connection can't be guaranteed.

Considering 1

Our current model would probably assume that this type of leg would never show up in a response. It could happen during refinement, so we might need to deal with it more directly.

So I propose to update ServiceStatusGroup with UndefinedDelay boolean

Considering 2

This certainly should be part of the TransferLeg. Perhaps something can be done with Situation.

But we might add information about the Interchange to TransferLegStructure :

herlitze commented 1 year ago

Regarding 2 When can a connection be guaranteed/not guaranteed? In my understanding there are guaranteed connections where they wait on the feeder. This would be a flag showing a guaranteed connection. Or does this refer to a request with useRealtimeData:explanatory, where a change with the current delay is no longer possible?

ue71603 commented 1 year ago

@herlitze The idea is to have a guaranteed connection, that is no longer guaranteed (because the delay of the feeder is too great, breaking the interchange "contract").