Closed njroussel closed 2 months ago
osrm-customize
just prepares the datafiles - you need to refresh osrm-routed
by either:
osrm-datastore
and osrm-routed -s
in combination.Simply running osrm-customize
isn't sufficient to suddenly get updated results from a running osrm-routed
process.
I am using shared memory and updating it with osrm-datastore
.
Maybe I wasn't clear enough, currently I'm observing something like this for a given source & destination: (values are durations) | Service | Before traffic update | After traffic update |
---|---|---|---|
Route | 120 | 180 | |
Table | 120 | 120 |
Where the 180 duration is completely expected and correct for the update I made.
I experienced the same issue see #5723
This issue seems to be stale. It will be closed in 30 days if no further activity occurs.
Algorithm: MLD
When using the
table
service to get route durations, it seems that traffic updates (applied withosrm-customize
) are not being used/applied.Reasoning:
route
service differ with those of thetable
service.route
result are coherent with the traffic updates (can be checked with the annoations).table
request on a fresh OSRM build (no traffic updates), the output is unchanged.Is this inconsistency between
route
andtable
intended behaviour ?Am I simply misunderstanding their individual use-cases?