There doesn’t appear to be any standard way of naming state and county roads. I propose a standard be set and the state and national wiki is updated and an attempt to clean up the map is made as time permits.
The wiki for U.S. Highway naming has for Virginia …
That is technically incorrect. Virginia DOT doesn’t designate highways. In Virginia there are interstates, primary and secondary routes, and frontage roads (reference). For mapping purposes in Waze we should treat the primary routes as state highways. Secondary routes, numbered 600 and above (exceptions: 664, 785,& 895) should be treated as their functional class. Virginia doesn’t have county roads as some other states (i.e. maintained by the county). If a road has a route number then it is maintained by VDoT and falls under one of the above categories.
That said, you’re right. There is not a statewide standard set. I’ve seen all the variations that you mentioned (and a few others) and have corrected many. I’ve been using State Hwy and State Rte for primary and secondary. If we get a consensus on this the wiki can be updated.
Well the county route thing was an easy decision. I corrected the US wiki (with edit note pointing back to this thread) saying N/A on the county block.
Now… beings that I’m just a half-time resident and still a bit wet behind the ears as an editor, I’ll let the rest of you decide the state route name convention. I live to serve, whatever y’all decide!
At least IN MY AREA the convention seems to be SR-xxx which does TTS correctly, but I don’t know if that is a formally agreed upon convention, or just what’s happened.
The SR-xxx convention does not throw up a shield on the screen, unlike in MD where State Hwy xxx seems to be more commonly used and does provide a shield (oval, in this case)
US-xx provides a US highway shield, and I-xx provides an Interstate shield, and those also are commonly used in my area (NoVA, Loudoun County)
As an aside, in my area the BGSs all seem to use SR numbers to indicate the road onto which you are exiting, however, those SRs are not common usage for the various roads (e.g. a BGS near me uses SR-625 as the primary identifier for an exit, whereas all other signs and everyone I know would refer to it as Church Road or Waxpool Road depending on which direction you’re going.) Only major exception I can think of is SR-7 a.k.a. Leesburg Pike/Harry Byrd Highway which is always “Seven.”
Agreed; the only real argument against using that convention that I can see is the shield issue. However, my understanding is that Virginia uses “State Route” instead of “State Highway” and only “State Highway” or variations thereof actually produce a shield on the map, so it’s not so much of a concern in this state. Just my opinion of course.
In Central Va, the road names are used over the SR-XX numbers. As n8nagel said, this is just my opinion, but it is not that big if a concern in my area of the state
Agreed when it comes to naming the roads themselves, although if I know it and/or am using the official county maps as a reference while editing I will put the SR-xxx in as an alternate road name. I was assuming that this discussion was in reference primarily to BGS text/exit ramp naming, where at least in NoVA the SR numbers are nearly universally present on the BGS even if they are not in common conversational use, and therefore I include them so that the directions correspond as closely as possible to the BGS for the benefit of those not familiar with the area.
Yes, sorry for not being clear. Mainly for exit ramps and for what to write in the alternate street field. Out here in ole Page County it’s the same thing. Except for the two US routes that bisect the county, no one talks about route numbers. And Waze standard is to always use the local naming convention as the main street name anyway. But the ramp names are supposed to match what the BGS have on them.
So yeah, this is for ramp TTS directions and alternate street names mainly
