Previously we only allowed itineraries of rh -> transit -> rh when the mode ride_hail_transit was selected. This should allow for either the access or egress leg to be walk. There's nothing explicitly preventing the router from constructing a walk_transit itinerary as well, but that one should be filtered out in ChoosesMode if it is not allowed based on the agent's input plans.
This PR also captures RH cost in router so that we don't have as many routes with really long ride-hail legs and short transit legs
Previously we only allowed itineraries of rh -> transit -> rh when the mode
ride_hail_transit
was selected. This should allow for either the access or egress leg to be walk. There's nothing explicitly preventing the router from constructing awalk_transit
itinerary as well, but that one should be filtered out in ChoosesMode if it is not allowed based on the agent's input plans.This PR also captures RH cost in router so that we don't have as many routes with really long ride-hail legs and short transit legs
This change is