New Immissions/Updates:
boundless - educate - edutalab - empatico - es-ebooks - es16 - fr16 - fsfiles - hesperian - solidaria - wikipediaforschools
- wikipediaforschoolses - wikipediaforschoolsfr - wikipediaforschoolspt - worldmap -

See also: Liber Liber - Libro Parlato - Liber Musica  - Manuzio -  Liber Liber ISO Files - Alphabetical Order - Multivolume ZIP Complete Archive - PDF Files - OGG Music Files -

PROJECT GUTENBERG HTML: Volume I - Volume II - Volume III - Volume IV - Volume V - Volume VI - Volume VII - Volume VIII - Volume IX

Ascolta ""Volevo solo fare un audiolibro"" su Spreaker.
CLASSICISTRANIERI HOME PAGE - YOUTUBE CHANNEL
Privacy Policy Cookie Policy Terms and Conditions
Wikipedia talk:WikiProject New York State routes/Archive 3 - Wikipedia, the free encyclopedia

Wikipedia talk:WikiProject New York State routes/Archive 3

From Wikipedia, the free encyclopedia

Archive This is an archive of past discussions. 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.

Contents

Where should the exit list be?

I came across New York State Route 7, which has both a junction table and an exit list. For future reference, if an article has both a junction table and an exit list, should they be in separate sections (==Major intersections== and ==Exit list==) or in the same section, separated by a third-level heading (==Major intersections== and ===Exit list===)? --TMF Let's Go Mets - Stats 21:08, 1 November 2006 (UTC)

Being familiar with New York State Route 7 and I-890 in Rotterdam, the duplex is just a minor portion of the overall length of NY 7, and has just one exit between the duplex termini exits. Therefore, I'd suggest that the exits be part of the Major Intersections just as the rest of the highway is right now. I'd leave them as they now are, although since there is an exit (Exit 8 of I-890 for Highbridge Road), that should be added on the Schectady County (Town of Rotterdam) section. There needs to be quite a bit of additions, though, to the section known locally as "Alternate Route 7" (betwen I-87 and I-787) as there's an unnumbered exit for US 9/NY 9R, the exit for I-787 South/NY 787 North, and the duplex with I-787 North across the Hudson River into Troy...that duplex terminates on the Troy side of the bridge, a block west of the intersection with NY 40 (which is there). Fwgoebel 01:32, 19 November 2006 (UTC)

Showing junctions with concurrencies

Lately, I've found myself using a method already in use at WP:PASH and WP:OHSH by showing junctions with concurrencies as a "side-by-side" entry rather than by a "stacked" entry. See New York State Route 9D, especially the US 6/US 202 and I-84/NY 52 junctions in the table, for an example of this. Though I think we can use either method to show junctions with concurrencies, I'd prefer the side-by-side entry. Thoughts? --TMF Let's Go Mets - Stats 19:22, 5 November 2006 (UTC)

Article cleanup complete! and other news

Hey everyone. A piece of good news - all of the NYS articles (at least, the ones in Category:New York state highways) have been cleaned up and upgraded to the current project standards! My thanks to everyone who helped in the cleanup efforts, and with that said, we can, once again, focus on creating new articles now that all of the ones we have are good to go. Also, in case you haven't noticed, we've begun a "Featured article" subproject, if you will, here at WP:NYSR. If you haven't seen it, check out the top of the project page, where you can see the current featured article and nominate an article to be a featured article in the future. Regards, --TMF Let's Go Mets - Stats 05:19, 12 November 2006 (UTC)

Also of note: {{Routeboxny}} and {{Nysr box}}, now both unused, have been put up for deletion at WP:TFD. --TMF Let's Go Mets - Stats 17:13, 12 November 2006 (UTC)

Several new additions, including a couple of Decommissioned Routes

I've recently joined, having made a couple of small corrections to some of the existing route pages. Among them were changing termini (North should be West, for example) and adding an interstate overpass where it didn't exist. My best recollection is that I've made minor changes to at least 30 and 29A. On 29, I added quite a bit of description on a good segment, how its original routing is very visible along the current road. Perhaps I could get some pictures next year when there's some foliage. My school bus traveled that route K-12, so that's why I'm so familiar with it.

In addition, I've added the following pages within the past week, having driven the entire lengths of them: 30A, 66, 103, 146A, 136, 203, 150. I invite comment on them. I still hope to get to 145 and a number of those in the 159-170 range, and 10A.

The following decommissioned routes were also added: 154, 339. In addition, I added the decommissioned highways to the intersection lists where appropriate, but because I could not determine the mileage right away, I used the notation of "?.?" for mileage. Those occur on NY 50 (for 339 WT), NY 22 (for 154 ET) and 29 (for 29A WT). 29A used to have a different routing and it's described on 29A, mentioned accurately on 30A, but added without mileage on 29. Meanwhile, I will soon research decommissioned 152. I'm wondering if it's acceptable to use the same New York shield on the decommissioned highways, or instead a grayed-out or brown image?Forget that...on other pages for decommissioned highways, particularly US 66, the "standard" shield is used. Let's keep it consistent.

Finally, I also have information on NY 546. It's not listed, it's not signed anywhere, but the number is reserved for Balltown Road, Schectady. Probably named because it connects 5 and 146. It's 2.0 miles long. Reference markers for 546 appear between 5 and 7, and 146 for the short segment between 7 and where 146 arrives on Union Street. That suggests that NY 7 may have once duplexed 146 throughout Schenectady (city), so that last segment might better be described as a decommissioned segment of NY 146, and listed as such on the pages for 7, 146, and 546 if that's put into existence. Oddly, that's where my doctor's office is located. There's no NY 546 .svg placard. For what it's worth, 546 is mentioned in Official Description of Highway Touring Routes, Scenic Byways & Bicycle Routes in New York State (PDF). Fwgoebel 04:00, 19 November 2006 (UTC)

First off, welcome to the project! =) Any and all contributions are definitely welcome. Some notes:
  • If a decommissioned route has been completely reassigned as another road (such as New York State Route 432), the article and its name should reflect its current, not former designation (as the NY 432 link redirects to County Route 119 (Steuben County, New York), which is what NY 432 is today). If the route is now multiple roads (such as two county routes), then an article can be made for the decommissioned route as a whole.
  • In situations where the mileage is unknown, the mile= parameter can be omitted.
  • An argument for using the same shield style for all routes, active or not: if a decommissioned route is reassigned in the future and we used "grayed-out" shields for decommissioned routes, we would then have to make a new "standard" shield to replace the decomd. one. By keeping the style consistent, it eliminates this need.
  • After doing a Google test, it appears that NY 546 does/did/will exist in some fashion. According to Empire State Roads, Balltown Road is Reference Route 914T, but, as you said, is signed with NY 146 and NY 546 reference markers. I'd say that until Balltown Road officially becomes NY 546 (as the PDF indicates reserved for the time being), any article created for it should be at New York State Route 914T, its current number. --TMF Let's Go Mets - Stats 20:50, 22 November 2006 (UTC)
Thank you for that feedback. Given that: My NY 339 (decommissioned) would be eliminated, but I don't think there's a Saratoga County Route 339 page yet in existence, so...leave it as it (for the time being?) with commentary? I don't (yet) know how to set up a redirect (eventually, I'm sure I will). The NY 154 that I did - that will indeed stay up as it is as is has been incorporated into at least two city streets, two county highways, and one state highway. For now though, what shall be done with the NY 339 that I put up? Fwgoebel 02:48, 23 November 2006 (UTC)
It's easy! Up at the top of the New York State Route 339 article, between the "history" and "unwatch" tabs, is a tab that says "move". Click the move tab, type County Route 339 (Saratoga County, New York) as the new article name, and type an appropriate reason for the move. You're all set; the redirect will be made automatically for you. However, then you do have to go through and make sure there are no double redirects; any redirects to New York State Route 339 should be changed to redirect instead to County Route 339 (Saratoga County, New York). Powers T 15:56, 24 November 2006 (UTC)

Noaccess tag used for two routes entering a municipality

In a couple of instances—articles on state routes that I've added—I've come across two highways that enter a town, but do not intersect (they come close). These differ from overpasses (usually between minor state highways and an interstate) in that there's no overpass, but the roads are close enough to have "To" signs in town for both. Among these are US 9W and NY 203 in Valatie (0.5 mile); NY 146 and NY 156 in Altamont (0.1 mile); and NY 443 and NY 157A at Warren Lake, East Berne (1.3 miles). For each, I've used the "noaccess" tag, and where I was able to determine, if a reference route between the two if it's used (together with the length of that access route). I don't think the "noaccess" tag should be used willy-nilly, but judiciously. In each instance, even without a direct intersection, the routes enter the same municipality and both have a sign "To" the other route. Fwgoebel 21:23, 21 November 2006 (UTC)

To expand on this: I've put up NY 103 and expanded on it and while it serves solely as a link between NY 5 and NY 5S, I have not indicated a "noaccess" tag for either of the two. NY 103 is shorter than many reference routes, but because it's a touring route and not a reference route, and crosses a river, plus the hamlet is only at one end, it doesn't qualify per what I've outlined above as a "noaccess" junction. This is the judicious non-use that I'm employing here. Fwgoebel 15:08, 22 November 2006 (UTC)
I really think using the noaccess shading for non-junctions is a bad idea. The idea for the shading was derived from Template:Routebox legend, which explicitly states crossing with no access. Since all of the examples above involve roads that do not cross, I strongly feel that using the noaccess shading for these situations is inappropriate. It also gives me, as a reader, the impression that the two roads cross, regardless of what's written in the notes column. Instead, I'd rather do something like the pseudo-NY 89/96 junction with New York State Route 79 in Ithaca. So, for this example on New York State Route 146:
County Location Mile Road(s) Notes
Albany Altamont 11.7 NY 156 Access to NY 156 via Reference Route
912C, about one block (0.1 mile).
Legend
Crossing, no access Concurrency termini Decommissioned Unconstructed Closed
I would rather do this:
County Location Mile Road(s) Notes
Albany Altamont 11.7
NY 156
Access to NY 156 via NY 912C.
Legend
Crossing, no access Concurrency termini Decommissioned Unconstructed Closed
or
County Location Mile Road(s) Notes
Albany Altamont 11.7
NY 156
Access to NY 156 via Reference Route 912C.
Legend
Crossing, no access Concurrency termini Decommissioned Unconstructed Closed
--TMF Let's Go Mets - Stats 21:07, 22 November 2006 (UTC)
Thank you for such a detailed and educating response. I hadn't had to use banners over signs until this point and your response, together with an excellent demonstration, set me straight. I agree, now that I see this technique, that it is the way to go. Check out NY 146 now, I've made this change on that page, I'll do the others when I get a chance. I also used the "nospace .svg" to clean up the centering of a couple other banners and their respective shields. I learned more than you intended there, so that's definitely a feather in your cap. Fwgoebel 02:38, 23 November 2006 (UTC)

Articles nominated for project FA

Two articles have been nominated for project featured article status. Check out Wikipedia:WikiProject New York State routes/FA/Recommend to view the articles and vote. If both are approved, the top vote-getter will be the featured article for December. Regards, --TMF Let's Go Mets - Stats 01:43, 22 November 2006 (UTC)

December update: NY 52 was selected as the December NYSR featured article. NY 55 remains up for nomination as the January article, but more noms are desperately needed. --TMF Let's Go Mets - Stats 00:44, 1 December 2006 (UTC)
Two more noms added, making a total of three routes to choose from for next month. --TMF Let's Go Mets - Stats 05:35, 4 December 2006 (UTC)

Issue with template:NYint

I need to disambiguate the link to Unionville, New York on New York State Route 284, but I don't think the template supports this. --NE2 23:55, 25 November 2006 (UTC)

It does have that function using the ctdab= parameter. I have added it to the junction list of NY 284. --Polaron | Talk 01:05, 26 November 2006 (UTC)

NYint template to be used exclusively?

I recently re-worked all of the articles I created to the NYint template. That took less time than I thought. Still, there are many other articles that follow the NYSRInt template (as of now: NY 5A NY 5B NY 5S, among others. Shall it be a "to-do" task to move them all over to the NYint format, as it appears to be the format called for in the project article? Fwgoebel 21:04, 27 November 2006 (UTC)

Definitely. --TMF Let's Go Mets - Stats 21:10, 27 November 2006 (UTC)
I don't know if it's as high-priority as other tasks, but the very presence of the older template is what caused me to do my first article (30A) in that format, simply by copy/paste/adapt/edit. It was a "learn as you go" process. If the older template isn't used anywhere, then it's unlikely that it'll be copied and used on another new article (and perhaps the template could be submitted for deletion). But, I have some time, so I think I can go into it. Looks like, for now, 5S will take the longest.Fwgoebel 21:36, 27 November 2006 (UTC)
As of 12:00:00 EST, I've made these changes as high as NY 36. NY 35 was the highest I've done. NY 37 needs to be done, and I will check on that later. But for now, I'm taking a much-needed break, to do some driving, in addition to getting info on a couple other un-done route articles. Fwgoebel 17:00, 28 November 2006 (UTC)
Sounds good. I've checked all the articles up to 36 (as directed on the talk pages) and they look good to go. One thing though - when you update the template, please change the footer template from {{NYSRIntBottom}} to {{NYintbtm}} as well. --TMF Let's Go Mets - Stats 01:47, 29 November 2006 (UTC)
I left that footer alone as I though I'd seen (at least one) of the NYint -based blocks have that NYSRInt footer, yet work fine, so I dismissed it as nonessential. (Perhaps, the footer isn't as critical, as it just ends what's above it?) From this point forward, I'll make that change.Fwgoebel 04:00, 29 November 2006 (UTC)

Back to the left: I'm now up to NY 64. I am finding many that are already on NYint, so it's not overwhelming.Fwgoebel 05:07, 29 November 2006 (UTC) Continuing: Now up to NY 111. The highest number that needed re-working was 104B.Fwgoebel 13:49, 30 November 2006 (UTC) And, now up to NY 140. I do know that 141 needs a change as a lot of many "short" one-county routes are done without any county designations on the chart. As of now: NY 250 and below (though I have noted a few articles without a description box at all).Fwgoebel 05:49, 1 December 2006 (UTC) As of now; Through NY 400. Fwgoebel 16:49, 3 December 2006 (UTC)

Okay, here we go. I think I've got them all done, the last one needing the change was NY 990V. If it can be verified that the NYSRInt format is no longer found on any of the NY State Route articles, then the To-Do list item can be removed (I cannot find a way to remove it, or to do a "strikeout" on it. But as of now, it appears to be complete.Fwgoebel 01:04, 4 December 2006 (UTC)

To verify that all of the usages of NYSRInt have been replaced, what you can do is to go to Template:NYSRInt, then, on the left side of the screen in the toolbox, click "What links here". As you can tell by carrying out this procedure, all usages have been replaced, which means it can be sent to WP:TFD, a process that I can take care of. Also, as for editing the to-do list, there is a series of links above the to-do template on the project page - one of which (the leftmost one, I think) is edit. --TMF Let's Go Mets - Stats 03:46, 4 December 2006 (UTC)
I just couldn't find (and still can't find) the applicable "edit" for that template, just the edit for the various text blocks above and below it. It's no big deal, just that it would have been nice if I could have actually done it myself, and I won't really be in a position to do the others, I don't think. But as otherwise, thank you for taking care of it. And, I have to remember to sign this: I felt really sick yesterday and I did leave a few talk posts without four tildes. Fwgoebel 14:09, 4 December 2006 (UTC) Okay, I went to your user page (User:TwinsMetsFan) and saw your To-Do list, and the four links there. On my browser, the title of the To-do either spaces them out, or they're hidden under the right-side matter. I'm not using a wide-format screen. The fact that I'm on a Mac shouldn't be a factor, I thought it might be. Fwgoebel 14:37, 4 December 2006 (UTC) Never mind, I found the "Edit" (and Refresh, etc.) On my screen, they wound up "floating" near Kentucky on the right. Fwgoebel 15:51, 4 December 2006 (UTC)

Just to bring your attention to...

Croton Expressway, a stub article on an expressway in Westchester County that's part of US 9, in desperate need of wikification and general cleanup. It would be great if someone could take that up in the near future. If not, that's fine. I plan to create a U.S. Route 9 in New York article in the near future (sometime before year's end), and will be happy to merge the salvageable information into it at that time. -- NORTH talk 07:00, 1 December 2006 (UTC)

The best thing to do would probably be to move the Croton Expressway article to the US 9 in NY page and use that as a basis for writing the article. I had to do that for Lehigh Valley Thruway in Pennsylvania, which became the basis for U.S. Route 22 in Pennsylvania. --TMF Let's Go Mets - Stats 02:11, 3 December 2006 (UTC)

New parameters for reference routes

A quick technical update regarding {{Infobox NY Reference Route}}: the "route=" and "alternate_name=" parameters were added tonight, allowing for routeboxes like the one on New York State Route 940U. One drawback, however: the "name=", "shield=", and "reference_route=" parameters cannot be used with route= and alternate_name= for technical reasons. --TMF Let's Go Mets - Stats 02:16, 3 December 2006 (UTC)

To do: Aligning Thruway entries

I won't take up a lot of space on this talk page with progress, but I've started doing a little standardizing, particularly the Thruway. I believe we have, albeit possibly unwritten? a policy of having the appropriate interstate logo (87, 90, 190) on the same line as the Thruway sign. Many articles have them on separate lines, and I'm going through and putting them on the same line. To see progress on this, see my user page (scroll down to "What's next"). I'm doing the same for I-86/NY 17. Of note: NY 9J passes under the Thruway but not I-90, so I deleted that I-90 logo. Fwgoebel 14:15, 4 December 2006 (UTC) Complete. Fwgoebel 03:31, 6 December 2006 (UTC)

Now that it's complete, does every entry of I-190 call for a Thruway logo? Is every inch of I-190 under the Thruway? Some articles don't mention Thruway with I-190.Fwgoebel 04:27, 6 December 2006 (UTC)
I-190 is part of the Thruway from I-90 north to NY 384, where it becomes just I-190. --TMF Let's Go Mets - Stats 11:56, 6 December 2006 (UTC)
Thank you for that clarification. For that, I'll leave every article as it is, trusting the editors there. Fwgoebel 13:43, 6 December 2006 (UTC)

Suggestions for NYint template

I'm wondering if two new "types" can be created, added to the five choices already in existence. They are: Grade separated interchange (|type=grade) and Roundabout/Rotary/Circle (|type=circle). I imagine they'd create more "to-do" work to place them on articles where they'd be appropriate, but as it is, they're commonly mentioned in the Notes column. Fwgoebel 23:31, 7 December 2006 (UTC)

I see your point, but I don't know if we should add extra types based on the type of junction. Granted, we do have "noaccess", but this is to indicate that no junction exists. Plus, the notes column was initially created so that special notes about the junction in question (such as whether the junction is an interchange, traffic circle, etc.) could be added. Input from others on this issue is welcome. --TMF Let's Go Mets - Stats 22:39, 10 December 2006 (UTC)

Template:Infobox_road

I’m coming across another thing that isn’t consistent from article to article. Whenever I put up a new one, invariably I’m starting by copying the wiki code from one as similar as I can find, doing the natural “learn by doing”. The copy, though, is a time-saver. This is how I replicated the old “NYSRInt” template on some articles, perpetuating it for a bit. Now, I’m coming across another: Some articles have a “length_km” (a manual entry of the length in kilometers) and others, a “length_round” followed by a “length_ref” (and the kilometer length is calculated automatically). The final appearance of the article doesn’t seem to be different.

I didn’t notice it right away, but some of the newer articles I created were cleaned up by TMF and had that change made (among others), but many are still there. For example, I just started doing NY 196, and with NY 197 being nearby enough (in numeral, location, and depth of article), made sense to copy from that. NY 197 uses the “length_km” line. Within this very talk page, even NY 27 uses it (although NY 135 does not), so I’ll adapt for now and do it with “length_ref”. But given that the remaining routes that need articles are starting to get way too far for me to go out and drive (my preferred method), perhaps doing this sort of cleanup might be a to-do list for me.

PS: After looking at the template proper, I noticed that one could enter “length_km” and have the miles calculated, and listed second. Functionally, any of these methods work. Fwgoebel 14:16, 14 December 2006 (UTC)

"length_km" is a deprecated parameter that was used until SPUI incorporated the automatic calculation of kilometers into infobox road. Ideally, all articles should use "length_round" and "length_ref". --TMF Let's Go Mets - Stats 16:09, 14 December 2006 (UTC)
Agreed, if only because I trust a computer calculation more. (After implementing "length_round" instead of "length_km" on Interstate 195 (New Jersey), I realized that the manual entry of "length_km" was incorrect by about 0.3.) -- NORTH talk 21:31, 14 December 2006 (UTC)

Reference Route articles

I put up three yesterday: NY 920D, NY 920J, NY 910F. Comment invited on all three, as well as the touring routes in Fulton County that the first two intersect: NY 29 and NY 30A. NY 910F has a manually placed noaccess “tag”, so a manually placed legend is there too (it's an exit listing, not an intersection list). More are to come, but I just wonder what might be done differently, and if/how they should appear when they intersect touring routes - displaying the reference route's marker, and/or the decomissioned touring route shield, as appropriate. Fwgoebel 13:49, 16 December 2006 (UTC)

  • And, here's my first question: Today I put up an article for a route that's not numbered: 913T. I created a reference marker that would go on that route, if posted. Otherwise, markers are placed that bear what's actually posted (as 29A on 920J. Shall that be the protocol? —The preceding unsigned comment was added by Fwgoebel (talkcontribs) 23:03, December 28, 2006 (EST).
  • Here's some more stuff: Reference routes aren't always going to have termini at cross routes, but possibly a city line. See 910C and 910E: Infobox, I used "City Line, Albany" as the appropriate terminus, and in the junction list "Albany City Line" as the route entry. If a cross street or waterway exists at the city line, I placed that in the street entry. For 913T, I used "Ramps to I-787" for the terminus in the infobox. My intention is to continue doing these with consistent entry, so if this is acceptable, fine; if not, please let me know. Fwgoebel 02:05, 31 December 2006 (UTC)

I STILL hate the new Intersection Template

Upon adding two formerly proposed roads to the new intersection template for New York State Route 25, I ended up making the last two intersections lobsided, again! I NEVER had this problem with the old intersection template. Why the hell does it always cause me to have these problems?! DanTD 02:33, 28 December 2006 (UTC)

You forgot to adjust the cspan and lspan values accordingly for the new rows. I've fixed them both. --TMF Let's Go Mets - Stats 03:01, 28 December 2006 (UTC)
Ah, I see. Since I already added one of the links to the shields, could you make one for Suffolk County Roads 8, 65, 88, and 94A? SCR 65 is going to be for my future article on Suffolk County Road 19, and the others are for the ones I already added to routeboxes and intersection boxes. DanTD 18:33, 29 December 2006 (UTC)

Wikipedia Day Awards

Hello, all. It was initially my hope to try to have this done as part of Esperanza's proposal for an appreciation week to end on Wikipedia Day, January 15. However, several people have once again proposed the entirety of Esperanza for deletion, so that might not work. It was the intention of the Appreciation Week proposal to set aside a given time when the various individuals who have made significant, valuable contributions to the encyclopedia would be recognized and honored. I believe that, with some effort, this could still be done. My proposal is to, with luck, try to organize the various WikiProjects and other entities of wikipedia to take part in a larger celebrartion of its contributors to take place in January, probably beginning January 15, 2007. I have created yet another new subpage for myself (a weakness of mine, I'm afraid) at User talk:Badbilltucker/Appreciation Week where I would greatly appreciate any indications from the members of this project as to whether and how they might be willing and/or able to assist in recognizing the contributions of our editors. Thank you for your attention. Badbilltucker 16:04, 30 December 2006 (UTC)

Browse function on Reference Routes

Check out 915E, I added a browse function to the template Template:Infobox NY Reference Route. Displays fine on articles that need them (since this reference route covers a decommissioned route (381), I redirected that, and added the browse function. However, it adds {{{browse}}} junk to other reference routes. If you have a fix, please do what you can. Fwgoebel 15:49, 18 January 2007 (UTC)

I managed to fix it on my own: It needed a pipe ( ). Looked into the county route template to find that. All is fine. Fwgoebel 16:02, 18 January 2007 (UTC)

Exit list guide

Just wanted to run this by everyone here at WP:NYSR. Changes are being proposed to the exit list guide that will change the way exit lists appear, albeit slightly, on articles covered by this project. Check the proposed changes out at the link above. If anyone has any concerns, please post them there. --TMF Let's Go Mets - Stats 03:43, 25 January 2007 (UTC)

Cleaning up after ourselves

Remember back in the springtime when we were all busy creating and uploading .PNG state route signs because the routeboxny template was designed to automatically install them?

Well, we've replaced all of them in articles with .SVGs per the standard infobox format. But the PNGs are almost all still here. Most are orphaned but you still find some used in the odd article like "List of highways numbered ..." and some lists of river crossings.

I've been going through the ones I uploaded and requesting speedy deletion (with {{db-g7}}). Could everyone else do the same? Yes, they will eventually be deleted as orphans but that's no reason we can't pick up after ourselves and free up space on the server. I've come across quite a few of other people's .PNGs; only the uploader can request speedying and I don't really want to clog up IFD. A little help here?

Also, check each one for pages they're used in and change to the .SVG version if you can. I've done these where I've come across them but I haven't hit every one yet. Daniel Case 05:05, 7 December 2006 (UTC)

As of 19:20, 11 December 2006 (UTC) I have finished with all mine, which was the bulk of the remaining .PNGs. However, there are a scattered few others left. If you uploaded any, go look, they're still there. Daniel Case 19:20, 11 December 2006 (UTC)

Palisades' sign removed from intersecting routes' articles

While the article for the Palisades Interstate Parkway (PIP) maintains its sheild it has been summarily removed from most if not all of the route articles that intersect it. So has the Mass Pike's and Garden State Parkway's shields from the Thruway article. "Fair use abuse" was cited, "The material must contribute significantly to the article and must not serve a purely decorative purpose." If this is the case, then I suppose the Thruway sign should be taken off every article that references that. Before I revert anything, I invite comment here. I'm trying not to show emotion at this point. Fwgoebel 20:41, 21 December 2006 (UTC)

The Thruway sign was taken off every article along with the above shields. Personally, I think the reason given for removing the shields is extremely weak and, like yourself, am trying to refrain from becoming emotional. Needless to say, however, I'm not pleased by what transpired. --TMF Let's Go Mets - Stats 21:18, 21 December 2006 (UTC)
The Thruway sign should also be removed; if you would like to help, feel free. --NE2 22:46, 21 December 2006 (UTC)
The signs are not decorations; they are the actual routes that are being crossed at the mileage point noted in the particular articles as cited. And they do contribute significantly, as they illustrate the actual signage present on the routes that are crossed along its path. We would not be inserting them if this was not the case, and there is always a link to the article about that very route, and if there's an external link associated with it (such as the Thruway), it's accessible through that. Fwgoebel 23:18, 21 December 2006 (UTC)
If you want to see the shield used on the road, you can click the link; note that I did not remove the shields from the articles actually about the roads. The use for decoration on intersecting roads does not follow Wikipedia's fair use policy and may not follow U.S. law. --NE2 23:23, 21 December 2006 (UTC)
It is not decoration - it is identification. The presence of the shield can help one who is unfamiliar with the route identify the road better than a text-alone link. IMHO, the shields have just as much a right to be on junction lists than they do on their actual articles. Under your arguments above, all uses of the shields would be removed, including on the main pages, and the shields would be deleted as orphaned logos. --TMF Let's Go Mets - Stats 00:01, 22 December 2006 (UTC)
I agree. They shouldn't be deleted. The next thing we know, they are going to try to remove Green & White New York Parkway shields too. They'd better not! DanTD 04:56, 24 December 2006 (UTC)
Further, we follow, or at least try to follow, specific protocols on things including placement and size. For example, I spent several days a few weeks ago moving the Thruway logo to be on the same line as the interstate highway with which it is duplexed. These logos are to be 20 pixels in width (25 pixels for a shield that's rectangular to maintain the same final height, also 20 pixels). And again, they are not placed willy-nilly. While I appreciate your enthusiasm, I think it would be better served to have posted a comment in this talk page stating your opposition to the presence of these shields, rather than go into so many articles and just delete them. We then could work together to determine what the proper interpretation of policy is (or should be) and possibly modify it in specific instances if necessary. Fwgoebel 04:28, 22 December 2006 (UTC)

I'm not going to give my interpretation of fair use policy because to be honest, I don't have one. My question is on specifically the Palisades Parkway shield. All the state/US/Interstate shields are SVG images listed as public domain. Most toll highway shields are PNGs listed as copyrighted and fair use.

When TwinsMetsFan first uploaded the Palisades shield as an SVG, he listed it as public domain. Before he started taking the images off, NE2 switched it to copyrighted. So... my question is: what makes toll highway shields different from the numbered highway shields? And to TMF specifically, what IYHO makes the Palisades shield different from (ex.) the Thruway shield? -- NORTH talk 02:15, 26 December 2006 (UTC)

I hadn't looked for such a change on the PIP logo, but now that you looked at it, I found this in the edit summary: "I'm pretty sure this is copyrightable by the PIP authority." Now, there is already a lengthy (somewhat heated) discussion at Wikipedia_talk:Fair_use#Removal_of_decorative_fair_use, started by NE2 after the discussion here began. I don't want to get into a discussion here on the issue of "copyrighted" and "copyrightable" since it really belongs there. I'm still assuming good faith, but I can't help but question the autonomous actions and the manner in which they were taken. Now, while I can't speak on the the PIP and its shield, the NYS Thruway sign is freely downloadable from their official website without any listed restrictions on use. The font in the downloadable file differs from what's actually found on road signs, but matches what's uploaded at The Commons. Fwgoebel 04:20, 27 December 2006 (UTC)

Since it was pointed out to me in the Wikipedia talk:Fair use discussion that the Thruway authority does have a requirement about written permission, yesterday I mailed a letter to their legal department asking for their interpretation and permission. In that letter I included links to the Thruway article here, as well as an example route article (I used 30A). I asked for their analysis, if they were "decorations". It had been mentioned that if one wanted to see a shield for a route, to click on the route link. I would counter that by mentioning that without presence of the small image, one wouldn't even know there was a shield associated with that intersecting route. My argument is that the artistry (for lack of a better word) of that shield (call it a logo or icon if you wish, I don't care) would be a greater impetus for a reader to venture into the parkway's article than just a text link (especially if the link is abbreviated "PIP"). I will share the response of said letter from the Thruway authority if/when I receive it, although I don't know how I could convey its ruling to the powers-that-be here. Further, I tried to find a website for the PIP (www.pipc.org is for the commission of the park, not necessarily the parkway [route]) and may be a dead link besides. So I don't know if there can be similar permission granted through that means, but that doesn't mean it's out of the question altogether. Fwgoebel 23:47, 28 December 2006 (UTC)

Precision in junction lists

Now that we've finally found a stable format for articles, I'd like to draw attention to an issue that's been gnawing at me for some time - precision in our junction lists. When I first proposed the idea to round to the nearest tenth, I did so because at that time, I was using trip planning software (which only went to the nearest tenth) to measure the distance. Now that I know of the NYSDOT traffic counts (which provide mileposts to the nearest hundredth), there is no longer a need to manually calculate the distance, plus I can now (as well as anyone using the counts can) calculate the distance to the nearest hundredth.

My point is that I believe we should "up" the precision in our junction lists from the nearest tenth to the nearest hundredth as soon as possible. Thoughts? --TMF Let's Go Mets - Stats 05:03, 5 January 2007 (UTC)

Agreed for the sake of common sense.  :-) If you have a reliable source that gives mileage to two decimal places, then you should give mileage to two decimal places. -- NORTH talk 05:38, 5 January 2007 (UTC)
I've used the "ruler" function in Google Earth to check for a distance when I've overlooked an intersection when driving a route, or to do the reference routes that I've put up. The ruler function does have a "path" function and uses hundredth of a mile (but does not compensate for elevation changes, as far as I know). Still, I've rounded to the nearest tenth every time, and used the mileage posted on whatever reference, for the final terminus.Fwgoebel 23:30, 5 January 2007 (UTC)

Structure suggestion - Related routes

Having noted in the US Interstate and Interstate article structures both include sections for related routes (such as US 9 having US 209, and I-87 having I-287, I-587, and I-787 on them), I'm wondering it it would be good to have such a notation on those NY state routes that have suffixed routes. Such a listing would have the suffixed route number and whether the route is a loop, spur, or primarily parallel (such as NY 5S). I have added an example to NY 30, illustrating the suffixed route's termini, and a short list of munipalities it passes through (which are not accessed by the parent route) and, in this case, how the route is west of the parent. Suffix route spurs would note the general direction away from the parent it follows. A decommissioned route (like 12C) could be listed in the past tense. In all, the notation would be brief (but wikilinked). Thoughts? Fwgoebel 05:06, 8 January 2007 (UTC)

Sounds like a good idea to me, but it'd probably be better if it was formatted similar to the "Spur routes" section on Pennsylvania Route 58. We tried a single, second-level section for Spur/related routes in the early days of WP:PASH, but eventually settled on a third-level section that was part of the see also section. Another example that may be more relevant in this case is the "Suffixed routes" section on New York State Route 17. --TMF Let's Go Mets - Stats 05:16, 8 January 2007 (UTC)
Those sound good also, I suppose the exact way of doing it would depend on the routes. They'd all be suffixed, so that term can be used as well. Regardless of format, the goal should be one line per suffixed route. Fwgoebel 06:04, 8 January 2007 (UTC)

1930 renumbering

I'm planning on expanding the 1930 renumbering article over the next few days. I just wanted to see what kind of information other people think would be useful to put in this article. Any suggestions on content and/or presentation would be greatly appreciated. Thanks. --Polaron | Talk 21:54, 27 January 2007 (UTC)

You can check the Virginia renumbering articles for what I chose to include. Of course if you have anything from that period that explains why it was done, it would be a good thing to include. --NE2 22:59, 27 January 2007 (UTC)
The Virginia articles seem like they'd be a good springboard in terms of style of presentation. Another thing I'd include as well as tables showing the new routes in 1930 would also be one going the other way - detailing routes as they existed before 1930 and showing what route(s) they became. The table that SPUI began a while ago on top of the 1930 renumbering talk page may be a good format for the new route table(s). For the old route table(s), well, that design may work as well, just flipping the new and old columns.
Off-beat comment (well, maybe not): on the bottom of the talk, I noticed there's now a section detailing the clusters of route numbering that appeared around the state post-1930. Two questions: (1) Were NY 250-253 commissioned in the Rochester area simultaneously in 1930 and (2) if so, would that be considered a cluster? --TMF Let's Go Mets - Stats 05:14, 28 January 2007 (UTC)
Unfortunately, the Green Book route log doesn't go beyond 150 for some reason so I have to rely on the map in the New York Times article for higher numbered routes. However, not all routes are indicated on the map, especially around cities. I will try to get a hold of a 1931 map next week. But to answer your question, the NYT map shows routes 251 and 253 as newly designated routes. The NYT map does not always show the complete route. 253 is shown only as Caledonia-West Henrietta but my guess is (based on a 1927 map which shows the road but unnumbered) it extended east to old 15 (current 64) near Pittsford as it does now. The Caledonia-Scottsville segment is now current 383. 251 is shown only as Mendon-Scottsville but from the route continuity of the unnumbered road, I would guess it continues north past Chili via current 386 to 33. While I can't be certain until I get a hold of a better map, I am pretty sure that this is indeed one of the clusters that were created in 1930. I would even suggest the entire range 250-262 is the Rochester metro area cluster. --Polaron | Talk 08:13, 28 January 2007 (UTC)
I should also note that in 1927 (and also in some other years) when U.S. Routes were commissioned, renumbering to avoid duplication was also done (i.e. NY 4, NY 6, NY 9, NY 11, NY 20 were decommissioned in 1927; NY 1 became US 1). --Polaron | Talk 08:13, 28 January 2007 (UTC)
Given that so many new routes in these clusters were assigned, do you know when the mileage was added? Did a bunch of it get added right in 1930, or was it a gradual process in the 1930s, and many of these were planned routes? --NE2 08:23, 28 January 2007 (UTC)
The article says that most of these newly designated roads were pre-existing state maintained roads but were simply unmarked at the time. --Polaron | Talk 09:00, 28 January 2007 (UTC)

Welcome Route 747!

Today's Times-Herald Record has a huge center article on the process of upgrading Drury Lane in the towns of Newburgh and New Windsor to provide better access to Stewart Airport via the under-construction Exit 5A on I-84.

I drive this road to work regularly at the moment, and I thought to myself, given what they're doing here I wouldn't be surprised if they made it a state highway. According to this little sidebar, they are ... Orange County Route 54 is going to become New York State Route 747.

Drury Lane is going from County Route 54 to State Route 747 and getting the kind of facelift that befits a state highway that connects an interstate and an airport in the process. When construction is completed this year, the narrow, winding local road — a not-so-secret shortcut for thousands of people seeking to avoid the traffic at Route 17K and Union Avenue — will be transformed into a wide, fairly straight one with red lights and shoulders..

747? For an airport access road? Cute.

I am not sure from the article whether 747 will follow the current Drury Lane to 207 or go along the airport access road from its junction with Drury. The latter routing makes more sense to me. But it looks like the junction list will be fairly simple: 207 as ST, I-84 with a three-quarters diamond interchange (no access from Drury/747 south to 84 west due to wetlands) and the Catskill Aqueduct bridged to protect it.

I will take pictures of the construction to augment what I've already got in the Route 17K article. Could a shield be created (I'll create the article)? Daniel Case 23:02, 11 February 2007 (UTC)

747 for a road going to an airport...clever work by the DOT. The shield is ready to go. (Image:NY-747.svg) --TMF Let's Go Mets - Stats 00:33, 12 February 2007 (UTC)
I hope that the actual shields used on the route are at least close to that, not the odd-looking variants that have sprung up all over the place. Fwgoebel 05:39, 12 February 2007 (UTC)

Section shuffle

Similar to my proposal at WT:IH, I believe that the exit list/major intersection sections should be moved below all prose in the article structure. I have implemented this idea on New York State Route 104, and I believe that it makes the article appear more robust. Thoughts? --TMF Let's Go Mets - Stats 04:53, 6 February 2007 (UTC)

In the time since this comment, I've experimented with a bit of different formatting on New York State Route 104 and New York State Route 531. Most notably, the communities were moved into a separate infobox in the route description (similar to those specified by WP:IH and WP:USH) and a new section, "Future", was created. If no one has any objections, I'll make the changes on the project page to mirror these two articles. --TMF Let's Go Mets - Stats 20:44, 12 February 2007 (UTC)

Replacement of "multiplex"

Who is this Krimpet person replacing all the uses of "multiplex" and derived words like "triplex" and "duplex" in so many articles on the grounds that it's a "neologism"? Is this something that consensus was reached for at the top level of the U.S. Roads project? I sure don't see any discussion of this here, and I don't think the MoS says anything about removing neologisms from articles just for that reason. Daniel Case 19:10, 10 February 2007 (UTC)

I have to concur given that the term "duplex" and "multiplex" is already used in highway websites, including New York Routes (even the term "quadruplex" is there). Playing devil's advocate though, the term "duplex" may be the first notion one conceives when reading/hearing the word, and the word "concurrency" appears on the legend for major intersections. I will note though that at the dab page for duplex, there is already an entry for concurrency (road). On that ground I do not consider the term "Duplex" to be a neologism. For what it's worth, the term "OLAP" (overlap) is used by NYSDOT in records. There should be a consensus first before such a broad scale modification is used, especially for so many articles in a project, and if one exists, it should be cited in each edit. I wonder if this is a back-handed way of getting around how, at one point, all of the highway articles in the nation were threatened for AFD. Fwgoebel 06:01, 11 February 2007 (UTC)
This is being addressed at WT:USRD. --Rschen7754 (talk - contribs) 06:05, 11 February 2007 (UTC)

Junction tables should use "overlap" instead of "concurrency", if nothing else than for space constraints. --TMF Let's Go Mets - Stats 20:44, 12 February 2007 (UTC)

Verification for routes 18C and 18E

I couldn't find confirmation of these in the maps I have. Based on the north-south progression of suffixed routes, 18C should be in Tonawanda and 18E in Lewiston. My guess (and this is only a guess) is that 18C was the portion of 425 between NY 324 and US 62. 425 originally ended at then NY 18 (US 62) in Martinsville and was later extended. Also this thread in misc.transport.road notes that NY 18E used the old Lewiston-Queenston bridge (the one that existed in 1899-1965). If anybody has information on these, we can then have articles for the entire Route 18 family. Thanks. --Polaron | Talk 15:18, 15 February 2007 (UTC)

Static Wikipedia (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - en - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu -

Static Wikipedia 2007 (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - en - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu -

Static Wikipedia 2006 (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu

Static Wikipedia February 2008 (no images)

aa - ab - af - ak - als - am - an - ang - ar - arc - as - ast - av - ay - az - ba - bar - bat_smg - bcl - be - be_x_old - bg - bh - bi - bm - bn - bo - bpy - br - bs - bug - bxr - ca - cbk_zam - cdo - ce - ceb - ch - cho - chr - chy - co - cr - crh - cs - csb - cu - cv - cy - da - de - diq - dsb - dv - dz - ee - el - eml - en - eo - es - et - eu - ext - fa - ff - fi - fiu_vro - fj - fo - fr - frp - fur - fy - ga - gan - gd - gl - glk - gn - got - gu - gv - ha - hak - haw - he - hi - hif - ho - hr - hsb - ht - hu - hy - hz - ia - id - ie - ig - ii - ik - ilo - io - is - it - iu - ja - jbo - jv - ka - kaa - kab - kg - ki - kj - kk - kl - km - kn - ko - kr - ks - ksh - ku - kv - kw - ky - la - lad - lb - lbe - lg - li - lij - lmo - ln - lo - lt - lv - map_bms - mdf - mg - mh - mi - mk - ml - mn - mo - mr - mt - mus - my - myv - mzn - na - nah - nap - nds - nds_nl - ne - new - ng - nl - nn - no - nov - nrm - nv - ny - oc - om - or - os - pa - pag - pam - pap - pdc - pi - pih - pl - pms - ps - pt - qu - quality - rm - rmy - rn - ro - roa_rup - roa_tara - ru - rw - sa - sah - sc - scn - sco - sd - se - sg - sh - si - simple - sk - sl - sm - sn - so - sr - srn - ss - st - stq - su - sv - sw - szl - ta - te - tet - tg - th - ti - tk - tl - tlh - tn - to - tpi - tr - ts - tt - tum - tw - ty - udm - ug - uk - ur - uz - ve - vec - vi - vls - vo - wa - war - wo - wuu - xal - xh - yi - yo - za - zea - zh - zh_classical - zh_min_nan - zh_yue - zu