Wikipedia talk:WikiProject U.S. Roads/Washington/Archive 1

Route maps
I was quite happy to find this WikiProject. I will start adding relevant content from my Washington State Highways site, which I haven't worked on in years because it got to be a pain to manage. Better that it should live on as a collaborative effort than continue to be neglected.

One thing that I've been doing as part of that effort is creating maps showing the route of each state highway, like this one for SR20. (The interstates are also shown for context.) Unless there are objections, I'd like to modify the routebox template to show a route map for each Washington highway, approximately the size of the route shield and perhaps located between "Highway in Washington" and the RCW statute. This would of course be a slight departure from the routebox format used for other states' highways, like California's, but maybe if enough people think it's a good idea it'll be adopted for other states as well.

I use Adobe Illustrator to create the maps and should be able to generate maps pretty quickly for all of the Washington highways that currently have articles. Please also chime in with any comments or questions about the colors, format, line thickness, etc. --PHenry 23:55, 3 October 2005 (UTC)
 * We'd love to have the maps, but I'm not quite sure if they should go in the routebox due to size. Maybe at the top or bottom of the article? I'd have to see how it looks though to make sure the routebox isn't too big. --Rschen7754 (talk - contribs - count) 02:02, 4 October 2005 (UTC)


 * The routebox is 225 pixels wide, so I was thinking that maybe 180-200 pixels wide for the map would be appropriate (example). At that size it would be about as tall as the route shield is, and wouldn't cause the routebox to get any wider. --PHenry 02:12, 4 October 2005 (UTC)
 * For routes like Washington State Route 102 is there any way to zoom in on the map? --Rschen7754 (talk - contribs - count) 04:48, 4 October 2005 (UTC)
 * What I typically do for short highways is zoom in on the region to the extent practical, with a locator map in the corner showing the area in relation to the rest of the state. See the SR-520 map for an example (this, too, would appear much smaller in the routebox). My source file is a PDF map from nationalatlas.gov that shows most of the state highways, so it's pretty easy to arbitrarily zoom in on part of the state for a better look. --PHenry 05:34, 4 October 2005 (UTC)

I've uploaded the maps and updated the routebox. I think I've created maps for all the pages that currently use the routebox template, but if I've missed any please let me know. Next I'll create maps for the pages that don't yet use the routebox template, so that when the template gets added to a page its map will be ready to go. If you have a request for a specific highway, leave me a message and I'll make it as soon as I can. --PHenry 19:09, 8 October 2005 (UTC)
 * Thanks... they look great so far! --Rschen7754 (talk - contribs - count) 19:11, 8 October 2005 (UTC)

Love the maps. However, I see that that many have some errors.
 * SR-525, travels too far up on Whidbey Island on the map. The actual route ends just above the point where the Island extends west after the long northward neck.  TEG 20:20, 20 October 2005 (UTC)
 * Fixed it... thanks. --PHenry 23:51, 20 October 2005 (UTC)

About WA-SR Signs
I have been creating SR signs using AppleWorks, and the Road Geeks Fonts (Similar to FHWA) at. TEG 19:07, 31 October 2005 (UTC)

Don't delete me
Don't worry, I'll come back and work on this. I just ran out of time. --Rschen7754 July 5, 2005 20:30 (UTC)

Improvement drive
The article on Transportation is currently nominated on This week's improvement drive. Vote for Transportation there.--Fenice 09:11, 8 August 2005 (UTC)

Title of the WikiProject
I've been thinking (a dangerous thing) and was wondering why this WikiProject is called Washington State Highways. Shouldn't it be Washington State Routes, since State Highways have not existed since the 1970s. I think it might make us look a little more organized to do this, and change the bottom of the route box, because it says Washington State Highways as well. TEG 20:03, 20 October 2005 (UTC)


 * In the law, they're still called highways. --PHenry 02:27, 21 October 2005 (UTC)
 * They're "state highway routes" called "State Route X". --SPUI (talk - don't use sorted stub templates! ) 15:10, 9 March 2006 (UTC)
 * I'd say leave it because the other projects are called the same thing. But it doesn't really matter to me. --Rschen7754 (talk - contribs) 02:32, 21 October 2005 (UTC)

Counties
I think the current milepost format might be improved a bit. The current format was apparently inherited from the California standard, which uses a 2- or 3-letter code to signify each county. This is necessary in the case of California, because mile numbering on California highways starts over in each county--Route 1 has a mile 1 in Sonora County, a mile 1 in Mendocino County, and so on--and the three-letter codes are actually stenciled on each milepost in the state. To copy this county system for Washington highways is, I think, undesirable for three reasons: Check out the SR-20 page to see my idea for a standard that would solve these problems while still providing information about the counties a highway travels through. If everyone hates it, it can certainly be reverted. If people like it, we can make changes to the existing pages as we get to them. --PHenry 02:27, 21 October 2005 (UTC)
 * California has an official list of county abbreviations, but Washington has no such list, to my knowledge. (But please correct me if I'm wrong.)
 * Therefore, any such abbreviations generated for Washington counties are arbitrary, and two different editors working on different pages may unknowingly choose different abbreviations for the same county, causing confusion.
 * Someone familiar with the California postmile system might get the inaccurate impression that Washington uses a similar county-based system for mileage numbering.
 * Looks good, the font is a little small though. What is the code you used? (So that it looks the same on every article) Sorry about the mess... California has become a model for WikiProjects, but the problem it creates is that CA is the exception when it comes to highway standards... --Rschen7754 (talk - contribs) 02:32, 21 October 2005 (UTC)
 * I just created a template for it. The format is:


 * which produces
 * Skagit County
 * It uses font size 1. Font size 2 is the normal text size, which I was afraid would overwhelm the more important information in the routebox. If it does need to be bigger, at least we only need to change it in one place, instead of hundreds of places. --PHenry 19:20, 21 October 2005 (UTC)
 * I like it, but I feel it is more overhead than what we need. I think we should just drop the idea of the county.  All the junctions I've been doing have been based on actual mileage, not county mileage, as it would be nuts to do it any other way in Washington. TEG 14:24, 21 October 2005 (UTC)
 * I agree that the county names are, at best, optional for every state but California. Do you think it will still require too much overhead, with the new template? My preference would be to leave the template in place for people to use if they want to, but not have an expectation that every highway needs to list counties.


 * On a related note, I made another change to SR-20--which I seem to be increasingly using as my own personal guinea pig article--so that the route shields in the mileage list all line up nicely down the center, a la most of the California articles. I think it looks a lot better this way. --PHenry

Portal
I have just created Portal:U.S. Roads. If you have any feedback, please place it under "Portal" at Wikipedia talk:WikiProject U.S. Roads.Rt66lt 03:23, 11 February 2006 (UTC)

SVG maps and shields
You may have noticed that several highway WikiProjects are gradually converting shield graphics to SVG format because SVG graphics scale better to both larger and smaller sizes. I have created a sample route shield and map in SVG for your inspection and, hopefully, approval.

I'm using Adobe Illustrator CS for both images and can create SVG versions of the rest of the graphics fairly easily, though it will take some time to do them all. If you have any feedback for me, post it here. --phh 20:29, 15 March 2006 (UTC)
 * GOOD the GIFs scale like crap, I had to make them 30px in my exit lists to be readable! A dmrb♉ltz (T | C) 21:22, 15 March 2006 (UTC)
 * But if you could upload them to the commons, It would be appreciated :) A dmrb♉ltz (T | C) 21:22, 15 March 2006 (UTC)
 * Great idea. I'll do that. Thanks. --phh 21:50, 15 March 2006 (UTC)
 * SVG is a good idea as we're moving to that across the board. --Rschen7754 (talk - contribs)  23:10, 15 March 2006 (UTC)`

Okay, I've created and uploaded all the SVG route shields (there are over 200 of them!) to the Commons, and swapped them in on the routebox templates and on all the articles I could find that use them. Within the next few days I'll go ahead and list the existing gifs on WP:IfD, so if you find any I missed, just replace "gif" with "svg" in the image name—the rest of the file name is the same as before.

Some of the shields will need to be redone. I used a script to generate the SVG files from the original Illustrator artwork, and it positioned the numerals poorly on some of the shields. The problem seems to mostly affect shields with 2s and 4s in them, although not all of those will need to be fixed. I'll get to it some time soon, after I get a very large amount of sleep.

Maps next… —phh 07:28, 19 March 2006 (UTC)
 * Instead of listing for IFD, tag them for speedy deletion with  A dmrb♉ltz (T | C) 02:18, 21 March 2006 (UTC)
 * Boy, I wish I'd known about that tag before I'd tagged all 200 shields with ! (Actually, the  tag is probably more appropriate anyway, because the new shields aren't pixelwise identical to the old ones.) --phh 16:28, 23 March 2006 (UTC)

I have now replaced the old PNG route maps with SVG maps on every page where I could find them, and modified the routebox template to use the SVG versions. If you find a missing map, or need one for an article you're creating or expanding, post a note here or on my talk page and I'll upload it. (The SVG format also makes it a lot easier for anyone with access to Illustrator, Inkscape, Visio, or a similar application to create maps on their own if they like; I'll post information and instructions on the project page.) --phh 16:35, 23 March 2006 (UTC)

Shrunken infobox
Any comments on User:SPUI/SR 599 vs. Washington State Route 599? Any reason I shouldn't start using the smaller one? --SPUI (talk - don't use sorted stub templates! ) 01:40, 27 March 2006 (UTC)
 * No. There is no consensus. Also, this is simply the continuation of SPUI's edit warring from California. There is much loss of information in your template. --Rschen7754 (talk - contribs)  01:43, 27 March 2006 (UTC)
 * Er... what? Why the hell do you think I asked here? TO GET CONSENSUS THAT YOUR SHIT IS TOO BIG. --SPUI (talk - don't use sorted stub templates! ) 01:45, 27 March 2006 (UTC)


 * Dude, when you say stuff like "TO GET CONSENSUS THAT YOUR SHIT IS TOO BIG." it just tends to bring in people to oppose you, blindly or not. I know it's perhaps like asking the tide not to come in, but if there is any way you could be more civil and less confrontational, it might get things done faster and with less turmoil. On the specifics of these two, I like the smaller size shield and map in your version, as well as the ends, but think mileposts and the "RCW 47.17.808" are useful things to have from the other version. I'm not sure how a state route can be a child of an interstate so am not sure about that part. Hope that helps. + +Lar: t/c 02:44, 27 March 2006 (UTC)
 * The smaller shield is fine. I'm not sure about the map though- as long as people can see the whole red line without squinting and stuff, maybe. --Rschen7754 (talk - contribs)  02:47, 27 March 2006 (UTC)
 * The 5XX routes are all numbered based on I-5 (which is of course officially SR 5). 599 itself is also numbered from 99, but if it was mainly from 99 it would be 995. Can you explain why you think including the mileposts in the infobox (rather than a separate table in the article body) is important? --SPUI (talk - don't use sorted stub templates! ) 02:55, 27 March 2006 (UTC)
 * I'm a visual person. I like having all the important things in the infobox. I think mileposts are important. YMMV. + +Lar: t/c 04:03, 27 March 2006 (UTC)
 * I don't understand that at all. How do the mileposts help you to visualize where the route goes? --SPUI (talk - don't use sorted stub templates! ) 04:20, 27 March 2006 (UTC)
 * They don't help visualise WHERE the route goes, that's the job of a map. But they DO help me visualise WHAT the mileposts are and HOW they relate to each other. Ever use Hertz NeverLost? I swear by it's "next five exits" view... this is like that. I'm a visual person. I like spreadsheets better than numbers in text, I like pictures better than prose. I'm a fan of big, detail rich infoboxes in general. You may not agree, which is why I said "YMMV" (your mileage may vary) ... Maybe show/hide would be useful here? + +Lar: t/c 05:19, 27 March 2006 (UTC)
 * I still don't get it, but whatever. Note that I'm not at all opposed to a table in the article body that includes junctions and mileposts, just including that in the infobox. --SPUI (talk - don't use sorted stub templates! ) 05:27, 27 March 2006 (UTC)
 * Why not in the infobox? It's just going to be somewhere else on the page if you move it. Why does it matter where it's presented? Afterall infoboxes are there for a short overview. Mileposts fit that definition IMHO.JohnnyBGood 21:32, 27 March 2006 (UTC)
 * Mileposts make it a long overview, and don't do all that much to help see where the road is. Putting them elsewhere on the page puts the more important stuff near the top. --SPUI (talk - don't use sorted stub templates! ) 21:50, 27 March 2006 (UTC)
 * &lt;-- (shift) What about show/hide though? That would put it all in the box but not cluttered. + +Lar: t/c 23:21, 27 March 2006 (UTC)
 * Hmmm. Seems rather hackish. And the junctions themselves are a lot more useful than the mileposts. --SPUI (talk - don't use sorted stub templates! ) 23:24, 27 March 2006 (UTC)

I have a few more at User:SPUI/onthecaca. I welcome discussion, but not blind opposition. --SPUI (talk - don't use sorted stub templates! ) 01:53, 27 March 2006 (UTC)
 * How is that blind opposition? I'm not blind. In fact I knew that this was coming long before. --Rschen7754 (talk - contribs)  02:10, 27 March 2006 (UTC)
 * Blind opposition as in not thinking, just opposing because you dislike my actions. --SPUI (talk - don't use sorted stub templates! ) 02:11, 27 March 2006 (UTC)
 * Because they're controversial and are confrontational. And because your infobox has less information. --Rschen7754 (talk - contribs)  02:20, 27 March 2006 (UTC)
 * My infobox has all the important information. We don't need mileposts in it. --SPUI (talk - don't use sorted stub templates! ) 02:21, 27 March 2006 (UTC)
 * Um yes we do. And I'm not blindly opposing- look at the changes to routeboxwa I'm making. Just because I dislike your infobox doesn't mean that everything is bad about it. --Rschen7754 (talk - contribs)  02:22, 27 March 2006 (UTC)
 * Mileposts, and listing every junction on long routes, makes the infobox too long. --SPUI (talk - don't use sorted stub templates! ) 02:27, 27 March 2006 (UTC)
 * It provides a good overview of the route. And there aren't any exit lists for the WASRs anyway. --Rschen7754 (talk - contribs)  02:36, 27 March 2006 (UTC)
 * Yeah that sr20 is way too long as well. Maybe we can just move the junctions list out into the main article as a compromise?  That will both shorten the infobox and make the article longer, making it more pleasing on the eyes. atanamir 02:39, 27 March 2006 (UTC)
 * Really, the junctions need to stay in the box. Maybe on SR-20 we should move the smaller junctions out into an exit list, but only for the extremely long ones. Most WA highways are short compared to their CA counterparts. And I've made many drastic changes to the box already. --Rschen7754 (talk - contribs)  02:45, 27 March 2006 (UTC)
 * Those "drastic changes" weren't very drastic, just some minor tweaking. There is no reason to have (a) every junction or (b) mileposts in the infobox. --SPUI (talk - don't use sorted stub templates! ) 02:53, 27 March 2006 (UTC)
 * The color coding? Removing of red links? Shrinking the map and shield? Added "formed" field? Removed "Highway in Washington"? Removing the legend? And we need the stuff in the infobox because it gives a complete quick summary of the route .... where people expect it. In the infobox. --Rschen7754 (talk - contribs)  03:00, 27 March 2006 (UTC)
 * My box provides a quick summary; yours provides useless details. --SPUI (talk - don't use sorted stub templates! ) 03:47, 27 March 2006 (UTC)
 * why "must" the junctions remain in the box? atanamir 05:34, 27 March 2006 (UTC)
 * See above. --Rschen7754 (talk - contribs)  05:43, 27 March 2006 (UTC)
 * They expect it because they're used to it. Give any format some time and i'm sure people will end up expecting it as well. atanamir 07:13, 27 March 2006 (UTC)

Accord
Why don't we get the principles to leave the floor for a while and see what the peanut gallery has to say? For aesthetics alone I like the smaller template, but I'm going to have to look over the arguments to see about the other ways to present the information. brenneman {L}  03:02, 27 March 2006 (UTC)
 * I haven't looked at the status quo on these infoboxes is yet, but how about we leave it like that until everyone is equally unhappy. If it's half way done, whatever, that it just gets left for a couple of days.
 * It's clear what SPUI and Rschen7754 want, and they've had a chance to make their case. *hint*
 * erm, you want the "principals" (that is, SPUI and Rschen7754) to leave the floor. but please, let us all stay firmly rooted in our "principles", that is, what is best for the readers? (and to a lesser extent, where it makes a difference, best for the servers, best for the editors (and in the case of, for example, copyright, libel, et al, best for the foundation)... I think we all can agree that both proposed boxes have a lot of merit, help the reader out a lot, and in the absence of alternatives, would be considered quite good. What we're talking about, presumably, is which version takes things farther in the direction of "best" rather than it being "icky" vs. "awesome". At least I hope so. Signed, (with some considerable glee at having caught Aaron in a typo!!!)  + +Lar: t/c 03:38, 27 March 2006 (UTC)
 * That's twice in recent memeory, dammit! - brenneman  {L}  04:45, 27 March 2006 (UTC)

Note Mediation Cabal/Cases/2006-03-12 U.S. Roads. --Rschen7754 (talk - contribs)  03:41, 27 March 2006 (UTC)


 * Ok, I reviewed that. - brenneman  {L}  04:45, 27 March 2006 (UTC)
 * Although it was fascinating reading, I could not figure out where to put in a comment, which was kind of a bummer, because I wanted to comment. That's what I do... Some people do, some watch, some talk. + +Lar: t/c 05:19, 27 March 2006 (UTC)
 * Mediator response or comments are probably good. --Rschen7754 (talk - contribs)  05:34, 27 March 2006 (UTC)

Whoa. Whoa. Whoa. I think the current routebox leaves much to be desired, and irrespective of my disagreement with SPUI on the article names and the general way he's gone about all this stuff, I think his proposal is generally an improvement. But please, let's table this debate until the mediation process has run its course. There are so very many reasons why it's a bad idea to try to discuss this while that thing is still going on, and I can't imagine any reason why we have to tackle this now. The template will still be there when mediation is taken care of. There's no rush. --phh 06:24, 27 March 2006 (UTC)


 * I agree, I like the shortened routebox as well, but we need to have a consensus. A dmrb♉ltz (T | C) 07:01, 27 March 2006 (UTC)


 * I like some of the improvements, however fighting about these changes is not productive. I feel that keeping all the current information in the routebox is important.  I say this, as it makes these pieces of information more accessible, and for some routes, they can be completely summed up in the route box. (Washington State Route 525 Spur) as an example.  I also like SPUI's idea of having a special field with the West/South and East/North Termini information.  I'm beginning to think we are trying to over tech this project.  I also feel that including the 'year formed' in the routebox is a stupid idea, since 90%+ of all WSR were created after the 'Great Highway Renumbering' from 1963 to 1971, with the first "new" signs going up in 1964.  Therefore I suggest that that field be removed from the routebox, and suggest that we expand the main article for Washington State Routes to include this information.  TEG 03:58, 28 March 2006 (UTC)


 * Personally, I find the year formed useful. For instance, one might assume that State Route 14 has always had that number (post-renumbering) east of Maryhill (where US 830 ended), but it was actually State Route 12 until 1967, when US 12 was extended into Washington (taking over what had been SR 14 from I-5 to Naches). So the box would list 1967 rather than the 1964 renumbering, and someone browsing through would quickly see that something interesting happened. --SPUI (talk - don't use sorted stub templates! ) 04:39, 28 March 2006 (UTC)

"Correct" names
Attention! SPUI has created this page with a long list of links like "State Route 3 (Washington)," which he says are "the correct names." But this is wrong! Anyone may look at the law creating the route and see that, according to the state, its "correct name" is "State Route Number 3." SPUI's "correct names" do not contain the word "number" anywhere in them at all! These so-called "correct names" are simply works of fiction that SPUI has created out of whole cloth, which have no relevance to anything in this great state!

MOREOVER, it appears that state route number 3 in Washington is, in fact, the only "state route number 3" in the entire world. Wikipedia's disambiguation guideline states quite clearly that "Disambiguation serves a single purpose: to let the reader choose among different pages that closely relate to various meanings of a particular term.… Please use them carefully and only when needed." (Emphasis mine.) It is therefore self-evidently obvious that, to be "correct," we must have a single page called State Route Number 3 that points to this page, as State Route Number 3 (Washington) would amount to unnecessary disambiguation and, of course, State Route 3 (Washington) is just entirely incorrect.

If you believe, dear reader, that I'm just being hyper-pedantic and stupid here… well, you're probably right. Please keep this in mind when parenthesis-crazed editors start talking about the "correct" name of anything. --phh 06:54, 27 March 2006 (UTC)


 * WSDOT always* uses State Route X or SR X. --SPUI (talk - don't use sorted stub templates! ) 08:25, 27 March 2006 (UTC)
 * *All but a few pages.


 * Wrong! Actually, the DOT uses "SR" much more often than "state route", as do traffic reporters and people in casual conversation. But so what? No less a person than yourself has made it clear that this is about what is "correct," not about what people actually do in any kind of real-world situation—like, say, looking something up in an encyclopedia. You can't win this one. Let it go. --phh 14:26, 27 March 2006 (UTC)


 * You're just trying to confuse the issue. The names of the routes, as used by WSDOT, are State Route X, abbreviated SR X. We don't put pages at abbreviations - Interstate 90, not I-90. --SPUI (talk - don't use sorted stub templates! ) 21:52, 27 March 2006 (UTC)
 * So... the common sense principle-of-least-astonishment name is not correct, the name as established by law is not correct, the name used most often by the DOT is not correct. Only the particular bit of jargon that you, personally, have taken a fancy to is the correct one. Okay. Got it. Forgive me if I disagree. --phh 21:59, 27 March 2006 (UTC)
 * The name used most often by the DOT is an abbreviation for State Route X. Please stop being a dick. --SPUI (talk - don't use sorted stub templates! ) 22:12, 27 March 2006 (UTC)
 * The law couldn't be clearer. Why are you so intent on unilaterally imposing your personal interpretation of "correct" on everyone else? --phh 22:20, 27 March 2006 (UTC)
 * I thought State Route Number XX was the state STD in Washington? JohnnyBGood 22:26, 27 March 2006 (UTC)
 * And what WSDOT uses couldn't be clearer. State Route X. Stop confusing the issue. --SPUI (talk - don't use sorted stub templates! ) 22:33, 27 March 2006 (UTC)

Let's please use what the rest of the world uses, "Washington State Route x." Bridges the gap between technically correct and common names. --Rschen7754 (talk - contribs)  05:00, 28 March 2006 (UTC)
 * Here we go again with your editing people's comments and inserting fact where you disagree. --Rschen7754 (talk - contribs)  05:07, 28 March 2006 (UTC)

Question for those who want milepost information
What kind of information do you want? Raw mileposts? Mileage from the beginning of the route, adjusted for milepost equations? To me, the first seems somewhat useless, and the second seems somewhat "impure". Putting that question aside, what do you think of something like User:SPUI/SR 599, combining mileposts, junctioned routes and cities? --SPUI (talk - don't use sorted stub templates! ) 04:35, 28 March 2006 (UTC)
 * Does the 2nd type exist in WA? --Rschen7754 (talk - contribs)  04:44, 28 March 2006 (UTC)
 * Hard to tell with a short route like 599. --Rschen7754 (talk - contribs)  04:45, 28 March 2006 (UTC)
 * There are milepost equations - I had to take one into account when I calculated SR 500 (on User:SPUI/onthecaca). There are also cases of routes not beginning at zero, though I can understand wanting to keep that information. More troublesome is something like SR 18, where it begins at 2.20, runs to 2.73, and then resets to 0.00. Basically, the question is whether to use the real milepost, which matches what is posted on the road (see - that's MILE 1 on the right), but is rather useless otherwise in cases like SR 18, or to use the "accumulated miles". --SPUI (talk - don't use sorted stub templates! ) 04:53, 28 March 2006 (UTC)
 * I'd like to see Milepost Information from Start to End, placed at each intersection with each State Route, US Route, or Interstate. Based on actual milepost Info.  Like for SR-900 it would start at 14, not 0, because SR-900 used to start near downtown Seattle, but now starts in Renton.  An estimate of the mileage if an actual value is not available would be acceptable.  I would like to see the deleted color and the removed color combined, since they should be the same.  Only add unbuilt intersections, if they cross, or if there is evidence that there was to be a connection originally.  At least the mileage in WA is a lot easier than Oregon (with their state highways and state routes, with no standardizations).  TEG 05:14, 28 March 2006 (UTC)
 * Look at Washington State Route 10. It is close to what I'm talking about. TEG 05:18, 28 March 2006 (UTC)
 * The part about including every intersection doesn't work on long routes like State Route 20. --SPUI (talk - don't use sorted stub templates! ) 05:42, 28 March 2006 (UTC)
 * What I'm thinking is do a route-by-route exception there for like 2-3. SR 20 should only have the major ones. Just like CA 1 and CA 99- there are exceptions there because otherwise the routebox would be too long. But the other ones should have all junctions. --Rschen7754 (talk - contribs)  05:46, 28 March 2006 (UTC)
 * If you're willing to do it for those, why not the others? --SPUI (talk - don't use sorted stub templates! ) 05:56, 28 March 2006 (UTC)
 * Only on those is there way too much info. --Rschen7754 (talk - contribs)  06:03, 28 March 2006 (UTC)
 * I've already refuted that. - still TOO BIG. Combining the cities with the routes, and removing a few of the many US 101 intersections, solves that, and makes it MORE USEFUL, as you know where the intersections actually are. --SPUI (talk - don't use sorted stub templates! ) 06:08, 28 March 2006 (UTC)

The state route log gives two kinds of mileage, the state route milepost (SRMP) and the accumulated route mileage (ARM). The ARM is the "real" distance of the route, which means that it changes whenever construction activity lengthens or shortens a route segment. The SRMP is the mileage according to the little green milepost signs, which are uprooted and moved much less frequently, if ever.

My informal practice has been to use the SRMP mileage, because it's going to be more meaningful to the average user--as far as s/he's concerned, mile 8 is where the little "8" sign is, not at some secret location determined by a log book. In cases where the two differ significantly, as with Washington State Route 17, I put the ARM in parentheses after the SRMP and add a footnote. (SR-18 is a weirdo outlier either way, so I just kind of winged it.) --phh 07:08, 28 March 2006 (UTC)

Historical information recovery
At some point within the last 2 days, the DOT purged everything under http://www.wsdot.wa.gov/research/History/. If it's been relocated, I can't find the new location. Fortunately, I've been able to recover a lot of this content from the Google cache and from archive.org. Here's where we stand:
 * Historical Collection - 40 Years with the Washington Department of Highways - Appears to be mostly or fully recoverable from Google and archive.org  except for .doc version, which may be lost
 * The Development of Washington State Highways and Transportation - recovered from archive.org
 * State Roads As Established by Legislature, 1893 to 1935 - recovered from archive.org
 * Washington State Highway Commission, December 1, 1965, Identification of State Highways, part 1 and part 2 - Part 1 apparently lost. Part 2 recovered from archive.org.

Please check your cache, Google Desktop history, etc. to see if you have a copy of part 1 of the 1965 document, or of anything else that's been taken down. We should also consider mirroring Washington State Department of Transportation Library's Biennial Reports Historical Image Library - it's still there, but for who knows how much longer. There was a tremendous amount of information here on the history of the state highway system and now it's in danger of being lost. I'll try to make the files I've recovered available via some other means at some point over the next few days. --phh 19:00, 7 April 2006 (UTC)

I saved the following files, if you want me to email them:
 * 06-08 p20w h map.jpg
 * 08-10 p182a-46 h map.jpg
 * 10-12 pXXXIIa h map.jpg
 * 20-22 p39 h map.jpg
 * 22-24 p16 h map.jpg
 * 22-24 p16a h map.jpg
 * 22-24 p24a h map.jpg
 * 22-24 p28a h map.jpg
 * 22-24 p48 h map.jpg
 * 24-26 p12a h map.jpg
 * 24-26 p14a h map.jpg
 * 24-26 p16a h map.jpg
 * 24-26 p18a h map.jpg
 * 26-28 p20a h map.jpg
 * 36-38 p107a h map.jpg
 * 38-40 p74a h map.jpg
 * 38-40 p74b v map.jpg
 * 52-54 p31 h map.jpg
 * 54-56 p16 h map.jpg
 * 54-56 p21 v map.jpg
 * 56-58 p16 h map.jpg
 * 60-62 p60 h map.jpg
 * idpart1.pdf
 * idpart2.pdf
 * stateroads1893-1935.pdf

Yes, this includes part 1 of the renumbering document. --SPUI (T - C - RFC) 14:59, 8 April 2006 (UTC)

Historical primary and secondary highways
Please see Primary State Highway 7 (Washington) and Child routes of Primary State Highway 7 (Washington) for my ideas for covering the PSH and SSH system that existed from 1937 to 1964. Some points: Hope you like 'em. Any feedback is welcome. —phh 21:54, 7 April 2006 (UTC)
 * The routebox should be fairly self-explanatory. "Signed with" refers to any U.S. or interstate routes the highway multiplexed with at any point. "Succeeded," where applicable, would refer to any pre-1926 named auto trails posted along all or part of the route. It'll look something like this:
 * The map is similar to the routebox map for today's highways, except that the old U.S. routes are shown in gray instead of the Interstate routes. The appropriate primary state highway is shown as a heavy red line; branch routes of the PSH are shown as thin red lines; and secondary state highways are shown as thin blue lines. To help restore some sense to this ridiculous system, I've added labels to the maps, which unfortunately aren't legible unless you view the map at full size. I hope it'll be possible to change this in the future.
 * The design of the old PSH shield is taken from a photograph I found on the Web years ago; I can't remember where. The design of the old SSH shield is taken from here, the only photo of such a shield I've ever seen. Please let me know if you have a better one.
 * I uploaded a US-10 shield for Washington that uses the original U.S. route shield design. I used the old, blocky typeface that was used on American road signs until the late 1940s, because it's more fun that way. :) (The typeface is called US Highway Old Style). I also created a PSH shield using the blocky typeface as a proof of concept, though I don't think it works as well at the small sizes and don't intend to keep using it for PSH shields. If you have an opinion. let me know.
 * As you can see, I've grouped all of the SSH 7X routes into a single page, instead of having a separate page for each one. I don't think having a separate page for each silly little SSH cowpath is justified, as none of them are around anymore and it's hard to imagine any of them ever warranting much more than a few sentences.


 * Very cool looking! A dmrb♉ltz (T | C | k) 21:56, 7 April 2006 (UTC)
 * Many of the secondary routes were replaced by a single number in 1964 - how about redirecting those? --SPUI (T - C - RFC) 15:01, 8 April 2006 (UTC)

SR-16 Spur vs. SR-302 Spur
My question is... which is it? Both are listed on the List of Washington state highways when they refer to the same road. Evidence online points to either one: SR-302 ending at SR-16 Spur which connects to SR-16 at both ends... or ...SR-302 continuing south to SR-16 with the northern half being designated SR-302 Spur.

Does anyone live near Purdy and knows what the actual signing states?

(By the way, the SR-16 infobox lists the junctions as SR-302 and SR-302 Spur, but then has a link at the bottom to SR-16 Spur.) -- Northenglish 03:48, 4 May 2006 (UTC)


 * Never mind, I've figured it out. According to WSDOT route logs, the section of road I questioned above is in fact SR 302 Spur.  There is however a separate highway designated but not signed SR 16 Spur; it is half of the wye interchange with SR 3 in Gorst.  Thus the SR 16 Spur article is incorrect, as is the SR 302 article.  The List of Washington State Routes, however, is correct for listing both.


 * I will correct the articles in question shortly, probably sometime this weekend. -- Northenglish 23:45, 5 May 2006 (UTC)
 * The actual signing is SR-16 Spur. I've been on that road. There might be a 302 Spur in Allyn though. --Rschen7754 (talk - contribs)  18:11, 6 May 2006 (UTC)
 * I hate to say I don't believe you... but I don't believe you. The Washington State Highway Log clearly indicates the existence of a 302 Spur in Purdy and a 16 Spur in Gorst -- and no 16 Spur in Purdy.  Mapquest and Yahoo maps both mark Purdy Drive as SR 302.  SRweb has photos available of all state routes, and while the photos are blurry, it appears to me that the signing is for a 3-digit state route number.
 * All DOT documentation labels Purdy Drive as SR 302 and SR 302 spur, and until I see photographic proof otherwise, I think Wikipedia should match. -- Northenglish 22:52, 6 May 2006 (UTC)

Looks like 302 to me. --SPUI (T - C - RFC) 11:26, 7 May 2006 (UTC)

Sorry for my tone earlier, Rschen, but I stand by my claim. -- Northenglish 17:45, 7 May 2006 (UTC)

I'll look through my pictures when I get a chance. For now it's the last thing I'm worried about though. (Arbcom... ) --Rschen7754 (talk - contribs)  21:52, 10 May 2006 (UTC)


 * No problem. I might get a chance to head out there myself this weekend to take a look at it. -- Northenglish 23:00, 10 May 2006 (UTC)


 * Clearly when I said I'd head out there, I meant to Arbcom, not to Purdy :-P... Just kidding, but point is, I can't get to Purdy this weekend. Shame... -- Northenglish 19:33, 13 May 2006 (UTC)

SR 520--why isn't it an interstate
Better question is, have any state highways been converted to interstates recently? It's so vital to the economy of the area, more so than I-705 in Tacoma. Wonder why it's not I-305 or something so we could get federal funding. Or are we getting federal funding for its rebuilding anyway? --Lukobe 06:24, 11 June 2006 (UTC)
 * I agree that it should be an I-something; but alas it isnt. I also think 405 should extend past I-5 in Tukwilla to the airport (which it use to do...) A dmrb♉ltz (t • c • [ log]) 07:17, 11 June 2006 (UTC)
 * If it was to become an Interstate, as it's already been built, federal funding probably wouldn't be affected - it can get it, but so can non-Interstates. Where federal funding is really increased is with proposed roads becoming Interstates. --SPUI (T - C) 19:23, 16 June 2006 (UTC)
 * SR 520 doesn't meet basic construction standards for Interstates. "Original" (1956) standards dictated a 2-foot left shoulder and 6-foot right minimum; current standards dictate 4-foot left and 10-foot right, while many states prefer 10- and 12-foot lefts as well. SR-520, which possesses *no shoulders* for much of its length, would not be eligible. Other issues (merge, ramp lengths) would also need to be resolved. —Preceding unsigned comment added by 131.191.39.223 (talk • contribs) 12:16, July 3, 2006

I think SPUI's right about the funding. The other reason is that 520 simply isn't up to interstate standards. From I-405 west across the bridge, the roadway has virtually no shoulders. This may be corrected in the next decade after they replace the Evergreen Point Bridge.

I think better options for an interstate designation would be 512/167, and SR-18 (although I'm not sure what the status of the SR-18 upgrade project is). -- Northenglish (talk) -- 04:42, 19 June 2006 (UTC)

New project leader
Rschen7754 has temporarily left Wikipedia for the summer. As per his talk page, I have taken over as "leader" of this project. As I said on his talk page, however, I don't view the leader position as in any way official, and would be happy to share the position if someone would like to be my co-leader. Feel free to contact me on my talk page or this talk page if you have any questions, or would like to help lead this project. -- Northenglish (talk) -- 21:23, 14 June 2006 (UTC)

Temporary compromise
And for my first act as unofficial leader, I propose thistemporary compromise. The fact is that for the time being we have two naming conventions. Please do not move any articles between the two conventions, regardless of what side of the aisle you're on. -- Northenglish (talk) -- 23:13, 14 June 2006 (UTC)

US 202?
A sign with the US highway shield rather than the normal Washington state highway shield around 202 has appeared on eastbound SR 202 just past 292nd Ave SE. There is a new traffic light being installed in this area as part of a WSDOT project. This may have just been an ordering error when they got the sign.

Or it could be part of continuing confusion on the part of the state. There are one or two Washington state shielded signs on US 2 towards Stevens Pass. Or perhaps the designation of the highway is changing? (Could be a trying to get better funding for some of the improvement projects on this highway between Redmond, Washington and Sammamish, Washington

-- wac (talk contrib) 05:55, 28 June 2006 (UTC)


 * It's definitely not a designation change, if for no other reason than there is already a U.S. Route 202 in the Northeast, and because it's a short route that doesn't cross state lines.


 * Signing mistakes like these happen all the time, whether they be from ordering mistakes, confusion, or just plain laziness. To this day, there is still a US 99 shield at the Columbia St entrance to the Alaskan Way Viaduct.  At this point, it's probably going to stay there until the viaduct is replaced. -- Northenglish (talk) -- 18:07, 28 June 2006 (UTC)