Template talk:Routelist row/Archive 1

Disambiguation

Resolved

 – |dab= added

On Draft:1969 Iowa highway renumbering, I need to create the link Iowa Highway 23 (1969–1997). How would I go about doing that? –Fredddie™ 03:11, 26 May 2013 (UTC)

Feature request

Establishment and decommissioning date references. It seems that if you put a reference right after a date, you are thrown a script error. –Fredddie™ 03:01, 8 November 2013 (UTC)

Do you want those in the cells, the header, or both? -happy5214 08:38, 8 November 2013 (UTC)

It would probably be best to have the option to put them both places, so that if you are getting all information from one source, you can stick the ref in the header, and if you are using a different source for each row, you can stick it there. —Scott5114↗ [EXACT CHANGE ONLY] 09:39, 8 November 2013 (UTC)

 Done for {{routelist row}}. {{routelist top}} still needs to be modified. -happy5214 11:08, 11 November 2013 (UTC)

Curious sorting issue

On User:Fredddie/List_of_Iowa_state_highways, I wanted to sort by formed year and look what happens. The four entries that use |beltway= are at the top of the list. –Fredddie™ 03:59, 4 December 2013 (UTC)

From Help:Sorting:

Javascript sorting may not work properly on tables with cells extending over multiple rows and/or columns (however, sorting of columns up to and including the first with colspan does not seem to be affected).

So it doesn't look like it's an issue with this template. -happy5214 07:08, 4 December 2013 (UTC)

Behavior may also vary from browser to browser. —Scott5114↗ [EXACT CHANGE ONLY] 22:09, 4 December 2013 (UTC)

Even different reloads in my browser can yield different results. -happy5214 04:20, 5 December 2013 (UTC)

Negative lengths

On Draft:1969 Iowa highway renumbering, I am trying to show how Iowa 64 lost a big chunk of mileage during the renumbering. I would like to use a negative length in |length_mi=. It works, but not according to the MoS.

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed	Notes
Iowa 64	-272	−438	US 151 in Anamosa	US 52 / IL 64 at the Illinois state line	—	—	Shortened in 1969

272 miles does convert to 438 km, so the conversion itself is correct, but they should read −272 and −438 using − instead of a hyphen. This isn't a life or death situation, but it would be an issue at FLC. –Fredddie™ 18:33, 17 January 2014 (UTC)

Now that {{Convert}} is on Lua, could we invoke that module instead? Or do we have our own because of the need for in-cell refs? –Fredddie™ 18:35, 17 January 2014 (UTC)

Regardless of the template/MOS implications, is this the best way to convey this? I would interpret the row as reading that IA 64 itself had a negative length (maybe due to being mileposted in reverse). I think it may be better to stray from the route list standard for this sort of page in favor of some other format that can convey this with greater clarity. —Scott5114↗ [EXACT CHANGE ONLY] 23:30, 17 January 2014 (UTC)

row headers

The cells with the highway number should be set up to be a row header, just as the mileposts do in {{jctint}}. This will be an issue at a future FLC. I've already updated the {{routelist top}} so that the headers won't be in bold. Imzadi 1979 → 01:36, 21 March 2014 (UTC)

color keys for footer

I posted at Template talk:Routelist bottom looking for input on potentially adding color keys to the bottom of routelist tables. -- LJ ↗ 23:37, 29 March 2014 (UTC)

Sorting

We're going to need to fix the sorting issue at some point relatively soon. List of Interstate Highways in Michigan is at WP:HWY/ACR, and it is bound for WP:FLC afterwards.

1. A |sort= parameter is added allowing an editor to manually specify the sort key to be used. This is probably the easiest, but it allows for errors if editors don't set something for each row.
2. The sort key is automatically generated by the |route= parameter, padded with leading zeroes to make a four- or five-digit number. There could be issues though with repeated numbers, like the two I-196s or the multiple BL I-75s. A |sort= parameter may still be needed to allow the order to be customized; in the case of the multiple BL I-75, |sort=a could generate 0075a as the key, allowing it to be sorted first before a 0075b, etc.

Ideally, a reader can resort the table by another column, and then he or she can sort again by the number to get back to the original order presented. Failure to do so may keep a list from passing FLC. Thoughts? Imzadi 1979 → 08:05, 12 April 2014 (UTC)

As far as I know, both explicit sort keys and route number-based keys are already supported. I'm not exactly sure what you're asking for. -happy5214 20:13, 12 April 2014 (UTC)

If they are, there is no documentation on how to override the sorting, which just doesn't work right on List of Interstate Highways in Michigan. Imzadi 1979 → 21:57, 12 April 2014 (UTC)

Looks like it's sortkey=. (I never added this to the documentation because when I wrote the docs it was still on the to-do list.) Try that. —Scott5114↗ [EXACT CHANGE ONLY] 22:03, 12 April 2014 (UTC)

An interesting consequence of the sortkey including the type code is that states which use different types to denote former highways (i.e. types which use older shield designs) will have those types sorted separately. See List of Oklahoma numbered highways, and note how the sorting separates the highways by type first and by number second. Presumably this behavior is undesirable, since if anyone really wanted just the old highways they would sort by decommissioned date. —Scott5114↗ [EXACT CHANGE ONLY] 23:35, 17 April 2014 (UTC)

Another issue, this time with the year columns...sortkeys consisting of just the year need to be generated when the circa flag is turned on to avoid sorting all of the circas separately. —Scott5114↗ [EXACT CHANGE ONLY] 23:50, 17 April 2014 (UTC)

Bumping thread. –Fredddie™ 03:57, 22 November 2014 (UTC)

Would it be a good idea to switch the order of the sortkey so the number is first? Right now it's <type><padded number>, so State Highway 1 would have SH0001 as the sortkey. Would 0001SH would better? –Fredddie™ 03:57, 22 November 2014 (UTC)

I'd support that. It would mean that sorting wouldn't separate highway types, but a routelist generally shouldn't include highways of multiple types anyway. —Scott5114↗ [EXACT CHANGE ONLY] 19:04, 22 November 2014 (UTC)

I don't think there's any loss in that. It's the most frustrating to me when I click on the route column to sort it and it doesn't sort by number. –Fredddie™ 19:39, 22 November 2014 (UTC)

The sandbox now has this sorting behavior. The sort key is derived from the abbreviation being displayed, and does not include the route type itself. Anything before a number is moved to the end in the sort key. Chinissai (talk) 11:48, 30 April 2016 (UTC)

Glitch in List of U.S. Highways in Louisiana

Hey all, Just letting you know that something seems to be broken with the routelist row template on the aforementioned page. All the links in the mainline route section are all redlinked, and hovering over them changes the route number to "%route&". Take a look when you have a moment. 25or6to4 (talk) 21:55, 1 May 2014 (UTC)

 Fixed There was a typo in the data module. -happy5214 22:35, 1 May 2014 (UTC)

localnames not working?

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Local names	Formed	Removed	Notes
CR 601	0.63	1.01	CR 602 in Blairstown	CR 521 in Blairstown	—	—

As you can see, |localnames=High Street does not seem to be working in this example. –Fredddie™ 06:50, 10 June 2014 (UTC)

Try this: -happy5214 07:18, 10 June 2014 (UTC)

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Local names	Formed	Removed	Notes
CR 601	0.63	1.01	CR 602 in Blairstown	CR 521 in Blairstown	High Street	—	—

You might want to add that to the doc. Localnames is there currently. –Fredddie™ 16:11, 10 June 2014 (UTC)

Circa dates

It seems to me that some efficiency could be gained by better utilizing {{{circa_established}}} and {{{circa_decommissioned}}}. Currently, to trigger circa, you have to type out:

|established=1926
|decommissioned=1980
|circa_decommissioned=yes

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed	Notes
US 16	—	—	US 16 towards Sioux Falls, SD	US 61/US 14/US 16 towards La Crosse, WI	01926-01-011926	01980-01-01c. 1980

Whereas, I think it would be simpler, and more logical to use

|established=1926
|circa_decommissioned=1980

Then, when you find the actual date, you just remove the circa and you're good to go. –Fredddie™ 20:05, 14 June 2014 (UTC)

I've noticed that circa dates don't sort properly. The circa dates in a table seem to bunch together separately between regular dates and 'current' entries, almost as if the dates are sorting with the "c." in front. -- LJ ↗ 22:24, 14 June 2014 (UTC)

