Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Show realtime road segments duration in match. #2609
The match plugin has a "duration" field in output, but takes information for it from the road graph. It is a strange behavior when we have timestamps in the query.
Thanks for looking into this!
This is not the function of the
If you need this behavior it is quite simple to implement this client side using some weighted scaling:
Thanks again for the effort. Hope this explanation helps.
EDIT: Fixed that calcualtion.
"Hey what do you think this route would look like". - this is the function of "route" call.
There are both temporal and spatial components in the trace. What you offer is to ignore the temporal component of the path at all and just treat is as /route call - then:
The result should always reflect the state of the internal data - that is unlikely. I'd say that result should always be dependant on inputs, and inputs are OSM graph (going to internal data, but we don't actually care - treat it as cache), speed profile, and trace with timestamps.
It is not expected in match call to get back timestamps that are not related at all to the timestamps fed into it.
Having weighted scaling doesn't resolve the issues of being stuck in traffic and moving disproportionally.