Non optimal trips shown
xivk opened this issue · 2 comments
xivk commented
There are two cases here:
- Same departure time but different arrival time.
- Same arrival time but different departure time.
This could be acceptable if the # of transfers is different but those tradeoffs should be in the user profile. We should build a default that approaches the current routeplanners and give reasonable default results.
pietervdvn commented
Could you please provide the search query?
And are the number of transfers the same on both trips? If they are, this is clearly a bug.
This will need #37 to be fixed first
pietervdvn commented
Has been taken care of by #44
Note: I'm gonna keep the 'same arrival time'-journeys; if the traveler misses his direct train, they know they still can take a later train with transfers (although this should become a profile preference too)