Un-named segments for better navigation

[kentsmith9]

Thanks, Kent, for the 1:1 guidance.

My pleasure.

[kentsmith9]

segments don't know anything, only the client or route server (collectively "Waze") knows.

I believe AlanOfTheBerg told me from a prior conversation with Waze that the database tracks the average transit times from segment to segment so it can be applied to routing decisions. The problem with a short segment just before the Y-split is only the short segment will have two different average speeds exiting that segment. So when the traffic backs up longer than the short segment, the next segment with only one exit (to the short segment) will only have a single average speed from the two segments beyond it's reach. So yes the routing server knows where the next car is going, but it only has one average speed from the segment before the short one.

I added some material in the Wiki on this topic (separate segment routing times based on different exit segments) under "Turn delays" and also "Segment exit times." Are there other terms that come to mind I should link?

[Machete808]

Think I'll test this theory on these ramp segments:

https://www.waze.com/editor/?lon=-157.9 ... 5,12925503

Attention was called to it with this UR:

https://www.waze.com/editor/?lon=-157.9 ... TTTFTTTTFT

In case it's closed, here's what it looks like:

H1H3.png

(240.69 KiB) Downloaded 995 times

The stated problem:
it told me to go the comlplete wrong way on the merger it split into 3 lanes and the map didnt even recogonize that

Just guessing that this was the "merger" that was meant, though it may not be. Drove there and when the highlighted segments then led either to the E-H3 or to the E-H201, I got no nav guidance telling me there was a choice.

Any idea on how to test this? Should I delete the name on both the highlighted segments, or just the first? (In any case, I'll save it someplace so I can put it back if it doesn't work!)

[Machete808]

Nacron, I don't know. But a fairly minor change may work. The turn-off onto the EH-3 access gets a nav prompt just fine (tried it on my way home tonight).

But my recollection from an earlier test is that the ramp leading to the E-H201 gets no prompt -- I'm guessing because there's no "turn." I tweaked a geometry node where it pulls away, and after the next update, I'll check it. Meantime, no harm, no foul.

[Machete808]

Thanks! Looks like I have to add an unnamed highway segment where the split appears to be straight, and then resume the ramp type. Will look a bit odd on the map, but I tested it again last night after dropping my husband off at the airport. The need for a navigation prompt to the EH201 is that if you don't get a "stay to the right" instruction, you may be in the left lane that takes you off to the EH-3.

[Machete808]

I agree with the sentiment. I don't mind the experimental tweaking of the map to achieve this or that -- this is all rather inexact. I just wish we could communicate with Wazers who post update requests, that's all.

Returning to my ramp-segment issue: It appears that bending the geometry of the ramp generated a navigation prompt, which is great. Now I'm easing the angle slightly to see if I can get it to say "stay to the right" instead of "turn right." May not need to add a wayfinder segment, after all.

[Machete808]

I didn't see the angle to cause the turn instruction. The turn seems to be back to no instruction.

Well, at max zoom, it shows, now less acute:

Screen Shot 2013-04-20 at 6.29.24 PM.png

(48.17 KiB) Downloaded 986 times

But it seems that won't work, right? (Haven't had a chance to recheck it.) Read the wiki, and it looks as if I should insert an unnamed ramp segment at the start of the split. I'll try that. Thanks again!

[Machete808]

Nacron,

I noticed the same thing as I drove past today, so I decided to follow the wiki advice. I've just inserted an unnamed wayfinder segment (ramp type), 15 meters in length, at the point where the ramp continues to E201. Next update, let's see if the prompt kicks in.

[Machete808]

Permalink:

https://www.waze.com/editor/?zoom=5&lat ... s=12947865

Just to circle back on my issue noted earlier. Adding a short unnamed FREEWAY road segment produced the navigational prompt I wanted at the split between the EH-3 freeway and the EH-201. Now as you approach the split, you're told to stay to the right to get on the EH-201. That warns drivers so they don't find themselves bearing left onto the H-3:

wayfinder.png

(38.54 KiB) Downloaded 485 times

Previously I had tried an unnamed RAMP segment before the split and it didn't work. I'm sure that's explained somewhere in the Wiki, but I didn't get it.

[Machete808]

Vicki, the segment which should be unnamed is this one: https://www.waze.com/editor/?zoom=6&lat ... s=12925503. There's no reason for it to be named as it will never be shown on the navigation guidance. Then you can use two named ramp segments (one ramp segment named "to E H3 Fwy / Kaneohe" and the other named "to E H201 Fwy / Honolulu") at the split and both will be announced because the previous (long) segment was unnamed.

There's no need for all this extra kludgy stuff to be done.

Huh! OK, simpler is better. Thanks.