Not satisfied with "to xxx" ramp naming
This is rather US-specific, but has applicability elsewhere I believe.
I've been following the current naming standards for limited access road on-ramps and it seemed right, but lately, I have not been satisfied. The primary reason for this is that when there are slow traffic conditions being reported at multiple on-ramps for a segment of freeway, then what you see on the client is a series of "Moderate traffic on to I-xx S" and "Standstill on to I-xx S" and on and on. When the freeway traffic is bad, the on-ramp traffic is bad, and then you get very unhelpful popups because every single one of those ramps is named identically.
I believe we need a way to concisely differentiate these on-ramps similar to the Exit ramps having the exit number, which is usually a mileage/milepost number. Or perhaps just add the road name of the previous segment to the ramp, like "to I-xx from <source road name>".
Thoughts?
I've been following the current naming standards for limited access road on-ramps and it seemed right, but lately, I have not been satisfied. The primary reason for this is that when there are slow traffic conditions being reported at multiple on-ramps for a segment of freeway, then what you see on the client is a series of "Moderate traffic on to I-xx S" and "Standstill on to I-xx S" and on and on. When the freeway traffic is bad, the on-ramp traffic is bad, and then you get very unhelpful popups because every single one of those ramps is named identically.
I believe we need a way to concisely differentiate these on-ramps similar to the Exit ramps having the exit number, which is usually a mileage/milepost number. Or perhaps just add the road name of the previous segment to the ramp, like "to I-xx from <source road name>".
Thoughts?
Re: Not satisfied with "to xxx" ramp naming