The results of /nearest don't always result in routable point

Open Source Routing Engine
1

Hey,

am I wrong in expecting the following workflow to work:

  • if /route returns 400 with “Cannot find point #”, call /nearest iteratively with the missing point slightly offset (with a concentric, increasing radius from the original point logic) until it returns a valid point result
  • with that offset point, do the same routing query with success.

I’ve found, however, that /nearest doesn’t actually return routable points in all cases, and doing /route with that offset point still fails with the same error.

What’s going wrong here?

Thanks

2

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.