A User Request was submitted in this area that I know well. The user says the ramp is now being favored over the thru route on the highway. This is similar to other issues we’ve been discussing on other roads. Can we change the level for a segment so waze won’t prefer it? What’s the protocol for a situation like this?
You can do a couple of things:
- You can change the name of the freeway so it doesn’t change from where the route exits the freeway to where the route reenters the freeway (e.g. name this segment “SR 28 S / Sully Rd”), or
- You can bring the clover leaves together and prohibit the straight through movement as explained here: http://www.waze.com/wiki/index.php/Limited_Access_Interchange_Style_Guide#Collector.2FDistributor_Cloverleaf .
I think the main problem here is that Waze sees an exit from Sully Rd and an entrance to “SR 28 N / Sully Rd”. Waze can’t see the two as being the same road because of the change in name. (This is what cbenson was referring to in his #1)
BTW, “SR 28 N / Sully Rd” doesn’t follow any naming convention in the Wiki in any way shape or form.
So, what should the road name be? Officially, it is called Virginia State Route 28.
It looks like Rt 50 and Rt 7 both use their long names, Leesburg Pike and Lee Jackson Memorial Hwy. So, should we just call it Sully Rd? South of I-66, in Centreville it becomes Centreville Rd.
How is it signed? If VA State Route 28 (or some variant thereof), then it should be State Rte 28 (or SR-28 maybe…this is a standard that is being tested, but won’t currently generate a shield…if you do this, make sure it has a hyphen). Put Sully Rd in the Alt Name Field.
If it’s signed Sully Rd, name it Sully Rd and put the State Rte 28 in the Alternate name field (once again, this currently won’t generate a shield, but it might at some point int he future).
If it’s signed with both names, then use whatever most locals call it, putting the other name in the Alt Name Field.
The double name takes up way too much space on the screen, and is awkward for TTS.
The full guideline is here: http://www.waze.com/wiki/index.php/Road_Naming_(USA)
It is not signed Sully Rd, for sure. Most people probably don’t know it’s name is Sully Rd. The signs all say “28 North” or “28 South”. Just verified with google street view.
At I-66 for example, signs say, “28 North Dulles Airport” OR “28 South Centreville”. Signs on Rt 50 say the same thing.
Everyone just calls is 28.
Just verified signage for Rt 50. From Rt 28 N it says, “50 Fairfax Winchester”.
Yeah, I haven’t been routed out there in quite a while (over a year). If I recall correctly, the ramps weren’t yet named, the road was named “Sully Rd” and all the signs just used the 28 shield. I was somewhat confused.
Wait, maybe the ramps were named like this. I’m guessing that “Sully Rd” is not on the BGS and am almost sure that the 28 shield is. This seems confusing to me.
The Dulles Airport, Centreville, Fairfax and Winchester are just pathfinders and should be used on ramps only (e.g. Exit ##: SR-28 N / Winchester) as dictated by the BGS.
If nobody knows it’s Sully Rd, and it’s not signed Sully Rd, get rid of Sully Rd from the map (or put it in the Alt Name field if you feel compelled to do so).
I would suggest State Rte 28 N or State Rte 28 S, unless you see that a lot of the other VA editors are using the SR-## convention. You might even get shields if you’re lucky!
That might be where “Sully Rd” came from initially. According to the BGS, that particular exit should be labeled “Exit 9B: SR-28 N / Sterling”
No wonder it was confusing if Waze was TTSing “Exit 9B: Sully Rd” and there’s no sign saying anything like that and no road with that name visible anywhere.
I notice that it’s labeled Sully Rd on GM, but of course, we know that GM is not necessarily a credible source.
I went through yesterday and renamed a bunch of segments so that they all had the same (wrong) name. ie SR 28 S / Sully Rd.
So, it sounds like using the proper format will get the shields to appear automatically? Are both of these (State Rte 28 N VS SR-28) formats equally likely to get the shields?
I was just looking over the other highways in the area and it appears all of them use the long name (Leesburg Pike) instead of the number. Rts 29, 50, 7, 11 all use long names. While I prefer the numbers, it would be nice to have both.
Is convention to put the number in the name and then use the long name as an alternate?
That just makes it easy for you to do a “select entire street” in the editor to change the name 
Even when wrong, consistency is helpful!
Just “State Rte…” SHOULD give shields, but shields are more or less broken no matter what we do right now. Improvements to shields should be coming soon, or so we hear.
It depends on the area. If everyone uses the name, that should be primary. If everyone uses the route number, then that should be primary. If you pull up to an intersection and the road signs say “Such-and-such Pike”, naming the road “US Hwy blah” probably isn’t helpful even if it is accurate.
Looks like I’m going to need some segments unlocked so I can fix the whole road.
I scanned the whole road and found 2 or 3 locked segments, which are now unlocked.
Ok, I cleaned up all of RT 28 from Centreville to Sterling with consistent names, and locked it down to my level. I also closed out that UR.
I’ll tackle from Centreville south next.
If you get a change to look at the ramp names that would be good as well.
I took care of RT 28 all the way South to Manassas City.
I started working on the ramp exits and these are locked out.
In my experience around the Northern Virginia area there are always route signs at intersections of primary routes. Sometimes the signs are rather smallish, but always there. There aren’t always signs for road names though. For instance the main subject of this thread, route 28, is always signed as route 28 and only sometimes signed with Sully Rd or Centerville road (though Centerville road is more common the farther into Manassas the road goes). It is locally referred to by all three names but 28 is probably the most common so I guess that should be the primary, at least north of 66. South of 66 at some point it may be better to switch to Centerville road as it gets into Manassas.
Right now it looks like the primary name is fine as state rte 28 from Manassas to route 7. But the Alt name is a hodgepodge, oftentimes no alt name. The assigning of alt names with multiple segments selected is quirky. If any segment has an alt name then that is listed when it is included in a multi-segment selection. It is very unclear (at least to me) that not all the selected segments have the displayed alt names. I’ve found that WME will not add a redundant alt name so if you have a multi-segment selection you can add an alt name that matches a listed alt name and it will get applied to the segments that don’t already have it but will not cause redundancy on segments that do. I’ve found that to be very handy when renaming complete roads when using the select all segments.
Thanks, Mike. I spent a decent amount of time redo-ing all of RT 28 from Sterling (RT 7) all the way down to Manassas (RT 234). I tried to be consistent and logical. As a NOVA native I agree with your assessment on naming our local roads. I will go through and double check the alt names. I may have missed a couple.
There is a similar problem happening in my area where users are reporting that exiting and re-entering the highway is the route given instead of staying on the highway. In this scenario, the segment names along the highway are consistent between exit and entry, but the city name is different. Would a city name difference cause a similar behavior, or only the street name?
This is the area in question. The routing has users exit off of US Hwy 75 N on the highlighted ramp, then re-enter immediately since US Hwy 69 merges there. The highway name is consistent, but the segment north of where the entry ramp connects is listed with the city of “Denison”, where the segments south do not have a city.
Yes different city names is enough of a difference. This is why some people prefer to not use any city names on freeways.
I have recently discovered a variation on this… if you have a long term construction area with road segments labeled with a “CONST ZN” suffix, now the road names are different and the ramps start looking like a valid shortcut 