Bumping this; there's a parameter option|sortable=yes in {{circa}} to resolve the sorting issue. Imzadi 1979 → 21:58, 21 February 2016 (UTC)

The sandbox now sorts circa dates correctly. Chinissai (talk) 13:09, 30 April 2016 (UTC)

Default type=state?

The most common use of this is for state highways, so why not default the type parameter to the state if none is specified? --NE2 08:51, 23 November 2014 (UTC)

Problem with length_km parameter

Hello,

When I try to add the length_km parameter, it throws an error: Lua error in Module:Routelist_row at line 157: attempt to concatenate local 'first' (a nil value).. TheWombatGuru (talk) 01:10, 20 December 2014 (UTC)

@TheWombatGuru: row 157 sounds like the error I was having with List of toll roads in Texas, and that's there it's trying to concatenate the values together to make the sort key. It has nothing to do with the length parameter. In short, if |route= doesn't have a numerical value, you need to supply a |sortkey= to clear the error. A suffixed number will work, as in |route=183A, but |route=CTP would not. Imzadi 1979 → 02:21, 20 December 2014 (UTC)

@Imzadi1979:, I understand why |route=CTP might not work, but why doesn't |route=19 work? TheWombatGuru (talk) 09:15, 20 December 2014 (UTC)

Facepalm Because the adjusted-precision kilometer measurement was being assigned to the mile value in the function's length table. All fixed now, and I converted the measurements in the E-road list to kilometers for you. -happy5214 10:47, 20 December 2014 (UTC)

@Imzadi1979 and Happy5214:, thanks! :-) TheWombatGuru (talk) 11:12, 20 December 2014 (UTC)

Help with adding new column

I added a State(s) column to {{Routelist top}}, but how do I add it on this template?

First it would help to start a discussion to gain consensus for doing so. I'll bite. What benefit is there to adding a state column? –Fredddie™ 04:26, 14 January 2015 (UTC)

Considering that this template, and its brethren, is designed to implement WP:USRD/STDS/L, I'd be of the opinion that the guideline should be amended to allow the column before the templates are altered. To that end, I agree with Fredddie's core question: what's the benefit? Imzadi 1979 → 05:06, 14 January 2015 (UTC)

Shields request

Pennsylvania has some state routes which were decommissioned in the late 20s or early 30s and have never been revived because of conflicts with US or Interstate routes. For these routes, we've been using the 1926 version of the shields. For example, we use this shield, instead of , for PA 2. Is there a way for this template to incorporate these for decommissioned routes from that era? --hmich176 11:08, 4 March 2015 (UTC)

This template uses the exact same types as {{Jct}}. That being said, the PA road data module provides a list of all available types that can be used. PA["SR 1926"] and PA["PA 1926"] are on the list, so "SR 1926" and "PA 1926" may be used interchangeably as a type. –Fredddie™ 16:10, 4 March 2015 (UTC)

Ah! I wasn't using the proper type...I was attempting to plug in PA-old, which obviously didn't work. Thanks for clearing that up for me! I'm still fairly unfamiliar with Lua modules, since they've been in development during times I haven't been editing much. --hmich176 22:12, 4 March 2015 (UTC)

Yeah, we've tried to do away with the XX-old types because they are not very useful when a state, like Pennsylvania, has used more than one version of shield over the years. –Fredddie™ 23:02, 4 March 2015 (UTC)

Aliases

So other templates use either |established= or |formed= and either |deleted= or |decommissioned= when dealing with years. It would help if this template had the appropriate aliases as well. Imzadi 1979 → 23:44, 16 March 2015 (UTC)

Null length value

Is it possible for items where length_mi or length_km is nonexistent or is invoked but without a value (ie |length_mi=) to not display a value? Currently, a 0 is displayed in such cases but this is not necessarily (well, never) true for routes, be it past, present, or future. —Mr. Matté (^Talk/_Contrib) 00:14, 21 June 2015 (UTC)

Could you please provide an example where this is an issue? -happy5214 00:53, 21 June 2015 (UTC)

While it's not on templates at this time, Interstate 487's entry on List of Interstate Highways in New York is a good example. –Fredddie™ 00:58, 21 June 2015 (UTC)

See List of State Routes in Nevada for several examples on templates - SR 166 & SR 167 (mileage not available when I converted the list), SR 439 (future route to be completed by NDOT, exact length as yet unknown), among a few others on the page. -- LJ ↗ 08:35, 21 June 2015 (UTC)

The sandbox now displays an em-dash instead of a 0 when the parameter is missing or passed without a value, but will continue to display 0 if |length_mi=0. Is that suitable? -happy5214 04:16, 22 June 2015 (UTC)

Seems reasonable to me. -- LJ ↗ 07:08, 25 June 2015 (UTC)

@Mr. Matté: Fine for you? -happy5214 01:20, 27 June 2015 (UTC)

Seems fine to me. —Mr. Matté (^Talk/_Contrib) 01:29, 27 June 2015 (UTC)

 Done -happy5214 22:28, 27 June 2015 (UTC)

Error while editing New Jersey State Highways

When I add routes like route S1, the error occurs. -Alexlatham96

I'll look at it in a little while. I've reverted the broken table for the time being. –Fredddie™ 18:35, 29 April 2016 (UTC)

@Alexlatham96: I have a workaround that you can use. –Fredddie™ 23:12, 29 April 2016 (UTC)

{{Routelist row
|state=NJ
|type=SRS 1926
|route=1
|length_mi=
|terminus_a=
|terminus_b=
|established=1927
|decommissioned=1953
}}

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed
Route S1	—	—	—	—	01927-01-011927	01953-01-011953

That's a bug in the live version. The sandbox has this working correctly, although the sort key might need to be worked out:

{{Routelist row/sandbox
|state=NJ
|type=SR 1926
|route=S1
|length_mi=
|terminus_a=
|terminus_b=
|established=1927
|decommissioned=1953
}}

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed
Route S1	—	—	—	—	01927-01-011927	01953-01-011953

Chinissai (talk) 00:27, 30 April 2016 (UTC)

+1 Switching to this will be as simple as a find and replace once the sandbox goes live. –Fredddie™ 05:38, 30 April 2016 (UTC)

List of state highways in Colorado

I can't get the dab= field to work on SH 76 :-( (Redirect page Colorado State Highway 76 (1923-1976) looks the best option.) Narky Blert (talk) 16:24, 4 November 2016 (UTC)

@Narky Blert: that was because Module:Road data/strings/USA/CO didn't have a way to apply a disambiguation term to the link generated by this template in that list. I've added the missing snippet of code. In short, that module, or one like it, is used to generate the links, abbreviations, and marker graphics for this template, {{jct}} and parts of {{infobox road}}, and if a module doesn't know where to insert a dab item, no dab item can ever be inserted. Imzadi 1979 → 19:36, 4 November 2016 (UTC)

"dab" parameter not working

According to the template documentation, the following code should create disambiguated links for the two (former) I-410s in Louisiana; but it doesn't work:

{{routelist row |state=LA |type=I |route=410 |dab=Baton Rouge |sortkey=10Louisiana-4 |length_mi=1.90 |terminus_a=[[Louisiana Highway 67|LA 67]] in [[Baton Rouge, Louisiana|Baton Rouge]] |terminus_b=I-10 in Baton Rouge |established=1961 |established_ref= |circa_established= |decommissioned=1964 |decommissioned_ref= |circa_decommissioned= |notes=Renumbered as I-110 }} {{routelist row |state=LA |type=I |route=410 |dab=New Orleans |sortkey=10Louisiana-4 |length_mi= |terminus_a=I-10 west of [[New Orleans, Louisiana|New Orleans]] |terminus_b=I-10 in [[Eastern New Orleans]] |established=1969 |established_ref= |circa_established= |decommissioned=1977 |decommissioned_ref= |circa_decommissioned= |notes=Cancelled southern bypass of New Orleans }}

The actual output is below; both of the links in the first column point to the same disambiguation page (via the redirect Interstate 410 (Louisiana).

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed	Notes
I-410	1.90	3.06	LA 67 in Baton Rouge	I-10 in Baton Rouge	01961-01-011961	01964-01-011964	Renumbered as I-110
I-410	—	—	I-10 west of New Orleans	I-10 in Eastern New Orleans	01969-01-011969	01977-01-011977	Cancelled southern bypass of New Orleans

Please fix. --R'n'B (call me Russ) 19:37, 18 January 2018 (UTC)

@R'n'B: that should now work. This template uses the same modules as {{jct}}, in this case Module:Road data/strings/USA/LA, so if a link can't be disambiguated with jct, it can't be disambiguated here. Imzadi 1979 → 19:51, 18 January 2018 (UTC)

Auto disambiguation

I'd like to suggest |dab=auto for instances only where there are values in |established= and |decommissioned=. By and large, we use numeric disambiguators, so it seems redundant to type out the dates twice. It could use the same logic that strips the dates down to display only the years for this. –Fredddie™ 19:34, 15 June 2019 (UTC)

{{routelist row
|state=UT
|type=UT 1966
|route=187
|dab=auto
|length_mi=
|terminus_a=[[U.S. Route 91 in Utah|US-91]] in [[Draper, Utah|Draper]]
|terminus_b=[[Utah State Prison]]
|established=1941
|decommissioned=1969
|notes=Renumbered SR-287
}}

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed	Notes
SR-187	—	—	US-91 in Draper	Utah State Prison	01941-01-011941	01969-01-011969	Renumbered SR-287

Displaying full dates, hiding removed column

I know in many cases years are the best available infomation... but in my particular jurisdiction, I have specific dates for a good 80%+ of the routes at List of provincial highways in Ontario. Is there an option to display full dates, or any thought towards making this possible (I'm curious why it was decided to limit the display to the year)? Secondly, to avoid absolutely massive tables (seeing as there are a good 500 routes, past and present in Ontario), there is one page for current highways and one for past highways. The "removed" column is redundant in the current tables and would also free up space to display the above referenced full mdy dates. It would be nice to have a value of, say "|decomissioned=NA", that would prevent that cell from generating. (Note I brought this up at Template_talk:Routelist_top, but I'm guessing that page isn't heavily watched) - Floydian ^τ _¢ 16:07, 9 February 2021 (UTC)

Template-protected edit request on 13 March 2021

On List of Interstate Highways#Alaska, it is showing normal Interstate shields. Please fix this. Thanks! -³²²UbnBr₂ (Talk | Contributions | Actions) 03:17, 13 March 2021 (UTC) -³²²UbnBr₂ (Talk | Contributions | Actions) 03:17, 13 March 2021 (UTC)

It's not this template. Each US state has a Lua module used by this template, {{jct}} and others to set up which graphics to use. Module:Road data/strings/USA/AK updated to use the other graphics. Imzadi 1979 → 03:23, 13 March 2021 (UTC)

Routelist template error in List of named state highways in Oregon

There is an error in the Routelist top template in the List of named state highways in Oregon#List of state highways article, exposing the text "[[File:|x25px|alt=|link=]]" in the leftmost Highway column. I don't know enough about this template to resolve the issue. We'd appreciate it if someone could take a look at this and resolve the issue, whether it's an error in the template itself or in the way it's used in the article.

I posted the above on Wikipedia:Help desk and got the following response, so I am posting it here in hopes that someone can fix it. Thanks, Truthanado (talk) 21:42, 8 June 2021 (UTC)

Hello, Truthanado. Looking at other articles which use the template {{Routelist row}}, it is clear that the first column is supposed to contain an automatically generated highway symbol. Presumably somewhere down under the template (presumably in Module:Routelist row) there's something that needs to know the format of Oregon highway badges and hasn't been told. I suggest posting at Template talk:Routelist row. --ColinFine (talk) 18:03, 8 June 2021 (UTC)

Thanks for the heads up. In this case, it's not supposed to produce an image. I will look into it. –Fredddie™ 01:39, 9 June 2021 (UTC)

Thanks for the temporary fix in the article. I'm always interested in learning more about Wiki templates and their use and would like to to see what a permanent fix might be. I'll keep monitoring this. Truthanado (talk) 16:40, 11 June 2021 (UTC)

Pacific Highway No. 1
Route information
Maintenance	ODOT
Location
Country	United States
State	Oregon
Highway system
Oregon Highways Interstate US State Named Scenic

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed	Notes
Pacific Highway No. 1	—	—	Pacific Highway No. 1	—	—	—	Live version
Pacific Highway No. 1	—	—	Pacific Highway No. 1	—	—	—	Sandbox version
Pacific Highway No. 1	—	—	Pacific Highway No. 1	—	—	—	Sandbox version

I'll have to dig deeper. Like I mentioned, it's not supposed to create an image and certainly didn't when I converted the list to this format last year. In the different templates that use the same route information code as this template, this is the only one that does this. –Fredddie™ 18:35, 11 June 2021 (UTC)

Use shieldmain for route number

The shield listed next to the route name under the "Number" column should use shieldmain and shield as a fallback instead of just shield. It is more appropriate to use shieldmain for this template as shieldmain is meant to be the shield that better represents the highway/road, hence why it is used by {{Infobox road}} for the shield image in the infobox.

The code at Module:Routelist row should be replaced with this rev of the sandbox. The only change is that parser(args, 'shield') is replaced with parser(args, 'shieldmain') or parser(args, 'shield'). – BrandonXLF (talk) 08:38, 7 September 2021 (UTC)

What is the rationale behind this edit? You only mention that it should be changed not why it should be changed. –Fredddie™ 23:28, 7 September 2021 (UTC)

I ask because this would have far-reaching consequences; we split shieldmain from shield for a reason. Interstate Highway lists and county road lists use generic shields because you can't read the small text at 25px. This would all change with this edit. Personally, since you seem to be Ontario-focused, I would create a new type in Module:Road data/strings/CAN/ON that uses the same formatting as ON.ON, but only declare the non-crown shield. –Fredddie™ 01:02, 8 September 2021 (UTC)

My rationale behind the edit is when shield is a generic symbol it doesn't represent the road as well as the shieldmain, especially for county roads. Looking at the uses of this template, it doesn't seem like there's very many that would change by switching to shieldmain. Also, a lot of routes are already using symbols with small text on them and although the text isn't always readable, the general of the shape of the text is still visible and I don't see how the extra detail has a negative effect.

I also noticed for some routes shieldmain also contains data for special routes certain roads are apart of, which might not be desirable to display for this template. Would be a good idea to add a shieldextra key to Module:Road data/strings that would contain symbols for these special routes? The symbols in the key would be included in {{Infobox road}} but not this template. – BrandonXLF (talk) 08:19, 8 September 2021 (UTC)

In many cases, the version of the marker graphics in shieldmain just isn't legible at the smaller sizes. To be perfectly honest, according to the MOS, we could/should remove the graphics from the junction lists, the route lists and even the browser in the infobox, leaving only the main graphic for the subject of the article at the top of the infobox because they're considered decorative graphics and not necessary. Rather than remove them, I'd retain the status quo for the reasons Fredddie mentioned, using the more generic options. Imzadi 1979 → 20:58, 8 September 2021 (UTC)

Which is why I suggested setting up a new type as an equitable workaround. ON.Ontario is all ready to use. –Fredddie™ 00:20, 9 September 2021 (UTC)

Number	Length (mi)	Length (km)	Southern or western terminus	Northern or eastern terminus	Formed	Removed	Notes
Highway 401	—	—	Highway 401	—	—	—	Live version
Highway 401	—	—	Highway 401	—	—	—	Sandboxed version

My main concern about having a special type is all the articles that would need to be updated. Also the type name you chose in particular is very confusing and there's no clear indication that the "Ontario" type would be different than the "ON" type. Would it be possible to add a new shieldlist that would be used when the shield is being included in a list/browse template such as this one and the browse at end bottom of the infobox?– BrandonXLF (talk) 22:03, 9 September 2021 (UTC)

I've thought about it for a couple days and I'm starting to come around to it. I can think of a few examples in the US where we might want to use shieldlist. I've updated the example to show that it works. –Fredddie™ 12:17, 11 September 2021 (UTC)

I'm marking this as answered since I don't see a need for an uninvolved template editor to do anything here. If Fredddie wishes to implement this, then he can do so, but otherwise there isn't sufficient consensus for me (or someone else involved) to override his hesitation and forcibly implement it. * Pppery * _{it has begun...} 21:05, 25 September 2021 (UTC)

Shields instead of crowns for Ontario

Is it possible to have Ontario use the shield in this template instead of the crown? It looks like this runs off the same parser as jct so it may have to be an override like California and a few other states have... either way I'm not nearly capable enough with Lua to try and make the change myself on a template like this. - Floydian ^τ _¢ 02:41, 10 April 2022 (UTC)

There was another request for this somewhere and I thought I had it working. –Fredddie™ 04:42, 10 April 2022 (UTC)