Routing penalties: Difference between revisions Discussion View history

(Added images)
(Added category)
Line 33: Line 33:
== Preventing routes with certainty ==
== Preventing routes with certainty ==
If a segment should never be used for routing, it should not be connected to the road network. For example, Waze may route over railroad, walking trail or stairway segments connected to the road network if conditions are such that the penalized route is still found to be the best route. This is common where there are no alternate routes, such as when Waze finds that the origin or destination is on the penalized segment.
If a segment should never be used for routing, it should not be connected to the road network. For example, Waze may route over railroad, walking trail or stairway segments connected to the road network if conditions are such that the penalized route is still found to be the best route. This is common where there are no alternate routes, such as when Waze finds that the origin or destination is on the penalized segment.
[[Category:Waze operations]]

Revision as of 00:59, 17 March 2014

This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. This content is open to changes from anyone during construction. If you would like to make changes or have questions, please post a message in this forum.

The Waze routing servers use a system that associates restricted turns and directions as a penalty amount. When it then compares the different routes, it looks at the cumulative penalty points and the lowest amount of penalty points is the better route.

Background

Waze routing is intended to work in two very different environments at the same time. One uses map information that has been carefully corrected by a group of dedicated editors. The other uses map information that was imported from an external database with no editor corrections. To support both systems the Waze development team decided to use a penalty-based routing system. That means the various segment and junction node properties that restrict certain directions between segments are applied as a routing penalty. For example, a turn restriction indicated by the red turn restriction arrow does not prohibit the turn, rather the turn restriction applies a high penalty to any route through the turn. This penalty-based routing system permits routing to a point on street where all turns onto the street are incorrectly set as restricted. This provides for some routing in areas that have not been edited carefully or correctly.

Segment properties

The following segment properties cause routing penalties:

Road configurations

Other routing penalties are based on road configurations.

  • Segment too short to allow two left turns
    Segment too short to allow two left turns
    Waze will penalize a route with two left turns in less than 52.49 ft (16 m) in right hand drive jurisdictions or with two right turns in less than 52.49 ft (16 m) in left hand drive jurisdictions.
  • Ramps should prevent detour
    Ramps should prevent detour
    Waze penalizes some routes that leave a highway or freeway only to immediately return to the same freeway or highway. This is covered in more detail in Detour Prevention Mechanisms.

Preventing routes with certainty

If a segment should never be used for routing, it should not be connected to the road network. For example, Waze may route over railroad, walking trail or stairway segments connected to the road network if conditions are such that the penalized route is still found to be the best route. This is common where there are no alternate routes, such as when Waze finds that the origin or destination is on the penalized segment.