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.

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

Fare for each Leg of an Itinerary #1699

Open
scrudden opened this issue Jan 16, 2015 · 2 comments
Open

Fare for each Leg of an Itinerary #1699

scrudden opened this issue Jan 16, 2015 · 2 comments

Comments

@scrudden
Copy link

@scrudden scrudden commented Jan 16, 2015

In the current implementation the total fare for the full journey/itinerary is displayed and returned in a plan request.

This should change so that the plan request returns a fare element in each of the legs of the journey.

@thatsmydoing
Copy link
Contributor

@thatsmydoing thatsmydoing commented May 5, 2015

A problem with doing this is that some fares are not tied to a leg, but a group of legs when transfers are involved. In that case, it's not as obvious how to attach a fare element to each leg.

Do you attach the fare element to all legs they're a part of? Or only the first leg, or the last leg?

Or should the fare still be part of the itinerary, but each fare element lists which legs it is a part of?

@scrudden
Copy link
Author

@scrudden scrudden commented May 14, 2015

I think there needs to be two fares captured.
One is the "base fare" for each leg of the journey but also the "actual fare" for the complete itinerary. Then it would be easy to calculate and show the discounts applied for transfers while still showing the cost of each individual leg.

As this is for passenger info only who pays for the discount is not relevant. The passenger will only care that they are getting a discount.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants