Archive 1 Archive 2

Common name/Numbered name (Miami Problem) RfC

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
No consensus for the proposed change. There has not been an establishment of consensus in favor of of a rule favoring the use of local common names for roads having a designated highway segment as part of a longer road with a common name. However, the absence of such a rule does not by itself dictate the names for the eight South Florida streets highlighted as examples; the appropriate name for each of these may still be considered on a case-by-case basis, which will necessarily take into account both the degree to which each usage is common, and the preference for consistency in article titles about similar topics. bd2412 T 16:35, 7 September 2013 (UTC)

In light of the lack of consensus reached in the requests to move Miami area-based common name-titled articles to numbered highway-titled articles and numbered highway-titled articles to common name-titled articles, should the common name of a road prevail as the article's title if:

  1. The numbered highway is a segment of the road that:
    1. Is shorter in length than the commonly-named road; and
    2. Lies completely (or with very minor deviation) from one terminus to the other terminus on that same road; and
  2. The common name is able to meet the article title criteria of precision, conciseness and naturalness?

-DyluckTRocket (talk) 07:31, 26 July 2013 (UTC)

SEE HERE FOR FURTHER CLARIFICATION

Common name/Numbered name survey

I fear that the scope of my intent is getting out of hand, i.e. a can of worms has been opened. What I originally intended it for was the succinctly described conditions above, and not an open invitation to rename every single numbered road to a common name. For most commonly-named roads with notability, they are part of a longer route that is common to more than one named segment of road: Numbered Route XY contains locally-named Road AB and Road CD. The way I see it, Route XY automatically gets naming priority over AB and CD because of this factor unless Road AB etc. is a notable-enough segment of Route XY to stand on its own merit without the Route XY designation. What I'm proposing here is for the opposite: Road AB contains all (or with a very minor deviation) of Route XY, and the length of Route XY is less than the length of Road AB. Pending the outcome of this proposal, perhaps we can look at expanding the scope at that time. -DyluckTRocket (talk) 15:09, 17 August 2013 (UTC)

Common name/Numbered name discussion

By "very minor deviation", I mean like in the example of Florida State Road 973 (Galloway Road) which uses a 190-yard-long (170 m) section of SW 132nd Street so as to link U.S. 1 to Galloway Road as the two roads do not have a direct intersection. Perhaps some more detailed criteria for this could be worked out? -DyluckTRocket (talk) 07:36, 26 July 2013 (UTC)

I don't think splitting the articles into two, one for "common" and one for "numbered" segments of the road would work without creating two articles that can't stand on their own very well and have less chances for improvement, and thus should be avoided. -DyluckTRocket (talk) 07:31, 26 July 2013 (UTC)

I did my own personal survey of the highways in the discussions about moving the road name article to the state highway article to aid my understanding:

All of these road names but Flagler Street are signed concurrently with or subservient to numbered streets. It is not clear (to me, anyway) whether these names or the numbered street names are in more common usage.  V 02:43, 27 July 2013 (UTC)

I also found the Template:Greater Miami navbox, which has a list of 50 Major thoroughfares. That is presumably a list of streets that some editors would like to see used in preference to state route numbers.

I was specifically looking for a street that contains two different state highways on different parts of the same road. An example of such a thing is Old Court Road, which carries Maryland Routes 125 and 133, which are separated from Old Court Road's endpoints and each other by county sections of the highway. The closest thing to that in this list is Red Road.  V 16:48, 27 July 2013 (UTC)

The issue that these articles are facing is that one type of naming seems to break the another's convention according to WP:CRITERIA. As the counter-argument put forward at the Name to Number Proposal shows, WP:COMMONNAME (and to a lesser extent, WP:OFFICIAL) was the preferred method of naming those articles as it was more recognisable and natural. The counter-argument put forward at the Number to Name Proposal was that the State Highway-hoodiness of those roads gave them notability (WP:N) and that WP:USSH allows for a more precise and consistent method of naming the roads. I believe that both of these arguments are equally valid, and that a compromise needs to be reached between the two. As VC pointed out, Old Court Road already provides a precedent to my suggestion with it wholly containing not one but two separate state highways in Maryland and is more precise as to what I meant. I think there's been confusion as to how my proposal would apply, as it appears that the opposing arguments address it not in the light of the qualifiers but with a broadbrush approach. I can see from a map of OK SH-3 how it could be called the Northwest Expressway in Oklahoma City; but would it be referred to that name in Broken Bow or Guymon? I doubt it. And it seems pretty obvious to me that the designation of CA SR-17 is intrinsic to one section of a notable road that is numbered otherwise from its northern terminus (though, please forgive my ignorance as to any prior contention). In both of these cases, according to my proposal, the State Highway article titles would apply and it would make sense that they would apply. I'm fairly confident in saying that the status quo would continue to apply to the vast majority of articles in USRD's care. -DyluckTRocket (talk) 10:47, 29 July 2013 (UTC)

