[OSRM-talk] Map matching for live data-streams, one point at a time

[Daniel Patterson]

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 previous response, instead of
many candidates within range.  Much of the time this will work fine, but
won't if your GPS data is inaccurate and you're closer to an incorrect
road.  Don't pass in hints at all to avoid this bug.

daniel

On Fri, Dec 6, 2019 at 4:52 PM Alex R <ralienpp at gmail.com> wrote:

> 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" coordinates are in the
> end?)
>
> 2. If I provide a "hint" value (taking it from a previous request), would
> that simplify OSRM's calculations? (or is the "hint" only useful when
> querying different endpoints?)
>
>
> Alex
>
> _______________________________________________
> OSRM-talk mailing list
> OSRM-talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osrm-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20191206/ed36b72f/attachment-0001.html>