Skip to content

Different snapping results for /Nearest and /Route #7137

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

Open
N40 opened this issue Mar 24, 2025 · 0 comments
Open

Different snapping results for /Nearest and /Route #7137

N40 opened this issue Mar 24, 2025 · 0 comments

Comments

@N40
Copy link

N40 commented Mar 24, 2025

Issue

The result of the Routing Service yields another street point than the Nearest.
Even if doing an Inplace Routing (origin = destination), the result from Nearest is again mapped to the snapping location of the Routing API.
They differ in the 6th digit. (8.950574 -> 8.950573)

Steps to reproduce

  1. query arbitrary position router.project-osrm.org/nearest/v1/driving/8.95065400,48.02984700
  2. read resulting street point 8.950574, 48.029807
  3. route this point in-place https://router.project-osrm.org/route/v1/driving/8.950574,48.029807;8.950574,48.029807
  4. check used street point 8.950573, 48.029807

Specifications

Demo Api http://project-osrm.org/

Visualization

Image

@N40 N40 added the Bug Report label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant