imported>Kentsmith9 |
imported>Forumtestuser |
| (11 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| {{construction
| | #REDIRECT [[USA:Routing penalties]] |
| | contact = http://www.waze.com/forum/viewtopic.php?f=276&t=68126&start=20#p725964
| |
| | contacttype = forum
| |
| | draft = yes
| |
| | open = yes
| |
| | section = no
| |
| | talk = no
| |
| }}
| |
| 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 [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|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:
| |
| | |
| * [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|Turn restrictions]] and [[Scheduled_restrictions#Turns|scheduled turn restrictions]] during the designated time for the designated vehicle type.
| |
| * [[Creating_and_Editing_street_segments#Set_Road_Type.2C_Direction.2C_and_Elevation|One-way roads]] against the designated direction of travel and [[Scheduled_restrictions#Segments|scheduled segment restrictions]] for the designated time for the designated vehicle type.
| |
| * [[Road_Types_(USA)#Non-drivable|Non-drivable road types]] including Walking Trail, Pedestrian Boardwalk, Stairway, Railroad and Runway/Taxiway.
| |
| * [[Best_map_editing_practice#Toll_roads|Toll roads]] for clients with avoid toll roads selected in the app.
| |
| * [[Road_Types_(USA)#Dirt|Dirt road/4x4 Trail]] for clients with avoid dirt roads selected in the app.
| |
| * [[Road_Types_(USA)#Parking_Lot_Road|Parking lot roads]] and [[Road_Types_(USA)#Private_Road|private roads]] when transitioning to another road type
| |
| | |
| == Road configurations ==
| |
| Other routing penalties are based on road configurations.
| |
| | |
| *[[File:MinSegLengthUturn2.png|border|390px|right|Segment too short to allow two left turns]] Waze will penalize a route with two left turns in less than {{:Routing penalties/U-turn minimum}} in [[right-hand traffic]] jurisdictions or with two right turns in less than {{:Routing penalties/U-turn minimum}} in [[left-hand traffic]] jurisdictions.
| |
| {{clear}}
| |
| | |
| *[[File:OffOnFreeway.png|border|390px|right|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]].
| |
| {{clear}}
| |
| | |
| == 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.
| |
| | |
| [[Category:Waze operations]]
| |
