1. Supply the coordinates in the order travelled:
/match/v1/oldest;second-oldest;second-newest;newest
2. Hints aren't quite so helpful for the /matching API - reading the code
I actually think there might be a bug here. If you pass in a hint, it'll
only use the first snapped candidate from the
Thank you for the fast, detailed and reassuring response.
I have some additional questions:
1. In what order must the list of coordinates be given? (i.e.,
http://127.0.0.1:5000/match/v1/driving/most-recent;second-most-recent;third-most-recent
OR is it the other way around, and the "most-recent"
Hi Alex,
If you simply want to find the nearest road to a GPS coordinate, the
/nearest service is simpler. The /match service is specifically designed
to match a sequence of GPS coordinates *with error* to the most likely path.
The problem with using /nearest is that it has no context - if
Hi,
I ask for advice in using OSRM with a live stream of data. The examples
I've seen relate to tracks that can be passed into OSRM and it will apply
"map matching" to snap all points to the roads, in one move.
My scenario is different, I am trying to understand whether it is feasible
with in
