This is the
talk page for discussing improvements to the
Infobox mountain range redirect. |
|
Archives: 1Auto-archiving period: 180 days |
Mountains NA‑class | |||||||
|
I have created Wikipedia:WikiProject Mountains/List of mountain ranges to act as a project watch list for recent changes to articles using this template. I did an initial population although my approach is more manual than if you can run AWB. I will update the talk page when I get a chance. I will also add a new section on watch lists to the main project page. RedWolf ( talk) 07:04, 7 May 2012 (UTC)
Copied from User talk:Hike395#Concerns with conversion
So, I think, these things need attention.
There are examples of the white space issue here and the markup is here. Please read my comment, on another issue at Template talk:Infobox mountain#Change to relief map setting. – droll [chat] 18:24, 12 May 2012 (UTC)
This template is impacted by a bug in {{ Decdeg}} which I reported on the template's talk page. — Stepheng3 ( talk) 18:26, 7 June 2012 (UTC)
range_lat_s > 59.5
. In that case, {{#expr:{{{range_lat_s}}} round 0}}
produces 60, which is an invalid input to {{
Infobox coord}}. There's also an analogous bug involving the range_long_s parameter. —
Stepheng3 (
talk) 20:19, 7 June 2012 (UTC)
|range_lat_d=35
|range_lat_m=23
|range_lat_s=59.873
, turning that into 35°24'0", it doesn't handle situations like |range_lat_d=35
|range_lat_m=59
|range_lat_s=59.873
- these still come out as 35°60'0" not 36°0'0". --
Redrose64 (
talk) 20:44, 7 June 2012 (UTC)
| data28 = {{#if:{{{range_lat_d|}}}{{{range_long_d|}}} | {{Infobox coord | lat_d = {{{range_lat_d|}}} | lat_m = {{{range_lat_m|}}} | lat_NS = {{{range_lat_NS|}}} | long_d = {{{range_long_d|}}} | long_m = {{{range_long_m|}}} | long_EW = {{{range_long_EW|}}} | type = {{ifempty|{{{coord_type|}}}|mountain}}
|range_lat_s=
and |range_long_s=
parameters would then be unrecognised. According to
WP:OPCOORD, the difference between 35°23' and 35°24' is under 2 km and the chances of two different ranges having their centres any closer together than this is extremely unlikely. --
Redrose64 (
talk) 07:27, 8 June 2012 (UTC)I think we want to go for a wee bit more precision than that. You're probably thinking of ranges like the
Alps. But, some ranges are more like ridges: they're only several kilometers long to begin with and not that wide, so truncating to 2 kilometers (per your suggestion) may fall off the ridge entirely. Rounding to the nearest 50-100m point seems like a good compromise, introducing no more than 50m of "error" (I wish that decdeg did dms rounding, but it's a pretty simple template). I put error in quotes, because range location is not well defined.
As an example, consider the case under consideration:
Black Hills (San Bernardino County). The current infobox uses
35°24′00″N 117°18′43″W / 35.4°N 117.312°W, while your proposal would use
35°23′N 117°18′W / 35.383°N 117.300°W, which jumps to the next ridge over! So, we do need the extra factor of 40 precision. —
hike395 (
talk) 10:17, 8 June 2012 (UTC)
I just put this template on Hawaiian–Emperor seamount chain and was wondering about filling things in - specifically, the mountain range obviously exist because of the Hawaii hotspot, but I'm not sure where to put it in this template. Ideas? Ego White Tray ( talk) 04:01, 31 January 2013 (UTC)
Related to above section, very little change would be needed for this template to work well with undersea ranges. As I see it, add a parameter to name a highest point as a depth for ranges that don't surface, to name an ocean or sea, and add parameters to name up to 9 islands (island1, island2, etc, listing island chains rather than individual islands when possible). After than, throw an undersea range on the test page, ideally as the second example, so users can see that it works, even if the idea never occurred to them. Ego White Tray ( talk) 13:48, 31 January 2013 (UTC)
There is some sort of problem with it. I'm looking into it right now. — hike395 ( talk) 21:39, 28 April 2013 (UTC)
{{{map_relief}}}
to 0 to force it off. —
hike395 (
talk) 22:11, 28 April 2013 (UTC)It is producing this as the error {{#coordinates:}}: cannot have more than one primary tag per page I am not sure what I am doing wrong, or even if I am to blame. Please help. speednat ( talk) 21:06, 7 November 2013 (UTC)
The geology section of this template currently has three parameters: orogeny, period and type of rock. There is another parameter that would be useful: "type of range". Mountain ranges are formed by different processes, including fold and thrust, fault-block and volcanic activity. Volcano guy 03:02, 18 July 2014 (UTC)
|formed_by=
with a link to
Mountain formation, but I can certainly change it to |geological_type=
with a link to
List of mountain types instead if that's better (or you can do it!).
Frietjes (
talk) 18:28, 29 July 2014 (UTC)
Recently I have been wondering why there are separate infoboxes for both mountains and mountain ranges. Can someone please explain? It's just that {{ Infobox mountain range}} can be used in articles about individual mountains, especially large ones, since it is possible for a mountain to have secondary summits. Most if not all of the fields in this template can refer to a single mountain and be used the same way. The range coordinates could refer to the mountain coordinates and the highest point coordinates could refer to the highest summit of a mountain. Volcano guy 13:23, 30 January 2015 (UTC)
|location=
parameter. I think that the latter makes a lot of sense (it's much easier for editors), but I could not figure out how convert the Geobox articles without losing information. There's also two different location parameters for ranges, the "range_lat_d" style parameters, and the "lat_d" parameters. The former are central coordinates for the entire range, while the latter is the coordinate of the highest point. This may be confusing to mountain article editors and lead to incorrectly filled-out infoboxes.|prominence=
, |isolation=
, |parent_peak=
, |easiest_route=
. I suppose you could put these into the "Highest point" section for the mountain, but that might be a little strange in an article about an isolated mountain. —
hike395 (
talk) 04:38, 31 January 2015 (UTC)
|range_coordinates=
and |parent_range=
, which are for mountain ranges and not isolated mountains. There must a way to merge {{
Infobox mountain range}} and {{
Infobox mountain}} into a single infobox. I assume the use of the mountain and mountain range parameters could be explained. For example, in {{
Infobox mountain}} there is a distinctive description for the |volcanic_XXX=
parameters: If the mountain is a volcano, the arc, belt or field in which it is situated. Obviously these parameters are inappropiate for non-volcanic mountains since they are not volcanic in origin but they are included in {{
Infobox mountain}} anyway.
Volcano
guy 07:42, 31 January 2015 (UTC)|range_lat_d=
for a mountain, which would appear under "Range Coordinates" in the Geography section. Editors can use it to specify inexact coordinates of massifs, for example. There is also already a parameter, |highest=
, where you can specify the name of the highest peak (separately from the name of the mountain/range). —
hike395 (
talk) 03:30, 4 February 2015 (UTC)|volume=
, |volume_km3=
, |volume_mi3=
, |volume_note=
. Seems good for volcanoes. —
hike395 (
talk) 18:28, 4 February 2015 (UTC)
|area=
because it just gives "Area" in the infobox but after looking at {{
Infobox mountain range}} it gives |area_km2=
so I'm not sure if |volume=
would be redundant with |volume_km3=
and |volume_mi3=
unless someone uses smaller measurements which I have not seen for mountains.
Volcano
guy 21:10, 4 February 2015 (UTC)|area=
(and other parameters, like |length=
or |volume=
) are used for free-form entries, typically expressing uncertainty ranges, e.g., |area={{convert|4|to|6|km2|mi2}}
. —
hike395 (
talk) 02:53, 5 February 2015 (UTC)
The result of the discussion was to merge this template into {{ Infobox mountain}}. Further discussion on the design of the merged template is at the Mountain WikiProject talk page — hike395 ( talk) 03:50, 15 February 2015 (UTC)
There was consensus at TfD to merge this template into {{ Infobox mountain}}, but some issues remain to be resolved. A draft is at User:Hike395/MtnComboBox. How should the merge take place? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:13, 23 May 2015 (UTC)
{{{region}}}
to {{{region_code}}}
. This new parameter is already part of {{
Infobox mountain}}, and will avoid errors in the next step.This is the
talk page for discussing improvements to the
Infobox mountain range redirect. |
|
Archives: 1Auto-archiving period: 180 days |
Mountains NA‑class | |||||||
|
Geography Redirect‑class | ||||||||||||||
|
I have created Wikipedia:WikiProject Mountains/List of mountain ranges to act as a project watch list for recent changes to articles using this template. I did an initial population although my approach is more manual than if you can run AWB. I will update the talk page when I get a chance. I will also add a new section on watch lists to the main project page. RedWolf ( talk) 07:04, 7 May 2012 (UTC)
Copied from User talk:Hike395#Concerns with conversion
So, I think, these things need attention.
There are examples of the white space issue here and the markup is here. Please read my comment, on another issue at Template talk:Infobox mountain#Change to relief map setting. – droll [chat] 18:24, 12 May 2012 (UTC)
This template is impacted by a bug in {{ Decdeg}} which I reported on the template's talk page. — Stepheng3 ( talk) 18:26, 7 June 2012 (UTC)
range_lat_s > 59.5
. In that case, {{#expr:{{{range_lat_s}}} round 0}}
produces 60, which is an invalid input to {{
Infobox coord}}. There's also an analogous bug involving the range_long_s parameter. —
Stepheng3 (
talk) 20:19, 7 June 2012 (UTC)
|range_lat_d=35
|range_lat_m=23
|range_lat_s=59.873
, turning that into 35°24'0", it doesn't handle situations like |range_lat_d=35
|range_lat_m=59
|range_lat_s=59.873
- these still come out as 35°60'0" not 36°0'0". --
Redrose64 (
talk) 20:44, 7 June 2012 (UTC)
| data28 = {{#if:{{{range_lat_d|}}}{{{range_long_d|}}} | {{Infobox coord | lat_d = {{{range_lat_d|}}} | lat_m = {{{range_lat_m|}}} | lat_NS = {{{range_lat_NS|}}} | long_d = {{{range_long_d|}}} | long_m = {{{range_long_m|}}} | long_EW = {{{range_long_EW|}}} | type = {{ifempty|{{{coord_type|}}}|mountain}}
|range_lat_s=
and |range_long_s=
parameters would then be unrecognised. According to
WP:OPCOORD, the difference between 35°23' and 35°24' is under 2 km and the chances of two different ranges having their centres any closer together than this is extremely unlikely. --
Redrose64 (
talk) 07:27, 8 June 2012 (UTC)I think we want to go for a wee bit more precision than that. You're probably thinking of ranges like the
Alps. But, some ranges are more like ridges: they're only several kilometers long to begin with and not that wide, so truncating to 2 kilometers (per your suggestion) may fall off the ridge entirely. Rounding to the nearest 50-100m point seems like a good compromise, introducing no more than 50m of "error" (I wish that decdeg did dms rounding, but it's a pretty simple template). I put error in quotes, because range location is not well defined.
As an example, consider the case under consideration:
Black Hills (San Bernardino County). The current infobox uses
35°24′00″N 117°18′43″W / 35.4°N 117.312°W, while your proposal would use
35°23′N 117°18′W / 35.383°N 117.300°W, which jumps to the next ridge over! So, we do need the extra factor of 40 precision. —
hike395 (
talk) 10:17, 8 June 2012 (UTC)
I just put this template on Hawaiian–Emperor seamount chain and was wondering about filling things in - specifically, the mountain range obviously exist because of the Hawaii hotspot, but I'm not sure where to put it in this template. Ideas? Ego White Tray ( talk) 04:01, 31 January 2013 (UTC)
Related to above section, very little change would be needed for this template to work well with undersea ranges. As I see it, add a parameter to name a highest point as a depth for ranges that don't surface, to name an ocean or sea, and add parameters to name up to 9 islands (island1, island2, etc, listing island chains rather than individual islands when possible). After than, throw an undersea range on the test page, ideally as the second example, so users can see that it works, even if the idea never occurred to them. Ego White Tray ( talk) 13:48, 31 January 2013 (UTC)
There is some sort of problem with it. I'm looking into it right now. — hike395 ( talk) 21:39, 28 April 2013 (UTC)
{{{map_relief}}}
to 0 to force it off. —
hike395 (
talk) 22:11, 28 April 2013 (UTC)It is producing this as the error {{#coordinates:}}: cannot have more than one primary tag per page I am not sure what I am doing wrong, or even if I am to blame. Please help. speednat ( talk) 21:06, 7 November 2013 (UTC)
The geology section of this template currently has three parameters: orogeny, period and type of rock. There is another parameter that would be useful: "type of range". Mountain ranges are formed by different processes, including fold and thrust, fault-block and volcanic activity. Volcano guy 03:02, 18 July 2014 (UTC)
|formed_by=
with a link to
Mountain formation, but I can certainly change it to |geological_type=
with a link to
List of mountain types instead if that's better (or you can do it!).
Frietjes (
talk) 18:28, 29 July 2014 (UTC)
Recently I have been wondering why there are separate infoboxes for both mountains and mountain ranges. Can someone please explain? It's just that {{ Infobox mountain range}} can be used in articles about individual mountains, especially large ones, since it is possible for a mountain to have secondary summits. Most if not all of the fields in this template can refer to a single mountain and be used the same way. The range coordinates could refer to the mountain coordinates and the highest point coordinates could refer to the highest summit of a mountain. Volcano guy 13:23, 30 January 2015 (UTC)
|location=
parameter. I think that the latter makes a lot of sense (it's much easier for editors), but I could not figure out how convert the Geobox articles without losing information. There's also two different location parameters for ranges, the "range_lat_d" style parameters, and the "lat_d" parameters. The former are central coordinates for the entire range, while the latter is the coordinate of the highest point. This may be confusing to mountain article editors and lead to incorrectly filled-out infoboxes.|prominence=
, |isolation=
, |parent_peak=
, |easiest_route=
. I suppose you could put these into the "Highest point" section for the mountain, but that might be a little strange in an article about an isolated mountain. —
hike395 (
talk) 04:38, 31 January 2015 (UTC)
|range_coordinates=
and |parent_range=
, which are for mountain ranges and not isolated mountains. There must a way to merge {{
Infobox mountain range}} and {{
Infobox mountain}} into a single infobox. I assume the use of the mountain and mountain range parameters could be explained. For example, in {{
Infobox mountain}} there is a distinctive description for the |volcanic_XXX=
parameters: If the mountain is a volcano, the arc, belt or field in which it is situated. Obviously these parameters are inappropiate for non-volcanic mountains since they are not volcanic in origin but they are included in {{
Infobox mountain}} anyway.
Volcano
guy 07:42, 31 January 2015 (UTC)|range_lat_d=
for a mountain, which would appear under "Range Coordinates" in the Geography section. Editors can use it to specify inexact coordinates of massifs, for example. There is also already a parameter, |highest=
, where you can specify the name of the highest peak (separately from the name of the mountain/range). —
hike395 (
talk) 03:30, 4 February 2015 (UTC)|volume=
, |volume_km3=
, |volume_mi3=
, |volume_note=
. Seems good for volcanoes. —
hike395 (
talk) 18:28, 4 February 2015 (UTC)
|area=
because it just gives "Area" in the infobox but after looking at {{
Infobox mountain range}} it gives |area_km2=
so I'm not sure if |volume=
would be redundant with |volume_km3=
and |volume_mi3=
unless someone uses smaller measurements which I have not seen for mountains.
Volcano
guy 21:10, 4 February 2015 (UTC)|area=
(and other parameters, like |length=
or |volume=
) are used for free-form entries, typically expressing uncertainty ranges, e.g., |area={{convert|4|to|6|km2|mi2}}
. —
hike395 (
talk) 02:53, 5 February 2015 (UTC)
The result of the discussion was to merge this template into {{ Infobox mountain}}. Further discussion on the design of the merged template is at the Mountain WikiProject talk page — hike395 ( talk) 03:50, 15 February 2015 (UTC)
There was consensus at TfD to merge this template into {{ Infobox mountain}}, but some issues remain to be resolved. A draft is at User:Hike395/MtnComboBox. How should the merge take place? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:13, 23 May 2015 (UTC)
{{{region}}}
to {{{region_code}}}
. This new parameter is already part of {{
Infobox mountain}}, and will avoid errors in the next step.