Template talk:Infobox road/Archive 8

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Template-protected edit request on 27 October 2018

Adding List of state highways serving Utah state parks and institutions and List of Utah State Routes shorter than one mile to the Utah entry seems to be a good idea. I'd implement it like so:

* [[List of Interstate Highways in Utah|Interstate]]
* [[List of U.S. Highways in Utah|US]]
* [[List of state highways in Utah|State]]
** [[List of state highways serving Utah state parks and institutions|Minor]]
** [[List of Utah State Routes shorter than one mile|Short]]
* [[Utah Scenic Byways|Scenic]]

But I'm not entirely set on what to name them. SounderBruce 04:16, 27 October 2018 (UTC)

 Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template.
If you're not sure what you want, this isn't the way to ask. Us gnomes are just here to do stuff, not to make aesthetic decisions. Perhaps Wikipedia talk:WikiProject United States is the place to gather ideas and a consensus? Cabayi (talk) 13:13, 28 October 2018 (UTC)
 Done @Cabayi: SounderBruce is an active member of WP:USRD and someone who has written a handful of FAs and over 100 GAs. I trust this request isn't coming out of left field and that he only made this request because he doesn't have the TemplateEditor right. –Fredddie 14:12, 28 October 2018 (UTC)
Fair enough. That wasn't apparent. I've tagged this page with the project template so hopefully it'll be a little clearer in future. Cabayi (talk) 14:19, 28 October 2018 (UTC)

Template-protected edit request on 27 November 2018

Under Minnesota, please change [[List of Minnesota state highways|State]] to [[List of state highways in Minnesota|State]] to avoid an unnecessary redirect. Thanks. --Sable232 (talk) 00:15, 28 November 2018 (UTC)

@Sable232: I did a F7 page search for Minnesota and 0 responses. - - FlightTime (open channel) 00:38, 28 November 2018 (UTC)
@FlightTime: It should come up, it does for me in the page source here. --Sable232 (talk) 01:02, 28 November 2018 (UTC)
 Done Got it. - FlightTime (open channel) 01:07, 28 November 2018 (UTC)

Can someone explain what makes this so different from Template:Infobox street?? Was going to TFD them for a merge but there MUST be something I'm missing... --Zackmann (Talk to me/What I been doing) 23:59, 10 February 2019 (UTC)

@Zackmann08: this one is for components of a national/state/provincial highway system (or in the US, a county road system), and that one is for city streets. There are a number of different parameters in IR that aren't present in IS, and vice versa because they're designed for different use cases, let alone the visual differences between them. Imzadi 1979  00:09, 11 February 2019 (UTC)
@Imzadi1979: gotcha. I figured there was a good reason. To an outsider road = street so I was curious why 2 separate templates. Thanks for the info! --Zackmann (Talk to me/What I been doing) 00:10, 11 February 2019 (UTC)

Canada road template issue

Hello: through some formatting error, the Infobox Road template on Nova Scotia (eastern Canadian province) route articles (e.g. Nova Scotia Route 208) references Winnipeg routes (a western Canadian city). I dare not guess where the problem originates, so perhaps a knowledgeable editor can take a look. Verne Equinox (talk) 18:13, 6 March 2019 (UTC)

Fixed with this edit. -- WOSlinker (talk) 21:46, 6 March 2019 (UTC)

Edit request: Add spaces to the date range fields

@Plastikspork, Zackmann08, Fredddie, Jonesey95, and Rschen7754: Most recent editors: Greetings and felicitations. Would someone please be so kind as to add a space on either side of the en dash in the date range field(s), per MOS:ENTO? I'd like to avoid violating that guideline, as is currently the case in the U.S. Route 25W article. — Preceding unsigned comment added by DocWatson42 (talkcontribs)

This isn't a simple fix solved by adding a couple spaces. There are plenty of instances where there are only years in the date range; in those cases, the lack of a space is acceptable. –Fredddie 12:59, 4 March 2019 (UTC)
There is probably a way to put spaces in by default but omit them if the values of |established= and |decommissioned= are both four digits (or shorter than a given length). One of the tools at {{String-handling templates}}, combined with a couple of if statements, might do the trick. – Jonesey95 (talk) 23:57, 9 March 2019 (UTC)

Add support for Namibian "A routes"

Please add support for Namibian "A route" marker images. Creating an instance of the template with values country=NAM,type=A,route=1 does not display any highway marker image (the Namibian A1 route marker is expected to be displayed), whereas creating an instance of the template with values country=NAM,type=B,route=1 correctly displays the Namibian B1 route marker: the only difference is changing the type between A and B.

At present, the only "A route" in Namibia is the A1, and its route marker can be found here. Ron2K (talk) 03:58, 12 March 2019 (UTC)

A1 road shield}}
A1 road
Location
CountryNamibia
Highway system
We should be good to go. Let us know if you need anything else. –Fredddie 04:09, 12 March 2019 (UTC)

Template-protected edit request on 1 April 2019

Please change List of State Routes in Ohio to List of state routes in Ohio. Cards84664 (talk) 20:55, 1 April 2019 (UTC)

 Done Imzadi 1979  22:55, 1 April 2019 (UTC)

Wikidata

For images from Wikidata, please, change code {{{photo|}}}{{{image|}}} to {{{photo|{{{image|{{Wikidata|properties|P18}}}}}}}}. — Preceding unsigned comment added by 217.117.125.72 (talk) 16:08, 9 May 2019 (UTC)

This merits discussion. Should a Wikidata image be preferred over the existing photo/image, for example? Please implement the suggested change in the template's sandbox and use the testcases page to show how it works in different circumstances. – Jonesey95 (talk) 18:27, 9 May 2019 (UTC)
The US road articles have long blocked this parameter out of concerns that it would be misused. --Rschen7754 18:32, 9 May 2019 (UTC)
@217.117.125.72: please provide us a good reason for why we should add this code to the infobox. As noted already, this isn't going to work for articles in the U.S. –Fredddie 13:46, 22 May 2019 (UTC)

Template-protected edit request on 15 August 2019

I would like to request a change in the title for "Arizona Highways". ADOT refers to all the state designated and maintained routes within Arizona as the "Arizona State Highway System" within its documents. I feel the name change would be more accurate and better reflect Arizona's highways. -MatthewAnderson707 (talk|sandbox) 02:26, 15 August 2019 (UTC)

@MatthewAnderson707:  Done Imzadi 1979  02:29, 15 August 2019 (UTC)
Thanks! -MatthewAnderson707 (talk|sandbox) 03:05, 15 August 2019 (UTC)

Template-protected edit request on 1 November 2019

I would like to request some additions to the following section:

 |AZ 1927|AZ pre-1956|AZ 1956|AZ 1963=Maintained by [[Arizona Department of Transportation|Arizona Highway Department]]

