CTCNetwork wrote:Would this have anything to do with the time that the routing is done? Is it confined to a particular time/s of day?
dknight212 wrote:Chris - I think you have these tests scripted now, is that right? Is it very difficult to tabulate these results so Waze HQ have an easy reference for their checking? No worries if not.
Ideally something like: start lat/lon/street, finish lat/lon/street, time of day, success/fail, distance A, distance B
Just shoot me if I'm asking too much!
Something else that crossed my mind regarding the interaction between the routing algorithm and the traffic data - since the traffic data changes quite frequently at certain times of the day, I wonder if the routing code takes a snapshot of the data before starting to generate each new route, or if it just assumes that the live data isn't going to change significantly during the calculation of the new route. If the latter, then there's always the chance that during the calculations the data has changed in such a way that the intended route breaks whatever internal thresholds/sanity checking are set for the routing code.
Given that it generally seems to be the quickest route option that starts to fall short of the intended destination before the routing code gives up completely, this would tie in with it being traffic data related - the shortest route would only be affected if the road closure data got updated during the routing calculation, whereas changes in traffic density shouldn't affect it at all (it doesn't care how long it takes to get from A to B...).
Users browsing this forum: PhantomFlanFlinger