Misplaced Pages

talk:WikiProject U.S. Roads: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 21:28, 18 March 2007 editRschen7754 (talk | contribs)Autopatrolled, Extended confirmed users123,234 edits →March 16 meeting recap← Previous edit Latest revision as of 04:19, 21 December 2024 edit undoImzadi1979 (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, File movers, Mass message senders, New page reviewers, Pending changes reviewers, Rollbackers, Template editors151,547 edits um, no, this page project is not part of that projectTag: Undo 
Line 1: Line 1:
{{tmbox
{{Shortcut|]}}
|image=]
]
|text=<div style="font-size:large; text-align:center;">Centralized discussion for the U.S. Roads WikiProject</div>
{{Shortcut|WT:USRD}}
*If you would like to discuss the standards for route junction lists, please use ],
*If you would like to request a map, please use ],
*If you would like to request a route marker (shield), please use ],
*Featured Article candidates, Good Article nominations, and deletion discussions are listed automatically within 24 hours at ] and
*For all other comments or concerns, please post below.<hr>
'''Archives:''' ],&nbsp;{{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads}}<br>IH: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Interstate Highways}} • US: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/U.S. Routes}} • USAT: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Auto trails}} • USRD/STDS: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Standards}} • USRD/A: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Assessment}} • USRD/NT: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Notability}}<br>
'''States:''' AL: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Alabama}} • CA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/California}} • CT: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Connecticut}} • FL: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Florida}} • GA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Georgia}} • IL: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Illinois}} • IN: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Indiana}} • IA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Iowa}} • KS: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Kansas}} • KY: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Kentucky}} • LA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Louisiana}} • MD: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Maryland}} • MA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Massachusetts}} • MI: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Michigan}} • MN: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Minnesota}} • MO: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Missouri}} • NV: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Nevada}} • NJ: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/New Jersey}} • NY: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/New York}} • NC: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/North Carolina}} • OH: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Ohio}} • OK: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Oklahoma}} OR: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Oregon}} PA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Pennsylvania}} • RI: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Rhode Island}} • SC: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/South Carolina}} • TN: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Tennessee}} • TX: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Texas}} • UT: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Utah}} • VT: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Vermont}} • VA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Virginia}} • WA: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Washington}} • WV: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/West Virginia}} • WI: {{Archive list|nobr=yes|sep=dot|root=Misplaced Pages talk:WikiProject U.S. Roads/Wisconsin}}
}}
{{User:HBC Archive Indexerbot/OptIn |target=Misplaced Pages talk:WikiProject U.S. Roads/Archive Index |mask=Misplaced Pages talk:WikiProject U.S. Roads/Archive <#> |leading_zeros=0 |indexhere=no}}
{{mbox
|type=notice
|small=
|image=]
|imageright=]
|smallimage=none
|smallimageright=none
|textstyle=text-align:center;
|text=<inputbox>
type=search
break=no
placeholder=Search the archives
prefix={{FULLPAGENAME}}
width={{#ifeq:{{{small|}}}|yes|30|50}}
</inputbox>
}}
{{WikiProject banner shell|
{{WikiProject U.S. Roads|class=Project}}
}}
{{Archives|bot=lowercase sigmabot III|age=14|large=yes}}
{{User:MiszaBot/config
|maxarchivesize = 450K
|counter = 25
|minthreadsleft = 2
|minthreadstoarchive = 1
|algo = old(14d)
|archive = Misplaced Pages talk:WikiProject U.S. Roads/Archive %(counter)d
}}
{{Misplaced Pages:Misplaced Pages Signpost/Templates/Signpost article link for WikiProjects|link=Misplaced Pages:Misplaced Pages Signpost/2010-05-03/WikiProject report|writer=]|day=3|month=May|year=2010|dateform=mdy}}


== AARoads Wiki ==
{| class="infobox" width="150"
|- align="center"
| ]
''']'''
----
|- align="center"
| ] ] ] ] ]
|}


Please join us over at the . We look forward to seeing you soon! <span style="background:#006B54; padding:2px;">''']&nbsp;]'''</span> 20:27, 12 September 2023 (UTC) <!-- ] 20:27, 9 September 2033 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|2009910459}}
== Photo galleries? ==


:I sure hope that this project isn't shutting down. It would be unfortunate for us to cave to the opinions of non-content contributors at an RfC who probably don't even know how to read a map. ] (]) 02:16, 24 September 2023 (UTC)
This seems to be an issue only on New Jersey pages, but I figured I'd bring it here for a couple of reasons (the relative inactivity of ], and that it ''could'' turn into an issue on any USRD article). What's the opinion on photo galleries? Specifically, should they be included? And if so, where in the article?


