I would like to suggest exposing additional routing parameters currently available in OpenTripPlanner (OTP), notably walkReluctance and minTransferTime, if supported by the underlying R5 API.
These parameters are important for producing itineraries that better reflect real-world traveller preferences in public transport networks. In some cases, strictly fastest paths may involve tight transfers or additional interchanges, whereas users may prefer slightly longer but more reliable routes with fewer transfers. Parameters such as walkReluctance (to weight walking time relative to in-vehicle time) and minTransferTime (to enforce realistic transfer buffers) can meaningfully influence route structure and transfer patterns.
If technically feasible, adding these arguments to r5r functions would further strengthen the package and broaden its applicability for transport research and planning analyses.
Thank you for considering this suggestion!
I would like to suggest exposing additional routing parameters currently available in OpenTripPlanner (OTP), notably walkReluctance and minTransferTime, if supported by the underlying R5 API.
These parameters are important for producing itineraries that better reflect real-world traveller preferences in public transport networks. In some cases, strictly fastest paths may involve tight transfers or additional interchanges, whereas users may prefer slightly longer but more reliable routes with fewer transfers. Parameters such as walkReluctance (to weight walking time relative to in-vehicle time) and minTransferTime (to enforce realistic transfer buffers) can meaningfully influence route structure and transfer patterns.
If technically feasible, adding these arguments to r5r functions would further strengthen the package and broaden its applicability for transport research and planning analyses.
Thank you for considering this suggestion!