Add walking to the cycling costing model
- Dominant language
- C++
- Stars
- 6.2k
- Forks
- 981
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 14
Description
We're exclusively using the cycling costing model on the mobility API. Having switched from another provider, we noticed that your routes seem to avoid walking as much as possible, even to the detriment of the overall trip time. This is especially true at the start/end of a trip on a one-way street (See examples below).
Our users find the short walking segments more desirable than going around the block. I suggest reducing the penalty for walking in your costing models.
Example 1: The user has to go an extra 0.5km out of their way.

Example 2: The user has to go 0.7km out of their way.

Contributor guide
Assessment
This issue has not been assessed yet.