Match Service returning .0 node ids and miss node ids sometimes #7222
Description
I'm trying to use the OSRM match API to match 2 points (in my example it's more, but here these 2 points should be enough to describe the problem).
Here is my first API call:
This will return the following list of nodes - in the only leg/annotation object in the result:
[2354330292, 1757124316, 12048921950.0, 11630879020.0, 7166186928, 17200929, 7166186929, 11630879020.0, 8259716038, 1067415735]
Here are my questions to this:
- What are these nodes ending with .0 about ? For example if i search for these nodes via simple osm (https://www.openstreetmap.org/node/11630879020.0) is simply not existing, if i cut the .0 it seems to point to a traffic light related node (which is fine).
- If i check this one https://www.openstreetmap.org/node/12048921950 it seems to be any node on the comores really far away :D
- Why is this 11630879020.0 repeating in there? It seems to be the traffic light in front of the crossing...i see no reason why it should repeat in a straight matching.
Here is my second API call:
Its just a few meters more ahead on the same street.
Again just one leg as a result with these nodes:
[3432945284, 10139453990.0, 3405335504, 414267420, 3405335064, 10139453990.0, 3446450866, 3442740736, 2117890512]
- Again i get this node with .0 which if i cut the .0 is pointing to any other location really far away. This time at least in Germany.
10139453990 - And again two times?
- I' really missing node number https://www.openstreetmap.org/node/10139453988 which seems to represent the traffic light here?
To sum it up:
- What are these strange .0 nodes in the results ? Is this behaviour documented anywhere?
- Why does one call include the traffic light nodes and the other does not ?
- Why is it included 2 times in the first call?
- What is this node id 10139453990.0 and why it is included in the result?