Closing this thread

This discussion has been mostly dead for two weeks. Can an uninvolved admin make a finding and close this down?  V 01:57, 12 August 2013 (UTC)

Clarification of "Miami Problem" proposal

Since there's been some confusion as to what I've proposed here, I've created a diagram to explain what this guideline would apply to (updated August 20 07:00 UTC). This proposal is for the road/route combinations that meet conditions 1 and 2 at the start of this section and as illustrated in the diagram that may occur anywhere in the United States and not just Miami. Just so that I'm doubly clear, this proposal is not an open invitation to change the title of every numbered route article to a common name title.

Please (re-)state whether or not you support this proposal here. I would also like to hear thoughts on what would be considered an acceptable "very minor deviation". -DyluckTRocket (talk) 01:31, 19 August 2013 (UTC)

I will wait a little before introducing some categorical exceptions.  V 11:48, 19 August 2013 (UTC)

I'm going to go through Imzadi1979's points one-by-one first:
  1. I hope I am now using better or the correct terminology in the diagram in regards to the difference between the common and officially-designated names.
  2. As above. Also, as per established practice, an officially-designated name would continue to apply over a number used for internal inventory purposes (e.g. HEFT and not Florida State Road 821).
  3. Like VC, I think this is the crux of conjecture; everything else is a technicality. I've addressed my views of this below these numbered points.
  4. This guideline is not designed to nor should be used to circumvent the notability criteria for a county-designated road. The status quo would continue for them.
  5. The fourth example in the grey box is meant to illustrate situations like Oklahoma State Highway 3, as Scott5114 highlighted, which I believe covers the majority of articles under WP:USRD's care: an officially-designated route (XY) contains multiple commonly-named roads (AB, CD ... n1n2). The article would continue to be called by the official name. Also, I support merging of articles as in the case of Interstate 90 in Illinois: this, too, would also continue, especially since the officially-designated route is longer than and is unconstrained by the common names (thus not falling under this guideline at all). Furthermore, in the case of sub-pages of longer routes, such as the state pages of national routes, these would also continue in their current format.
  6. I totally agree with Imzadi1979 here. If a common name segment of an officially-designated route can demonstrate independent notability, it should continue to be or else become its own article. Once again, the common name is a segment of the official route (XY > AB), so the guideline would not apply.
I feel most of the arguments in opposition so far have been on the basis of notability, and have tried to qualify by opposing the objective, technical aspects of the proposed guideline (which the first condition covers). VC has pointed out what the true issue of contention is with the guideline by referring it back to WP:CRITERIA, the subjective aspects of the proposed guideline (the second condition). The title criteria is what sparked me to suggest the guideline in the first place! Let me recap what's happened in regards to that:
  1. I put forward a move request on eight articles that are still referred to by their common names. This was rejected on the basis of WP:COMMONNAME (WP:UCN), with the argument that WP:USSH is applied in contradiction to WP:COMMONNAME and thus the Recognisable WP:CRITERIA, going so far to say: "WP:COMMONNAME is clear that WP prefers commonly used names to 'official' names when there is a conflict".
  2. Apparently emboldened by this decision, a counter-proposal was put forward after the first proposal's closure to move four articles from their official-designation titles to their common names. This argument was rejected on the basis of notability, which has been repeated many times in the arguments against this proposed guideline. VC suggested that a RfC should be made regarding this issue: you're looking at it right now. (On a side note, I find it odd that Florida State Road 990/"Killian" was not suggested for a move in the counter-proposal: my guess is due to it being both Killian Parkway and Killian Drive.)
So, let us put any technical issues aside, here, as I feel they've been addressed; or if not, are secondary in importance. What the real issue is regarding these articles and any others like it is that, in striving to meet WP:CRITERIA, it either sacrifices WP:COMMONNAME or WP:NOTABILITY. The method I'm proposing is intended to be a compromise between WP:UCN and WP:N, and can act as a reference for this situation across the entire project. Perhaps in my endeavouring to be succinct I haven't made my intentions clear, but there it is in black and white.
In regards to VC's concerns regarding WP:CRITERIA, the use of the common name leans more in favour of Recognisability and Naturalness, while the use of the official name leans more towards Precision, Conciseness and Consistency (particularly the last one). If you want to go on a simple majority rule, then the official name wins 3 to 2. Judging by the arguments, though, particularly when I tried to change the commonly-named articles to officially-named ones, it seems to me like a lot of weight is put on Recognisability and Naturalness, suggesting ordinality rather than cardinality of the criteria. Is this the case? I don't know for sure, but if Recognisability alone was able to quash my move request, then that is what I feel the greatest concern is, too. This is something that, should this guideline be approved, that we will have to work out criteria for. Do we use the newspaper of record of the city or state the road's in? Do we use state DOT inventories? Or what do we do? We can't rely on original research and do straw polls; even so, I'm sure the answer will be similar to if I was to ask someone in Brisbane whether they know it as and call it Route 32 or Milton Road (and I'm fairly sure it's the latter). I'm pretty confident to say that the Recognisable road name for most people interested in a road are going to be those who are local to it. Does that make it notable? Probably not as much as, say, State Route XYZ123, and I concede that fact; but, it brings it into line with WP:UCN. The same goes for Naturalness; yes, they will probably need parentheses on articles. As it is, I want to see Galloway Road become Galloway Road (Miami) even though there's no other article called that due to the simple fact that when I type "Galloway Road" into Google Maps, none of the auto-suggested Galloway Roads are in Miami. Doing so would make it more Precise, but at the cost of being Concise; and certainly at the cost of Consistency. Heck, I suggested the move in the first place so that they would be Consistent; but, apparently that doesn't weigh much in the face of WP:UCN. With this guideline, the article titles would be Consistent - consistent with this guideline as an exception to the normal consistency of WP:USRD's articles. It would also meet WP:UCN and be notable for those most likely to read the articles. Look, I agree it's not perfect, but it's better than having this issue unresolved. -DyluckTRocket (talk) 13:14, 20 August 2013 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Interstate 595 problem

Look at Talk:Interstate 595. I proposed a move of Interstate 595 to Interstate 595 (disambiguation) and Interstate 595 (Florida) (the only highway officially signed as I-595) to Interstate 595. But people were against the move, not paying enough attention; they were under the impression that this move was as arbitrary as a move of Interstate 295 (Florida) to Interstate 295. It was not. All 8 (or more generally, at least 2) of the highways on the Interstate 295 dis-ambiguation page are officially signed as "Interstate 295", and each highway has a vicinity where residents know the highway as "Interstate 295". On the other hand, for Interstate 595, the Florida highway is officially signed and known as Interstate 595, but the Maryland highway is not. I find it very natural to think that someone who searches for Interstate 595 will very unlikely want to find the Maryland highway because people who live there know the highway as part of US 50, and will unlikely expect Wikipedia to have an article about the highway titled Interstate 595. It's surprising that people support equal-topic dis-ambiguation for the Florida and Maryland highways in this case as if both were officially signed as Interstate 595. Any questions?? Georgia guy (talk) 19:05, 16 December 2014 (UTC)

Yes, one big suggestion. Drop the combative attitude. Make a case without denigrating other editors. As for your points, I'd support moving The Florida I-595 to primary topic and using a hatnote to point to the unsigned Maryland highway, which despite your protestations, is still officially I-595 albeit unsigned. (I-296 is still officially I-296, even though Michigan has had official permission not to sign it for 35 years now.) When there are only two ambiguous titles, one primary with a hatnote to the other would be appropriate. However, we have the proposal out of Maryland to number the I-170 freeway and an uncompleted stub of I-70 in Baltimore as I-595, and there's the Virginia proposal for a segment of US 1. Even if we could discount the I-70/I-170 situation (like we mostly discount the 1958 proposal out of Michigan to number what is now I-275 as I-73 and what is now I-696 as I-98), we can't currently eliminate the Virginia proposal. That means 3 ambiguous titles, and that means a disambiguation page.
The short version: if there were only Florida and the current Maryland highways, we could do this with a hatnote. However, we have a three- or four-way ambiguity, so the status quo is appropriate. Imzadi 1979  23:57, 16 December 2014 (UTC)
You're implying that I want the dis-ambiguation page deleted, rather than moving it to Interstate 595 (disambiguation). Moving the page won't affect what it means; and it doesn't imply that we don't need it. Georgia guy (talk) 23:59, 16 December 2014 (UTC)
Long-standing consensus is not to use "(disambiguation)" as part of an article title in these cases. Various templates are built with the underlying assumption that an undisambiguated Interstate Highway is either the national article (for a 2dI) or a disambiguation page (for a 3dI, when not unique). Your proposal would upset that assumption. That's one example, and proposing changes to the scheme of the naming conventions has been viewed as highly contentious. Imzadi 1979  01:42, 17 December 2014 (UTC)
Look at Interstate 410 for an analogy. This is the only other Interstate highway number with exactly one highway that's current, official, and signed; and at least 2 highways that don't meet this criterion. Georgia guy (talk) 17:46, 1 May 2015 (UTC)
For I-595, I oppose making the Florida route the primary topic since there is also a current route in Maryland, even though it is unsigned, along with a couple former routes. As for I-410, I am okay with the Texas route being the primary topic since it is the only current route and a dab page handles the former routes well. If there are two or more current Interstates of the same number, then none of them should be the primary topic, regardless of signage. Dough4872 23:19, 1 May 2015 (UTC)
You mean, many Marylanders know the highway as if it were actually signed as I-595 (whether it is or not)?? Georgia guy (talk) 23:46, 1 May 2015 (UTC)
No, most Maryland residents know the freeway connecting Washington and Annapolis as US 50 but it is still officially I-595 according to the official FHWA and MDSHA sources. Therefore, there are officially two current I-595's that exist along with the couple planned ones that were cancelled. Signage or lack thereof should not determine the primary topic, as Maryland may choose one day to sign that portion of US 50 as I-595. Therefore, I feel the status quo is best. Dough4872 00:19, 2 May 2015 (UTC)
See this. It suggests that the event you're talking about is very unlikely. Do you have any arguments supporting the statement that it's possible?? Georgia guy (talk) 00:22, 2 May 2015 (UTC)
I still think using signage as the barometer for what the primary topic should be is not the best way and that we should stick to disambiguating if there are at least two current roads with the designation, in addition to the two former roads. Dough4872 00:28, 2 May 2015 (UTC)
Why?? Why should current-official-unsigned highways be as significant as current-official-signed highways?? Georgia guy (talk) 00:32, 2 May 2015 (UTC)
My $.02 we should be using common names in articles (except where it is not practical to do so, which admittedly does happen a lot with road articles). Wikipedia is written for a general audience, not roadgeeks. As such if the general public is not aware of the I-595 designation, that should not be the article title provided the common title (US 50) is workable (which it is in this case). Of course the I-595 designation does need to be mentioned (preferably in the lead) of the article and redirects should be created, as appropriate. I will admit that there are several scenarios where no common title is workable and we have little choice but to use the unsigned designation for the article title. Now if we were writing an article for Roadgeekapedia, I would have a different POV.Dave (talk) 00:41, 2 May 2015 (UTC)
I get it, that what I'm basically implying in this case is that the I-595 (Maryland) article be merged back into the US 50 article (since both articles already exist). I do believe it is appropriate in this case. If consensus is against the merge, then I guess we have no choice but to use I-595 (Maryland) as the article title. Given that, the Interstate in Florida is the primary topic to a general audience, to Georgia Guy's point. I'll leave it to others to determine how badly that would break templates and if we should not go with that convention to avoid breaking templates. i'm out of the loop on templates. Dave (talk) 00:50, 2 May 2015 (UTC)
Of all of the goals of article titles, one is consistency, and the proposal would completely toss out a consistency goal in this case. Even though there is nothing else named "M-185" or "M185", we still use M-185 (Michigan highway) as the title to be consistent with the couple hundred other articles on highways in Michigan. There are multiple I-595s, but if there were only the two, I wouldn't have an issue with using the un-disambiguated title for the Florida one with a hatnote to the Maryland one. However there are others, and it's not appropriate to use hatnotes to point to multiple alternate articles. For that reason, and to stay consistent with the other auxiliary Interstate Highway articles, the un-disambiguated title should be the disambiguation page and each highway gets the appropriate state name to give each a unique title, even if those titles are used on redirects. Imzadi 1979  01:28, 2 May 2015 (UTC)
You're saying, "...and it's not appropriate to use hatnotes to point to multiple alternate articles." But this is not what I want. I merely want Interstate 595 (Florida) to be at Interstate 595 with a hatnote pointing solely to the dis-ambiguation page at Interstate 595 (disambiguation). And note the part of this discussion absent from the part we already had; this brought up a new title, Interstate 410, to compare Interstate 595 with. Georgia guy (talk) 01:33, 2 May 2015 (UTC)

