Discrepancies between max_walk_dist
and max_bike_dist
and actual distances travelled during routing
#273
Labels
v1.0
Features to be included in r5r 1.0
The
max_walk_dist
andmax_bike_dist
parameters define the max travelling distance to access transit stops or for direct trips in all routing functions.r5r
converts those parameters to max walk and bike times under the hood, according to walking and cycling speeds provided.The issue here is that the conversion is not as straightforward as it used to be, now that R5 takes the city's topography into account. Thus, a trip that is well within
max_walk_dist
is not retrieved because its adjusted walking time (due to topography) is longer than the pre-calculated walking time considering flat terrain.Reproducible example:
In the example above, the first trip is 1583 meters long, but it's only retrieved when
max_walk_dist
is above 1800. Ifelevation = "NONE"
insetup_r5()
,max_walk_dist
works as expected.The only solution for this problem that I can think of is to change the parameters to
max_walk_time
andmax_bike_time
, because that's how R5 works natively.The text was updated successfully, but these errors were encountered: