User talk:DeFaultRyan/Archives/2008/July
This is an archive of past discussions about User:DeFaultRyan. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Hey, thanks for the fix on the termini. I was looking at the map funny, it was soo zoomed in I lost my since of direction. Thanks! --Admrb♉ltz (t • c • log) 19:41, 11 July 2008 (UTC)
- Not a problem at all. I'm in the area at least every week, and it just sounded a little funny to me. Funny that the official Weber county declaration for the parkway goofed up and mixed up the termini themselves. DeFaultRyan (talk) 20:56, 11 July 2008 (UTC)
When creating new articles...
Hey, Ryan (if I can call you that). Just a tip when creating new articles on Utah state routes, if that's alright. First, when linking over cities, you don't have to say Salt Lake City, Utah. Instead, pipe the link so it reads Salt Lake City. One easy way to do this is the pipe trick. For example, entering [[Salt Lake City, Utah|]] will read Salt Lake City.
Also, the junction list shouldn't have a reference in the header (like on SR-108). It's some sort of Manual of Style violation. Instead, make sure the links are in the box itself, like on (SR-45). Above all, take this advice lightly, I'm just giving you what pretty much every article does in terms of style. Regards, CL — 19:32, 12 July 2008 (UTC)
- Thanks for the help. I had been putting the reference in the header because it didn't see how to put the reference in the top of the table using {{Jcttop}}. Maybe we could get a couple of parameters added to it... DeFaultRyan (talk) 15:55, 13 July 2008 (UTC)
- I have no idea how to deal with templates, unfortunately. But you can put the refs in the box by copying and pasting the code from a box that contains a ref (like the one in SR-45) and modifying the refs as needed. CL — 18:58, 14 July 2008 (UTC)
- Actually, I just noticed that the {{Jcttop}} template has a length_ref parameter that will put a reference in the length column, which is just what I wanted (I updated Utah State Route 108 to use it - pretty slick). Perhaps, based off of that, we could get another reference parameter added to deal with referencing the location column. DeFaultRyan (talk) 19:47, 14 July 2008 (UTC)
- Wow, I had no idea. I know someone in USRD created the jct template, if we could have them do that that would be great. You learn something new every day . . . CL — 20:28, 14 July 2008 (UTC)
- Done. I added the parameter. It's called location_ref, and I used it on Utah State Route 42.
US-89 category on SR-38
In this edit you removed the category, but US-89 did in fact use SR-38 (and part of SR-30) from 1938 until the mid-1950s (it's on [1] but not on a 1956 map). I intend to expand the history of that article (and SR-106) at some point. --NE2 16:01, 17 July 2008 (UTC)
- OK, my bad. I was looking for it, and couldn't find any reference to US-89 anywhere, so I thought it must be in error. Sorry. DeFaultRyan (talk) 18:52, 17 July 2008 (UTC)
SR-78
Hey. Thanks for creating those articles on the minor state routes, I never got around to it and I lost interest in it, so I decided to be rather lazy and make a note of it on the to-do list. Anyway, in the termini in the infobox in SR-78, you can go ahead and put I-15 in there (besides, it's some sort of "violation" of the Manual of Style to but text before the shield) because the connection to the railroad is more of a technicality than anything (the legal definition even says "From Route 15..."), but that technicality should still be listed in the major junctions list, as you've already done. Hope this helps - CL — 05:23, 26 July 2008 (UTC)
- 'Nother thing, SR-76 ends at I-70 (even the road itself, it doesn't continue past then), and UDOT lists the interchange beginning at 0.000 (at least I think so), so in this case I don't think the cattle guard is worth mentioning. Feel free to disagree by the way, we're all new here and I'm guessing most of what I'm saying isn't a rigid form of consensus. Happy editing. CL — 05:44, 26 July 2008 (UTC)
- Thanks for the tips. The only reason I listed it the way I did, is that the road doesn't actually make it all the way to the I-70 interchange. It ends at the cattle guard just short of it on the south side. The junction itself isn't listed on the highway reference. If you check out Google Maps (http://maps.google.com/?ie=UTF8&ll=38.756786,-111.424853&spn=0.003196,0.00751&t=h&z=17), you can even see where the cattle guard is, just short of the eastbound on and off ramps. The Google Maps data is wrong, in that SR-76 doesn't continue north to cross under the freeway - it ends at that little dark strip (the cattle guard) south of the ramps. Technically, the route doesn't hit I-70, which explains my choice of wording. However, for all intents and purposes, it basically connects to the I-70 interchange, which fits your change. I'm OK either way, because I don't know how much of an anal-retentive approach to details we take here... DeFaultRyan (talk) 14:51, 28 July 2008 (UTC)
- Ah, you show just how new I still am to Wikipedia (or at least the whole roads thing). I didn't realize that SR-76 ends just short of the on-ramps...however, we might as well keep the western terminus at I-70, as it makes no sense that UDOT doesn't maintain the remainder of that road (it ends right at the westbound ramps). That's just my opinion though - CL — 21:21, 28 July 2008 (UTC)
- The frontage road that SR-76 is part of was removed from the state highway system when I-70 was completed. It was readded a few years later, but the part within I-70's right-of-way was already a state highway, so UDOT didn't bother transferring it to SR-76. (This is original research, but almost certainly correct.) --NE2 19:01, 29 July 2008 (UTC)
- Ah, you show just how new I still am to Wikipedia (or at least the whole roads thing). I didn't realize that SR-76 ends just short of the on-ramps...however, we might as well keep the western terminus at I-70, as it makes no sense that UDOT doesn't maintain the remainder of that road (it ends right at the westbound ramps). That's just my opinion though - CL — 21:21, 28 July 2008 (UTC)
- Thanks for the tips. The only reason I listed it the way I did, is that the road doesn't actually make it all the way to the I-70 interchange. It ends at the cattle guard just short of it on the south side. The junction itself isn't listed on the highway reference. If you check out Google Maps (http://maps.google.com/?ie=UTF8&ll=38.756786,-111.424853&spn=0.003196,0.00751&t=h&z=17), you can even see where the cattle guard is, just short of the eastbound on and off ramps. The Google Maps data is wrong, in that SR-76 doesn't continue north to cross under the freeway - it ends at that little dark strip (the cattle guard) south of the ramps. Technically, the route doesn't hit I-70, which explains my choice of wording. However, for all intents and purposes, it basically connects to the I-70 interchange, which fits your change. I'm OK either way, because I don't know how much of an anal-retentive approach to details we take here... DeFaultRyan (talk) 14:51, 28 July 2008 (UTC)
Road infobox
Hey Ryan, I'm notifying everyone at UTSH of the fact that I've modified the road infobox to link over to List of numbered highways in Utah. Is everything okay with the change? CL — 06:33, 29 July 2008 (UTC)
- I noticed that the main link (State highways in Utah) always points to state routes, even when the infobox is looking at a US highway or interstate in Utah. For example, US-6 in Utah - the infobox still links back to State highways in Utah. Is there a way to dynamically change that to link to the correct category? (Also posted to the template's talk page) DeFaultRyan (talk) 18:43, 29 July 2008 (UTC)
- NE2 made that final infobox change. He left the link to "State highways in Utah" (notice it doesn't link to "List of state highways in Utah) because one day, there might be an article on it such as the one for Washington detailing the history and what-have-you of the state route system. CL — 18:50, 29 July 2008 (UTC)
Utah editors
That column of the table has not been updated in quite some time, primarily because the USRD participants page is a total mess (halfway through a transition to a new style). Also, it's not a particularly useful piece of information, since it doesn't do you much good to know how many editors there are if you don't know who they are to contact them, plus there's no accounting for how active an editor might be. I hope that answers your question, and I apologize for any confusion. -- Kéiryn (talk) 04:20, 30 July 2008 (UTC)