Detour detection mechanism in the wiki

Moderator: Unholy

Re: Detour detection mechanism in the wiki

Postby kentsmith9 » Sat Feb 22, 2014 12:25 am

CBenson wrote:Seems to me that it would be appropriate to note this on the detours page in a "Notes" or "Side-effects" section. I've added this to the detour page, but consider it a draft that can be freely edited. Is there any reason not to put this on the detour page?

I like it.

Clarification question:
New Addition to Detour Page wrote:Thus in the intersection below, the configuration on the left will be used to route a U-turn, but the configuration on the right will not.

I propose (if accurate):
Modified New Addition to Detour Page wrote:Thus in the intersection below, the configuration on the left will be used to route a U-turn because it uses a single segment between the two parallel roadways with the same name. In contrast, the configuration on the right will not use the U-Turn road because it branches from another segment causing multiple segments between the two parallel roads with the same name.
USA: California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 11104
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1485 times
Been thanked: 1691 times

Re: Detour detection mechanism in the wiki

Postby kentsmith9 » Wed Jan 08, 2014 3:01 am

CBenson wrote:Hmm, maybe just say detour prevention mechanism. Then have sections for both "big" detours and "small" detours. Can we say the following at this point?
Waze plans to implement a small detour prevention mechanism to deal with instances where waze calculates that that its a few seconds faster to to continue straight or make a right at an intersection a make a u-turn rather than just turning left. Waze will eliminate such detours if there is under a 30 sec difference in the routes.

It sounds good if we have any indication they will actually be getting to this as some point.
USA: California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 11104
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1485 times
Been thanked: 1691 times

Re: Detour detection mechanism in the wiki

Postby kentsmith9 » Wed Nov 27, 2013 2:50 am

Should we consider linking this to the Limited Access Interchange article as well covering how to deal with the issue when the listed items are not present?
USA: California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 11104
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1485 times
Been thanked: 1691 times

Re: Detour detection mechanism in the wiki

Postby eaglejm7 » Mon Dec 01, 2014 11:35 pm

Sorry, mine was a comment to the developers. Non routable routes should be just that. Information on the map, but strictly off limits for driving.
ImageImageImage
eaglejm7
Area Manager
Area Manager
 
Posts: 300
Joined: Fri Oct 31, 2014 3:05 pm
Has thanked: 79 times
Been thanked: 11 times

Re: Detour detection mechanism in the wiki

Postby eaglejm7 » Fri Nov 28, 2014 11:39 pm

It should also probably prefer to say no route found than route down any non-routable road type.
ImageImageImage
eaglejm7
Area Manager
Area Manager
 
Posts: 300
Joined: Fri Oct 31, 2014 3:05 pm
Has thanked: 79 times
Been thanked: 11 times

Re: Detour detection mechanism in the wiki

Postby CBenson » Fri Mar 14, 2014 10:09 pm

What should a Routing Penalty section say?

I would suggest something along the lines of:
==Routing Penalties==

Waze routing is intended to work were the Waze map has been carefully corrected by a corp of dedicated editors and where the map is imported without editor correction. For this reason, Waze routing is penalty based. That is, the various segment properties and junction node properties that restrict routes 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 set as restricted. Thus, providing for some routing in areas that have not been edited carefully.

The following segment properties cause routing penalties:
  • Turn restrictions (and time based turn restrictions during the designated time for the designated vehicle type)
  • One-way roads against the designated direction of travel (and time based segment restrictions for the designated time for the designated vehicle type)
  • Non-drivable road types (Walking Trail, Pedestrian Boardwalk, Stairway, Railroad and Runway/Taxiway
  • Toll roads for clients with avoid toll roads selected
  • Dirt road/4x4 Trail for clients with avoid dirt roads selected
  • Parking lot roads and private roads when transitioning to another road type

Other routing penalties are based on road configurations. For example, Waze will penalize a route with two left turns in less than 15 meters in right hand drive jurisdictions or with two right turns in 15 meters in left hand drive jurisdictions. Waze also penalizes some routes that leave a highway or freeway only to immediately return to the same freeway or highway.

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 alternative routes, such as when Waze finds that the origin or destination is on the penalized segment.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

Re: Detour detection mechanism in the wiki

Postby CBenson » Tue Mar 11, 2014 10:48 am

Where is the routing penalty discussion page?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

Re: Detour detection mechanism in the wiki

Postby CBenson » Mon Mar 10, 2014 7:31 pm

In response to the routing discussed here waze has confirmed that the big detour prevention mechanism is merely a high penalty that may not be effective to prevent routing when the traffic on the highway is very slow. I thus propose to change
Waze routing will not present routes over a detour off a highway/freeway and back on that same highway/freeway when all of the following conditions are met:

to read
Waze routing will heavily penalize routes over a detour off a highway/freeway and back on that same highway/freeway when all of the following conditions are met:


We could also add a note that the detour prevention mechanism may not be effective in extremely slow traffic.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

Re: Detour detection mechanism in the wiki

Postby CBenson » Sat Feb 22, 2014 1:40 am

The proposals look good to me.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

Re: Detour detection mechanism in the wiki

Postby CBenson » Thu Feb 20, 2014 7:59 pm

Seems to me that it would be appropriate to note this on the detours page in a "Notes" or "Side-effects" section. I've added this to the detour page, but consider it a draft that can be freely edited. Is there any reason not to put this on the detour page?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

PreviousNext

Return to Wiki Updates and Discussion

Who is online

Users browsing this forum: No registered users