Had a UR on this, segment should be renamed US Hwy 6.
Aren’t they called “US Routes” in NY and not “US Highways”?
Well we would just say “Route 6” but in Waze naming convention I have always used “US Hwy x” as the wiki doesn’t give any reference to using “Rte” on US signed roads, only for state roads in which case it should be State Rte x / SR-x.
http://www.waze.com/wiki/index.php/How_to_label_and_name_roads#United_States_Numbered_Highways
Shhh… Don’t tell anyone, but we just use it in CT & it works…
I’ve tried to find out what the official US government name is, but I haven’t been able to find it on anything official… The best explanation is on Wikipedia, but it’s Wikipedia & I won’t use it as a basis for an argument here unless it can be verified by a governmental source… http://en.wikipedia.org/wiki/United_States_Numbered_Highways#Naming
Interesting. And that “shields” the road?
It certainly makes more sense and goes with local spoken word. Although I didn’t do US-6 other than a couple of locked sections pointed out by the UR. Other than the divided section not having their direction indicated it’s at least consistent. I’ll put it on the list to go back and rename later along with US-9.
It did… but then all shields broke again… We don’t even have shields on most of the interstates here in CT now…
In NYS, we are using “US-6”, “US-11”, “US-219”, etc., as the segment names. This takes up less screen space in the navigation list (and on the map screen as well, particularly since shields don’t work well any more and aren’t likely to be fixed any time soon :roll: ), while still conveying the pertinent information. IIRC, the TTS voice properly pronounces “US-6” as “you ess route six” (or maybe it was “you ess highway six” – can’t remember offhand which one it is).
While I agree that that is probably the best solution for US Routes (or highways or whatever people call them), the wiki specifically says not to do that… http://www.waze.com/wiki/index.php/Road_Naming_(USA)#United_States_Numbered_Highways
It is indeed the best solution that we currently have, and the Wiki is out of date with regard to the comment about “this is the format that the Live Map and client will parse”. That sentence needs to be removed, since neither the LiveMap nor the client are actually parsing the name data to generate highway shields (which I believe was the original intent of that sentence – it has nothing to do with routing, since that is dependent on the road type and the historical data stored with the road segments).
I figured as much… Any word on when we’ll get shields back? Or what we’re going to need to do to have them generated (i.e. new name field in WME, name them a certain way, etc)?
For right now it seems that we should just hold off on changing existing road names until we hear what will actually generate shields, right?
I agree that US-x looks better and (you ess number) in TTS gets the point across. Luckily I haven’t done much renaming on US routes except to fix mistakes.
The wiki should be updated to reflect that change if it’s to be global, otherwise maybe updating the NY page or putting a sticky for local naming conventions in the NY forum.
With that said, why aren’t we using SR-x for State Rte segment names as well if we don’t care about shield generation any more? It will look a whole lot cleaner in the client and navigation. According to the wiki the only time SR is to be currently used is on ramps.
Speaking of shields, I saw one this morning on I-287. But mostly I was just seeing I-287 W/E.
For state routes, I’d rather see them label as “CT-##” and “NY-##” and displayed as such… TTS should be able to have a look list that would read “CT-” as “route” or, using an example from the wiki, “PA-” as “Pennsylvania” or “Pee-Aye” (or whatever it is called locally). TTS would have to insure seeing the following dash (-) so as not to confuse the state abbreviations with the road designation.
As for shields, this would allow for 50 state specific ones (they are all mostly rectangular) and keep the oval available for other numbered roads (County Road/Route ##, Country Road ##, Rural Route ##, etc)
I agree it would be better to use the state abbreviation as the route instead of SR, an in NY that is actually how they are written in maps (NY-123), but to hear “Enn Why 123” is just weird. It would have to be parsed like you said as “Route 123” or maybe “Enn Why Route 123” or “New York Route 123” (I think saying “state” in the last two examples wouldn’t be necessary).
If you look at the wiki, some places actually refer to the roads at “Pennsylvania 123” or “Pee Aye 123” (not saying Pennsylvania does, but using it as an example).
Oh I read the Wiki and know some places do that, but it’s not something we are accustomed to saying here in NY (or even CT, AFAIK) which is why I think the included word “route” would help for the TTS. Not that my opinion matters. Just tell me what to type and I’ll do it. 
Sorry to have dropped out of the conversation temporarily, but I spent most of the day on the road. (You should see some changes on the NY scoreboard if Waze ever updates the points – they’re 2 days behind again, what a shock. :o NOT!! 
) At any rate …
Have you looked at the New York page in the Wiki yet? (I realize that the link back to the Wiki standards page there probably causes some confusion – I’ll address that later, depending on the outcome of the discussions. However, the examples listed after the link do show the current NY naming conventions.)
Refer to my previous question. SR-x is what is in place on that Wiki page, and has been for some time (I’ve been using it extensively in WNY, and it works well). It was chosen because it does play nicely with the TTS, as well as taking up less screen space, particularly when making some necessary changes to a segment will destroy its shield anyway. Also (and I just noted this again on my travels today), when driving down an Interstate and a major route crosses as an overpass, a little green sign on the side of the bridge labels it as “SR-x”, “US-x”, etc. (at least that’s what I’ve been seeing over here in DOT Region 6 … I would assume that this is probably an NYSDOT standard nomenclature, although NYC might use something different).
I agree with your sentiment that “enn why sixty” in TTS just doesn’t get the meaning across as well as “state route sixty” does – especially since in my forty years in and around this state, I’ve never heard a local talk about “enn why sixty”, only “state route sixty” or (more commonly) just “route sixty”.
I’ve looked into this and it seems that Pennsylvania does do that, as does Louisiana (ellay ##). However, it seems to be unique to these two states.
The wiki says “SR-#” is ok for ramps, but not for Road Names, mainly to save space on the exit ramp…
Which is why I suggested the lookup table, so each state can have their local reference… (and custom shields)
It’s just par for the course
I have read the NY Wiki and yes having the link back was confusing. :oops: My mistake but easily corrected. It makes more sense to use the same nomenclature for both the roads and ramps. Looks like it’s going to be a rainy day, I know what I’m doing! :lol:
I also need to update that page since I completed I-684 a while ago. Also, not to go off topic, I’m currently working with the DOT functional maps in Westchester an making sure the roads are classified properly and am working quadrant map by quadrant map, not sure how or if you want to note that on the page.
Just a quick FYI before I go back to tiling the downstairs half-bath – I moved this to the New York forum, as the discussion that has evolved from it doesn’t need to take place in the “Update Requests” forum. 