Template talk:Infobox river

map zoom?

@Hike395 could you have a look at - 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)

OK so after fixing many, many river articles to split units from dimensions, I also happened to encounter uses of |map={{maplink}} that were reasonably well zoomed in already. Maybe we just need to do what that template does by default, instead?

An example is Blesbokspruit. If you add |mapframe=yes to the infobox there, it's fairly clear that the zoom operates on the whole browser window (after one clicks the button), but it's fairly obvious that it could also operate on the initial infobox frame like the maplink call does.

@Hike395 could you have another look? --Joy (talk) 13:26, 16 May 2025 (UTC)

Discussion of default rendering of shapes/lines in Template:Infobox mapframe

We're discussing how to handle the rendering of shapes/lines in Template:Infobox mapframe, given that OSM data is unreliable. This will likely affect this template. You're welcome to join in the discussion. — hike395 (talk) 09:49, 8 November 2025 (UTC)

How hide wikidata photo at top of the InfoBox?

I'm working on the Nile article, and the InfoBox is unusually tall. How tall is it? It goes all the way down the lead; all the way through the first body section, and into the second body section. That is 2 1/2 sections.

The biggest issue is the photo & map are both displayed at the top. There are hundreds of photos of the Nile available to display throughout the body of the article, so I'd like to experiment with displaying only the map. I cannot figure out how to remove the wikidata photo from the top of the InfoBox. The wikidata photo is File:Cairo skyline, Panoramic view, Egypt.jpg. Anyone know how to hide that photo?

Alternatively, if a photo of the river cannot be hidden, is there a way to hid the map from the InfoBox? I understand that maps are commonly used in InfoBoxes, but the Nile article has many body sections that discuss hydrography and geology, and maps can be placed there.

It cannot be that the the river infobox forces InfoBoxes to be extremely tall, can it? Noleander (talk) 03:00, 5 January 2026 (UTC)

You can use |suppressfields=image to do this - I have applied it to the infobox — Martin (MSGJ · talk) 05:36, 5 January 2026 (UTC)

I also tried removing the map, and the default one (while inferior) takes up much less space. You might use the better map lower down in the article if that helps — Martin (MSGJ · talk) 05:38, 5 January 2026 (UTC)

@MSGJ - Thanks for the information. What about keeping the top image but suppressing the map entirely? Is there a way to do that? I tried:

|suppressfields=map

but that didn't seem to work. Also, is there a help page that discuesses these behaivors of InfoBox? Maybe I can go there and learn about it myself. Noleander (talk) 15:29, 5 January 2026 (UTC)

You can use |mapframe=no. I am not aware of a single page which will explain all this because each infobox is set up slightly differently. So you are relying on the template's documentation. — Martin (MSGJ · talk) 16:17, 5 January 2026 (UTC)

Thanks, that worked.

I added this info into the Template Doc page:

To completely suppress the default image in the Infobox, including any image from Wikidata, use |suppressfields=image. To completely suppress the default mapframe in the Infobox, including the map based on Wikidata, use |mapframe=no.

I think it is incredibly useful information that future editiors will want. If anyone can improve the formatting or wording, that would be great. But please do not delete the info because a non template editor added the info ... the encyclopedia does not need more WP:ownership. I've build a lot of Sidebar InfoBoxes over the years, but suppressing the image and map in this InfoBox was not intuitive at all; and was not documented in this Doc page. Noleander (talk) 16:38, 5 January 2026 (UTC)

The mapframe parameter is already documented at Template:Infobox river#Mapframe parameters — Martin (MSGJ · talk) 16:41, 5 January 2026 (UTC)

Thanks for pointing that out; I removed the duplicated "how to hide map" text. Noleander (talk) 17:24, 5 January 2026 (UTC)

Discussion at Wikipedia:Templates for discussion/Log/2026 February 4 § Template:Mapriver

 You are invited to join the discussion at Wikipedia:Templates for discussion/Log/2026 February 4 § Template:Mapriver. -- Joy (talk) 11:09, 4 February 2026 (UTC)

as a followup, are there any objections to implementing the more complete "mapriver" maps in this infobox? if you look at this demonstration, the map in the infobox is what we currently have, while the maps directly below are generated by "mapriver". the mapriver maps show the tributaries, and a second map zoomed out map. we could also do a hybrid of these two approaches (e.g., tributaries plus source marker) or use a "switcher"? what do you think? Frietjes (talk) 16:39, 24 February 2026 (UTC)

Pushpin map cleanup

As part of a larger refactor of Module:Location map, I will be refactoring the way that this Infobox calls the location map code. The only noticeable change for most will be that the parameter names related to the pushpin maps will now all start with |pushpin_...=. This is part of a larger effort to make things consistent across Infoboxes. When this is done, ALL infoboxes using pushpin maps will use the same parameters. For more information about this, please see this post. As part of this cleanup, I am also going to resolving any conflicting parameters that I can find and cleaning up parameter names that fail to conform to MOS:INFOBOXNAME. Note that this follows a long list of similar clean ups that I have done on countless other Infoboxes. The parameters I plan to replace are the following:

Deprecate	Replace with
|name_other=	|other_name=
|pushpin_map_alt=	|pushpin_alt=
|pushpin_map_relief=	|pushpin_relief=
|pushpin_map_caption=	|pushpin_caption=
|name_etymology=	|etymology=
|name_native=	|native_name=
|parent=	|river_system=
|landmark=	|basin_landmarks=
|city=	|cities=
|country_type=	|subdivision_type1=
|country=	|subdivision_name1=
|state_type=	|subdivision_type2=
|state=	|subdivision_name2=
|region_type=	|subdivision_type3=
|region=	|subdivision_name3=
|district_type=	|subdivision_type4=
|district=	|subdivision_name4=
|municipality_type=	|subdivision_type5=
|municipality=	|subdivision_name5=

While I am at this, do we also want to eliminate the following conflicting parameters? Happy to do them as well!

| subdivision_type1; country_type 
| subdivision_name1; country 
| subdivision_type2; state_type 
| subdivision_name2; state 
| subdivision_type3; region_type 
| subdivision_name3; region 
| subdivision_type4; district_type 
| subdivision_name4; district 
| subdivision_type5; municipality_type 
| subdivision_name5; municipality 

Please chime in below with any questions, comments or concerns about this cleanup. Zackmann (^{Talk to me}/_{What I been doing}) 04:01, 28 July 2026 (UTC)

After consulting the param report, it is clear that these parameters are barely used so going to go ahead and deprecate them as well. --Zackmann (^{Talk to me}/_{What I been doing}) 02:05, 29 July 2026 (UTC)