You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can get some contents in the Annotation object by add parameter &annotations=true when we request a route.
In the Alternatives Ranking, we're using nodes from annotation object to match traffic data. But it's not very easy to use since our traffic data indexed by wayID instead of nodes. Also, most of our other services are heavily based on wayID, so if we can add wayID in annotation object will be very helpful.
Two proposals:
Use an new microservice to do it between osrm-ranking and osrm-backend.
The new microservice will have to load wayID->nodes mapping and indexed by nodes to unpack the wayIDs.
Disadvantage: maybe possible to cost too much memory(not sure whether 64GB is enough for NA or not).
Advantage: easy to implement since don't need to change the C++ flow.
Support it in C++ implementation directly.
It may not that easy to implement, need to do some research & estimation.
I think we may go with proposal-1 at present. @CodeBear801 How's your idea?
The text was updated successfully, but these errors were encountered:
We can get some contents in the Annotation object by add parameter
&annotations=true
when we request a route.In the Alternatives Ranking, we're using
nodes
from annotation object to match traffic data. But it's not very easy to use since our traffic data indexed bywayID
instead ofnodes
. Also, most of our other services are heavily based onwayID
, so if we can addwayID
in annotation object will be very helpful.Two proposals:
osrm-ranking
andosrm-backend
.wayID->nodes
mapping and indexed bynodes
to unpack thewayID
s.C++
flow.C++
implementation directly.I think we may go with proposal-1 at present. @CodeBear801 How's your idea?
The text was updated successfully, but these errors were encountered: