Template talk:Infobox river

  1. Home
  2. Wiki

map zoom?

[edit]

@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)[reply]

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)[reply]
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)[reply]
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)[reply]
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)[reply]

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)[reply]

mapframe on by default even if pushpin map present?

[edit]

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)[reply]

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)[reply]
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)[reply]
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)[reply]

mapframe coordinates at Danube

[edit]

For some reason Danube map is centered on eastern Atlantic rather than on the river shape. I first thought my recent edits broke it somehow, but the previous revision seems to show the same...? --Joy (talk) 13:43, 22 March 2025 (UTC)[reply]

I've made a fix in OSM. Regs, The Equalizer (talk) 03:45, 28 March 2025 (UTC)[reply]
@The Equalizer thanks. So I guess this is one of the classic reasons why there was opposition in RFCs such as Wikipedia:Requests for comment/Mapframe maps in infoboxes - stuff breaks and the process for fixing it is so obfuscated. --Joy (talk) 14:13, 29 March 2025 (UTC)[reply]

Template:Mapriver

[edit]

Cf. Template talk:Mapriver. --Joy (talk) 10:47, 7 May 2025 (UTC)[reply]

errors in wikidata coordinates

[edit]

Cf. Template talk:Infobox settlement#on rendering wikidata. --Joy (talk) 08:54, 15 May 2025 (UTC)[reply]

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

[edit]

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)[reply]