Which would look as follows if the additions were to be implemented:

 |BL|BS={{#switch:{{{state}}}
  |AZ=Maintained by [[Arizona Department of Transportation|ADOT]]
  |NM=Maintained by [[New Mexico Department of Transportation|NMDOT]]
  |TX=Maintained by [[Texas Department of Transportation|TxDOT]]
  |#default=
  }}
 |AZ 1927|AZ pre-1956|AZ 1956|AZ 1960|AZ 1963=Maintained by [[Arizona State Highway Department|ASHD]]
 |US 1926=Maintained by {{#switch:{{{state|}}}
  |AZ=[[Arizona State Highway Department|ASHD]]
  |CA=[[California Department of Public Works|CDPW]]
  |NM=[[New Mexico State Highway Department|NMSHD]]
  |NY=[[New York State Department of Highways|NYSDH]]
  |OR=[[Oregon State Highway Department|OSHD]]
  |PA=[[Pennsylvania Department of Highways|PDH]]
  |TX=[[Texas State Highway Department|TSHD]]
  |WA=[[Washington State Department of Highways|WSDH]]
  |#default=
  }}
 |US 1956=Maintained by {{#switch:{{{state|}}}
  |AZ=[[Arizona Department of Transportation|ASHD]]
  |#default=
  }}
 |US 1960=Maintained by {{#switch:{{{state|}}}
  |AZ=[[Arizona State Highway Department|ASHD]]
  |#default=
  }}
 |US 1963=Maintained by {{#switch:{{{state|}}}
  |AZ=[[Arizona Department of Transportation|ADOT]]
  |#default=
  }}

These add the various organizations and highway departments that maintained the above set of highways. Thanks. — MatthewAnderson707 (talk|sandbox) 06:53, 1 November 2019 (UTC)

I didn't do it exactly this way, but all the functionality you requested has been added. –Fredddie 17:44, 3 November 2019 (UTC)

Dates for when under construction?

I have a suggestion, or query: I've added the infobox to Transmission Gully Motorway currently under construction in New Zealand, and there doesn't seem to be a way to specify dates correctly. I suppose useful additional parameters would be "began construction" and "scheduled opening date" (or perhaps reuse "established" to mean "scheduled opening date" when "status = under construction"). Unless I'm missing something? Edit: perhaps while we're about it we could have a "cancelled" date, perhaps also a reuse/alias of "decommissioned/deleted"? For example, the M12 motorway (Great Britain). — Jon (talk) 22:51, 31 December 2019 (UTC)

The practice has been to use |established= for the date that a driver could first drive the roadway under that designation. There is |history= that's useful for more free-form information. For example, Interstate 96 was designated in 1959 on an existing roadway, so that's when drivers could first use I-96. The highway wasn't completed until 1977 though, so we have |history= Completed November 21, 1977 to indicate that. If the designation had been removed from use, that's when it's |deleted=. For M12, I see that infobox as done well because it never existed except on the drawing boards. Imzadi 1979  01:38, 1 January 2020 (UTC)

Template-protected edit request on 22 February 2020

So, why is the info box being moved. And, also, for the info box can you mention what it is used for, and why only 23k pages have it? Gale5050 (talk) 01:44, 22 February 2020 (UTC) Gale5050 (talk) 01:44, 22 February 2020 (UTC)

It's not being moved. There is a discussion taking place at Wikipedia:Templates_for_discussion/Log/2020_February_19#Template:Infobox_road regarding merging {{Infobox Australian road}} into this template. –Fredddie 02:06, 22 February 2020 (UTC)

Tracking categories by country

I have deployed tracking categories for Infobox road that sort based on country or international network. Countries that used the country mask (AUS, CAN, MEX, and USA) have subcategories by state or province. Basically, I wanted an easy way to get a list of all articles in a country that use IBR. It is located at Category:Infobox road instances by country. –Fredddie 01:05, 21 February 2020 (UTC)

@Fredddie: You should have a look at Category:Infobox road instances in which currently has 172 instances of this tracking not working, mostly in Mexico. Please can you fix this asap, as it's getting in the way of the backlog of pages which genuinely have red-linked categories on them? TIA Le Deluge (talk) 21:04, 25 February 2020 (UTC)
Thanks for the heads up. I will look at it right away. –Fredddie 21:07, 25 February 2020 (UTC)
@Le Deluge: all cleared out. I didn't realize that State of Mexico has the same ISO abbreviation as the country. –Fredddie 21:33, 25 February 2020 (UTC)

@Fredddie: Non-article pages are also being tracked, e.g. Category:Infobox road instances in Australia... not sure you really want sandboxes, testcases, and the like to be included - Evad37 [talk] 01:30, 26 February 2020 (UTC)

Yeah I thought about that. I suppose it's a good way to make sure that the infobox is working like it should, even in sandboxes. But, I can also see why you'd only want pages in the articlespace. –Fredddie 04:20, 26 February 2020 (UTC)
I think there's no real need to track such non-article uses. But if you want to keep them, maybe put them under a different sort key so at least they'll be listed separately from articles. - Evad37 [talk] 07:28, 26 February 2020 (UTC)

Template:Infobox street

This infobox has the option to implement multiple sections of a road/highway. Does {{Infobox street}} have the same option? If so, how do I utilize it? Morriswa (Charlotte Allison) (talk) 09:14, 6 March 2020 (UTC)

Costa Rica support in Module:Infobox road/locations

Hi again, I would like to request to add support for Costa Rica (CRI) in the Module:Infobox road/locations for the "Province" administrative divisions of first order (below country level) and of second order "Canton" (each province is composed of cantons). Documented here in Administrative divisions of Costa Rica.

The provinces are already supported for other countries in 'local function provinces(args, country)' , but not cantons in any other function, which may be a special request.

In CRI each canton has a local government called a municipality, but the geographical location is known as canton, not municipality, which is just an office building to pay taxes :-), so, municipality while already in the Module, will not work for Costa Rica's purpose administrative divisions/geographic situation.

Cantons can be added to 'local function counties(args, country)' , I think. They are used in other countries as well: Canton (country subdivision).

I already have all the provinces/cantons/districts for all the routes ready to be added (as well as length) from the official gov. GIS sources, I would like to add these two level locations to the infobox, and district level (third order) in the article itself, as there are a lot of those in some routes.

At this point I think I can create the stubs to fill up all the 300+ routes very quickly, and then work little by little by adding junctions lists and details one by one through the years, is this an acceptable approach? I'm afraid nobody else is interested in creating these articles. --Roqz (talk) 00:12, 26 May 2020 (UTC)

Oh, I think "Province" is enough for the Infobox. Some routes cover a lot of Cantons, it would overload/clutter the Infobox. Roqz (talk) 17:31, 27 May 2020 (UTC)
@Fredddie: about the location issue. I think that is a good approach for creating the articles - but I would make sure that there's enough content to start with so the articles don't get deleted under "no content" (i.e. have more than just an infobox). --Rschen7754 18:39, 27 May 2020 (UTC)
Not quite sure why I was pinged here, but I can make sure CRI gets provinces. –Fredddie 23:45, 27 May 2020 (UTC)
Awesome! Thanks Fredddie for adding the provinces locations, just noticed that doing some tests! @Rschen7754:, this is a preview of how those articles might look like, generated from the gov. GIS data: User:Roqz/RNP21CRfromGIS, please see the code too, I commented out some sections to have them ready to fill in the future. Most of the tertiary routes (the bulk of the total) might only have that content in the short therm and then the junction list and that's it, unless there is some news about them (which is way I have filled up some of the already existing articles in the navigation template). Should I proceed? I can add add ten or so articles per day, to avoid looking like a spam bot. The district listing is important for my next Wikipedia project, to create proper content for all the district stubs out there (try visiting some of that Route 21 draft, some are basically empty, like Mansion District, others have a bit more of proper information and infobox), so I can link back the transportation availability by each region, to the route article. :-) Roqz (talk) 01:20, 28 May 2020 (UTC)
I think that should be fine - worldwide there's a lot of articles that look like that. --Rschen7754 01:24, 28 May 2020 (UTC)

Image (photo) does not show sometimes

Image (photo) does not show sometimes for me: I specify it as "image=filename.jpg" and it wont show for example at Interstate 20. But I was able to add the image to D1 motorway (Czech Republic). So I am confused.--Kozuch (talk) 16:48, 7 June 2020 (UTC)

There was a consensus to prohibit the use of this in US road articles a while back, because it would only add more to an infobox that was already too long and the subject of edit wars. However, many other countries wanted to use that parameter, so it was left on for them. --Rschen7754 16:54, 7 June 2020 (UTC)
Ok. How are the photos from US roads technically blocked?--Kozuch (talk) 17:28, 7 June 2020 (UTC)
PS. What about putting the photos/maps beside (next to) each other horizontally so that we save vertical space? I see very few such solutions in infoboxes (at least I think I have seen some already) yet they may be pretty elegant - sure the content is smaller, but it is clickable for higher resolution (or fullscreen map).--Kozuch (talk) 17:32, 7 June 2020 (UTC)
{{Infobox road/hide/photo}} controls whether or not to hide the photo. If that subtemplate returns yes, which it will for anything in the US, the |photo= or |image= parameter will be ignored. Imzadi 1979  17:49, 7 June 2020 (UTC)

Image from wikidata

What about pulling an image from Wikidata in case there is no local image specified? The map currently pulls from wikidata (from P15 - "route map") but the image does not (from P18 - "image")--Kozuch (talk) 16:15, 7 June 2020 (UTC)

Given the attitudes of English Wikipedia towards Wikidata use, we have hesitated to add more Wikidata integration in the event that English Wikipedia decides to prohibit Wikidata use entirely. I agree this is an unfortunate state of affairs (I am an admin on Wikidata), but that is how it is. --Rschen7754 16:56, 7 June 2020 (UTC)
Really not very fortunate state. Is Wikipedia:Wikidata/2018 Infobox RfC the latest discussion or is there a newer one? From this one it looks like the consensus reads like "There is a consensus that data drawn for Wikidata might be acceptable for use in Wikipedia if Wikipedians can be assured that the data is accurate, and preferably meets Wikipedia rules of reliability." Do you think this speaks against including and image from wikidata?--Kozuch (talk) 17:27, 7 June 2020 (UTC)
I think that was the last one. The issue is that there are some folks on English Wikipedia who really hate Wikidata and won't rest until the site goes away. --Rschen7754 18:42, 7 June 2020 (UTC)

Generating short descriptions

I've noticed an effort to copy short descriptions from Wikidata onto road articles. Personally, I think it's a waste of time, but I know how some people on ENWP feel about Wikidata. Rather than do all that work, would it make more sense to add something to the infobox that would generate short descriptions automatically? –Fredddie 23:56, 8 June 2020 (UTC)

It could be useful to generate more standardized and consistent short descriptions. Imzadi 1979  00:53, 9 June 2020 (UTC)
{{Infobox settlement}} has a pretty sophisticated method that could probably be adapted here. It's at least a little bit tricky, since if you are going to generate something like "{type of road} in {country}", you have to do some error-checking and also account for situations like {country} = "United States" where the word "the" may need to be added before the country name. – Jonesey95 (talk) 04:58, 9 June 2020 (UTC)
Accounting for countries that require a definite article isn't that difficult. I did it for the category instances a few months back. –Fredddie 21:39, 9 June 2020 (UTC)

See above. --Rschen7754 18:18, 24 June 2020 (UTC)

Error at Romantic Road

Can someone please take a look at Romantic Road and see why the template is populating Category:Infobox road instances in instead of Category:Infobox road instances without location. Timrollpickering (talk) 09:37, 23 August 2020 (UTC)

country param should be DEU rather than DE. I also had to remove the route param as it was using {{AB}} which is a Canadian template. -- WOSlinker (talk) 10:41, 23 August 2020 (UTC)

Using this template for Roman Roads in Britain

Hi. I am in the process of preparing the article on Stane Street (a Roman Road in south east England) for GA nomination. I requested some input from a fellow editor, who has informally reviewed the article (and promoted it to B class). One of their recommendations was to incorporate an infobox at the top of the article. I have used Infobox Roads, which is also used for the Ermine Street article. I’m presuming that creating a new infobox specifically for Roman Roads would be strongly discouraged, especially as there is a historic option available for this template, so I wondered if it would be possible to add a few extra parameters to this template to accommodate these roads please?

  • Firstly Roman Roads in the UK are classified by their Margary numbers, so would it be possible to add a |Margary_number parameter? (This should display in the 'Route information' section, rather than at the top of the infobox.)
  • Secondly, would it be possible to add a Roman Roads in Britannia option for the |system parameter, which might perhaps link to Roman roads in Britannia?

I'm not entirely sure if this is the best way of going about this and I'm very happy to discuss what might be the best form of infobox for these roads might be. Thanks and best wishes, Mertbiol (talk) 18:21, 31 October 2020 (UTC)

@Mertbiol: I have added |margary= to display the Margary number. I also updated the GBR subtemplates so that |country=GBR |type=Roman displays the desired link at the bottom. Imzadi 1979  18:49, 31 October 2020 (UTC)
Thanks very much Imzadi1979!! Looks great and thank you for resolving this so speedily. Mertbiol (talk) 19:58, 31 October 2020 (UTC)

Hi, I have two more requests.

  • Firstly I am reminded that many (but not all) of the more important Roman roads (not just in the UK, but also across continental Europe) are listed (and given a number) in the Antonine Itinerary, which describes routes between major towns. Could I therefore ask that an |antonine parameter is added (similar to the |margary parameter above) please?
  • Secondly I wondered if there was a way in which we could make it clearer at the top of the infobox that a road is in fact a Roman road? For modern roads which use standardised signage (and for which a symbol is automatically), it is obvious what type of road they are. However most Roman roads in the UK are called ‘streets’, which implies that they are shorter, urban roads rather than being long distance. As a test, I have misused the |alternate_name parameter to add ‘Roman Road’ at the top of the infobox for a couple of roads (see Stane Street (Chichester) for one example), but I realise that this is a break of policy. Would it be possible for the |type = Roman option to add this text (or similar) instead please?

Thanks and best wishes Mertbiol (talk) 09:29, 8 November 2020 (UTC)

Template-protected edit request on 14 March 2021

For Template:Infobox road/maint/USA: Change Connecticut Department of Transportation abbreviation from ConnDOT to CTDOT, as the DOT now uses CTDOT as its abbreviation. On its website, only the CTDOT abbreviation is used. 2018rebel 20:52, 14 March 2021 (UTC)

 Done Imzadi 1979  21:41, 14 March 2021 (UTC)

Template-protected edit request on 6 April 2021

{{{margary}}} is a valid parameter, but is missing from the list passed to Module:Check for unknown parameters. Please change map_notes | marker_image to map_notes | margary | marker_image -- John of Reading (talk) 08:50, 6 April 2021 (UTC)

 Done Elli (talk | contribs) 11:41, 6 April 2021 (UTC)

Compare two nil values

Some articles are showing "Lua error in Module:Infobox_road/route at line 40: attempt to compare two nil values." Examples: Glenn Highway + Sterling Highway. Fredddie Would you please have a look. Johnuniq (talk) 10:50, 4 July 2021 (UTC)

I fixed these two. I am in the process of going through about 860 articles, but I hit a wall at 4am my time. –Fredddie 18:00, 4 July 2021 (UTC)
Yikes! Thanks for your work and there is no deadline. Johnuniq (talk) 05:07, 5 July 2021 (UTC)
You can see what's left to fix with petscan. -- WOSlinker (talk) 06:45, 5 July 2021 (UTC)

Template-protected edit request on 14 August 2021

{{Infobox road/shieldmain/USA}} lists U.S. Bicycle Routes that are marked by either the standard black-and-white shield or the alternative green-and-white shield, depending on the state, and therefore need to show both shields in the infobox. This change updates the list to reflect ASHTO's approvals from fall 2020 and spring 2021. Thanks! – Minh Nguyễn 💬 10:30, 14 August 2021 (UTC) – Minh Nguyễn 💬 10:30, 14 August 2021 (UTC)

 DoneFredddie 19:14, 14 August 2021 (UTC)

I missed that USBR 15 is also using both shields (different in Florida than in Georgia): Special:Diff/1038971807. – Minh Nguyễn 💬 22:16, 15 August 2021 (UTC)

 DoneFredddie 00:46, 18 August 2021 (UTC)

Template-protected edit request on 14 August 2021

If I'm not mistaken, {{Infobox road/shield/USA}} is intended to list U.S. Bicycle Routes that are marked only by the alternative green-and-white shield. This change updates the list to reflect all the latest AASHTO approvals and FHWA interim approvals. USBR 230 is tricker than the others: there are two distinct route 230s, each with a different shield in a separate mini infobox on U.S. Bicycle Route 30. That already works, so I'm not sure exactly what this template is used for, but I made this change just in case. – Minh Nguyễn 💬 11:14, 14 August 2021 (UTC)

 DoneFredddie 19:15, 14 August 2021 (UTC)

I missed that USBR 15 is also using both shields (different in Florida than in Georgia): Special:Diff/1038971927. – Minh Nguyễn 💬 22:17, 15 August 2021 (UTC)

 DoneFredddie 00:47, 18 August 2021 (UTC)

Lengths

I reconfigured Module:Infobox road/length to use {{Convert}} rather than our homebrew code. This should resolve any past concerns about 100 miles converting to 200 km instead of 160 km and so on. –Fredddie 20:30, 20 August 2021 (UTC)

Also, any length under 1 mile will convert to meters and under 1 km will convert to miles and feet. –Fredddie 21:46, 20 August 2021 (UTC)

Locations module: change request

I am pretty new to this so I hope I am doing this the right way. My request concerns the "regions" restriction in the road infobox. While I have been revitalizing the S-highway route pages of Georgia (country) recently, I bumped into the region restriction in the infobox (as indicated on this template page). However, Georgia is administratively divided in "regions" (and not provinces or else): Administrative divisions of Georgia (country). The two autonomous republics (Adjara and Abkhazia) can be practically equalled to a region when looking beyond their constitutional position. While the municipality property is obviously available, I would like to have the region property available as well for Georgia (country), as there is no other subnational location indicator apart from the municipalities.

Is that a reasonable request, if so, how to go about this? If no, why not? Thanks, Labrang (talk) 12:53, 22 August 2021 (UTC).

Use shieldmain for browse

Right now, the browse listing produced by this template are using the shield tag from Module:Road data/strings. It makes more sense to use shieldmain when defined as it better represents the route than shield, which is only used for guide markers at intersections when shieldmain is defined. It is also more consistent to use shieldmain since it is already used at the top of the infobox.

The changes can be seen in the example below at the bottom of the infobox where the guide markers for the 405 and 407 and switch to the more appropriate reassurance markers:

Side by side comparison
{{Infobox road}}{{Infobox road/sandbox}}

Highway 406 marker

Highway 406

Route information
Maintained by Ministry of Transportation of Ontario
Length26.0 km (16.2 mi)
ExistedDecember 7, 1965–present
Major junctions
South endEast Main Street in Welland
Major intersections Highway 58Thorold
North end Queen Elizabeth Way in St. Catharines
Location
CountryCanada
ProvinceOntario
Highway system
Highway 405 Highway 407

Highway 406 marker

Highway 406

Route information
MaintenanceMinistry of Transportation of Ontario
Length26.0 km (16.2 mi)
Planned length26.0 km (16.2 mi)
Untolled length26.0 km (16.2 mi)
Tolled length26.0 km (16.2 mi)
Length under
construction
26.0 km (16.2 mi)
Overall length26.0 km (16.2 mi)
ExistedDecember 7, 1965–present
Major junctions
South endEast Main Street in Welland
Major intersections Highway 58Thorold
North end Queen Elizabeth Way in St. Catharines
Location
CountryCanada
ProvinceOntario
Highway system
Highway 405 Highway 407

The code at Module:Road data/browse should be replaced with this rev of the sandbox. All that changes is that roadDataModule.shield(route) is replaced with roadDataModule.shield(route, nil, nil, true) which tells Module:Road data to use shieldmain if it's available. BrandonXLF (talk) 08:24, 7 September 2021 (UTC)

 DoneFredddie 00:04, 8 September 2021 (UTC)
@BrandonXLF and Fredddie: as noted elsewhere, there is a specific reason why this was done for legibility reasons, and I'd reverse this change. Imzadi 1979  21:31, 8 September 2021 (UTC)
As I mentioned on Template talk:Routelist row, I thought about it for a couple days and I'm coming around to it. I've edited what BrandonXLF added and made it so shieldList, when it is even called, falls back on shield and not shieldmain. –Fredddie 13:04, 11 September 2021 (UTC)
@Fredddie When you updated the module with the sandbox version, you copied over some changes I was working on in the sandbox that aren't ready to be used in the live template. I've now updated the sandbox to only include the change to the call to roadDataModule.shield. BrandonXLF (talk) 02:30, 12 September 2021 (UTC)

Template-protected edit request on 12 September 2021

Could an admin or template administrator change List of County-Designated Highways in Michigan to List of county-designated highways in Michigan to reflect the recent page move? This way the infobox will correctly link to the current article name when MI is entered under "links=" Thanks.--Epiphyllumlover (talk) 02:03, 12 September 2021 (UTC) Epiphyllumlover (talk) 02:03, 12 September 2021 (UTC)

 Not done: it doesn't look like there's a clear consensus for the move. Wait until the page has a stable title for at least a week before asking again (and honestly, the page should go through an RM discussion). Elli (talk | contribs) 03:55, 12 September 2021 (UTC)
@Epiphyllumlover: since you apparently stalked some of my recent edits and things to know that someone wanted to move that page that wouldn't have been on your radar otherwise, it surprises me that you didn't see my recent reply that I don't have immediate access to some of the hard copy/offline sources used to write that Featured List, including one that I recall being the one that would be used to retain the previous capitalization as a proper name. So I find it rather impertinent for you to take it upon yourself to affect a controversial (in the sense that there is a disagreement at play) page move based on your own volition instead of requesting a page move. That being said, as disgusted as I am with the situation overall, I'm just moving on to better things, including letting the page move stand for now. As such, I'm fulfilling this edit request for now. Imzadi 1979  05:38, 12 September 2021 (UTC)
This is the wrong forum for discussing article page moves anyway. –Fredddie 16:52, 12 September 2021 (UTC)
Elli & Fredddie; my request is not urgent because the infobox still works via the redirect.--Epiphyllumlover (talk) 17:28, 12 September 2021 (UTC)

Template-protected edit request on 17 November 2021

Hi. Minor fix needed in data51: {{{terminus_b3||{{{end_b|3}}}}}}{{{terminus_b3||{{{end_b3|}}}}}}. Thanks. Jeeputer (talk) 23:41, 17 November 2021 (UTC)

Just noticed those double pipes! and it seems there are many of them in the source code. they can be found and fixed by searching ||{{{. Jeeputer (talk) 23:43, 17 November 2021 (UTC)
 DoneJonesey95 (talk) 00:37, 18 November 2021 (UTC)

Locations module: input requested

So I have an idea to rewrite Module:Infobox road/locations (Sandbox) and I don't know where to begin, so I am asking for help. There was a discussion a few years ago about adding country and state/province/etc information to the infobox, and that's what I'd like to implement. To recap, if you added |state=NY, the location section would fill in "Country: United States" and "State: New York" automatically.

After reviewing List of administrative divisions by country, I determined that there are at least 42 subnational division types around the world. No two countries name their divisions the same, so I was thinking we could use the Road data string modules for that and shoehorn the labels to fit the parameters. What I mean here is that using |territories= in Malaysia would output the label "Federal territories", while in Quebec it would output "Equivalent territories". There are dozens of other examples.

Here is the list of divisions if you want to see what I came up with
  • Country(s)
  • Autonomous region(s)
  • Region(s)
  • Canton(s)
  • Collectivity(s)
  • Department(s)
  • District(s)
  • Governorate(s)
  • Island(s)
  • Oblast(s)
  • Prefecture(s)
  • Province(s)
  • Republic(s)
  • State(s)
  • Territory(s)
  • Areas
  • Authorities
  • Boroughs
  • Capital
  • Comarcas
  • Communes
  • Councils
  • Counties
  • Dependencies
  • Divisions
  • LGAs
  • Municipalities
  • Parishes
  • Quarters
  • Regencies
  • Resorts
  • Rural municipalities
  • Sectors
  • Shires
  • Sub-districts
  • Sub-prefectures
  • Zones
  • Arrondissements
  • Cities
  • Communities
  • Towns
  • Villages
  • Wards
  • Primary destinations

Currently, there are about a dozen or so locations defined in the module and they're restrictive; you can't use |states= in a USRD infobox unless it's a national article. What I was thinking is that each country's string module defines the types it needs. India, for example, could be defined like this:

IND.locations = {
     ["data1"] = "India",
     ["param2"] = arg.states,
     ["label3"] = "Union territories",
     ["param3"] = arg.territories,
     ["param4"] = arg.districts,
     ["param5"] = arg.cities,
}

How this would work is that the param# fields define the type and the order in which they appear. If there is no accompanying label like label3, it uses the default, which would be Country, States, and Districts, respectively.

For the US and Canada, which are at present the only countries that have modules for each state or province, since the country module is attached to each submodule, I would assume that you wouldn't have to define the country each time. Louisiana could be defined like so:

LA.locations = {
     ["data2"] = "Lousiana",
     ["param3"] = arg.parishes
}

Essentially, if it's not defined in the string module, it shouldn't appear in the infobox. For instances where there is no country defined with its ISO 3166-1 alpha 3 code, there could be a default set of generic parameters that could be used (thinking region, area, cities). Does it make any sense at all?

The problem I need help with is that I don't know how to even begin tackling this in Lua. This module should output a Template:Infobox subbox complete with a Location header. I haven't really seen any clues on how to implement an infobox row from a module, but I could just not be seeing it. I believe the templatestyles cascade down from the main template but if they don't, that can be addressed. –Fredddie 07:09, 23 March 2021 (UTC)

Request Edit re Arabic module

I am the author of the Module:Convert to eastern arabic numerals and after a discussion with some other more experienced Lua editors I renamed convert_str to convert and instead of taking a number it now takes a table. So I propose changing L110 from

		local arabic = arabicModule.convert_str(route)

to

		local arabic = arabicModule._convert({route})


I have it so it should be backwards compatible until this change is made. Thanks! snood1205 16:03, 28 December 2021 (UTC)

 Done. P.I. Ellsworth - ed. put'r there 18:24, 28 December 2021 (UTC)

December 2021 updates

I've been working diligently migrating this template to Lua and I've taken a number of functions live as of today:

  1. WP:TemplateStyles for headers. It is now possible to set the color of a route based on its {{Jct}} type (soon to also be Infobox road type). If I missed a country, it will not have any header color or will be the default blue until it's added to Template:Infobox road/styles.css
  2. Secondary photo (turned off for USA)
  3. Sections that now run off of the route's Jct type:
    1. Translation (need to double check the Template:Infobox road/translation/ series)
    2. Maintenance (mainly USA/CAN but there may be a few others that use it)
    3. Defined by law (only 5 states in USA use it)
  4. Allocation (just the label)
  5. Some parameter-heavy functions were moved to Lua
    1. Time period which controlled Cultural significance and Related routes
    2. Part of e-road, ahn, tahn, or mrn
  6. Sections is the biggest advancement
    1. The main function controls direction_a/b and terminus_a/b, junctions, as well as beltways, orbitals, ring roads, etc.
    2. The template now supports up to 25 sections (direction_a/b#, terminus_a/b#, junction1, length_mi#, etc.), though in theory there really shouldn't be a limit. This will be the only advertisement of that number.
    3. The junction parameters use the plainlist class by default so it's no longer necessary to use {{plainlist}}. You can simply use a bulleted list.


Here are some things still in the pipeline:

  • Tracking categories
  • Deprecating |subtype= by unifying Infobox road, Jct, and {{Routelist row}} road types. These will occur when that happens:
    • Spur of (will be based on the |aux= in the Road data string modules)
  • Location section
    • Adding countries and states, provinces, or whatever
    • 20 default location parameters and the ability to customize them by country (AUS, CAN, CHN, FRA, GBR, MEX, NLD, RUS, USA are set up in the sandbox)
    • Simplifying the Template:Infobox road/hide system
      For instance, if |state= is not used for USA, |states= can be used by default
    • 5 generic parameters for those countries that don't use any of the 20 default parameters
    • Major cities is still turned off for USA
  • Browselinks still has some kinks to work out

Let me know if there's something you like or don't like about the current template or the sandbox version or if there any features you'd like to see. –Fredddie 05:34, 14 December 2021 (UTC)

This edit apparently broke a bunch of articles that use this template; see Category:Lang and lang-xx template errors.
Trappist the monk (talk) 14:21, 14 December 2021 (UTC)
You should probably change Module:Infobox road line 83 to something like this:
if not translation or '' == translation then
because blank template parameters are empty string not nil.
Trappist the monk (talk) 14:54, 14 December 2021 (UTC)
Some articles are in Category:Pages with script errors, for example:
  • "Lua error: frame:expandTemplate: invalid type table for arg '2'" at Inn Valley Autobahn.
  • "Lua error in Module:Infobox_road/length at line 37: attempt to compare nil with string" at A69 road.
Johnuniq (talk) 06:21, 15 December 2021 (UTC)

Stray li tag

It looks like there is a stray </li> tag generated by {{#invoke:Infobox road/sandbox|browseLinks|state=NE|type=road}} and {{#invoke:Infobox road/sandbox|browseLinks|state=CT|type=road}} (thank you for making a good set of testcases!). The generated code looks like this (I have bolded the stray tag):

<div class="hlist"><div style="font-weight: bold;">[[Nebraska State Highway System]]</div><div class="noprint"><ul><li>[[List of Interstate Highways in Nebraska|Interstate]]</li><li>[[List of U.S. Highways in Nebraska|US]]</li><li>[[List of state highways in Nebraska|State]]</li><li>[[List of Nebraska Connecting Link, Spur, and Recreation Highways|Link]]</li><li>[[List of Nebraska Connecting Link, Spur, and Recreation Highways|Spur]]<ul></li><li>[[List of state spur highways in Nebraska|State Spurs]]</ul></li><li>[[List of Nebraska Connecting Link, Spur, and Recreation Highways|Recreation]]</li></ul></div></div>

If someone could track that down before deployment, that would be helpful. – Jonesey95 (talk) 18:15, 15 December 2021 (UTC)

 FixedFredddie 14:38, 16 December 2021 (UTC)

Lua errors

Lua error in Module:Infobox_road at line 87: bad argument #1 to 'len' (string expected, got nil) is appearing on a ton of articles, for example 4th Ring Road. * Pppery * it has begun... 18:01, 18 December 2021 (UTC)

@Pppery: Bringing this back to explain what's going on. I'm working on translations and I had to write something for Hungary that was messing things up for everybody else. It should be fixed now as that code only triggers for Hungary articles and I see road articles are clearing out of Category:Pages with script errors. –Fredddie 18:20, 18 December 2021 (UTC)

/translation template subpages orphaned?

A few dozen /translation/XXX subpages of this template, for example {{Infobox road/translation/IRN}}, showed up in Wikipedia:Database reports/Unused templates/1 this week, which means that they no longer have any transclusions. Have they been replaced by Lua code intentionally, as possibly indicated by the OP's item #3 above, or has their functionality been removed inadvertently? Or is there another explanation? If they are no longer needed, I would like to nominate them for deletion, with a reasonable explanation that someone here may be able to provide. – Jonesey95 (talk) 21:18, 21 December 2021 (UTC)

I'm sorry I did not see this sooner. The functionality no longer requires these templates per se, but the content within them needs to be transferred over. There are also a lot of IRN articles that use manual translations, that is, using the translation param in the infobox itself. I don't have time right now, but I will tag them for deletion when I know for sure they are no longer needed. –Fredddie 18:11, 29 December 2021 (UTC)
Thanks. I will keep my eye out for a TFD nomination by other editors, who may not see this conversation. – Jonesey95 (talk) 23:09, 29 December 2021 (UTC)
Not necessary. Most of them are gone already. –Fredddie 02:16, 30 December 2021 (UTC)
(edit conflict) Generally Fredddie passes the list to me and I delete under WP:CSD#G6 as a technical/housekeeping matter, rather than sending it to TFD for what is an obvious conclusion. --Rschen7754 02:20, 30 December 2021 (UTC)

January 2022 updates

  1. Browselinks (the highway system links or Transport in X links) are now on Lua.
    • Instead of each country having a module or using the road data modules, it's all in one big module.
    • It is controlled first by country code first (standard USA/CAN/AUS mask rules apply) and then by type, then state/province.
    • Every country is set up, yes all of them. If there is no special coding, it defaults to "Transport in <place>".
    • Some consolidation was done to keep code size down; i.e. standardizing verbiage and removing duplicate links to the same page
    • @Jonesey95: some wikitext browselinks templates will become unused and can be deleted. The ones that are used can be changed to an invoke of the new module.
  2. |system#= added.
    • If an infobox needs more than one set of browselinks, use |system1= through |system10= instead of |system= and a line break.
    • The system# parameters have the right class (hlist) so everything will display correctly.
  3. I still need to go through articles that use system because I'm going to refactor it as an override to the automatic browselinks. This has not yet occurred!

More updates as they happen! –Fredddie 04:47, 6 January 2022 (UTC)

@Fredddie: These updates seem to have caused some rendering problems with the browse functions, as evident in the infobox for U.S. Route 8 and U.S. Route 141 as examples. Is there a way this could be fixed? -- Politicsfan4 (talk) 23:51, 6 January 2022 (UTC)
Point #2 addresses this. Each manual instance of {{Infobox road/browselinks/USA}} should go in its own system# parameter, starting with |system1=. –Fredddie 00:08, 7 January 2022 (UTC)
Here is a diff for how to fix it. –Fredddie 00:09, 7 January 2022 (UTC)

Minor syntax error

A minor syntax error, an unmatched trailing ''', has cropped up in one of the test cases. I have created a minimal case here. The bold formatting appears just after the "State-Named Streets" link in both the sandbox and the live template. I poked around some recent changes but did not find it. – Jonesey95 (talk) 14:42, 7 January 2022 (UTC)

I found it. Luckily it only affected 10 articles. –Fredddie 17:52, 7 January 2022 (UTC)
Thanks for tracking it down. – Jonesey95 (talk) 19:34, 7 January 2022 (UTC)

Lua error in Module:Infobox_road at line 90: bad argument #2 to 'gsub' (string expected, got nil).

The above error message is appearing in several articles, including Faisalabad–Jaranwala Road and Margalla Avenue. * Pppery * it has begun... 16:56, 29 January 2022 (UTC)

 Fixed I had reconfigured Pakistan's translations to call {{Nastaliq}} automatically, but I did so requiring a route number. That's been fixed. –Fredddie 18:03, 29 January 2022 (UTC)

Locations module discussion

Module:Infobox road/locations/sandbox is basically ready to go, so I would like to hear some input on what I've created. You can see it in action in the testcases. Here are some highlights:

  • Deprecation of the hide sub-templates. I think we can police just as effectively as the hide sub-templates have done.
  • Display of countries and states/provinces by default so long as a country code has been provided
    • Territories, federal districts, crown dependencies, etc. have been taken into consideration
    Example: |country=USA|state=PR will display Country: United States and Territory: Puerto Rico
  • Customization for the countries that will benefit the most from it:
    • Australia, Brazil, Canada, China, France, India, Mexico, the Netherlands, Russia, the United Kingdom, and the United States are customized at present.
    • The WP:USRD rule of excluding major cities has been added.
    • Easy to add more countries
  • All other countries will have the same table of parameters available to them
  • Five generic parameters were added for outlier subdivision names.
  • Updated documentation is ready to go in my sandbox.

There was a discussion nearly 10 years ago about moving the location box higher up on the infobox. I think Moabdave mentioned it back then. So what do you all think? –Fredddie 05:45, 23 January 2022 (UTC)

It's going to be problematic to have country named autolinked per WP:OVERLINK. Otherwise, things look good. I'd be in favor of leaving the location section at the bottom of the infobox. Imzadi 1979  16:38, 23 January 2022 (UTC)
You're asking me what I proposed 10 years ago? Not fair! ;) I think it looks great. Reading Imzadi's comment, I can't decide if I like having a dedicated line with a wikilink to the country or not. Maybe make another parameter to include or omit this line? Dave (talk) 23:00, 28 January 2022 (UTC)
I get where you're coming from with a parameter to turn off the countries, but I think it would cause inconsistency between articles. –Fredddie 22:27, 29 January 2022 (UTC)

Template-protected edit request on 10 March 2022

Just wanted to tweak Washington's browselinks entry as follows: replace [[List of Primary State Highways in Washington|Former PSH]] with [[List of Primary State Highways in Washington|Pre-1964]] to make its entry clearer, per a note at a related FLC review. SounderBruce 23:44, 10 March 2022 (UTC)

 DoneXref. P.I. Ellsworth - ed. put'r there 03:27, 12 March 2022 (UTC)

United States

This infobox is populating Category:Infobox road instances in United States which is a redirect to Category:Infobox road instances in the United States. Please can the template be fixed so that it populates the correct category. Timrollpickering (talk) 16:14, 22 March 2022 (UTC)

The problem was that both |country=USA and |state=CO were set. Only the Colorado call is needed as its category is a subcat of the correct USA cat. I removed the country calls and we're good now. –Fredddie 18:19, 22 March 2022 (UTC)

Recent edits have broken parameters for named highways

Edits made to this infobox recently have broken some of the parameters for articles about named highways. New Jersey Turnpike no longer has its name or shield in the infobox, and Atlantic City Expressway has its name and shield replaced with that of its unsigned highway number. I don't know all the coding well enough to know exactly what the error is, but I see that edits were made to this infobox in the last 2 days, which may have caused this issue. –Dream out loud (talk) 06:50, 8 August 2022 (UTC)

Just to add, this does not seem to affect Canadian named road infoboxes, so it may be strictly in the US code. - Floydian τ ¢ 12:44, 8 August 2022 (UTC)
It's not broken as much as the old way is no longer supported. The infobox, for US articles, is now synced up with {{Jct}}, which uses NJTP to get N.J. TurnpikeFredddie 13:59, 8 August 2022 (UTC)

Template-protected edit request on 9 August 2022

Fredddie: It seems that your recent edits have resulted in Misnested tag with different rendering in HTML5 and HTML4 lint errors whenever the template includes |marker_image=. Kindly fix. — Anomalocaris (talk) 03:37, 9 August 2022 (UTC)

 DoneFredddie 20:12, 9 August 2022 (UTC)

Other articles with issues since the last changes

Fredddie other articles with issues since the last changes that showed up at CAT:MISSFILE

Cheers KylieTastic (talk) 15:59, 9 August 2022 (UTC)

Got one fixed in the article. Imzadi 1979  16:15, 9 August 2022 (UTC)
 Done The last half of the list (as rearranged by me) were all New York county roads, and there was no shieldmain parameter in Module:Road data/strings/USA/NY for CR. There is now! –Fredddie 20:52, 9 August 2022 (UTC)

"Lua error in Module:Infobox_road/route at line 66: attempt to compare two nil values"

... is showing up on a bunch of road articles in Puerto Rico, such as Puerto Rico Highway 137 * Pppery * it has begun... 14:31, 9 August 2022 (UTC)

This one is a little trickier, but I'm working on it. –Fredddie 22:24, 9 August 2022 (UTC)
@Pppery: should be good now. Let me know if you see anything goofy. –Fredddie 23:49, 9 August 2022 (UTC)

The article linked in the header of this section is displaying the error "Lua error in Module:Road_data/parser/hooks at line 46: bad argument #2 to 'format' (number expected, got string)." I tried for a few minutes to puzzle it out, and then I figured that the folks here would do a better job than I would. – Jonesey95 (talk) 04:19, 18 November 2022 (UTC)

I will have more time to look at it later, but I at least got rid of the error. –Fredddie 16:25, 18 November 2022 (UTC)

Automatic photo

Similar to the functionality for route maps, if there is a photo listed on Wikidata, it will now display in the infobox.

Since this does not apply to US articles, I thought this would be fairly uncontroversial.

I will revert if the community thinks otherwise. –Fredddie 18:17, 29 November 2022 (UTC)

Hi, I'm not sure if this is related, but it looks like articles using this template don't have any images in the infobox. Can someone confirm if this change is causing the image parameter not to work? Ganmatthew (talkcontribs) 06:09, 30 November 2022 (UTC)
@Ganmatthew can you provide some example of articles that do not have pictures that should? –Fredddie 02:46, 1 December 2022 (UTC)
I think I have it fixed, but please spot check some articles. –Fredddie 02:55, 1 December 2022 (UTC)
The articles I noticed the problem on appear to have the images in their infobox now. Thanks! Ganmatthew (talkcontribs) 09:50, 1 December 2022 (UTC)
Not a fan of this, especially for Canadian articles. Some of the selected Wikidata photos are either the first/RD photo already used in the article or a low-quality shot chosen years ago that was never properly updated. The lack of captions and ALT text is also an issue. SounderBruce 06:27, 1 December 2022 (UTC)
Because of how the photo has been selected on Wikidata, I can't support this either. If editors want a photo in the infobox in articles that aren't in the US, they should have to take affirmative steps to include one and supply a caption rather than have one appear automatically. Imzadi 1979  09:59, 1 December 2022 (UTC)
I reverted my change before I went to bed last night. –Fredddie 23:41, 1 December 2022 (UTC)

Space in German road names

According to Transport in Germany#Roads, "All Autobahnen are named by using the capital letter A, followed by a blank and a number (for example A 8)." However, in the infobox, the blank is not present, e.g. in Bundesautobahn 66, it says A66 in the infobox, not A 66. Can the infobox be adapted to allow for this? --Jameboy (talk) 23:31, 10 December 2022 (UTC)

 Done. Imzadi 1979  01:09, 11 December 2022 (UTC)

Previous and next routes

Hello all, when reading motorway articles on UK roads, I noticed the icon for the previous and next routes has become smaller. An example of this is that if you were reading the M2 motorway page, the section at the bottom of the infobox, where the icon is for reading the page before (M1 motorway), or after (M3 motorway), is super small. Could someone please change it back to the original size? Thank you. Roads4117 (talk) 18:38, 1 February 2023 (UTC)

Obviously, if this isn't the most important thing on your to-do list, then this can wait, but just an FYI. Roads4117 (talk) 12:02, 26 February 2023 (UTC)
It's an issue that I can't track down. The more you ask, the lower priority it will be. –Fredddie 06:29, 28 February 2023 (UTC)
Thanks for letting me know Roads4117 (talk) 17:38, 17 March 2023 (UTC)

United States

This template seems to be populating the redirect Category:Infobox road instances in United States instead of Category:Infobox road instances in the United States when misused. It is not remotely clear how to fix this on Northern Parkway (Baltimore). Please can someone in the know fix the template once and for all so future entries are not miscategorised. Timrollpickering (talk) 13:18, 7 January 2023 (UTC)

Toll roads?

Are there any parameters for indicating whether the whole or part of a road is tolled? I swear I once saw these. 10mmsocket (talk) 12:00, 10 June 2023 (UTC)

What were you looking for? In the sandbox, there is an option to have a tolled length, but that's nowhere near ready for deployment. –Fredddie 17:39, 10 June 2023 (UTC)
I saw that thanks. Shame it's not ready - although from my (UK) perspective we only have one actual toll road. 10mmsocket (talk) 06:31, 11 June 2023 (UTC)

Edit request 14 June 2023

Description of suggested change:

  • Two states in Mexico, Chihuahua and Hidalgo, are disambiguated with "(state)" and the federal district is at State of Mexico, so line 376 needs to change to a condition.

Diff:

infobox_args['data2'] = frame:expandTemplate ({title='Flagg', args = {"xx" , state(args), nodata = 1 }})
+
if args.state == "CHH" then infobox_args['data2'] = '[[Chihuahua (state)|Chihuahua]]' elseif args.state == "HID" then infobox_args['data2'] = '[[Hidalgo (state)|Hidalgo]]' elseif args.state == "MEX" then infobox_args['data2'] = '[[State of Mexico|México]]' else infobox_args['data2'] = frame:expandTemplate ({title='Flagg', args = {"xx" , state(args), nodata = 1 }}) end

Niceguyedc (talk) 05:46, 14 June 2023 (UTC)

This is right, but it's a workaround, because the module is effectively calling {{flagg|xx|MX-CHH}} (and so on), which points to the correct link {{flagg|xx|MX-CHH}}. I'll look at state(args) closer when I get home from work. –Fredddie 18:16, 14 June 2023 (UTC)
 DoneFredddie 22:14, 14 June 2023 (UTC)
After looking it over, that's the same way I handled Georgia, New York, and Washington, so it's changed. –Fredddie 22:16, 14 June 2023 (UTC)

Feature request: catch unimplemented province= use

According to /doc, the |province= field has specific and different meanings, depending on |country=. And it's not even implemented at all for other countries, whereas |provinces= is more generic. That's not intuitive and it leads to editors reasonably assuming "'province' if one, 'provinces' if multiple" (singular vs plural). So it's error-prone, and the results are confusing in at least two ways (see Wikipedia:Village pump (technical)#Infobox road mess). It would be useful if the template threw a diagnostic when called with 'province' for a country that does not implement that field. DMacks (talk) 14:26, 29 June 2023 (UTC)

Previous / next routes - revisited?

Just wanted to query the previous / next succession boxes. I'm not sure that linking road number X to road number X-(something, usually 1) and X+(something, usually 1) is inherently valuable. Most articles seem to have junction listings for roads met but in most places I am aware of there is nothing to say that eg the A271 has to meet the A270 and A273 (and only them) - culminating in things like the A999 being 'next' to the A1000; and indeed there are very few geographies that would allow for this (wouldn't it just be one long road with no junctions then?)

Just curious as to the rationale of this. 90.241.197.102 (talk) 07:22, 2 August 2023 (UTC)

Value is subjective. They're typically used in the US where the numbering systems are a bit smaller. Route browsing isn't required by any guideline or policy, so if they bother you, just remove them. –Fredddie 23:41, 2 August 2023 (UTC)
Thanks - it seems a bit random even in the US to be honest. Why is Interstate 235 (Iowa) coupled with Iowa Highway 224 and U.S. Route 275. neither of which it seems to meet; as opposed to Interstate 35 in Iowa and Interstate 80 in Iowa which it does at both ends? 90.241.197.102 (talk) 18:37, 3 August 2023 (UTC)
The browser deals with the numerical sequence, not the physical connections. It's been that way for a long time and mirrors how several websites organize things. It also reflects how many state departments of transportation organize their logs. Imzadi 1979  21:02, 3 August 2023 (UTC)

Template-protected edit request on 25 August 2023

Marker image isn’t' loading for Z series highway in the infobox. See Cox's Bazar–Teknaf Marine Drive. I had to use marker image manually there. Please fix it. Mehedi Abedin 13:42, 25 August 2023 (UTC)

To editor Mehedi Abedin: please help me understand. This template's documentation specifically states, "marker_image: shield image to be displayed. Requires full wiki markup. Typically not needed for numbered routes...." The editors of this template, then, have set it up to automatically show the shield image for numbered routes... "typically". So if I understand that correctly, the marker image is typically automatic, but sometimes not automatic. Evidently in the case of Cox's Bazar–Teknaf Marine Drive, the marker image is not automatic, so you had to include it manually. Sorry, but I don't see anything that's broken here; don't see anything that needs to be fixed. You had to use the |marker_image= parameter to include the correct shield image, which seems to be the correct thing to do when the image isn't included automatically. That may not be "typical", but evidently sometimes it's necessary. P.I. Ellsworth , ed. put'er there 12:21, 28 August 2023 (UTC)
@Paine Ellsworth Is there any way to make it automatic? Mehedi Abedin 12:43, 28 August 2023 (UTC)
Yes, after some digging, I found a way to do it, and I'll update the documentation so future editors won't have to dig so deeply for a solution. P.I. Ellsworth , ed. put'er there 13:13, 28 August 2023 (UTC)