Kentsmith9 (talk | contribs) m (Kentsmith9 moved page Talk:How Waze calculates routes to Talk:Routing Server: More general name to support the page contents) |
Kentsmith9 (talk | contribs) (.) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
== Junction Exit Times == | == Junction Exit Times == | ||
In this [http://www.waze.com/forum/viewtopic.php?f=3&t=27482 forum thread] is a conversation around the tracking of different segment speeds based on the exiting segment. Follow up data was presented in [http://www.waze.com/forum/viewtopic.php?f=8&t=43819&hilit=segment&start=30#p423532 this thread]. | In this [http://www.waze.com/forum/viewtopic.php?f=3&t=27482 forum thread] is a conversation around the tracking of different segment speeds based on the exiting segment. Follow up data was presented in [http://www.waze.com/forum/viewtopic.php?f=8&t=43819&hilit=segment&start=30#p423532 this thread].''[[user:kentsmith9|<span style="background:palegreen;color:green">« kentsmith9 »</span>]] ([[User talk:kentsmith9#top|talk]])'' 15:04, April 30, 2013 | ||
:Since this original post, new information has been visible in routing that may indicate this feature may not be currently operating. ''[[user:kentsmith9|<span style="background:palegreen;color:green">« kentsmith9 »</span>]] ([[User talk:kentsmith9#top|talk]])'' 22:33, 14 March 2014 (UTC) | |||
== Content from section - Changes in routes due to different route lengths == | |||
This content was removed from the main page: | |||
:The specific quote from support was: "Above some distance (currently 10KM) from both end points (start and destination) the server prefers to go through non streets. Now as it happens here - this small distance was the difference between being less than or over 10KM. Now the penalty of going through a street in this case is high - so the server prefers the highway." In this particular case, the observed behavior was that extending the route by a short distance caused Waze to suggest a very different (and much longer, both in distance and estimated time) route. | |||
''[[user:kentsmith9|<span style="background:palegreen;color:green">« kentsmith9 »</span>]] ([[User talk:kentsmith9#top|talk]])'' 22:42, 15 March 2014 (UTC) | |||
Latest revision as of 07:02, 22 May 2014
Time of day variations
I'm almost certain Waze does not think the average speed is the same all day long on a specific street : streets traffic is modeled. This is based on 2 different sentences I've received from Waze support (even if not explicit).
The day is split in several time ranges and there is a value for the average speed during each of these time ranges. It calculates these values based on wazer's speed but probably also on a theoritical model (because many streets will probably lack data during each period of the day).
With the amount of data Waze has been able to gather accross all these years, they are definitely able to create a model based on (I guess) :
- Type of street
- Time of the day
- Day of the week
- Day of the year
It also makes waze able to predict trafic jams without any wazer driving by the road (which you can observe quite frequently on the waze map while driving).
Yoho 13:13, 12 January 2013 (UTC)
Junction Exit Times
In this forum thread is a conversation around the tracking of different segment speeds based on the exiting segment. Follow up data was presented in this thread.« kentsmith9 » (talk) 15:04, April 30, 2013
- Since this original post, new information has been visible in routing that may indicate this feature may not be currently operating. « kentsmith9 » (talk) 22:33, 14 March 2014 (UTC)
Content from section - Changes in routes due to different route lengths
This content was removed from the main page:
- The specific quote from support was: "Above some distance (currently 10KM) from both end points (start and destination) the server prefers to go through non streets. Now as it happens here - this small distance was the difference between being less than or over 10KM. Now the penalty of going through a street in this case is high - so the server prefers the highway." In this particular case, the observed behavior was that extending the route by a short distance caused Waze to suggest a very different (and much longer, both in distance and estimated time) route.
« kentsmith9 » (talk) 22:42, 15 March 2014 (UTC)