Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unify snapping behaviour across services #1798

Open
1 task done
aoles opened this issue May 23, 2024 · 1 comment
Open
1 task done

Unify snapping behaviour across services #1798

aoles opened this issue May 23, 2024 · 1 comment

Comments

@aoles
Copy link
Member

aoles commented May 23, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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:

  • 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)
  • matrix: service-specific, profile-independent config parameter maximum_search_radius = 2000, no query parameter
  • snapping: query-time parameter radius = 350

Proposed solution

Common defaults and handling of snapping across different endpoints based on the current one for the directions endpoint:

  • profile-specific config parameter for the default value of snapping distance
  • which can be overridden at query time
@aoles aoles changed the title Unify snapping bahaviour across services Unify snapping behaviour across services May 23, 2024
@aoles
Copy link
Member Author

aoles commented Jun 12, 2024

See also #538.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: To do
Development

No branches or pull requests

1 participant