Wikipedia talk:WikiProject U.S. Roads

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject U.S. Roads (Rated Project-class)
U.S. Roads WikiProject icon This page is within the scope of the U.S. Roads WikiProject, an attempt to build a comprehensive and detailed guide to state highways and other major roads in the United States. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to the discussion.
 Project  This article has been rated as Project-Class on the quality scale.


The most recent version of jctint templates for US states did mainly the following:

  • Assign the state name to |region=.
  • Pass through a parameter to Template:Jctint/core.
  • Rename a parameter to a core parameter.
  • Build a string for a _special parameter that shares the same structure across these templates, only to differ in the state name.

The approach above has several drawbacks:

  • A parameter available in the core module not exposed by these templates becomes unavailable. Parameter additions in the core module do not propagate to these templates automatically.
  • A lot of duplicate template code is difficult to maintain.
  • These templates can only diverge from one another over time. Template users will have to memorize multiple usage when the interface for these templates could have been uniform.

For the past few days, I have converted most of these templates to use Module:Jctint/USA to eliminate the drawbacks above. You might not have seen any observable changes to articles, because you shouldn't! I am happy to report that the module now handles jctint templates for 40 out of the lower 48 states.

Before I can go into what prevents the templates for the remaining 8 states from being converted, I need to go into some technical details about how |sub2_special= was implemented for most states.

|location_special= is used by default. Certain templates permitted multiple locations to be specified as |location1= through |location4=. These parameters are concatenated as a list of wikilinks that is passed to the core module as |sub2_special=. Other templates did the same, but with townships instead of locations (see Interstate 70 in Ohio). The module handles both: |sub2param=township is used in the latter case; location is the default.

Now, why the templates for 8 states haven't been converted:

  • State name is not the correct article link (GA and WA): Road data modules should handle this.
  • Different |sub1name= (LA): Road data modules should handle this.
  • Special handling for |indep_city= (CA, CO, and MD): Road data modules should handle this.
  • Cascading |sub2_special= (MN): A list of both townships and locations are permitted, but the module doesn't support cascading yet, though it can easily be done.
  • |town= (WI): It appears that town articles are not named consistently, e.g., Bristol, Dane County, Wisconsin vs Bristol (town), Kenosha County, Wisconsin. So, I could not decide which one to use.

For more details about handling by road data modules, see Template talk:Jcttop/core#sub1name order for an idea, and Module:Road data/strings/USA/NH for an example. This is a longer-term transition, but I would like to avoid adding a boilerplate in the module when this transition is anticipated. See also Template talk:Jct#Inheritance and overriding in road data modules.

During the conversion, I noticed a beginning of divergence in some of the templates. While most states use |mile_ref=, some use |length_ref=. Specifically, templates for AL, FL, OH, OR, and TX. This parameter should be deprecated and renamed to |mile_ref=.

The module opens up other opportunities for uniformly customizing parameters for US junctions, e.g., cascading (above) and support for a list of cities. Additional customizations will not be implemented until there is evidence that they are useful for multiple states.

The templates are still fully backward compatible with the previous version, but the module might have added new features, e.g., list of locations, to some states' templates. These features have already been used in several other states' templates. I hope it is okay for every state's template to have the same leverage.

Of course, if you see any undesirable, observable changes, I will appreciate your report so I can troubleshoot. Constructive comments will also be appreciated. Chinissai (talk) 15:45, 17 May 2016 (UTC)

Illinois has a mix of townships and precincts. There is no pattern that I can tell for which county uses which subdivision. –Fredddie 16:45, 17 May 2016 (UTC)
Interesting. I didn't see any use of precincts in jctint as a separate parameter, so I was able to convert {{ILint}} without trouble. The module should be able to support future customization for precincts, though, perhaps by using switch tables in road data modules. Chinissai (talk) 17:08, 17 May 2016 (UTC)
California has the funny postmiles stuff - is this properly supported? --Rschen7754 18:20, 17 May 2016 (UTC)
Yes, any "funny" parameters can be overridden by passing them to the module. See Template:ORint for example. It's only San Francisco that prevents me from converting CAint. Chinissai (talk) 18:46, 17 May 2016 (UTC)
On a side note, North Carolina has townships, but most, if not all, of the links don't exist, even as redirects. Charlotte Allison (Morriswa) (talk) 21:08, 17 May 2016 (UTC)

Tolls update[edit]

Hello everyone, A helpee in IRC help channel suggested that the information on tolls on articles: Florida State Road 408, Florida State Road 417, Florida State Road 429 are very old and need to be updated. Since I am unfamiliar with the information about tolls, could any of you guys have a look? Thanks! ‐‐1997kB (talk) 12:15, 9 February 2019 (UTC)

I don't have time to fix them myself, but this document has the updated toll rates for the Central Florida Expressway Authority tollways (near Orlando). -happy5214 01:34, 10 February 2019 (UTC)

Pelham Parkway[edit]

Some concerns over the neutrality of the above article were raised on my talk page here (I'll leave it when I archive on Friday). The OP's concerns appear, at least to my uninformed eye, to have some merit. I'm asking that any of you with interest or knowledge that would be pertinent to maybe look there with an eye to help. The OP was going to start a talk thread there, but doesn't seem to have done so yet. Thanks. John from Idegon (talk) 01:43, 28 February 2019 (UTC)

My mistake. I was working on other issues on the web, let alone Wikipedia, but the thought of the biased tone of that article never left my mind. ---------User:DanTD (talk) 04:52, 3 March 2019 (UTC)

Natcher parkway in Kentucky is now I-165[edit]

As of today, I-165 signs are being placed on the Natcher Parkway in Kentucky.[1] I just started updating relevant pages. Needforspeed888 (talk) 01:36, 7 March 2019 (UTC)

Please exercise caution, Needforspeed888. First off, not all of the parkway is being resigned as I-165. Additionally, you need to observe the legal technicalities about copying content between articles on Wikipedia, namely linking the right article (not a redirect) in your edit summary. Please slow down and discuss first before jumping the gun on mergers/renames/etc. Imzadi 1979  01:45, 7 March 2019 (UTC)
Another thing to note: is the name being totally retired from the I-165 section? If not, it would improper to remove the parkway name from other articles on intersecting highways. Until that question is settled, it's a bit premature to just change articles. Again, we need to exercise caution. Imzadi 1979  01:52, 7 March 2019 (UTC)


  1. ^ Missing or empty |title= (help)
It said in the article that it was being renamed, "William H. Natcher Expressway," as I put in the alt name slot.Needforspeed888 (talk) 02:01, 7 March 2019 (UTC)


Just an fyi, my watchlist is getting pretty clogged, I'm going to gradually start unfollowing non-ohio highways and such. Cards84664 (talk) 05:30, 8 March 2019 (UTC)

Cards84664: It's not clogged if you can still remove entries.  Nova Crystallis (Talk) 05:32, 8 March 2019 (UTC)

New article for TOTSO?[edit]

While browsing through the Glossary of road transport terms, (which I added a few terms to), I noticed that we don't currently have an article for Turn-off-to-stay-on (TOTSO), those scenarios where you have to exit to stay on the same highway. I think this would be a great addition to this Wikiproject, as we have a lot of examples here in the US. What do you all think? Needforspeed888 (talk) 19:06, 10 March 2019 (UTC)

It only makes sense to create an article if we can talk about it in depth and not merely list off places where this occurs. I don't think we can, so I do not support creating an article. –Fredddie 02:56, 11 March 2019 (UTC)
I agree, unless we have something like concurrency (road) that is more than just examples. Maybe you can take a stab at Draft:Turn-off-to-stay-on to see what shakes out, Needforspeed888? Imzadi 1979  03:09, 11 March 2019 (UTC)
Perhaps make it a separate section of Interchange (road)? Just a thought. Highway 89 (talk) 03:30, 11 March 2019 (UTC)
I think an article and listing examples of this occurrence is trivial and really not needed. Dough4872 04:11, 11 March 2019 (UTC)

Did I do the KML file right?[edit]

So, I haven't made a KML file in years, and after reading that you could seemingly easily create great quality KML files from Google Maps, I was interested in helping again. I made one for a small-ish route, Kentucky Route 399, at Template:Attached KML/Kentucky Route 399. In the article, the OSM map looks fine, but the template itself looks like a complete disaster, at least compared to other KML templates I made years prior, like Template:Attached KML/U.S. Virgin Islands Highway 38. Did I do something wrong? --AmaryllisGardener talk 01:27, 14 March 2019 (UTC)

AmaryllisGardener: Looks like you did.  Nova Crystallis (Talk) 02:09, 14 March 2019 (UTC)
I've gone ahead and removed some of the offending pararmeters to clean up the looks of the code. It still functioned properly, so it should be all good. SounderBruce 03:13, 14 March 2019 (UTC)
@SounderBruce: Thank you! --AmaryllisGardener talk 04:46, 14 March 2019 (UTC)

Comment: Since Google and Bing removed their ability to show KMLs on their map platforms, I would suggest in addition to creating and placing the KML files to create the "interactive map" for these articles as well. Pennsylvania Route 155 is an article where I created one recently with the code for it located at Wikipedia:Map data/Wikipedia KML/Pennsylvania Route 155. You can almost take the code from there, swap out the new coordinates (making sure each point has enclosed brackets "[x, y], ...") and name and post. The centroid coordinates of the route can easily be found from clicking for WikiMiniAtlas in the top right corner, hitting the fullscreen button, and getting the lat/long from the URL of the popup window. This would then help reduce our maps backlog too. —Mr. Matté (Talk/Contrib) 13:43, 15 March 2019 (UTC)

I've made a userscript User:Evad37/kmlToJson you can install to convert Attached KML subpages into JSON map data (the format used bu the "interactive maps") - Evad37 [talk] 23:16, 15 March 2019 (UTC)

Disambiguating locations in top templates[edit]

How do we disambiguate locations in the {{Jcttop}} template (and sub templates)? Some of the newly-made Kansas highway articles, using {{KSinttop}}, are entirely within Grand River Township, Sedgwick County, Kansas, but the template links to Grand River Township, Kansas (which doesn't exist). Thank you. Morriswa (Charlotte Allison) (talk) 00:22, 20 March 2019 (UTC)