Re: Un-named segments for better navigation
Posted: Sun Apr 28, 2013 8:00 pm
Damn, really? Then would what Alan suggested be better?
Waze: outsmarting traffic together
https://www.waze.com/forum/
I think that is an issue. But if you weigh it against a driver not being given enough of a warning about bearing left or bearing right, I side with the navigational advantage. This system isn't perfect.Nacron wrote: What will show if there's a map report on the unnamed segment? Police reported on unnamed road?
If it's the area next to the H201 that splits to go to the H3 or H201 I already noticed that a long time ago and made that guide naming there. I did the same thing at the W H1/W H201 split and it calls ut the guide naming correctly. Perhaps the segment before the split has to just be blank instead of having a name.vickimachado wrote: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:
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!)
Just drove it, no instruction given to stay right. What if we changed the h201 segment after the fork into the freeway road type?vickimachado wrote:Well, at max zoom, it shows, now less acute:CBenson wrote:I didn't see the angle to cause the turn instruction. The turn seems to be back to no instruction.
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!
http://img.tapatalk.com/d/13/04/28/gazypeva.jpgvickimachado wrote: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:
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.
What will show if there's a map report on the unnamed segment? Police reported on unnamed road?AlanOfTheBerg wrote: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.
I didn't understand that idea the first time around, and now that it seems to be becoming accepted dogma I would appreciate a clear explanation. Apparently I'm missing something.sketch wrote:I cannot agree with the use of unnamed segments as a replacement for pathfinder segments in the United States, especially in light of kentsmith9's traffic concern.