Snapping of coordinates to the road networks varies wildly across endpoints and services as it is controlled by parameters named differently and with varying default values:
directions: profile-specific config setting maximum_snapping_radius = 400 which can be overridden by query parameter radiuses
isochrones: no limit, the maximum available radius of location index is being used (same as radiuses = -1 for directions)
Is there an existing issue for this?
Problem description
Snapping of coordinates to the road networks varies wildly across endpoints and services as it is controlled by parameters named differently and with varying default values:
maximum_snapping_radius = 400
which can be overridden by query parameterradiuses
radiuses = -1
for directions)maximum_search_radius = 2000
, no query parameterradius = 350
Proposed solution
Common defaults and handling of snapping across different endpoints based on the current one for the directions endpoint: