The default search radius for deriving the closest point on the graph from the input point is/was by default 350m.
When you say it is ‘suddenly’ needed to pass radiuses:
did you previously find routes for the exact points you are having trouble with now?
Or do you just encounter the point not found error more often?
If it’s the first case there might be something wrong during the graph building. We recently developed some additional logic for cleaning up OSM data before building the graphs but as far as i know thats not used yet ( @adam or is it ?).
Maybe you just got unlucky when setting your points, so they have not been within the 350m range.
This may be a valid road, but it is not in included in the graph that is used for routing:
most probably because of the
highway=service tags which are both not suited for general routing:
Regarding setting -1 as radius, depends on your use case:
If you need a route by any means, do it. But in this case you would also get routes for switched lng/lat order when the waypoints would be in some ocean.
But as you are using the api directly there shouldn’t be a problem with setting the radiuses parameter by yourself to overwrite the default of 350?