@Georgia guy: The I-410 example should be changed to conform to the predominant situation followed by the other 3dIs. There a few rules at work here:

  1. If there is only one highway with the designation, then no disambiguation is necessary. Because the templates have assumed disambiguation by state, we have a redirect. For an example, Interstate 696 is unique, and so that templates would continue to link to it, Interstate 696 (Michigan) was created as a redirect.
  2. If there are exactly two highways with the same designation, and if both are current, then neither is the primary topic. See Interstate 375 and both Interstate 375 (Michigan) and Interstate 375 (Florida). For intentional links to the disambiguation page, there is the Interstate 375 (disambiguation) redirect.
  3. If there are exactly two highways with the same designation, and one was unbuilt/cancelled, then the current highway is the primary topic. The unbuilt/cancelled highway is disambiguated. A hatnote links readers from the primary topic to the secondary topic, as in Interstate 605 and Interstate 605 (Washington)
  4. If there are more than two highways with the same designation, the same rule is followed as example 2. See Interstate 270 and the four highways listed there for an example. Also note that for the Illinois–Missouri example, there is a pair of state-specific redirect from those two states to keep the templates happy.

There are multiple goals in determining what to title an article. One is to keep titles concise, but another is to keep them consistent. Your proposal would satisfy the former but not the latter. Imzadi 1979  07:56, 2 May 2015 (UTC)

Keep articles consistent?? Now, what is the current status quo of Interstate 595 consistent with?? My answer would be as follows: if the dis-ambiguation page George Bush had 4 people, exactly one of which is well-known as "George Bush", and each of the other 3 people is a person whose legal name is "George Bush" (middle name irrelevant,) but who is best known by a name like "Gus Bush". (I'm not saying that this is the status quo of the George Bush dis-ambiguation page; I'm merely giving this as an example of what the status quo of Interstate 595 keeps the page consistent with.) Georgia guy (talk) 12:26, 2 May 2015 (UTC)
Your example doesn't quite apply, Georgia guy. I want to keep the titling scheme consistent with other highway articles. How articles on biographies of politicians are title is not exactly relevant to a naming convention on highways in the United States. Imzadi 1979  04:40, 3 May 2015 (UTC)
Keep titles consistent?? Now, when is an appropriate situation for keeping titles consistent?? If the article subjects have consistent descriptions, then it makes sense for the article titles to be consistent. But look at this inconsistency:

The subjects have inconsistent descriptions; so I see the "keep titles consistent" artificial here. Georgia guy (talk) 12:41, 3 May 2015 (UTC)

The guideline says to use the "Interstate X (State)" naming convention for auxiliary interstates whenever the route number is repeated in more than one location. The guideline also does not use the "Interstate X (disambiguation)" theme, because of the state disambiguation practice. The naming of highway articles in this guideline is not contingent upon the status of highway signs on the route.
A similar case existed with Interstate 580. Prior to 2012, there was Interstate 580 (California) and an active but unsigned designation for Interstate 580 (Nevada) (a former Interstate 580 (Nebraska) designation also existed). Even though only the one I-580 in California was actually signed from the 1980's until 2012 (when Nevada I-580 was completed and signed), Wikipedia has used Interstate 580 as a disambiguation page since 2005.
Even though the Maryland I-595 may not be signed, it still exists as a separate entity from I-595 in Florida. Thus, the state name disambiguation is still needed for these articles, as what was done with the I-580 situation. Moving the title as proposed introduces an article naming inconsistency that is not currently present and that goes against precedent. Georgia guy, if you can produce a logical argument for changing article titles against guideline and current practice (and that isn't solely based on an "it's the only signed I-595 in the country" reasoning), then I'd certainly be willing to entertain it. -- LJ  19:21, 3 May 2015 (UTC)
For the Maryland highway, it's known by Marylanders as a part of US highway 50. Someone who wants to find an article on the highway would expect it to be found at US 50, not at Interstate 595. In fact, there's already an article titled U.S. Route 50 in Maryland, which is what someone would most likely expect. Now, here are 2 questions for you to answer:
  1. What if there were a Wikia wiki whose subject is the state of Florida?? What would you support??
  2. What if there were a Wikia wiki whose subject is the state of Maryland?? What would you support??

My answers are:

  1. Interstate 595 should actually be an article on that wiki.
  2. Interstate 595 should re-direct to U.S. Route 50 on that wiki.

What are you answers?? Georgia guy (talk) 19:34, 3 May 2015 (UTC)

This isn't Wikia, and how they do things has no relevance here. --Rschen7754 19:36, 3 May 2015 (UTC)
I'm asking these questions to show exactly the difference between a current-official-signed Interstate highway designation and an Interstate highway designation that's former, future, or unsigned. I see current-official-signed Interstate highways as more natural to expect than former, future, or unsigned highways. Many Interstate highways occur at least twice as current-official-signed highways, an example is Interstate 295. All the current-official-signed I-295's are known as I-295 by the residents of their vicinity. So it would make sense for someone who wants to search for any of those to search for the name Interstate 295. But Interstate 595 occurs only once as a current-official-signed highway. I'm sure that someone who searches for Interstate 595 will most likely want to find an article on the Florida highway; it's signed as I-595 and it's known by the residents of its vicinity as I-595. The Maryland highway is an unsigned I-595; the local residents of its vicinity know it as part of US 50. So it's most likely that someone will expect an article on the Maryland highway to be titled U.S. Route 50 in Maryland; I strongly doubt that someone who wants to search for the Maryland highway will type "Interstate 595". Georgia guy (talk) 19:54, 3 May 2015 (UTC)
If I want to read articles about every current official interstate numbered 595, having no prior knowledge of any of them, it is unreasonable to expect me to search for "U.S. Route 50".
You're pretty much repeating yourself now. I'm fairly convinced at this point that you don't have a reasonable rationale or explanation (other than signing status) to explain why we should rename the I-595 articles as something inconsistent with the long-established article naming convention. Time to let it go... -- LJ  21:44, 3 May 2015 (UTC)
Now, if you really want to keep me from having this discussion again, you should create a Wikipedia essay. Any thoughts?? Georgia guy (talk) 21:53, 3 May 2015 (UTC)
So in other words, WP:IDHT? --Rschen7754 21:57, 3 May 2015 (UTC)

Discussion to rename U.S. Highway System articles

I have started a discussion at Wikipedia_talk:WikiProject_U.S._Roads#Major_proposal_to_rename_USH_articles about renaming U.S. Highway System articles. Your input is appreciated. –Fredddie 22:47, 9 January 2016 (UTC)

NJ 23 versus Route 23 in text

I'm sure this has been discussed out the yin-yang, but I feel I must insert my thoughts. I don't think its appropriate to refer to New Jersey State Routes as simply "Route xx" in the article text, but to call Interstates and US Routes as "I-xx" and "US xx". Its inconsistent. To New Jerseyans, they are all simply "Route xx" while to NJDOT they get their prefixes (SLDIAG's all list the state routes as being "NJ xx", for example). Anyway, I'd argue that they should either all be simply "Route xx" (including the US and I routes) or that the state routes should be "NJ xx". Famartin (talk) 19:02, 29 September 2018 (UTC)

So if I understand you correctly, "Route xx" is used generically for any class of highway: Route 80, Route 30, Route 21. However, we apply specific abbreviations to Interstates, U.S. Highways, and even county roads. Is that correct? I personally wouldn't have any issue with changing it to "NJ xx". –Fredddie 13:07, 30 September 2018 (UTC)
Correct. Famartin (talk) 17:36, 30 September 2018 (UTC)
@Dough4872 and Mitchazenia: do either of you have an opinion here? Please ping any other editors who may want to voice either way. –Fredddie 13:38, 11 October 2018 (UTC)
I'm okay with switching the state routes to "NJ X" since it seems like "Route X" is a generic term to refer to any numbered route maintained by NJDOT. Dough4872 14:15, 11 October 2018 (UTC)
For the states I'm familiar with state documentation uses the term "SR" and the only time I see the state abbreviation is in roadgeek websites. The convention I have used so far is to use SR when talking about a route in the same state as the subject of the article, but when taking about a state route in a different state use "CA" or "NV" or "CO", whatever, for clarity. An example of this is U.S. Route 50 in Nevada which does mention Utah State Route 201. With that said, I don't think it matters what term we use (SR, SH, Route, Highway, state abbriviation, etc.), as long as we're consistent in style in side the same article. Dave (talk) 14:47, 11 October 2018 (UTC)