An analysis of the problem is here:
I am looking for a dataset with non-trivial fare information. The German ones, of course, don't have any.
Found one:
I test-based-developed all examples from https://code.google.com/archive/p/googletransitdatafeed/wikis/FareExamples.wiki
The result looks more like a separate project than like a part of graphhopper-pt, it doesn't share any code with it. Maybe instead of merging it, just pull it out and include it from the web project so the web site can calculate the fares.
Not real-world-data-tested yet.
The result looks more like a separate project than like a part of graphhopper-pt, it doesn't share any code with it.
Ok, sounds reasonable.
When this works, make a first try with optimizing for fare, but only with zone-based fares with unlimited transfers: Use the set of zones through which a trip has passed (or another signature of the possible fares) as another Pareto criterion. Then, in the end, look up the price and remove dominated alternatives.
Fare is now (4a12566) being calculated based on GTFS fare rules and included in the response.
Most helpful comment
Fare is now (4a12566) being calculated based on GTFS fare rules and included in the response.