Just chiming in here: as far as I’ve read and understood, there are no “county roads” in DE. Some of the instances I’ve seen from slower lower ( ) have “Rd 123”. When I’ve driven around some of those areas, I’ve noticed that “Rd 123” will occasionally be signed as such, but will more generally be “Roadname Rd”. For those instances, I will make the primary name “Roadname Rd” and set “Rd 123” as the alternate.
As for the “US-13” vs. Dupont Hwy argument (for example), I generally have been going with signage. For example, the majority of US-40 through Delaware is signed as Pulaski Hwy, but there are a few spots where it is signed as “US-40”. In those cases, I have left it as Pulaski Hwy and the alternate is US-40.
I made a change to the name of US-13 in Sussex County (from Bridgeville south to Delmar) to Sussex Hwy after I realized all the street signs at intersections showed the street name. I haven’t gone farther than that. Have you noticed anything other than that?
Looking at the WME, it appears as though much of US-13 is unnamed in Kent County. On the street blade signs, US-13 in Kent County is known as:
S Dupont Hwy (from the Sussex Co line to SR-8 in Dover)
N Dupont Hwy (from SR-8 in Dover to southern Smyrna limits)
S Dupont Blvd (from southern Smyrna limits to E Commerce Street in Smyrna)
N Dupont Blvd (from E Commerce Street in Smyrna to NCCo Line)
In NCCo, US-13 is known as Dupont Pkwy (no direction in the name) from the Kent County Line to SR-72.
If you’d like, I can certainly help out with this task.
I personally abhor street names in navigation, especially when I’m traveling in areas I’m unfamiliar with. I want to get instructions using route numbers. But the street names are pretty vital for address searching along those segments, so we’re stuck with it.
It also creates issues when people create place names because it suggests the address using the closest segment’s “street” name so there’s some things along Concord Pike with an address like “2015 US-202 N” instead of “2015 Concord Pike” (which I correct when I see them)
Not saying it’s not a bad idea to implement it. Just because I don’t like it doesn’t mean it’s a bad idea! :lol: If there are residential or businesses along a roadway that have addresses as a street name then the segment should probably be named after the street name.
Now I HAVE seen cases where addresses have the route numbers in them. For example:
The Luray Zoo * 1087 Us Highway 211 West * Luray, Virginia 22835
Now you want to see ugly? The west part of that address is because it’s on the west side of the town. However the business is on the eastbound side of the highway. So the standard for naming on Waze is the segment should be US 211 E and the other side is US 211 W. So the address shows incorrectly as 1087 US 211 E in this case. So to be correct I should make the primary name US Highway 211 West and the alt name US 211 E but then if someone is driving northbound and approaches 211 and has to turn right (east) they’d be instructed to “turn right on US Highway 211 West” which is confusing :shock:
But I digress… I do wish Waze would separate the route numbers as a separate field from street name instead of overloading them into one space… It’s pretty ridiculous.
I hear ya! I’ve been waiting awhile for Waze to allow us to use route shields as part of the naming system. I think this would be a major help. On the app, I see them on many of the interstates, but I don’t see many US Routes and State Routes. I think implementing these would make both sides happy. :lol:
This topic is being retired as 1) its main point is now a well-known standard and documented in teh wiki, and 2) some of the information is outdated and no longer correct. It will be locked and demoted to a standard topic.
) have “Rd 123”. When I’ve driven around some of those areas, I’ve noticed that “Rd 123” will occasionally be signed as such, but will more generally be “Roadname Rd”. For those instances, I will make the primary name “Roadname Rd” and set “Rd 123” as the alternate.