User talk:Detcin/Archive 1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Thanks

Thanks for fulfilling those requests for shields. Just remember to take credit for your work and sign ~~~~. —Fredddie 01:29, 6 April 2010 (UTC)

Some helpful advice

I thought that I could offer you some advice in making junction and exit lists that comply with MOS:RJL. The biggest thing that the lists you've created needs concerns the application of colors. If you're going to use the optional colors in the templates, you must include a text note in the table. A simple "Western end of <blah> concurrency" works great. The colors are great, and I use them all the time in Michigan articles, but the notes are required by the Manual of Style.

A second thing, linking to the county for a location is a bad practice. You get extra links to the same article on the county (overlinking), and that's not the purpose of the location column. The location should be a city, village or township. In states out west that don't have townships, they leave the location blank. You can do this by using |location=&nbsp; which inserts a non-breaking space for the location, producing a blank cell in the table. I know that Indiana has townships, since when I revamped the U.S. Route 131 article, I did a little digging to find that the Indiana section is in York Township in Elkhart County, and that's the location that I used. If you can't find the location, please leave it blank rather than link to the county.

There are additional templates available to make the tables. If you need to add a bridge crossing, there {{jctbridge}}. It works like {{INint}}, but instead of specifying a road and notes, it uses |bridge= to make a cell that spans the road and notes columns with centered text. It also has a |river= parameter to specify the body of water crossed. Interstate 75 in Michigan uses this template for the Mackinac Bridge and International Bridge crossing. (For the Zilwaukee Bridge crossing, since the body of water doesn't contain the county line, I used |location_special=[[Saginaw River]] to denote the river.) I've also used this template for the ends of freeway sections when they don't line up with another junction, like the US 131 article.

There's {{jctexit}}, which works just like {{INint}}, except it has an additional |exit= parameter. Like {{jctint}}, you need to use the |state=IN parameter whenever you specify a county or location so that the template knows the location is in Indiana. If you use the jctexit template, you can enter the exit numbers along the highway, or skip the exit number totally for at-grade junctions. The template that creates the top of the table is {{exittop}}. I use the {{MIexit}} template if a highway has a freeway section. Some highways only have freeway sections because they are concurrent with a freeway. I still use the exit templates for the whole list, and use the posted exit numbers. For an example of this, see M-55 (Michigan highway) (Please note that the list hasn't been mileposted yet.) I recently redid the exit list on the Interstate 94 in Indiana article. All it needs are completed mileposts (using the official source) and that would be a best-practice exit list for you to emulate.

You may notice that the Michigan lists have mileage columns that look different. The templates were switched to use right-aligned numbers so that the decimal points would line up. All of the regular templates have alternate versions: {{jctintr}}, {{jctexitr}}, {{jctbridger}}, with the "r" appended to the end for "right-alignment". Otherwise they work the same as the jctint, jctexit and jctbridge templates. It doesn't matter if you use the "r" variants or not, but you'll need to keep them consistent.

If you have any questions, please ask me. I'm happy to help. Imzadi 1979  20:57, 21 May 2010 (UTC)

US 31 in Indiana

Nice work on the junction list! Imzadi 1979  20:49, 1 June 2010 (UTC)

PRODs

If you think the list article is a better venue for those articles, just merge the content over, and redirect the old article to the list. Don't PROD them. Imzadi 1979  02:24, 16 January 2011 (UTC)

Also, in creating the redirect, you can send the redirect to a specific section of the list. After the article title, place a # and then then section name. That will cause the redirect to point the reader's browser to the specific section, instead of at the top of the list. Also, you should be copying over the rest of the content. SR 113 had a history section that you didn't copy, and that paragraph should be added to the list article's SR 113 section. (Don't use subheadings though because if multiple subheadings in an article have the same name, it can cause problems.) Imzadi 1979  21:17, 17 January 2011 (UTC)
The history was not copied due to the two sections (history and intro) were the same, word for word. See the diff Hers. Detcin (talk) 22:48, 17 January 2011 (UTC)

Notification: changes to "Mark my edits as minor by default" preference

Hello there. This is an automated message to tell you about the gradual phasing out of the preference entitled "Mark all edits minor by default", which you currently have (or very recently had) enabled.

On 13 March 2011, this preference was hidden from the user preferences screen as part of efforts to prevent its accidental misuse (consensus discussion). This had the effect of locking users in to their existing preference, which, in your case, was true. To complete the process, your preference will automatically be changed to false in the next few days. This does not require any intervention on your part and you will still be able to manually mark your edits as being minor in the usual way.

For established users such as yourself there is a workaround available involving custom JavaScript. With the script in place, you can continue with this functionality indefinitely (its use is governed by WP:MINOR). If you have any problems, feel free to drop me a note.

Thank you for your understanding and happy editing :) Editing on behalf of User:Jarry1250, LivingBot (talk) 19:08, 15 March 2011 (UTC)

