Template talk:Infobox river

Unused parameters?

• Should discharge1_(min / avg / max)_(imperial / metric) etc be removed / killed / expunged / deprecated? I found just four uses of any of these and changed them all to use {{convert}} instead — GhostInTheMachine ^{talk to me} 12:47, 5 November 2023 (UTC)

  I have now removed all uses of |discharge1_avg_imperial= |discharge1_avg_metric= |discharge1_max_imperial= |discharge1_min_imperial=

  Also |mouth_elevation_imperial= and |mouth_elevation_metric= — GhostInTheMachine ^{talk to me} 22:43, 7 November 2023 (UTC)

  I have removed all of the metric and imperial parameters; they were used in maybe a dozen articles total and are clearly not needed. They haven't been in the documentation for a while, it appears. Please keep an eye on the unsupported parameter category for any articles that might have been missed. – Jonesey95 (talk) 01:52, 8 November 2023 (UTC)

  Awesome – and somewhat bolder than I would have managed! I will get busy with the 21 articles now flagged — GhostInTheMachine ^{talk to me} 12:28, 8 November 2023 (UTC)

  Y — GhostInTheMachine ^{talk to me} 19:27, 8 November 2023 (UTC)

• Are the plain parameters discharge1 .. discharge5 live (and so should be documented) / obsolete (and so should be discouraged) / deprecated (and so should be deleted)? — GhostInTheMachine ^{talk to me} 19:10, 5 November 2023 (UTC)

  It sounds like you are asking if the parameter |discharge1= is a supported parameter in the template that affects the output of the infobox. If that is your question, the answer is yes, but only in a very few articles. It appears that the other four are unused. A helpful tip: to click on the monthly parameter usage report in the TemplateData section. Find the parameter in question, follow the "page links" link, and see how it is being used in articles. Doing these steps will take you to Escanaba River and other articles.

  These five parameters should probably be deprecated and replaced in articles with |discharge1_avg=. – Jonesey95 (talk) 16:13, 6 November 2023 (UTC)

  Mostly I was asking about policy: the removal or continued intended use of apparently obsolete parameters. I have edited the 7 articles using |discharge1= to now use something else — 4 to |discharge1_avg= and 3 to |mouth=. Please can we remove |discharge1= .. |discharge5= from the template? — GhostInTheMachine ^{talk to me} 22:46, 7 November 2023 (UTC)

   Done. – Jonesey95 (talk) 01:46, 8 November 2023 (UTC)

Additional image or map parameters

Are these available on this template, like on Template:Infobox settlement or Template:Infobox public transit? Trying to figure out if it is possible to include multiple maps in the infobox. See Wikipedia:Village_pump_(policy)#Preference_of_using_OpenStreetMaps. Shannon [ Talk ] 16:06, 29 March 2024 (UTC)

@Shannon1 I sandboxed that at template:Infobox river/sandbox here is an example output, note hidden map and shown map.

Seine
The Seine in Paris
Native name	la Seine (French)
Location
Country	France
Physical characteristics
Source
• location	Source-Seine
Mouth	English Channel (French: la Manche)
• location	Le Havre/Honfleur
• coordinates	49°26′02″N 0°12′24″E
• elevation	0 m (0 ft)
Length	777 km (483 mi)
Basin size	79,000 km2 (31,000 sq mi)
Discharge
• location	Le Havre
• average	560 m3/s (20,000 cu ft/s)
Basin features
River system	Seine basin
Tributaries
• left	Yonne, Loing, Eure, Risle
• right	Ource, Aube, Marne, Oise, Epte

— Preceding unsigned comment added by Hooman Mallahzadeh (talk • contribs) 29 March 2024 (UTC)

This proposal didn't attract any interest in the meantime. At the same time, it deviates from the by-now-conventional solution to Wikipedia:Mapframe maps in infoboxes. I'll go draft that instead. --Joy (talk) 19:08, 27 October 2024 (UTC)

Added that, and the above Seine testcase to Template:Infobox river/testcases, and another few ones to demonstrate variety in execution based on different parameters. --Joy (talk) 20:53, 27 October 2024 (UTC)

map zoom?

@Hike395 could you have a look at [1] - is it plausible to try to use {{map zoom}} with length and basin size here? --Joy (talk) 20:58, 27 October 2024 (UTC)

Sadly those won't work. {{map zoom}} will only take numeric values with the correct units. |length= is a "free" parameter that the documentation expects a call to {{convert}}. Same thing for |basin_size=.

What would work is if you added |length_km= and |basin_size_km2=, but then you'd have to modify the template to accept those and existing infoboxes wouldn't have them. — hike395 (talk) 23:17, 27 October 2024 (UTC)

As we don't necessarily need much precision, could we just fake it for a start, e.g. is there some template/module that would extract the numeric part from free-form parameters? --Joy (talk) 04:56, 28 October 2024 (UTC)

In the meantime this process continued with converting these template input dimensions in a way that can get passed automatically to the map template code, which then automagically fixes the mapframe zoom. I've been using WP:JWB for it and it's mostly simple, if tedious. --Joy (talk) 21:32, 21 November 2024 (UTC)

I've published the mapframe support in the infobox, with onbydefault it started showing up, and from the dozen examples I found, many had zoom issues. Obviously easy to work around on a case-by-case basis, but still a bit annoying. --Joy (talk) 12:04, 1 November 2024 (UTC)

Addition of discharge regime parameter

Hi,

I recently expanded the article about the discharge regime (which was previously grouped with river regime) to the point where it is not a stub anymore. I tried to decentralize it from the Alpine region where it is most commonly used and make it more globally balanced and I think now the article is developed to the point that a parameter for discharge regime could also be added to the infobox. I am thinking that the parameter would give just basic information about the regime, i.e. temperate pluvial, mediterranean, Texan, tropical pluvial/intertropical, equatorial, nival, nivo-glacial, glacial, nivo-pluvial, pluvio-nival, uniform, complex; and not all the subdivisions that are listed, maybe with addition of the month when the peak occurs, e.g. tropical pluvial (peak in September). What do you think? Garygo golob (talk) 09:00, 15 May 2024 (UTC)

redundant maps

This is a search that finds |extra= parameters that contain the start of a template transclusion syntax, as well as {{infobox mapframe}}, which typically leads to now-redundant copies:

https://wiki.riteme.site/w/index.php?search=hastemplate%3A%22Infobox+river%22+insource%3A%2Fextra+%2A%3D+%2A%5C%7B%5C%7B%2F+hastemplate%3A%22Infobox+mapframe%22&title=Special:Search&profile=advanced&fulltext=1&ns0=1

--Joy (talk) 16:13, 16 November 2024 (UTC)

mapframe on by default even if pushpin map present?

We currently enable mapframe to be on by default only if no other maps are present. This logic was imported from other infobox templates.

Other uses of mapframe where a single map point is common often match pushpin maps, and the mapframe generally provides only a different default zoom and the zoom in/out functionality, etc.

Rivers are rarely well defined by a single point, however, as there's always at least one source and at least one mouth. Accordingly, rivers are often defined by a line shape at OSM, not just a point, so a mapframe map can provide significantly more information compared to a general pushpin map.

Would anyone mind if we also enabled mapframe by default even if a pushpin map is present? --Joy (talk) 17:05, 18 November 2024 (UTC)

I think that is what |mapframe=yes is for. It always helps to link to an example article. – Jonesey95 (talk) 15:59, 19 November 2024 (UTC)

Well that's the problem - having to add an explicit mapframe=yes to tens of thousands of rivers is a chore, and probably a pointless one. We have so much busywork with these templates, if we could set a sensible default here it would relieve us of at least one bit of it. --Joy (talk) 21:30, 21 November 2024 (UTC)

I think infoboxes are getting too long as it is: automatically adding mapframe to every article is going to produce thousands of articles with poor layout that we won't be able to check. Jonesey has it correct -- we can allow editor opt-in for mapframe, but shouldn't add it by default. — hike395 (talk) 00:46, 22 November 2024 (UTC)