Different snapping behavior for matrix and directions?

[nilsnolde]

It seems like matrix endpoint might have a different snapping radius than the directions endpoint for input coordinates.

[sfendrich]

Findings so far:

• The relevant configuration parameters are supposed to be maximum_snapping_radius(routing) and maximum_search_radius(matrix)
• In the live app.config for driving-car neither maximum_snapping_radius nor maximum_search_radius are set, so probably some default values are used.
  *The default for maximum_search_radius is supposed to be 2000
• I couldn't find a default value for maximum_snapping_radius in the code. There is a boolean hasMaximumSnappingRadius that defaults to false and is set to true, when setting a maximum_snapping_radius.
• Maybe the default behaviour when hasMaximumSnappingRadius == false is an infinite or a very large snapping distance. This would explain the issue on the live ORS, which leaves the parameteres unconfigured.
• For my local instance, I have set maxiumum_search_radius to 5000 and maximum_snapping_radius to 400 resulting in the issue, which makes no sense because 5000 > 400. In both cases the unit is supposed to be 1 meter.
• 5000m is obviously larger than the beeline distance from the requested coordinate to the nearest accessible road, which is confirmed by routing finding this point within 400m.