:I've marked the page as per this. 20:59, 23 September 2023 (UTC)
I'd been meaning to tackle the issue for a while, but didn't have the guts to do it until a mini-edit war developped on ]. There are a couple of issues at play here. As Alansohn points out, putting the gallery where I currently have it prescribed on ] (where it is in ) might break the flow of the article. However, putting it anywhere else – specifically below the link sections, i.e. – violates ]. Taking the pictures out of a gallery – i.e. – is awkward when there's not enough article text to support it.
:I just want to state for the record that I intend to continue maintenance of Washington articles as well as those I brought up to GA status in other states. I'm going to be contributing to both projects, albeit with less detail for roads articles on here. ''']]''' 04:27, 24 September 2023 (UTC)
:In reality there are two more alternative sites we can choose from - and . The former is a Misplaced Pages-like site that forked all contents from here last year and has lenient notability requirements. ] (]) 13:30, 27 September 2023 (UTC)


== GAR ==
Which begs the question of whether we should have these ]. Certainly to some degree, it violates ]. The question is to what degree? How much do the seven images in the ] gallery contribute to the context of the article – especially when three of them are written with captions telling the story of a specific hazardous spill that happened one day? -- ] <sup>]</sup> 19:24, 21 February 2007 (UTC)
::Perhaps only one or two of those images is good for the article: the toll booth and traffic. However, they could both be put somewhere in the prose, I'm sure. Galleries, IMO, are not good for an article about a road. Pictures are good, yes, but only if they can be put into the prose. The rest of the images on NJTP are fine. There should be a link to the Commons where there can certainly be a gallery of images there (as there is on the NJTP, but I'd like to see it in a more prominent position than at the very bottom of the article). In the case of NJCR 549, it one of those images should be brought up to the prose, on the left, near where "segment 1" and "segment 2" are, IMO the second image. They should really all be on the commons if they're PD, then a Commons link to the gallery there. '''--]<sup> ] / ]</sup>''' 19:41, 21 February 2007 (UTC)

:::Maybe it's my text size or resolution, but when I hit a gallery, especialy if it runs to two or more rows, it appears that the article has ended. *I* know it hasn't, but other readers are unlikely to continue further to references and links. In many cases, these galleries are little more than laundry lists of uploaded pictures, that have no connection to the article other than showing a small stretch of the title roadway. I'd be happy with pushing them down to the bottom, which keeps them in the article, but makes them the afterthought they seem to be. It's not clear that ] requires that links be the last item or if it merely suggest an order. ] 20:19, 21 February 2007 (UTC)

: I booted all of the pictures on the ] article to the bottom because I couldn't pick the two or three best of the lot and put them in the article. I objectively (subjectively?) couldn't tell. Number of pictures should be directly related to the length of the road, though. A county route spur should have no more than 2 pics. I-80, one for each state and optionally the ends (but Misplaced Pages is not a <state name> Ends Page, either). State routes, 3-5, again depending on the length of the road, and if there's anything "visually notable". If all the pictures look the same, just pick the best one and be done with it. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 20:14, 21 February 2007 (UTC)

:My personal take is that galleries should be avoided whenever possible, as they (IMHO) detract from the quality of the article. Instead of a gallery, the images should accompany the prose or (if licensed freely) be removed from the article and get moved to the Commons, where a gallery can be made there. An example is on ], where a gallery of 8 images once existed. As part of my cleanup of the article a while ago, I ditched the gallery and included the images alongside the prose, improving the article in my opinion. --] <sup>] - ]</sup> 20:26, 21 February 2007 (UTC)

:: I agree with this philosophy; I was just having trouble with the "canyon of text" that runs down the middle of the page when you have pictures floating left and right. There's a length table floating on the left, a major cities table running the length of the page floated right, and any pictures will be under these two respective tables, creating the canyon. At 1024x768, it starts to look really crowded. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 20:58, 21 February 2007 (UTC)
:::Me too. I don't like "canyons of text", either. ] is on the upper limit of what an article should look like. Still looks better than it did. '''--]<sup> ] / ]</sup>''' 21:24, 21 February 2007 (UTC)
I say just keep what photos you need in the prose and use a Commons gallery for the rest with a link using <nowiki>{{</nowiki>]<nowiki>}}</nowiki>. --] 21:29, 21 February 2007 (UTC)
:Would it be possible to get a Commons link in the infobox? It'd be optional provided there's a corresponding Commons gallery. '''--]<sup> ] / ]</sup>''' 22:05, 21 February 2007 (UTC)
::Absolutely, just need to modify Infobox road, add a parameter such as commons=yes. --] 23:46, 21 February 2007 (UTC)
:::To answer a question that has yet to be asked: Best place for said link would probably be below the little-used links row that exists below the browse row. --] <sup>] - ]</sup> 23:49, 21 February 2007 (UTC)

I agree with moving to Commons. --] 01:53, 22 February 2007 (UTC)
:I'll support moving to Commons. But we also need a higher quality of pictures on most articles for the pictures that stay. Perhaps a ]? &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 16:55, 22 February 2007 (UTC)
::When you say a higher quality, do you mean using a better camera or better composition of the photograph? --] 18:33, 22 February 2007 (UTC)
:::Better composition. It's not too hard to make I-70, 80, 90 and 94 all look the same if you're in the Great Plains. I think the idea is to take photos of the highways that allow you to distinguish one from another visually, too. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 18:36, 22 February 2007 (UTC)
::::I agree, photos of rural interstates should be avoided unless there is something truly remearkable about the scene. All rural interstates look the same, 2 lanes in each direction, median in the middle, got it, don't need a photo of each one. Photos of interstates through urban areas are much more interesting. --] 18:42, 22 February 2007 (UTC)
:::::Agreed. Of course, I'm all about scenery. A rural interstate with mountains in the background is a great sight! But yes. A ''nice'' rural image is better than no image at all. But if there's a good urban image, it can take the place of a rural image should it need to be decided. But yes, higher quality and urban trump lower and rural. I'll comment more later, have to go'''--]<sup> ] / ]</sup>''' 19:25, 22 February 2007 (UTC)
::::::Extra points for pictures that actually have the shields of the highway in them. Shields happen to be great distinguishing visual markers. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 19:47, 22 February 2007 (UTC)
:I agree with the moving to Commons, too. The idea hadn't even crossed my mind. -- ] <sup>]</sup> 18:06, 22 February 2007 (UTC)

I couldn't finish earlier because my class started so I had to get off the 'pedia. So the consensus is that no galleries on articles; instead link to the commons where galleries can be housed. Add photos as long as prose can support them; valleys of text are ill-advised, and photos with shields (and signs?) are good. That sums it up?
Also, are we going to go through with adding the commons parameter at the bottom of the infobox? With the little commons logo? We'd still keep the commons template at the bottom. '''--]<sup> ] / ]</sup>''' 21:30, 22 February 2007 (UTC)

Okay, infobox road now supports a link to the commons, all you have to do is add the parameter commons=, if left blank it won't create the link, if there is something input, it will create the link, for simplicity, just put commons=yes if you want the link. I added it to ] so everyone can see how it looks. It links to a gallery that doesn't exist at present. It will automatically create the gallery link to the same name as the article title. --] 21:45, 23 February 2007 (UTC)

:Uh, this just screwed up every other infobox. Look at ]. --] 21:57, 23 February 2007 (UTC)

::Sorry about that; I saved a messed up version. Now it pulls the name displayed from what's at the top of the infobox. --] 21:59, 23 February 2007 (UTC)

:::We are going to have dab issues if we use what is at the top of the infobox. --] 22:02, 23 February 2007 (UTC)

::::That's not true; it still links to the right place. --] 22:05, 23 February 2007 (UTC)

:::::I see, I misunderstood what you meant. --] 22:06, 23 February 2007 (UTC)

::::::This could be harder than I thought. On "Interstate XX in " articles, how would it link to the general "Interstate XX" gallery on the commons? Like ] has a link that goes to ]. '''--]<sup> ] / ]</sup>''' 22:32, 23 February 2007 (UTC)

:::::::Simple, use a redirect. --] 23:01, 23 February 2007 (UTC)

I changed it so that now it links to a category on Commons instead of a gallery page, since thats what {{tl|commonscat}} does. See ] for an example. -- ] <sup>]</sup> 08:34, 26 February 2007 (UTC)
:I disagree with this, perhaps for interstates this works, but most roads will have one or two photos of them, why create a category for the road if just one photo is needed, it will just make it harder to maintain and to upload photos as well. I think it should point to a gallery page and if a cat exists for that road, then a redirect is put in place to have it point to that category. --] 11:11, 26 February 2007 (UTC)

::How about a parameter to choose whether you want a category or not? --] 15:09, 26 February 2007 (UTC)

:::That works, makes sense just as {{tl|Commons}} and {{tl|Commonscat}} both exist. --] 15:33, 26 February 2007 (UTC)

:::Okay, it's done, put either commons=category or commons=gallery, for those that have already put commons=yes, they will need to go back to make the change. I change NJ 7 and CR 549. --] 15:58, 26 February 2007 (UTC)

::::No problem, that's a good compromise. I wasn't aware that there were two different templates, and after reading ] a little more thoroughly, it seems like the best way to go about it – there's no consensus there as to whether galleries or categories are better, only that both are fine. -- ] <sup>]</sup> 16:32, 26 February 2007 (UTC)
:::::Is linking a reader to ] the goal? I clicked on it and there are a few shields, a lot of maps, and one picture on the first page. Are we creating separate categories for just the pictures? &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 17:20, 26 February 2007 (UTC)
::::::No, I wouldn't create another cat just for pictures, the link in the infobox just says media, it doesn't specify photos. If you just want to link to the photos, I would recommend the use of a gallery instead. --] 17:27, 26 February 2007 (UTC)
:::::::All right... that's entirely a stylistic issue, then. It depends on how unappealing dumping a user onto the commons page is. If there's over a certain number of pics in the category, I would consider making a separate gallery, otherwise it is what it is. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 17:32, 26 February 2007 (UTC)
I can't count that many colons, so I'm going back to the left. I think it's fine. A reader might find some interesting stuff with the maps and shields and whatnot. Never know. I think as they are, it's fine. Creating all new categorys might require discussing it on the Commons though. '''--]<sup> ] / ]</sup>''' 18:06, 26 February 2007 (UTC)

== Re-upload all shields? ==

] and ] have defied all of my attempts to purge and re-purge so that the images show up (see ]). Is it better to just re-upload all of the shields and hope this problem goes away once and for all? &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 19:41, 22 February 2007 (UTC)
:It's been confirmed above that reuploading the shields is a guaranteed way to fix the bug. I say go ahead. --] <sup>] - ]</sup> 20:13, 22 February 2007 (UTC)
::Are we talking reuploading all the shields, or just the buggy ones? I don't think we need to reupload all of them, I think the bug just comes from those made in Adobe. So maybe just those. --] 21:40, 22 February 2007 (UTC)
:::Only the buggy ones. No point in reuploading ones that already work. --] <sup>] - ]</sup> 21:41, 22 February 2007 (UTC)
I've already reuploaded I-76's shield, which is problematic. I have a bot on Commons, so you can tell me which shields need to be reuploaded. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 23:08, 22 February 2007 (UTC)
:If my memory serves me right, all of the U.S. Route and Interstate shields (except some of the newer ones like ]) that haven't been reuploaded are glitchy. Some state systems that may be affected are Florida and Virginia, but I'm not positive. --] <sup>] - ]</sup> 23:16, 22 February 2007 (UTC)
:::As I have mentioned once before, it's probably SPUI's using Adobe Illustrator to create the SVGs. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 23:32, 22 February 2007 (UTC)
::::&lt;sarcasm&gt; Yes, let's blame everything on SPUI, since he's been gone for months. Everything must be his fault. &lt;/sarcasm&gt; -- ] <sup>]</sup> 23:37, 22 February 2007 (UTC)
Most Virginia shields were uploaded by NE2. Only I believe 789, 895, and very few others are by SPUI. I personally haven't seen any problems with them though. '''--]<sup> ] / ]</sup>''' 02:08, 23 February 2007 (UTC)

Would you believe that re-uploading I-494.svg and I-794.svg didn't work? I might try something a little more drastic... &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 04:37, 23 February 2007 (UTC)
:Try clearing your cache. I-494 works for me on the article linked at the top of this section. --] <sup>] - ]</sup> 04:38, 23 February 2007 (UTC)

I re-uploaded ], but was not able to fix ]. --] 04:46, 23 February 2007 (UTC)
::I opened it in Inkscape (OS X, not that it matters) and re-saved it. That finally did the trick. I'll try doing the same to U.S. 278 now. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 04:47, 23 February 2007 (UTC)
:::WOW! It works! :) '''--]<sup> ] / ]</sup>''' 05:38, 23 February 2007 (UTC)

:I came here from ]. I noticed a few weeks back that in the image wasn't shown. This was the case even after I purged ] several times and even after I reuploaded the image. Still the 62px image doesn't work. Any solutions to this problem? -- ] 21:49, 23 February 2007 (UTC)
::What is that link you put in there, are you sure you have that right, it has two extensions, svg and png, I-476.svg shows up fine for me. Why do you want it at 62px, seems like a totally random size. --] 21:58, 23 February 2007 (UTC)
:::I uploaded a new version at 22:06 23 Feb 2007. That could be why it shows up fine -- I replace the broken SVGs as I hear about them. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 22:54, 23 February 2007 (UTC)
::::My computer and browser requires a .png extension after the .svg extension in order to show up. Sometimes, though. Only if I'm changing the file name in the address bar do I need a .png extension. It's weird, i know. If I go to a shield, right click, and select "copy image location" (PC), and then paste it, it adds a .png extension. '''--]<sup> ] / ]</sup>''' 23:05, 23 February 2007 (UTC)
:::::I think that's because IE 6 doesn't support SVGs, so Misplaced Pages automatically converts SVGs to PNGs (but possibly just for that browser). &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 17:22, 26 February 2007 (UTC)
:::::Firefox. But doesn't really matter though; the SVGs work after they're reuploaded. '''--]<sup> ] / ]</sup>''' 17:59, 26 February 2007 (UTC)

== Articles for Deletion ==

I am about to nominate a few articles for deletion, just wanted to run it through here, maybe I am missing something, they look like surface streets in ] and ]. ], ], ], ], ], ] and ]. None of these are associated with any state or county highway, if they are, they fail to mention it. Are any of these worth keeping? I am a bit surprised they haven't found their way to AfD yet. --] 19:58, 23 February 2007 (UTC)

:Since there wasn't a response, I have nominated them all at ]. --] 17:45, 14 March 2007 (UTC)

== Recent articles for deletion ==

I have solicited a response to recent listings at ] on the ]. You are invited to come participate. --] 05:04, 27 February 2007 (UTC)

== Deletion discussions ==

]; ] --] 12:27, 27 February 2007 (UTC)

== The "States traversed" section ==

Copied from ]:
:So... what's the balance between "a summary of U.S. Route 20 in X" and "not enough content"?
Thanks! &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 17:53, 28 February 2007 (UTC)

== ] AfD ==

] is up for deletion at ]. Please review the article and participate. ] 02:09, 1 March 2007 (UTC)
:I'm going to abstain from the AfD since I don't want to encourage a slippery slope of more road AfDs, but honestly wouldn't it be a good idea to draw the inherent notability line at state highways and above? I think the politician guidelines in ] set a good precedent: members of nationwide and statewide legislatures (thus Interstates, US routes, and state routes) are considered notable, while local politicians (thus county-level routes and city streets) must have an additional claim to fame to merit their own article. ] 03:30, 1 March 2007 (UTC)

== Proposed Merger ==

Due to the number of contributors to this project taking a big hit following SRNC, I think we need to look at some consolidation. I am proposing we merge ] and ] into this project. This would consolidate conversations to a central location. It would cut down on a lot of administrative tasks between the three. WP:IH and WP:USH have less highways combined than most of the states. --] 11:29, 1 March 2007 (UTC)
:I don't really know how I feel about that. I'm leaning toward opposing this...but I'd like to hear from other editors on this first before I really take a stand. '''--]<sup> ] / ]</sup>''' 21:28, 3 March 2007 (UTC)

:It seems like a good idea to me, since Interstates and U.S. Highways are just state or local highways with funny-looking shields. Other than the involvement of the FHWA and AASHTO, there's nothing that differentiates the process of writing them from that of any other U.S. road. --] 21:31, 3 March 2007 (UTC)

::To be honest, I don't see what the difference would be one way or the other. For me at least, I treat all highway articles the same for the bulk of my editing. The individual state WikiProjects (and USH and IH) just deal with little idiosynchracies between the states. -- ] <sup>]</sup> 21:35, 3 March 2007 (UTC)

:::I think the benefit is that we'd have a centralized place to discuss. --] 21:39, 3 March 2007 (UTC)

::::Then why not just redirect the talk pages for IH and USH to here? '''--]<sup> ] / ]</sup>''' 21:47, 3 March 2007 (UTC)

:(ec) I '''oppose''' this vehemently. An article on an Interstate has a distinctly different composition than that of a U.S. route. For the most part, the "centralized discussion" argument is moot: most of the discussion already occurs here anyway. It's not as if consolidation will lead to more getting done. Someone still has to make edits to work on the articles, and if the same amount of editors are present, it will take just as long to make the edits whether there is consolidation or not. --] <sup>] - ]</sup> 21:41, 3 March 2007 (UTC)

::What would be the difference between the article on ] and the article on ] had it not been redesignated in 1989? --] 22:09, 3 March 2007 (UTC)

::I also don't understand what difference there is between the composition of an Interstate and a U.S. Route. In my opinion they should be the composed the same if they aren't that way already. I personally believe all road articles should have the same basic structure. --] 14:35, 5 March 2007 (UTC)

:I support '''redirecting the talk pages''' as MPD suggested, centralized discussion is a good thing, but there's enough differences between writing about Interstates and US routes that it's a good thing to have separate style guides and such. ] 23:20, 3 March 2007 (UTC)

== Recent policy changes limiting primary sources ==

There have been recent changes in the merging of ], ] and ] into ], along with related changes at ]. One thing that may affect geographic projects is the tightening of the requirement for multiple secondary sources for all articles. Many geographic articles are created from a single primary source like census data or topo maps. Technically, this would subject these articles to deletion. If you have not checked these policies lately, you should. And be sure to check the supporting discussions. Remember WP policies and guidelines are supposed to incorporate a broad consensus. ] 20:18, 3 March 2007 (UTC)

:Given that any commercial map that shows the road can be added to the references, this "threat" has no teeth. I also don't see anything at ] that matches what you say. --] 21:15, 3 March 2007 (UTC)

:] states the following: '''"Edits that rely on primary sources should only make descriptive claims that can be checked by anyone without specialist knowledge."''' Route descriptions and such that rely on maps and topos are perfectly valid in this regard; they use maps to back up descriptive claims that can easily be backed up by consulting the map. ] 00:00, 4 March 2007 (UTC)

== ] ==

The new maintenance parameter puts a redlink on every state infobox that doesn't yet have the necessary template added. Not to mention that I don't think it's such a good idea, since some states have several different agencies that maintain the roads (NJ and MD come to mind. I'm going to revert again – if you find a way to do it so redlinks don't appear, then I'll let it stay, but I'd prefer the discussion happened on-wiki next time. -- ] <sup>]</sup> 22:01, 5 March 2007 (UTC)
:Well, sometimes some discussions won't happen on-wiki. It is, in fact, sometimes easier to have a talk on IRC, have a drink, and implement the change, since it can be implemented quicker and can be done without straw polls. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 22:10, 5 March 2007 (UTC)
::If it's done behind the scenes, then there's no way you can show the changes reflect consensus. Imagine if MPD and I decided to hold the discussion on ] off-wiki.
::I changed my mind about reverting, mainly because I noticed that it's not falsely claiming the ] is maintained by ]. Just next time you make a change to a template, don't leave me with broken infoboxes for so long. (You could have avoided that by creating the sub-templates first, ''then'' changing {{tl|infobox road}}.) And I guess this is fine since once it's implemented properly, it's a relatively minor change, but any major changes to the project need to have on-wiki discussion, so that (a) everyone can participate, and (b) we have some sort of discussion to point to afterwards. Telling me three users discussed it on IRC isn't enough. -- ] <sup>]</sup> 22:16, 5 March 2007 (UTC)

Also, the only reason the line isn't showing up on ] is because it uses the "highway_name" parameter. I have a feeling we're still going to run into problems with regular unnamed highways that aren't maintained by the main agency. ] for instance is NJDOT-maintained for most of its length, but county maintained near its eastern terminus. -- ] <sup>]</sup> 22:44, 5 March 2007 (UTC)

Problems can be solved if we change it so that if you use the '''maint=''' parameter, it supercedes the default "maint" template for the state. I'd do it myself, but I don't have the time at the moment, and I'm only 75% sure I'd know how.

I have a test case at ]. It's the ] infobox, but I added in the line <code>|maint=]</code>. If someone could fix {{tl|infobox road}} so that my test case read that it was maintaned by the Turnpike Authority instead of NJDOT, that would get rid of (I think) all my qualms about the change. -- ] <sup>]</sup> 04:53, 6 March 2007 (UTC)

This maint parameter should be hidden unless explicitly called. Some states have numbered routes that are not maintained by the state DOT. Why can't this new parameter be made optional? --] | ] 05:18, 6 March 2007 (UTC)

:Agreed, that's what I'm saying. I've tried doing the fix I proposed above with no success. -- ] <sup>]</sup> 06:16, 6 March 2007 (UTC)

::I've discovered a problem my proposed fix won't solve. What are we to do with an article like ], which is maintained by the highway departments of god knows how many counties? A list like that shouldn't be in the infobox, but the infobox already uses '''state=NJ County''' with a redlink for ] ready and waiting. -- ] <sup>]</sup> 06:58, 6 March 2007 (UTC)

Okay, the template is fixed, just put <nowiki>maint=]</nowiki>, no need for the creation of a bunch of subpages. --] 20:21, 6 March 2007 (UTC)

== 3dis and browse boxes ==

Since most 3dis are intra-state, I'm going to start moving multi-state 3di browse boxes into the infobox (there's 2 at most for any given 3di). They're essentially treated like state roads, which all use Infobox Road or a variation thereof, and the browse info won't be too big for the section. See ]. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 22:18, 5 March 2007 (UTC)

:I disagree. For 3dis that are intra-state, it's fine; a number of state WPs do this anyway. But having two browse rows in the infobox the way that version of I-280 just looks awkward. -- ] <sup>]</sup> 22:21, 5 March 2007 (UTC)

::Having to scroll down to the end of the page (or hit "End", alternatively) every time I want to move on seems pretty awkward too, though. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 22:23, 5 March 2007 (UTC)

:::Interesting, your edit summary said something like "consistency of sorts", but your comment doesn't have much to do with consistency.
:::I think what would be consistent would be for all single-state (whether state, US, or Interstate) routes to have it in the infobox, and multi-state routes to have it at the bottom. To me, the issue with having it the way you currently do on I-280 is that it's not clear what those links are. I know it seems like common sense, but it's missing that header, (i.e. the line that says ''']''' on ]. For multi-state routes, having it at the bottom in a box that's labeled "browse numbered routes" takes care of that. -- ] <sup>]</sup> 22:36, 5 March 2007 (UTC)

::::It depends what context - I'm thinking about "position on the page" and you're thinking about "easily identifiable as a state-level browse". The multi-state ones, with 10+ states, I can understand leaving off the top of the page. But I would go so far as to edit {{tl|Infobox road}} so it says "Browse state routes" in a row above the previous and next routes (for multistate 3dis only) if the browse parameter is not empty.
::::I'd even be willing to wager that that particular edit isn't all that difficult, but it would take more time to explain why than it's worth. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 00:24, 6 March 2007 (UTC)

:::::Agreed. There should be a way ''inside'' the browse parameter to include a header row like that (in other words, without editing any templates). It might be worth playing in a sandbox. If it looks okay, I'd be down with it.
:::::Keep in mind that I'm only one person though, and right now consensus is to put browsing on the bottom for multi-state routes (no matter how few "multi" is). -- ] <sup>]</sup> 01:05, 6 March 2007 (UTC)
::::::I don't think even that's necessary (explanation referred above follows, I ran a mile in the intervening time); the browse parameter isn't used for multiple-state 2di interstates, and it isn't used for any intrastate interstates. This leaves multistate 3di interstates, of which the entire set spans 2 states at most, except for I-275 right now and I-355 (possibly) in the future. So that's adding 2 rows 99.9% of the time, and 3 rows once. I'll try it out and see how it works... there's always the ability to revert. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 01:47, 6 March 2007 (UTC)
↓

Of course, the fact I need a piece of paper and an ] to weed through the browse structure might mean this'll take some time... &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 01:57, 6 March 2007 (UTC)

I put two browses in the infobox on ] a ways back with header rows. --] 02:43, 6 March 2007 (UTC)

:Looks like problem solved to me. -- ] <sup>]</sup> 04:47, 6 March 2007 (UTC)

::It's not a bad stylistic solution, but it's using two different ways to show the browse boxes; previous_road/previous_type/next_type/next_route, and browse. This is fine because it's the infobox for state highways of Texas, but for Interstates it's not going to work because we don't assign states to Interstate infoboxes.
::However, it should theoretically be possible to manually force a row into the browse box. But for whatever reason (I'm still thinking about it) it doesn't work that way. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 13:15, 6 March 2007 (UTC)
:::Who says we don't have state browse boxes in interstate infoboxes? See ]. --] 16:45, 6 March 2007 (UTC)
::::Hmm. That's got potential. It looks like it depends on creating something similar to {{tl|Infobox TX State Highway/Interstatebrowse}} for the states affected by multistate 3dis... &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 21:25, 6 March 2007 (UTC)
::::All right, I made it work. For people who like blazing trails, see the Texas version, or the Illinois version under the Infobox Road template (only 49 states to go...) -- {{tl|Infobox road/IL browse2}} and possibly associated templates {{tl|Infobox road/IL list link}} and {{tl|Infobox road/browse no route}}. On a related note, editing this thing so closely resembles ] it's not even funny. :-) &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 22:02, 6 March 2007 (UTC)

== IRC and this project ==

:''Refactored to ].''

== Sorting categories at the Commons? ==

I've been playing with the different road categories at the Commons, and I think I may have a way to make them little more organized and presentable to people coming in from the new Commons links. How about sorting them so the shield comes first, then a map of the route, then all photos of the route sorted roughly west-east/south-north, then all other miscellaneous media after that? (See ] for an example.) This would make it easier for the viewer to get an idea of the sights along the route in order, and make it easier to determine where along the route a picture was taken. ] 18:00, 6 March 2007 (UTC)

I've got a separate question about moving images from here to Commons... How does one go about actually doing this? Is it enough to just upload a new version with a {{tl|pd-username-en}} tag? Or do we have to actually transwiki the image pages here? -- ] <sup>]</sup> 07:49, 7 March 2007 (UTC)

:Yeah, it is pretty simple, just upload the image to the commons, then place {{tl|nowcommons}} on the image here and that's it, an admin will make there way to the image here and delete it eventually. --] 15:07, 7 March 2007 (UTC)

== Our own peer review section? ==

I've noticed that enough articles coming out of this project and various subprojects are heading to peer review and/or GA noms.

However, the community-at-large seems to have some difficulty with some of these road articles (see ]) due to unfamiliarity with the subject.

Perhaps we could follow the example of so many other projects and have a peer review section of our own? We wouldn't be the first transportation-related project to do so (there's already ]). I've found peer reviews by people specializing in a subject, particularly one on which so many people are doing so much good work, to be more informed and helpful than ones that come from the community as a whole. Plus it would reduce the backlog on peer review a little bit.

Anyone else? ] 18:04, 7 March 2007 (UTC)
:I'm game with something like this. I'll create the page ASAP. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 18:24, 7 March 2007 (UTC)
Page created at ], as this has to do with all highways/roads. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 22:03, 7 March 2007 (UTC)
:This is probably a good idea, but it's probably important that we do some regular peer review as well. Otherwise, we'll think an article is perfect just because it meets all of our standards, only to have those standards questioned later on because they don't meet Misplaced Pages standards, like at ]. -- ] <sup>]</sup> 23:38, 7 March 2007 (UTC)

::Maybe a tiered process will work, where articles are sent first to the Highways peer review and then, once those issues have been addressed, to the normal peer review. --] <sup>] - ]</sup> 23:42, 7 March 2007 (UTC)

:::Excellent plan. -- ] <sup>]</sup> 23:45, 7 March 2007 (UTC)

== AFD for List of highways numbered 888 ==

See ]. The list consists of three items that are all red links. People familiar with the roads might want to create reasonable stub articles to remove the red links. --] | ] 21:07, 9 March 2007 (UTC)
:Due to comments not related to the actual AFD nom and more in the direction of naming conventions, a meeting will be called on IRC. The date of this meeting has yet to be determined. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 23:23, 12 March 2007 (UTC)
::The meeting has been tentatively scheduled for this Friday at 9:30 PM EDT (6:30 PM PDT). An alternate date has been tentatively set for this Saturday at the same time. Please post here with any concerns or comments. --] <sup>] - ]</sup> 05:15, 13 March 2007 (UTC)
:::Is there a reason it has to be Friday or Saturday night? Nothing against Misplaced Pages or anything, but I rarely have it my weekend evening plans. Not to mention the NCAA tourney is on this weekend, so I won't make it to the meeting, I will discuss the issue on the wiki side. --] 13:38, 13 March 2007 (UTC)
::::Most of us are busy the other nights. If enough people can't make it we could consider holding duplicate sessions. --''']''' (] - ]) 04:07, 14 March 2007 (UTC)

:::::All the more reason to hold the main discussion on-wiki. -- ] <sup>]</sup> 04:25, 14 March 2007 (UTC)
::::::All the major discussions from now on will be held on IRC. You are always welcome to join. IRC supports Windows, Mac, and Linux. --''']''' (] - ]) 04:40, 14 March 2007 (UTC)
::::::If we actually had time to devote to discussions, then I could care less where discussions are held. But we have more important issues to take care of, like a dozen inactive projects, countless stub articles that are a "random article" click away from AFD, etc., and any wiki time spent solely on discussions isn't fixing either of the two. --] <sup>] - ]</sup> 04:48, 14 March 2007 (UTC)

:::::::I apologize for my snide remark. This is certainly one the cases where an IRC discussion is fine. We've all weighed in at the AfD, and it's pretty clear that some sort of change is in order. If the "select few" want to discuss it on IRC to decide whether the naming convention is going to by ], ], or even ] that was proposed recently, I couldn't care less.
:::::::But no, Rschen. All '''minor''' discussion can be held on IRC. All '''major''' discussion must be held on the wiki. That's what ''everyone'' save the three of you said on ]. -- ] <sup>]</sup> 05:22, 14 March 2007 (UTC)

:::::::I don't really see how it takes any more time to discuss here rather than IRC, the discussion itself may take longer, but it doesn't take any longer from an individuals viewpoint. It's not like you post a reply and then sit there refreshing the screen until someone replies, you go edit something else, check your watchlist from time to time, go back if there has been a change. --] 14:00, 14 March 2007 (UTC)

:(indent reset) Some of us have lives outside of this. I can't see how any issue is so urgent that it would take too much time to debate it here over the span of a day or two. --] 16:35, 14 March 2007 (UTC)

== New archival bot ==

Due to the loss of Werdnabot, we are switching to ] so that automatic archiving continues. Any projects still with Werdnabot code are encouraged to go to ] and request archival. --] <sup>] - ]</sup> 21:07, 11 March 2007 (UTC)

== Another question about the new maint parameter ==

Now that we've gotten all the kinks out, there's still one more question that's left unanswered. Just how much information are we planning on including there. For example, ] is maintained by:
*] for the westernmost 3 miles (more than just the bridge approach)
*] for most of the highway
*] on the Newark Bay Extension
*] on the Holland Tunnel approaches
How many of those should be included in the infobox? All of them? Just the DOT and the Turnpike Authority? The Bridge Commission, but not the Port Authority? -- ] <sup>]</sup> 17:06, 12 March 2007 (UTC)
:Include all of them. See ] for two, but generally it's the same idea. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 19:37, 12 March 2007 (UTC)
::Okay, I've already included two on several other New Jersey routes; I was just checking whether all four of these were worthy of inclusion. -- ] <sup>]</sup> 20:29, 12 March 2007 (UTC)

== Ridge Route ==

I have rewritten and expanded ]. Before I take it to peer review, can I have some advice and comments? Thank you. --] 22:08, 15 March 2007 (UTC)

:OK, I've taken it to ]. --] 02:54, 16 March 2007 (UTC)

== States that don't have a subproject yet ==

''The following is copied from ]. The discussion started when it was proposed to create a Louisiana WikiProject, and I thought, since there's not demand for it yet, to create a single general state highway WikiProject for all the states that don't have them yet. I didn't mean for the discussion to take off quite yet, but it did, so I copied it here. -- ] <sup>]</sup> 02:45, 16 March 2007 (UTC)''

:::Rather than creating a Louisiana WikiProject, I was thinking it might be a good idea to create a WikiProject for ''all'' the state highways that don't have their own. That way, we can standardize everything in the meantime while we wait for demand to increase for a separate wikiproject. I'll probably propose it on WT:USRD once I finish the LA shield images and the NJ infoboxes. -- ] <sup>]</sup> 19:31, 15 March 2007 (UTC)
::::Then what is USRD for? As stated on the project page, it explicitly states "To some extent, standardizing the state highway articles for which a WP does not exist yet." USRD already does just that. We do not need the new WikiProject. If you guys do propose it, be prepared to be shot down. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font></sup> 02:07, 16 March 2007 (UTC)
:::::Then to what extent do we need any state WikiProject? How does ] provide any guidelines for creating state highway articles the way ] does? -- ] <sup>]</sup> 02:16, 16 March 2007 (UTC)
::::::IMHO, state projects that are currently inactive shouldn't exist as standalone projects. USRD does provide a structure; however, it is through the subproject template and not the main project page. There's nothing stopping anyone from copying the structure from the template to the project page, though. --] <sup>] - ]</sup> 02:30, 16 March 2007 (UTC)
:::::::Yeah, to further explain, here is an excerpt from an IRC conversation:
<pre width=100%>
TwinsMetsFan: since every project should follow the subproject template, why not make a structure on USRD and then reserve the state pages for tweaks to that structure?
vishwin60: dunno
vishwin60: every project is different
vishwin60: especially MD
TwinsMetsFan: that's why if we really want to have consistency, and shut the others up at the same time, we should put a skeleton up
TwinsMetsFan: and let states warp it however they want
TwinsMetsFan: within reason
vishwin60: good idea
vishwin60: that would emphasize the statement "To some extent, standardizing the state highway articles for which a WP does not exist yet."
TwinsMetsFan: exactly
TwinsMetsFan: USRD is no longer a shell parent - we need to emphasize that
vishwin60: true
TwinsMetsFan: we are on the verge of massive changes, and all that remains is for someone to budge or say something before i spring it on them
TwinsMetsFan: after all, imho, the line between "consensus" and "be bold" is becoming very blurry
vishwin60: oh yeah, from very recent discussions
TwinsMetsFan: right
TwinsMetsFan: between people who read policies like the Bible and others who want to discuss adding a period to the end of a sentence, consensus and being bold is not matching up
TwinsMetsFan: the policy freaks don't have consensus but they do it anyway
TwinsMetsFan: the discussion lovers inhibit boldness by demanding consensus
vishwin60: so then IAR could be invoked???
TwinsMetsFan: based on everything we presented in the newsletter last week, we're almost to that point
vishwin60: ignoring them?
TwinsMetsFan: no, something has to be done, and if it means ignoring all rules, then so be it
TwinsMetsFan: If the rules prevent you from improving or MAINTAINING Misplaced Pages, ignore them (emphasis mine)
vishwin60: that's definite and indefinite
TwinsMetsFan: right, but i think it applies in the USRD structure case
TwinsMetsFan: heh, to answer North's second question, may as well use the idea i presented up above
TwinsMetsFan: with the flexible structure
TwinsMetsFan: er, "flexible" structure
</pre>
Hope that helps. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font></sup> 02:33, 16 March 2007 (UTC)

:If ] can serve as this proposed state highways project, I'm all for that. In it's current state, I don't see that, but it's certainly possible that we could tweak it so it could.
:Essentially, yes, that Subproject Template would work, and should be moved somewhere more easily accessible so that (for ex.) Louisiana editors can easily find and refer to it, even though there's not a separate Louisiana WikiProject and guideline. If this is no longer just a shell parent, the project page should probably be cleaned up quite a bit, as this is the first I've heard of this. -- ] <sup>]</sup> 02:51, 16 March 2007 (UTC)

There are differences between states and how their DOTs do things, so it makes sense to have variants in the "rules". --] 02:56, 16 March 2007 (UTC)

Changes have been made as detailed above. --] <sup>] - ]</sup> 21:20, 16 March 2007 (UTC)

IMHO USRD should have a basic structure, but should not hinder the creation of subprojects (as long as there are enough users of course. ) But let's discuss this tonight at meeting. --''']''' (] - ]) 21:54, 16 March 2007 (UTC)

:The project page looks good so far. -- ] <sup>]</sup> 06:21, 17 March 2007 (UTC)

== March 16 meeting recap ==

Here's a quick overview of the topics discussed during the ].

*Consensus advocated status quo on the disambiguation page naming convention.
*The proposal to demote inactive/struggling WikiProjects to task forces of USRD was introduced and unanimously supported. Kentucky and Utah will be demoted to task forces, with another three projects at risk of being downgraded as well. Projects that are demoted can be re-promoted at a later date if the state of the project improves. See ].
*The Illinois routebox was converted to use Infobox road. The browsing for some infoboxes now needs repairing.
*Recent changes to the USRD project page were supported.

For the complete log, see ]. --] <sup>] - ]</sup> 07:12, 17 March 2007 (UTC)

:Why were none of the proposals from the AfD for List of highways brought up during the meeting? The only options mentioned were Route X, Highway X, etc... which were all stated as not viable options during the AfD. I still stand firm that the word list needs to be taken out, they aren't lists, they are dab pages. I still don't understand how "Highways numbered X" doesn't work, it was never addressed in the meeting. --] 07:56, 17 March 2007 (UTC)

:Also, there was talk about the Texas highways and grouping them, but I was having trouble following the conversation. First off, What is INNA?? I would be glad to address the problem if I knew what the problem was. --] 08:12, 17 March 2007 (UTC)

::The reason no other proposals were brought up was because there was a great deal of support for the current naming convention ("List of highways numbered X"). INNA is the ], which sets standards for infoboxes and browsing across USRD. The portion directly related to the Texas discussion last night is ], which sets guidelines for the browsing order. --] <sup>] - ]</sup> 15:22, 17 March 2007 (UTC)

:::The problem with Texas browsing is that it treats Interstate and U.S. highways as entirely separate things. Ideally, the browsing on ] would go from SH 8 to IH 10, the browsing on ] would go from SH 9 to SH 10, and the browsing on ] would go from IH 10 to SH 11.
:::I think all the Loops, spurs, Farm to Market roads, etc. should stay as is, though. -- ] <sup>]</sup> 19:30, 17 March 2007 (UTC)

::::Agreed 100% on both points. --] <sup>] - ]</sup> 19:38, 17 March 2007 (UTC)

::::But Interstates and U.S. Highways are entirely seperate things, we do have two seperate projects for them after all. It just seemed the most logical to seperate them. How does one browse just the interstates of Texas? It doesn't make any sense to me to combine them all, can you point me to the discussion on the topic? --] 00:34, 18 March 2007 (UTC)
:::::It's been the status quo for a long time, they need to be combined, ever since the days of ] in 2005. --''']''' (] - ]) 00:52, 18 March 2007 (UTC)
::::::So regardless if it makes any sense, just because it was done that way by California it should be done every where else? Sorry, but ] does not fall under ]. Also, California doesn't have duplicates, in Texas, you can have a state highway and an interstate with the same number. I will buy off on combining Interstate and U.S. Highways, but State Highways will remain seperate. --] 02:29, 18 March 2007 (UTC)
:::::::There are other states, like Illinois, Indiana, Pennsylvania, and New York that duplicate routes as well. Under ], they will be combined, and that policy is not to be changed unless a suttle discussion is enacted. Projects under USRD follow policies, and ] is no exception. ''']''' <sup><font color="black">]</font> · <font color="blue">]</font> · <font color="green">]</font></sup> 02:41, 18 March 2007 (UTC)
::::::::INNA has only existed 2 months, TXSH has been doing their browse this way for much longer. Until someone directs me to a loction where this has been discussed at, then TXSH will continue to browse this way. You can't make up a guideline without a discussion, show me the discussion. --] 03:19, 18 March 2007 (UTC)
:::::::::First of all, you do not have the authority to arbitrarily declare that TX will not follow the guidelines set in INNA. Furthermore, you can look up the discussion yourself. --''']''' (] - ]) 03:23, 18 March 2007 (UTC)

::::::::::I'm not touching this with a ten and half foot pole, only to say that it got inappropriately ugly ''really'' quickly. -- ] <sup>]</sup> 03:57, 18 March 2007 (UTC)
::::::::::The main thing is, Holderca1, you work it out with INNA. You don't just declare that your project will no longer be subject to ]. Last I heard, Texas roads were U.S. roads. --''']''' (] - ]) 04:02, 18 March 2007 (UTC)
:::::::::::Just so you know, my comment was directed more towards you, Rschen, than Holderca. ] doesn't really scream consensus to me, despite what the section header says. Thus, I think Texas should be allowed to keep its browsing system until there's a clear consensus to apply INNA unilaterally on all the states.
:::::::::::I think there is some justification to doing things the INNA way in states like New Jersey and California that go out of their way to not assign the same number to two classes of highways, and to doing things the "Texas" way for states that do. -- ] <sup>]</sup> 06:46, 18 March 2007 (UTC)

::::See, this was the rationale behind the now-no-longer-in-existence Illinois Route Box... it's a list of Illinois Routes, not Every Route In Illinois. If it was another route (and in this case, I did lump together U.S. Routes and Interstate Routes), that's what See also was for. In case you managed to get U.S. 24 and I-24 confused or something silly. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 04:58, 18 March 2007 (UTC)
:::::IL is somewhat odd there, since US and I routes are allowed to be in the same state. --''']''' (] - ]) 20:36, 18 March 2007 (UTC)

I am just failing to see the point of having separate subprojects if everything has to follow what US Roads says to the letter. And no, not all Texas roads are US Roads, they are roads that are in the US, but they are not US Roads. If you are wondering why the number of contributors for this project is suffering, here is where you need to look. Rschen, neither you, nor anyone else ] this wikiproject, and telling someone they don’t have the “authority” to do something is not going to get people to rush back to help. Also, see your comment here: , “actually, if CA even decides to follow the ELG.” So, let me get this straight, everything here is optional for CA, but mandatory for everyone else? I had always thought that separate wikiprojects existed because every state’s highway system is different, with this being a perfect example. It makes sense for CA to browse this way, because CA treats interstate, U.S., and state highways the same and this is indicated by the way they number their highways. Texas doesn’t do it this way, this from the TXDOT web site:

State Highway System (SHS) The highways in the state built and maintained by TxDOT.
Each category of highways is its own system within the State Highway System, i.e.
Farm to Market Road system, State Highway Loop system, etc.

Getting back to my issues with this project as a whole, I think we need to change how we go about getting a consensus on things around here. One editor saying, "this looks good to me" and another saying "yeah, me too" is not a discussion, nor is it consensus. We should do it by state, a consensus (say 2/3) of the active state wikiprojects is required to pass a guideline, policy, etc… This will prevent a mass of editors from a particular state and influencing the overall project. This project has been broken for a long while, even before ], and if it is the hope to get the support back up, then changes need to be made on how this project is ran. --] 09:56, 18 March 2007 (UTC)

:(ec) I see your point, but considering the current state of U.S. Roads as a whole (which is not good), sometimes "be bold" has to trump "consensus". As for Texas being excluded from INNA...Washington is somewhat excluded since the SR numbering is derivative (SR 102 coming from US 101 and such), so it's not as if there can't be exceptions. Even so, their "derivative" browsing (that is, the browsing of the base routes) follows INNA as far as I've seen.
:Ample time was given to discuss everything that has been included as part of INNA. The existence of the page was not made a secret; in fact, it was well advertised, both in the newsletter and on this page. Since no one commented against INNA, they were made guidelines through ]. The place to discuss exemption would be at ]. I'm willing to listen, but the bottom line is that some standard has to be in place to fall back on. The same applies for the new structure on the USRD page. Why is it necessary? Simple; so people don't start WikiProjects with no support simply to establish a standard. Too many people have done that already and the result is that there are inactive projects with no editors. Most of the Canada road WPs have been declared inactive; two of ours have become task forces and three more are on their way there.
:The point of separate, state-level subprojects is to increase collaboration among editors with a similar focus, that being editing state highways in that state. These editors may also discover a flaw in the USRD structure, and can modify their structure to match. Bottom line, I'm not against WikiProjects for every state - I'm against WikiProjects that will have no support and no dedicated editors.
:The discussion that occurred above could have been done a bit more civil; that I admit. But the reality is that tensions are going to run high here right now because of the sorry state of USRD collectively. The reason standards are being established on the USRD level is primarily for the states that have no WikiProject and have no hope of getting one anytime soon. Yes, these standards do apply to the subprojects that exist and are already well-established, but we can be more lenient in that department.
:Holderca1, your contributions to Misplaced Pages are far too important to quit over something like this. My suggestion would be to bring the browsing issue up at ] and we'll take care of it there. --] <sup>] - ]</sup> 16:59, 18 March 2007 (UTC)

Yay, politics. This is why I hardly even do anything on here anymore. Too many people are trying to create too much control over projects that they assert they have jurisdiction over. It's all a bunch of crap. And as far as the demotion period, that's just stupid. MISH just finished creating articles for all the state highways a month or two ago, so of course a bunch of them are stubs. They'll get worked on eventually, but the gavel wielding and contract manifestations just make it more of a hostile environment in which to work. I think to the detriment of Misplaced Pages as a whole, not just the roads project. '''<font color="#FF0000">S</font>tratosphere''' <sup>(] ])</sup> 16:54, 18 March 2007 (UTC)
:To compare the projects that were demoted to MISH is giving too much credit to the demoted projects. Kentucky and Utah have seen no activity in months, they no longer have any active editors, and key issues (such as the existence of three infoboxes for Kentucky) have been ignored. The reason they were demoted was that at the current rate, they won't be worked on eventually.
:It is not necessarily a demotion "period" - if active editors are not found after the generic to-do list (found at ]) is completed by this project, then it will remain a task force for the foreseeable future, as there'd be no point in making it a non-supported (by editors) WikiProject again. --] <sup>] - ]</sup> 17:22, 18 March 2007 (UTC)
::That may be, but when I make edits anymore I don't even think about the U.S. Roads project. I'm here to contribute useful information to articles, not wade through wikiprojects to find pages that list standards for every freaking thing we can nitpick about. The politics is getting thick and the reason I starred myself on the active contributors list is because I want to get the newsletter in case another deletion issue comes up that needs shutting down. I understand the need for consistency and standards across certain subjects, but reading the discussion and some other comments, widespread imposition of "consensus by silence" is the wrong way to do it. I agree with a poster above that while the state highway projects are subsets of the USRD project, the sub projects were created to deal with the nuances that deviate from the prevailing national standard. Either way, I'll leave you guys to writing the "standards" and I'll stick to contributing to articles whenever I see fit. '''<font color="#FF0000">S</font>tratosphere''' <sup>(] ])</sup> 18:01, 18 March 2007 (UTC)
::I'll also point out that my counterargument to your "consensus by silence" is the second section on that very same page. The fact that issues are being arisen here, now, indicates that there probably wasn't genuine consensus to begin with. '''<font color="#FF0000">S</font>tratosphere''' <sup>(] ])</sup> 18:03, 18 March 2007 (UTC)
I'll start off by apologizing, I may have failed to keep my ], but it wasn't this isolated instance that set me off, it has been brewing for several weeks. IMHO posting on this talk page about a guideline is not enough, it needs to be posted on all the subproject subpages as well, not everyone involved in the subprojects monitors this talk page, nor are they members of this project. At least during the SRNC, every project was notified and every individual was notified via talk pages. Also, on another issue, why is the juction table recently placed on the project page drastically different than what we discussed at ELG? I understand the difference in the two, but the appearance of the two should basically be the same, just without the exit column. I just don't understand why we need to nitpick every little thing, it just makes it more difficult to keep everything within those standards. I have always believed that if it isn't broken, don't try to fix it. --] 19:33, 18 March 2007 (UTC)
:It took three long hours to post to everyone's page (and taht was before we had more people joining). It is simply not practical to do that again. --''']''' (] - ]) 21:28, 18 March 2007 (UTC)
:INNA was also mentioned prominently in the newsletter, but I see your point. Then again, I wasn't aware that any state used a different browsing system until recently. I'm not following you on the junction table...the design of it is the same as the ELG but without the exit column.
:In terms of the last comment, sure, the Texas WP isn't broken, the New York WP isn't broken, the Michigan WP isn't broken, but there are plenty of WPs that are. Those are the projects that these standards are aimed at. --] <sup>] - ]</sup> 19:43, 18 March 2007 (UTC)
::See the ] article under the Road(s) column, the street names are listed below the numbered route rather than all on the same line, also, I can't remember what we said on colors, but I thought we said no colors. --] 20:02, 18 March 2007 (UTC)
:::The junction table predates the ELG in both the color department and the display of roads. The table began as a junction list contained within '''Template:Routeboxny''', with colors derived from ]. When the decision was made to go to infobox road, the junctions were moved to their own table, designed in a way that no information would be lost. After some discussion (somewhere in ]), it was decided to convert the table into a template. This template then spread to numerous other states and, by request of another editor, I redesigned the template to look similar to the-then fledgling ELG. This is the only reason why the two seem similar, as the junction table was not based on the ELG, nor was the ELG based on the table. For this reason, the items discussed in the ELG discussion have no bearing on the junction table, a point that was agreed to during the ELG discussion. --] <sup>] - ]</sup> 21:25, 18 March 2007 (UTC)
:::I have advocated against colors for a long time, mostly after I figured out what sort of an accessibility problem it poses. Also, I discourage forcing readers to refer to legends, similar to maps created in the Maps Task Force. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 21:04, 18 March 2007 (UTC)

===Getting everyone on the same page===
Let's put the actual issue aside for a while and focus on the basics.
* Firstly (and yes that's a word :)) I apologize if I was uncivil or a bit harried above.
*Secondly, there are simply too many editors and too many projects to keep notifying them of every little change that happens at USRD. Too many of them are inactive too, so it's not worth notifying everyone. That's why we created the ] and the newsletter. Thus, it needs to be your responsibility to participate in discussions and to remain aware. It's just like in high school, teachers have too many students and can't pressure each one about missing assignments, right? It's the student's responsibility to do their work. If you're not aware of discussions that you want to be a part of, then there's nothing we can't do (we can't read your mind and know that you wanted to be a part of that discussion...) I personally believe that we have thus gone above and beyond the call of a WikiProject to keep their members informed (as most projects, to my knowledge, do not have that many mechanisms of keeping their members informed). Another tool you have is your watchlist- a main page you should have on your watchlist is this one. If nothing else, this one. This is where it happens. Even furthermore, we have our own IRC channel. This is one of two that do (the other is hurricanes, I believe). Thus, we can collaborate in real time. Those that are against it, I would advise you to try it out before you simply reject it. On a personal level, I did not want to join IRC. However, after joining it, I would never go back. You never quite get the full picture of things on Wiki.
*Thirdly, ] is not a shell project anymore. Sure, I created it as one. However, that is no longer the case. ] is the head of the U.S. Roads area, and it was also founded before about 75% of the other highway projects (only IH, USH, CASH, CACR, WASH, and KYSH predate this, if I remember correctly). However, even those projects need to follow these guidelines decided here for uniformity across teh board.
*Fourthly, when you have a concern about a policy or guideline, you don't refuse to follow it. You work to change it. For example, you don't just send to ] the policy ] just because you disagree with it. You go to the talk page of ] and work to have it changed. Furthermore, you don't constantly complain about 3RR, for that gets nothing done. You work to change it and cooperate with other people.
*Fifthly, there are no leaders at a highway project. We should never have allowed that from the start. It's just like how administrators have no special privileges in the determination of consensus. I'm strongly considering removing every occurrence of "leader" from every road project... because that is misleading. There are no official "leaders". But then how do you lead? You lead by doing work. You lead by putting in the work and by participating in the consensus discussions. "Leaders" don't get special privileges in discussions. "Leaders" cannot and do not arbitrarily decide to rebel (with or without their project) against a policy just because they do not like it.
*Sixthly, the turnout at the IRC meeting Friday was downright shameful. We got 8 editors, and I commend them for that. However, we have over 100 editors. Assuming there are 100, that means that '''8% of them participated'''. And considering that at least 5% more were complaining about the project's use of IRC and blatantly refusing to join in on the discussions (and then later complaining about not having any say in important issues), that is downright shameful.
*Seventhly, whether you realize it or not, WP:USRD is in deep trouble. Did anyone actually notice the AFD's? We barely squeaked by on a few of those. The whole project is simply in a state of trash right now. Yes, a '''state of trash'''. '''22''' projects out of the 37 that we have are in poor shape. '''That is over 50%'''. We have only 1 FA out of over 10000 articles. That is extremely sad. If this doesn't alarm you, then quite frankly, you should not be a roads editor.
*I'll start with that for now. --''']''' (] - ]) 20:53, 18 March 2007 (UTC)
:*And we're going to combine IH and USH and put them in as part of USRD, right? &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 21:04, 18 March 2007 (UTC)
::*I don't know at this point... but I think that we need to get everyone on the same team before we discuss something that fundamental. --''']''' (] - ]) 21:06, 18 March 2007 (UTC)
::*Now's not the time to discuss that. We have more important issues to settle first. --] <sup>] - ]</sup> 21:10, 18 March 2007 (UTC)

== March 17 request to edit West Virginia's shield ==
I realize that your wikiproject has remained as authentic as possible in its use of state road shields; however, West Virginia's is so plain and uninteresting that it can often be confused with the shields of other states. Therefore, I propose substituting ] with ]. As a West Virginian, I do prefer the design of the latter. Thanks for your consideration. ] 16:00, 17 March 2007 (UTC)

:Ummm, no... This is an encyclopedia... -- ] <sup>]</sup> 19:15, 17 March 2007 (UTC)
:Disagreed. --''']''' (] - ]) 19:18, 17 March 2007 (UTC)
:'''Disagree''' --] 03:21, 18 March 2007 (UTC)
:Not a bad shield though. If numbers look good in it, suggest it to (the DOT of) West Virginia. If they change theirs, we will too. '''--]<sup> ] / ]</sup>''' 05:06, 18 March 2007 (UTC)
:Alternatively, you should be able to use it on userpages and for the wikiproject symbol. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 06:23, 18 March 2007 (UTC)
::Yes, send it to WVDOH. Oklahoma changed their shield for the Centennial, perhaps you can find another reason that WVDOH might want to spend the money on new shields. Or, just send it to so other roadgeeks can see it. —]] 07:44, 18 March 2007 (UTC)
:In case anyone hasn't noticed, the "replacement" image above is neither centered nor a preferred image type. The edges of the shield are cut off and it is a JPEG, where the preferred non-vector format for this case would be PNG. Regardless, this shield is unencyclopedic and should not be used in article space. If you want to use it for your userpage, go ahead, but it does not belong in the WV stub template. --] <sup>] - ]</sup> 17:10, 18 March 2007 (UTC)

Latest revision as of 04:19, 21 December 2024

Centralized discussion for the U.S. Roads WikiProject Shortcut
  • If you would like to discuss the standards for route junction lists, please use WT:RJL,
  • If you would like to request a map, please use WP:USRD/MTF/R,
  • If you would like to request a route marker (shield), please use WP:USRD/S/R,
  • Featured Article candidates, Good Article nominations, and deletion discussions are listed automatically within 24 hours at WP:USRD/AA and
  • For all other comments or concerns, please post below.

Archives: Index, 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · 10 · 11 · 12 · 13 · 14 · 15 · 16 · 17 · 18 · 19 · 20 · 21 · 22 · 23 · 24 · 25
IH: 1 · 2 · 3 · 4 • US: 1 · 2 · 3 • USAT: 1 • USRD/STDS: 1 • USRD/A: 1 • USRD/NT: 1

States: AL: 1 • CA: 1 · 2 · 3 · 4 · 5 · 6 • CT: 1 • FL: 1 · 2 • GA: 1 • IL: 1 · 2 • IN: 1 • IA: 1 • KS: 1 · 2 · 3 • KY: 1 • LA: 1 • MD: 1 · 2 · 3 · 4 · 5 • MA: 1 • MI: 1 · 2 • MN: 1 · 2 • MO: 1 • NV: 1 • NJ: 1 · 2 • NY: 1 · 2 · 3 · 4 · 5 • NC: 1 • OH: 1 • OK: 1 OR: 1 PA: 1 · 2 • RI: 1 • SC: 1 • TN: 1 • TX: 1 · 2 • UT: 1 • VT: 1 • VA: 1 • WA: 1 · 2 • WV: 1 • WI: 1
Search
 
Search
This project page does not require a rating on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:
WikiProject iconU.S. Roads
WikiProject iconThis page is within the scope of the U.S. Roads WikiProject, an attempt to build a comprehensive and detailed guide to state highways and other major roads in the United States. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to the discussion.U.S. RoadsWikipedia:WikiProject U.S. RoadsTemplate:WikiProject U.S. RoadsU.S. road transport
 

Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25

This page has archives. Sections older than 14 days may be automatically archived by Lowercase sigmabot III when more than 2 sections are present.

WikiProject U.S. Roads was featured in a WikiProject Report in the Signpost on May 3, 2010.

AARoads Wiki

Please join us over at the AARoads Wiki. We look forward to seeing you soon! Imzadi 1979 → 20:27, 12 September 2023 (UTC)

I sure hope that this project isn't shutting down. It would be unfortunate for us to cave to the opinions of non-content contributors at an RfC who probably don't even know how to read a map. Bneu2013 (talk) 02:16, 24 September 2023 (UTC)
I've marked the page as per this. 20:59, 23 September 2023 (UTC)
I just want to state for the record that I intend to continue maintenance of Washington articles as well as those I brought up to GA status in other states. I'm going to be contributing to both projects, albeit with less detail for roads articles on here. SounderBruce 04:27, 24 September 2023 (UTC)
In reality there are two more alternative sites we can choose from - Justapedia and Encycla. The former is a Misplaced Pages-like site that forked all contents from here last year and has lenient notability requirements. 5.181.21.208 (talk) 13:30, 27 September 2023 (UTC)

GAR

Categories: