List all travel options between two stops in a timetable (no transfers)

[AndersVarmy]

The need is to add more journey alternatives to the result even if they are slower.

[AndersVarmy]

Skanetrafiken is working on a POC.

[t2gran]

Should this support lines where part of the line has a replacement service?
We can support one transfer, should we do that as an option?

[miklcct]

Should this support lines where part of the line has a replacement service? We can support one transfer, should we do that as an option?

I am following this. We have just encountered a situation where part of a trip is bustituted, and our software doesn't handle this relation and shows it as separate trips.

GTFS doesn't support this feature and I may need to discuss with our team to see if we want to add this feature and move our investment to NeTEx instead / submit a proposal to the GTFS specification.

I don't think our internal model in OpenTripPlanner supports this concept as well, where multiple physical trips are aggregated together.

[AndersVarmy]

Should this support lines where part of the line has a replacement service? We can support one transfer, should we do that as an option?

I think my answer will be "yes" for both of your questions, but i'm not quite sure if I understand you correctly.
First of all, the reason that we focused on "no transfers" is that it seemed easier. But if we could add journeys with transfers also, that probably is even better.
I'm not sure what you mean with "part of the line has a replacement service"? If there is a journey between two stops I would say it doesn't matter if it is a replacement or original journey.

[AndersVarmy]

Should this support lines where part of the line has a replacement service? We can support one transfer, should we do that as an option?

I am following this. We have just encountered a situation where part of a trip is bustituted, and our software doesn't handle this relation and shows it as separate trips.

GTFS doesn't support this feature and I may need to discuss with our team to see if we want to add this feature and move our investment to NeTEx instead / submit a proposal to the GTFS specification.

I don't think our internal model in OpenTripPlanner supports this concept as well, where multiple physical trips are aggregated together.

"bustituted"? Is that when a train is substituted by buses?

[miklcct]

"Bustitute" / "bustitution" is a slang for rail replacement buses (substitution by buses).

[miklcct]

I have just got a use case of this feature in our product.

Currently, if you have a leg, you can use nextLegs to fetch other options between the same two stations, even if they are slower / overtaken.

Unfortunately there isn't such an API to directly fetch legs between two stops / stations yet, which I believe is what this issue for. And I'll need such an API to handle the case if refetching a saved transit leg fails (for example, if the train is diverted with additional stops, or if the timetable is changed so the trip ID is changed), such that I can show options to the user to choose an alternative leg to complete his journey.

The API should receive:

• from stop ID
• to stop ID
• whether the search is expanded to the whole station
• transport modes
• date / time
• number of legs to return (probably needs to support paging as well)

And it should return a list of legs.

The actual implementation should be shared with nextLegs field in leg.