Walking profile with walkway/alleyBias=1 create 3x longer routes than expected

Hi all-

I am using turn-by-turn navigation with the Mapbox DirectionsAPI on Android and explore strange routing behavior when selecting the "walking" profile. Some routes are 3x longer than a comparable cycling route, especially highway=path and =footway seem to be avoided at all cost. I also pass walkwaybias=1 and alleybias=1 but it does not change the behavior.

An example here:

1. Walking Route: https://codepen.io/ulnn/pen/RwrYbja
2. Cycling Route (better route, but still mediocre): https://codepen.io/ulnn/pen/eYJLOKb
3. Best Route (desired outcome): https://www.openstreetmap.org/directions?engine=graphhopper_foot&route=50.13981%2C8.69852%3B50.13825%2C8.69507#map=18/50.13921/8.69745

Any idea?

首先，在 Android 上使用 Mapbox Directions API 重现链接的 CodePen 页面中的步行和骑行示例。将其行为与链接的 OpenStreetMap 路线进行比较，并验证是否正在应用 walkwaybias=1 和 alleybias=1。完成的标准是确定一个可采取行动的原因或已确认的限制，并记录预期的路由行为。