Template talk:Infobox mountain

Possible additional 'elevation' parameters
Browsing Mount Nebo I saw that it is about 700m above sea level. But it is also beside the Dead Sea whose surface is about 430.5m below sea level. This means that it is 1130.5m above a local baseline. So I wondered whether there might be a case for additional elevation information, e.g. "local elevation", for cases where such a concept might be relevant. Probably not, but I thought it might be worth raising the idea. Feline Hymnic (talk) 14:35, 4 November 2023 (UTC)

Template for mountain ranges
Quick question - is there a template which would be more suitable for articles about specific mountain ranges or mountainous areas? I see that Alps, Andes, and Rocky Mountains use this template, but it seems a bit cumbersome as it was really designed for single mountains. Thanks, A.D.Hope (talk) 23:42, 4 February 2024 (UTC)


 * Infobox mountain range was merged into Infobox mountain in 2015, so this is the best one. — hike395 (talk) 00:45, 5 February 2024 (UTC)

Mountain range names not showing up
I've noticed the names of mountain ranges don't show up on the infobox map while range_coordinates is being used. Is this an error? Volcanoguy 00:59, 19 March 2024 (UTC)


 * For example, see Mount Edziza volcanic complex versus Mount Edziza. Volcanoguy 01:05, 19 March 2024 (UTC)
 * I suspect this is a deep programming problem that removes the intended default overlay code and is likely deeper than the infobox mountain template although topo-map parameter which is definitely buggy is used on one of the maps you refer to. The various infobox templates do handle mapping code differently I have discovered over the years and I tend not to report as bug if I can figure away around to get the display I want as often the code author assumes a certain way maps are presented in infobox. For example at the moment I am in the process of moving some topo_map using maplink generated geological maps with frames to the embedded= parameter as topo-map parameter associated code assumes I think pure image code not surrounded by divs and can completely fall over with unframed maplink template maps.ChaseKiwi (talk) 09:56, 20 April 2024 (UTC)
 * As far as I can tell, this was for compatibility with Infobox mountain range, which did not have map labels, because of compatibility with Geobox. I can't think of a reason why we shouldn't display the label, so I fixed it. Apologies for the delay -- I missed your original post. — hike395 (talk) 11:17, 20 April 2024 (UTC)

Nowrap labels?
Is there some way to make parameters not break while using them in the infobox? This especially happens while lengthy parameters like "English translation" and "Range coordinates" are being used (e.g. Tennena Cone and Mount Edziza volcanic complex). Volcanoguy 19:34, 9 July 2024 (UTC)


 * Yes, this is an easy change to make on individual labels. I'll add nowrap to those labels and see how it affects the test cases. — hike395 (talk) 04:48, 10 July 2024 (UTC)
 * Per your request from a year ago, I think it's good to drop "English" from "English translation". I implemented nowrap for "Range coordinates", but it needs to make the infobox a little wider to not cause a lot of ugly wrapping of data fields. Now implemented in the sandbox, see the testcases. What do editors think? — hike395 (talk) 05:06, 10 July 2024 (UTC)
 * It looks good to me. I was thinking maybe the box would have to be widened a bit while I wrote my last comment but wasn't sure. Volcanoguy 06:02, 10 July 2024 (UTC)
 * to clarify --- the box is only wider if range_coordinates is not empty. — hike395 (talk) 11:37, 10 July 2024 (UTC)
 * I'm not against widening the infobox slightly as an alternative if there's opposition to nowrapping labels. <i style="color: red;">Volcano</i><i style="color: black;">guy</i> 04:52, 11 July 2024 (UTC)
 * I don't use this template so take this for whatever it's worth. I would oppose nowrapping labels.  Let your browser decide how best to render the infobox; don't micromanage.  Don't like label wraps?  Find a better (shorter) label.  Use nowrapping for things that matter, don't nowrap when it really doesn't matter; see.
 * —Trappist the monk (talk) 11:52, 10 July 2024 (UTC)
 * I have to say the infobox looks tidier without any line breaks. Not sure if range-coordinates can be shortened. <i style="color: red;">Volcano</i><i style="color: black;">guy</i> 16:01, 10 July 2024 (UTC)
 * Does it even need to be in the infobox? The coordinates of the mountain are the important information. The range seems secondary &mdash; Martin (MSGJ · talk) 21:50, 10 July 2024 (UTC)
 * The highest mountain in a range isn't always known so range-coordinates would be used instead. <i style="color: red;">Volcano</i><i style="color: black;">guy</i> 23:00, 10 July 2024 (UTC)
 * And the highest point sometimes isn't in the center of the range: without range-coordinates, geohack could show a lopsided view of the range. — hike395 (talk) 23:34, 10 July 2024 (UTC)

Embedded
I think it would be ideal to add embedded-caption and maybe embedded-alt for embedded images in the infobox. <i style="color: red;">Volcano</i><i style="color: black;">guy</i> 17:39, 11 July 2024 (UTC)


 * Since the mountain infobox isn't overly big, I'd suggest going for a fully automatic Infobox mapframe in all articles. Static (pushpin) maps are good for general orientation, but cannot be zoomed in and out, and when clicked, the pushpin disappears. The only thing that would need to be done is removing the manually added templates from these. Ponor (talk) 11:44, 15 July 2024 (UTC)