The multi-criteria range raptor uses uses cost as one of its criteria. We assume that we can time-shift the first access leg toward the transit leg, hence avoid waiting at the first stop by delaying the departure. But, the cost-function do not account for this and calculate a wait-cost between access and the first transit.
Expected behavior
No additional cost added to the cost criteria in multi-criteria Range Raptor.
Observed behavior
Same cost added between access and transit, as between transit and transit.
Version of OTP used (exact commit hash or JAR name)
f76183ef
Data sets in use (links to GTFS and OSM PBF files)
The multi-criteria range raptor uses uses
cost
as one of its criteria. We assume that we can time-shift the first access leg toward the transit leg, hence avoid waiting at the first stop by delaying the departure. But, the cost-function do not account for this and calculate a wait-cost between access and the first transit.Expected behavior
No additional cost added to the cost criteria in multi-criteria Range Raptor.
Observed behavior
Same cost added between access and transit, as between transit and transit.
Version of OTP used (exact commit hash or JAR name)
f76183ef
Data sets in use (links to GTFS and OSM PBF files)
Entire Norway Netex
Command line used to start OTP SpeedTest
I used the SpeedTest to verify this with :
--profiles mc --verbose --debugPath 2710,4452
travelSearch.csv
Steps to reproduce the problem
Change the departure time (18:05) above and observe the cost change at the first stop (log).