Post by WeeeZer14
CBenson wrote:Ok, then: When bearing left on a ramp (that is not a "best continuation") you always get a "Keep/Stay left" instruction. But when bearing right on a ramp the type of segment you are leaving matters - when leaving a highway/freeway segment you get an "Exit right" instruction but when leaving a ramp you get a "Keep/Stay right" instruction.
Thus, the statement in the wiki under Wayfinder Segments - Ramps that says
Note: will provide Exit left/right
should say "Note: will provide Exit right/Stay left."
And the statement under Ramp to Ramp Splits - Example that says:
If you are headed to "DestinationLeft", navigation would tell you:

Exit Right to Destination Left
Exit Left to Destination Left
should say:
If you are headed to "DestinationLeft", navigation would tell you:
Exit Right to Destination Left
Stay Left to Destination Left.
As long as you can confirm I am not crazy and that is accurate, I'll make the changes :) Typing that up recently in the wiki is what made me try to pay more attention in the car.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
CBenson wrote:
WeeeZer14 wrote:As long as you can confirm I am not crazy and that is accurate, I'll make the changes :) Typing that up recently in the wiki is what made me try to pay more attention in the car.
That is how all the examples I can find work, so I think I confirm that is accurate. Whether you're crazy or not, I don't yet have conclusive evidence.
Please let me know if you reach a conclusion on my sanity. The voices in my head are curious. :lol:

In the mean time I've started to update the wiki. A question though... for a split with a ramp leading to two more ramps, are we sure the right hand path given an "exit" and not a "keep"? I don't have any contrary evidence, I just want to make sure.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
Okay, I think I caught all the places where we needed to make a distinction for right-hand vs left-hand drive countries and the keep/exit differences.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
ncc1701v wrote:This is an important point. Here's one for the other side of the argument: suppose I see a section of road marked orange. I start in and there are no delays so I figure Waze is showing me old information ... until suddenly I have to slam on the brakes for stopped traffic. It would be safer for me if I had fine-grained information.
What could be finer grained than a user reporting a traffic jam? It is right where the traffic is, right? But how many times have you been driving and you hit traffic well before the pin for the jam? Or you pass the pin at full speed but then you find the ripple of traffic a mile ahead? If you guys haven't, this has happened to me many, many, many times.

My point is that the granularity may give a false sense of accuracy that doesn't really exist. It is accuracy vs precision. We don't need to be more accurate than we are precise.

Now that said, a 5 mile chunk of road may be reasonable. A mile I wouldn't be comfortable with. Less than a mile, no way.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
CBenson wrote:I'm wondering about the statement under Geometry:
Approximately 0 degree departure angle = no navigation instruction
I don't think small angles necessarily give no navigation instruction. For instance, I see many ramps that split between a straight section and section that bears off to the right. When I go straight I get an instruction usually a "stay left" instruction. Here is an example where the ramp splits going straight and bearing off to the left. Going straight here you receive a "stay right" instruction.

It seems to me that as most zero deflection roads have the same name and type as the entering segment, most don't get an instruction. However, if they don't have better name match or type match than another segment that has a deflection less than 45 degrees than I believe that they do get an instruction (typically a "keep/stay" instruction, but could be an "exit" instruction).
You do bring up a good point. If we have matching types and non-matching names, we may get instructions. I do still want to make the point about "close to zero" being important, but I guess it needs a disclaimer about special cases (most of which are probably discussed elsewhere). Let me mull it over a bit.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
I added this paragraph under the "table" of angles and their results:
NOTE: There are exceptions to these rules since geometry is not the only factor which determines instructions. See later sections for how Segment Naming and Type can impact instructions.
As you've drawn your example, the continuation onto A St and B St are such that I would expect NO prompt to go on A St (since name and type matches and the angle would not produce a "turn" prompt) and you should get a "keep/stay" for B St.

How to handle it depends on the real world lane stripping and signage to me. If the real world obvious continuation is onto B St, then I'd make A St come off at 90 degrees to force an instruction. Not sure that we could get a keep/stay right without hacks. If A St is the obvious continuation, we may be fine as is.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
Just a note that I DO want to add Tim's method to the page. I think it is an elegant kludge and it is in use in the UK already.

As long as what we do remains backwards compatible with whatever Waze comes up with for junctions in the future I think we are okay. We have millions of users using Waze today, so we have to do something for them. And I think any form of the wayfinder technique is simple and low impact enough especially since it isn't being done on EVERY junction.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
kentsmith9 wrote:We are about 9 months behind documenting the Bow Tie intersection. I created an entry for it in the JSG if someone wanted to tackle it.
I just posted a first draft of content. Some of the content is very general and may need some concrete numbers. What I've said is basically my personal rules, so let me know if someone has a better system.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by WeeeZer14
kentsmith9 wrote:I think it generally covers it although I used it when dual carriageways cross each other as well. I think that would be easy enough to add in without requiring an image.

Maybe we should also add an image of the H-intersection so it is clear what this intersection looked like before the bow tie. For that matter would it make more sense to show the intersecting dual carriageways image.
I agree with your suggestions. Probably won't be until Monday/Tuesday when I get a chance though.
WeeeZer14
Posts: 3761
Has thanked: 21 times
Been thanked: 252 times
Send a message
iPhone 5s (AT&T) • iOS 7.0.3 • Waze 3.7.6.0
[img]https:///V68te[/img]
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator

Post by Wolfeye
An idea about how far from the junction the geometry node should be set when making a 20-30° or 90° angle. My suggestion is to make this part of the segment equal to the size of the turn restriction arrow when fully zoomed in.


http://www.waze.com/wiki/images/1/13/Wa ... n_50px.jpgHörnefors-Umeå
Uppdaterar svenska Wikin: http://world.waze.com/wiki/index.php/Sweden
Wolfeye
Posts: 327
Has thanked: 5 times
Been thanked: 4 times
Send a message