I have again marked a number of articles regarding Indiana state roads. The articles I marked had been overestimated on the quality, and really need work even to be considered start-class. I have tried to be conservative and allow some to slide where it was a toss-up as to stub or start class. Please be realistic when applying even the Start-class designation. Dawynn (talk) 14:42, 18 April 2011 (UTC)

Please note, that USRD assesses articles differently. I'm in the process of re-assessing these articles back to start-class for USRD, but leaving the Indiana project's assessment alone, since most other project assess based on length where we assess based on structure. Of course being tagged as a stub on the article has no impact on what assessment class USRD applies on the talk page. Stub≠Stub-Class necessarily, any more than we are "required" to assess an article as GA-Class if it was listed as a Good Article. Imzadi 1979  16:43, 18 April 2011 (UTC)

Thanks

Thanks for your work with Illinois Route 122. Bigturtle (talk) 20:02, 12 May 2011 (UTC)

Consider joining us on IRC?

Hey, I have a question on behalf of the roads project. We'd like to invite you on Internet Relay Chat (IRC) in the roads channel (#wikipedia-en-roads) to help work with us more in the project. Considering the fact that we are trying to do the 2011-stub reduction project and the slowly expanding membership at US Roads, we'd love to have you join. Mitch32(Can someone turn on the damn air conditioning?) 21:28, 10 June 2011 (UTC)

It's also a great place to not talk about roads. –Fredddie 21:31, 10 June 2011 (UTC)

This edit of yours removed an entire reference from the article. That isn't necessary, and in fact, the first step to resolving a dead reference shouldn't be removal. Try copying the URL for the dead link and pasting it into the search box at the Wayback Machine to see if there is an archived version. If so, you can add that to the |archiveurl= parameter of the citation template with the date for the archive in the archivedate= parameter. That will prompt the template to add the archival details to the citation, and "resurrect" a dead link. If that fails, try again in 18–24 months, because there is a delay before the Wayback Machine displays webpages. The other option is to find a replacement link to the source and update the citation. The third option is to find a different source to cite the information and replace the whole citation. Sometimes, we can just leave the dead link alone as well, since it's proof that it was once cited. Imzadi 1979  00:23, 28 June 2011 (UTC)


A tag has been placed on Template:Indiana U.S. Highways requesting that it be speedily deleted from Wikipedia. This has been done under section T3 of the criteria for speedy deletion, because it is a deprecated or orphaned template. After seven days, if it is still unused and the speedy deletion tag has not been removed, the template will be deleted.

If the template is intended to be substituted, please feel free to remove the speedy deletion tag and please consider putting a note on the template's page indicating that it is substituted so as to avoid any future mistakes (<noinclude>{{transclusionless}}</noinclude>).

Thanks. Imzadi 1979  19:39, 29 June 2011 (UTC)

US 20 IN GA

Do you plan on working on this? --Rschen7754 19:44, 24 July 2011 (UTC)

junction and exit list templates

I know that you have been using the -r variants of the templates to right-align the milepost information in the table. That's no longer necessary; the main templates have been updated to right-align the milepost by default. In fact, {{jctexit}} and {{exittop}} are no longer needed anymore because they were merged into {{jctint}} and {{jcttop}}. Just like you would use {{jctbridge|exit}} to get the bridge template to work in an exit list, you can use {{jctint|exit}} now in instead of {{jctexit}}. As long as you add |exit to the template names, {{jcttop}}, {{jctint}}, {{jctbridge}}, {{jctco}}, {{jctrestarea}} and {{jcttunnel}} will all work to make an exit list. Just remember though, you have to add the |exit after the template every time in an exit list. If you skip that step at some point, the table will be messed up. Imzadi 1979  02:27, 28 July 2011 (UTC)

I've "retired" the -r variants except {{jctintr}} now, as you probably have seen. {{INint}} will handle your needs in Indiana articles going forward. Imzadi 1979  19:27, 18 August 2011 (UTC)

INint

There's no need to change it to jctint|state=IN... the template exists to be a shortcut and easier to enter. Imzadi 1979  02:37, 18 September 2011 (UTC)

Indiana Toll Road

Please reply at the discussion about the interchange names. WP:BRD, as a method, says that you were bold for making the addition, I reverted that change, and now we are discussing it. Imzadi 1979  22:47, 20 September 2011 (UTC)

Congratulations!

The WikiProject U.S. Roads Contributor Barnstar
You got the 2011th stub in the 2011 USRD stub drive, West Virginia Route 622! --Rschen7754 02:40, 23 December 2011 (UTC)

USRD WikiProject Newsletter, Winter 2012

Volume 5, Issue 1 • Winter 2011 • About the Newsletter
This edition is going out to all USRD WikiProject members (current, former, or potential) in addition to other subscribers as part of a roll call to update the participants list. Anyone that would like to continue to receive this newsletter in the future needs to update the subscription list if they are not already subscribed.
Departments
Features
State and national updates
ArchivesNewsroomFull IssueShortcut: WP:USRD/NEWS
Imzadi 1979  22:00, 4 February 2012 (UTC)