WikiProject U.S. Roads | (Rated Project-class) | ||||
---|---|---|---|---|---|
|
Module:Jctint/USA
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)
- 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)
- California has the funny postmiles stuff - is this properly supported? --Rschen7754 18:20, 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)
Whatever happened to this? I ask because Module:Infobox road/sandbox2 got nominated for deletion. --Rschen7754 03:50, 29 September 2020 (UTC)
- @Rschen7754: Chinissai hasn't edited since mid-2017. That's what happened. –Fredddie™ 04:38, 21 April 2021 (UTC)
Peer review request
I have requested a peer review for Atlantic City–Brigantine Connector, which is currently an A-Class article, and I plan to nominate it for FA soon. You can find the peer review at Wikipedia:Peer review/Atlantic City–Brigantine Connector/archive2. I'd appreciate any feedback! –Dream out loud (talk) 08:29, 2 August 2022 (UTC)
Interstate 87 exit list request
Interstate 87 (North Carolina) currently does not have the "future" exits in the exit list. If anyone has the time or can do it quick, I would greatly appreciate it! Thank you and have a great day!
I-87 Exit list from malmeroads.net
Thanks again! DiscoA340 (talk) 22:37, 7 August 2022 (UTC)
- @DiscoA340: Template:Sofixit, but also - are you asking us to use a WP:SPS to source this information? --Rschen7754 04:54, 8 August 2022 (UTC)
- Should be noted the website, which is WP:SPS, says "Potential Future Exit Number" not official with sources or anything. Sorry, but we cannot be speculative on this. --WashuOtaku (talk) 04:57, 8 August 2022 (UTC)
Does NCDOT have signing plans online? That would give it some authority. –Fredddie™ 06:31, 8 August 2022 (UTC)
- I understand the issue of it being self-published. I do know that there are five sections on the route that are already graded, 1. From the current eastern terminus I-87 to US-64 in Williamston, 2. Windsor Bypass, 3. Edenton Bypass, 4. Elizabeth City Bypass, and 5. VA 166 to I-64. I was able to find the Final Feasibility report by the NCDOT that lists out the route segments in NC starting Page 16. Thanks and have a good day! DiscoA340 (talk) 00:17, 9 August 2022 (UTC)
Infobox road update
This is just for the US for now, so I'm posting here instead of Template talk:Infobox road.
|subtype=
is dead
Use US-Bus
instead of |type=US
|subtype=Bus
going forward. –Fredddie™ 03:16, 8 August 2022 (UTC)
- Imzadi1979 likes this. Thank you for making this happen. Imzadi 1979 → 03:28, 8 August 2022 (UTC)
US 25 in Ohio accuracy
Task Forces
How many task forces are there 2600:1700:6180:6290:24FD:8ADE:56DE:6D19 (talk) 00:40, 15 August 2022 (UTC)
- There are:
- 1 each for Interstates, US Highways, Auto trails, county roads, junctions and US 66 (6)
- 50 more, one for each state
- 1 for DC
- 1 for Puerto Rico
- 1 more jointly for the remaining territories (AS, GU, MP and VI)
- Do the math, and that makes 59 total. Mostly though, they're statistical subdivisions now.
- Additionally, there are five Departments: Assessment, Maps, Newsletter, Resources, and Shields that provide additional support across all of the project. Imzadi 1979 → 00:54, 15 August 2022 (UTC)
Jct updates
You may have noticed that {{jct}} now displays directional banner plate graphics. This is part of an update being discussed at Template talk:Jct#Template updates that includes other features. Please join the conversation over there. Imzadi 1979 → 21:03, 15 August 2022 (UTC)
Tennessee state route maps
I see that Jk00190 has created maps for several Tennessee state routes (for example, File:TN_SR_53.jpg for Tennessee State Route 53). While KMLs would be ideal, having some sort of map is better than nothing, but ideally these should be in a vector format rather than as JPEGs. Does anyone with the time and resources have an efficient way to batch-convert these to SVG, while also updating the colors, etc., so that they would match the maps present at other route articles, or would creating the needed KML files be faster and ideal? Thanks. --Kinu t/c 02:46, 21 August 2022 (UTC)