Closed miklcct closed 6 months ago
This is expected as there are many, many factors other than walk reluctance that determine the cost of a walk (or indeed any) leg.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days
I want the walk legs of my journeys to be weighted by duration. I set walkReluctance to 1.0 for my query.
Expected behavior
It returns walking legs with generalizedCost exactly equal to the duraion
Observed behavior
It returns walking legs with generalizedCost not equal to the duration
Version of OTP used (exact commit hash or JAR name)
2.3.0
Data sets in use (links to GTFS and OSM PBF files)
DfT GTFS + National Rail from dtd2mysql
Command line used to start OTP
Router config and graph build config JSON
otp-config.json:
router-config.json
Here is some sample journeys with walkReluctance = 1.0
As shown above, the first itinerary is a walk-only itinerary but its generalizedCost is less than the duration for the walk leg despite walkReluctance is set to 1.0, and the walk legs of the other itineraries are similarly affected as well.