Un-named segments for better navigation

[AlanOfTheBerg]

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.

[sketch]

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.

[AlanOfTheBerg]

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

Cool then. I agree.

[ncc1701v]

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.

As the saying goes in Massachusetts, the light has dawned on Marblehead. Thanks, Kent, for the 1:1 guidance.

[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?