Make maxWheelchairSlope not a hard cut-off, but apply a cost instead #4088
Conversation
Also, remove retry without the limit, but instead add penalty
| * What penalty factor should be given to street edges, which are over the max slope. | ||
| * Set to negative for disable routing on too steep edges. | ||
| */ | ||
| public double wheelchairSlopeTooSteepCostFactor = 10.0; |
There was a problem hiding this comment.
Should this be part of the WheelchairAccessibilityRequest in the future?
There was a problem hiding this comment.
I think so, the same with maxWheelchairSlope
|
My sense is that the cost should be multiplier for the edge and it should be high enough so that if there is a reasonable alternative path, it would be used instead. There could be extra time multiplier as well for traversing an edge but I guess the normal walk elevation speed affects this as well already a bit so I don't know if it's necessary (although it might be slightly slower with wheelchair vs walking up a hill). Side note, I don't think the wheelchair access map layer currently takes into account the configured |
Summary
This changes the behaviour when an edge has steeper slope than the
maxWheelchairSlope. Previously, if no path was found, the limit was dropped and the search was re-done. In this PR the behaviour is changed, and instead a cost factor is applied, if the slope is too steep.Open questions