Open main menu

Wikipedia talk:WikiProject U.S. Roads

Active discussions
WikiProject U.S. Roads (Rated Project-class)
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.

Module:Jctint/USAEdit

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)


MfD nomination of Portal:Maryland roadsEdit

  Portal:Maryland roads, a page which you created or substantially contributed to, has been nominated for deletion. Your opinions on the matter are welcome; you may participate in the discussion by adding your comments at Wikipedia:Miscellany for deletion/Portal:Maryland roads and please be sure to sign your comments with four tildes (~~~~). You are free to edit the content of Portal:Maryland roads during the discussion but should not remove the miscellany for deletion template from the top of the page; such a removal will not end the deletion discussion. Thank you. Guilherme Burn (talk) 17:08, 14 November 2019 (UTC)

Interstate 335 disambiguation pageEdit

User:Georgia guy turned the Interstate 335 disambiguation page into a redirect to Kansas Turnpike#Emporia to Topeka. I reverted his edit, but he reverted it back. I don't want to cause an edit war. What is the project's opinion on this? Interstate 335 (Minnesota) was a proposed highway, so there could be a disambiguation page. If not, put a hatnote on each page. Morriswa (Charlotte Allison) (talk) 11:12, 21 November 2019 (UTC)

In contrast, Interstate 335 in Kansas is a current, official, and signed highway. Georgia guy (talk) 11:18, 21 November 2019 (UTC)
Precedent can be found with Interstate 494 and Interstate 494 (disambiguation). –Fredddie 21:50, 21 November 2019 (UTC)

Deletion discussions on CommonsEdit

In case anyone here has any comments, see commons:Commons:Deletion requests/File:County 15.png 2 and commons:Commons:Deletion requests/File:County 20.png 2. --Sable232 (talk) 00:01, 6 December 2019 (UTC)

List of highways bypassed by Interstate HighwaysEdit

I have restored List of highways bypassed by Interstate Highways to Wikipedia:WikiProject U.S. Roads/List of highways bypassed by Interstate Highways as requested by User:WikiWarrior9919 and suggested by others. Graeme Bartlett (talk) 21:23, 6 December 2019 (UTC)

What is the intended purpose of this list? Pretty hard to make this into an encyclopedia article when the transition from US Highways to Interstate Highways took 30 years with numerous interim changes during that time. To make this list manageable, we'd have to pick an arbitrary day. (For example for decommissioned highways most USRD articles use the definition of the highway on the day it was decommissioned, unless otherwise stated). Dave (talk) 03:16, 10 December 2019 (UTC)

U.S. Route 422Edit

The U.S. Route 422 article is showing an error message “The time allocated for running scripts has expired” all over the article in place of the infobox and major intersections. Dough4872 02:46, 10 December 2019 (UTC)

likely a syntax error introduced with recent edits, as older versions display properly [1]. I'd comb through the history between this revision and now and see if there's any malformed syntax introduced. Dave (talk) 03:01, 10 December 2019 (UTC)
Apparently I did a null edit and it looks fine now. Dough4872 03:02, 10 December 2019 (UTC)

Auxiliary route parameter for Pennsylvania state routesEdit

I know we use the auxiliary route parameter in the infobox for three-digit Interstate and US routes to indicate what route they are an auxiliary route of. For example, U.S. Route 113 indicates that it is an US 13 in the infobox. In Pennsylvania, there are several three-digit state routes that are auxiliary routes of two-digit state routes both past and present. For example, Pennsylvania Route 332 is related to Pennsylvania Route 32 and Pennsylvania Route 662 is related to the former Pennsylvania Route 62 (now Pennsylvania Route 100). Not all three-digit Pennsylvania state routes are related to a two-digit route. For example, Pennsylvania Route 863 was numbered to provide a connection to I-78 and is not related to Pennsylvania Route 63. Should we use the auxiliary route parameter for three-digit Pennsylvania state routes that are related to a two-digit route? Dough4872 01:55, 11 December 2019 (UTC)

Glendora CurveEdit

Hello! I just removed what seemed like a grossly invalid CSD tag (the subject was invented/coined/discovered by the article's creator or someone they know personally, and does not credibly indicate why its subject is important or significant) from Glendora Curve given there is a clear place name notability claim; it's even linked from California State Route 57. I also improved the stub a bit while there...don't know much about roads, but I hope I did the right thing! Thanks, PK650 (talk) 03:27, 11 December 2019 (UTC)

That does not look like that notable enough of an interchange to sustain its own article. The details can easily be covered in the I-210 and CA 57 articles. Dough4872 04:13, 11 December 2019 (UTC)
+1. It's officially designated somewhere, but California has hundreds of these such names. Google doesn't come up with a lot of results either. --Rschen7754 07:55, 11 December 2019 (UTC)
I know what the Glendora curve was (it no longer exists), but to me its no more notable than the Durango Curve (a similar situation in the Phoenix Freeway System, except the history is reversed. While the Glendora curve was eliminated and made into a fly-over ramp when a connecting freeway was built, the Durango curve started as a fly-over ramp and was converted to a curve when its connecting freeway segment was cancelled) or any number of unnamed similar examples, including a very similar situation to the Glendora curve at the intersection of I-215 (Utah) and SR-67 in Salt Lake City, and the similar in function but different history I-280/I-680 transition in San Jose. To my knowledge the Glendora curve is the only such instance to have a Wikipedia article, despite numerous examples existing in the USA, much less the world. IMHO, it merits a mention in the history section of the I-210 and/or CA-57 articles and nothing more. Dave (talk) 13:52, 11 December 2019 (UTC)
Whatever you think is best! I just wanted to know if my withdrawal of the CSD tag was justified, as it seemed to me that being an actual place was, in fact, a notability claim. Pedantic, perhaps... PK650 (talk) 01:29, 12 December 2019 (UTC)
Return to the project page "WikiProject U.S. Roads".