Un-named segments for better navigation

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.

As an example from my previous post, see this segment: https://www.waze.com/editor/?zoom=6&lat ... s=66095587

And, if you have Livemap navigation add-on, see how the instructions come out:

Into Clackamas Town Center (mall): http://www.waze.com/livemap/?zoom=15&lo ... g=70258916

Onto Sunnyside Rd westbound: http://www.waze.com/livemap/?zoom=15&lo ... g=61551280

That unnamed segment in the middle makes it so Waze will give a "keep left" or "keep right" the right place, and because of it being unnamed, Waze in the app automatically announces the name of the next named segment, which is exactly what we want.

Damn, really? Then would what Alan suggested be better?

I still can come up with a Good Idea every now and again!

What will show if there's a map report on the unnamed segment? Police reported on unnamed road?

I think that is an issue.

It will, Nacron. And that is an issue.

As I ponder this more...even if the segment is named, as long as the next two segments are named differently from the parent, and there is an angle of 30 degrees or so (can't remember exactly), from the parent to each following ramp segment, then you should get proper TTS for both right and left.

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.

The middle segment isn't a pathfinder segment and has no need to be named. It will never appear in navigation guidance because it is a segment after a merge of two ramps, and therefore never appears in the app, per what I wrote above and this specific situation. The only reason to name it is for traffic reports.

Sorry, I could have been more clear. This was a reply to the OP only.

Cool then. I agree.

I don't see any problems with your scenarios. They look to be a great description of the advantages of unnamed segments and make great sense. I don't think the unnamed section before the highway split is going to catch on around me because typically we are adding the control cities in the names at split so the instruction is not simply the highway name.

As far as other scenarios go there is the classic segment between carriageways of the split highway where the cross street changes name at the highway.

I also wonder if no name segments are useful to force prompts at street splits as well as highway splits. For instance at this intersection, without the unnamed segment traveling south on Arundel on the Bay Rd you get no instruction when staying left, but do get a "stay to the right at Thomas Point Rd" instruction if going straight. I'm wondering whether adding the no-name segment will cause instructions (both ways) if staying on Arundel on the Bay Rd. It seems to me this is exactly the same principle as you are using on highway splits (but with instructions in both directions to consider).

Lastly, I don't understand your caveat that TTS will not read out the name of the following segment, but it does display on the client.

So in the first screen shot you don't get a equivalent TTS instruction "at the roundabout take the first exit at A1237?"

I'm going to guess that its the roundabouts that disrupt the TTS as I'm not familiar with many double roundabouts. If I recall correctly I have been in parking lots with unnamed segments where I get multiple TTS instructions that recite the name of named road after the parking lot exit as I am routed through the parking lot.

I also wonder if no name segments are useful to force prompts at street splits as well as highway splits. For instance at this intersection, without the unnamed segment traveling south on Arundel on the Bay Rd you get no instruction when staying left, but do get a "stay to the right at Thomas Point Rd" instruction if going straight.

I can now confirm that the no name segment does trigger a keep left if traveling southbound on Arundel on the Bay Rd. Traveling northbound from either Thomas Point Rd or Arundel on the Bay Rd gives no instruction when continuing on Arundel on the Bay Rd. due to the slight angles. This seems to be ideal to me.