Parrtial fares are already possible with the LegRangeGroup:
However, it might not be a range:
E.g. Walk - Sharing - Transfer - PT1 - Transfer - PT 2 - Transfer - Demand Responsive - Walk
1 2 3 4 5 6 7 8 9
The PT calculator can do the PT legs. In this case: The range would be 3-7
E.g. Walk - Transfer - PT 1 - Transfer - PT 2- Walk
1 2 3 4 5 6
In this case. The leg range group can be omitted, as the whole trip was calculated.
Now to the tricky stuff:
Walk - PT1 - Transfer - Sharing - Transfer - PT 2 - bicycle
1 2 3 4 5 6 7
NOVA can here only calculate 1-3 and 5-7 (it even returns probably only 2 and 6)
So what should be the LegRangeGroup here? Or should it return two TripFareResults with the correct LegRange Group. Otherwise it might be necessary to add multiple LegRanges in the LegRangeGroup.
ue71603
commented
1 year ago
Parrtial fares are already possible with the LegRangeGroup:
However, it might not be a range:
E.g. Walk - Sharing - Transfer - PT1 - Transfer - PT 2 - Transfer - Demand Responsive - Walk 1 2 3 4 5 6 7 8 9 The PT calculator can do the PT legs. In this case: The range would be 3-7
E.g. Walk - Transfer - PT 1 - Transfer - PT 2- Walk 1 2 3 4 5 6 In this case. The leg range group can be omitted, as the whole trip was calculated.
Now to the tricky stuff:
NOVA can here only calculate 1-3 and 5-7 (it even returns probably only 2 and 6)
So what should be the LegRangeGroup here? Or should it return two TripFareResults with the correct LegRange Group. Otherwise it might be necessary to add multiple LegRanges in the LegRangeGroup.