This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||
|
Discussion at WT:WikiProject_Seamounts#Proposed_change_to_infobox_style. — hike395 ( talk) 05:33, 16 May 2010 (UTC)
Shouldn't this be {{ Infobox seamount}}? -- Stepheng3 ( talk) 18:40, 15 August 2010 (UTC)
@
RexxS: Could you explain your latest edits? I'm not sure why |module=
is named the way it is, nor what it's supposed to do. I'm also curious why the width of the infobox needs to change from article to article? —
hike395 (
talk)
10:12, 15 February 2019 (UTC)
|module=
parameter, and I saw no reason for using a different parameter name in this case. As far as I know, it was originally called 'module' because the included templates were often a kind of module (things like the player for audio clips).|map=
to get parameters for {{
Location map}}. The infobox calls {{
Location map}} itself: each infobox exposes a set of parameters to control the look of the map. Would you mind if I updated {{
Infobox seamount}} to match the other infoboxes? I will gladly change
Allison Guyot to use those parameters.
|map=
is already taken to mean an image map (which is probably more common for seamounts). In this case, like in {{
Infobox river}}, the parameter is called |pushpin_map=
. Not the nicest name, but we may need to bow to consistency. —
hike395 (
talk)
16:29, 15 February 2019 (UTC)|boxwidth=
is used? I would prefer to control the width of the infobox within the template. Usually geographic infoboxes control their own width, for consistency and to prevent inexperienced editors from squeezing the text of the article. The width of the map and photographs are limited. Since you're not using |boxwidth=
in
Allison Guyot, may I remove the parameter?Allison Guyot | |
---|---|
| |
Height | 1.5 kilometres |
Summit area | 35 x 70 kilometres |
Location | |
Group | Mid-Pacific Mountains |
Coordinates | 18°16′N 179°20′E / 18.26°N 179.33°E |
Geology | |
Type | Guyot |
@
Hike395: Unfortunately, the documentation of this template gives no indication of how {{
location map}} can be called from this template. I can't see how it will work from inspecting
Module:Infobox, so I have to ask if you're sure that you can display it using the map
parameter? Perhaps you can use this demo infobox to show how it's done before editing a Featured Article candidate.
If an editor supplies a location map using its default width (i.e. omits the width
parameter), then they get a wide left margin on the map. That will be similar for any other embedded modules that don't have the same default width as
Template:Infobox seamount. In addition, you'll see mismatches in different skins between any embedded object whose width is in pixels and this template, which has a default width of 23.5em. Although it is generally best practice to set sizes in ems, the exception comes when you are trying to match sizes with elements that are specified in pixels (like images). In order to overcome these sort of problems, I recommend that you retain the option of allowing this infobox to have its width set on a per-article basis. I understand your desire to lock-down templates against unwarranted changes, but unfortunately an infobox width needs flexibility in the units used as well as the values. --
RexxS (
talk)
17:48, 15 February 2019 (UTC)
|pushpin_map=
, and have also added a
test case for
Allison Guyot, reproduced here:Allison Guyot | |
---|---|
Height | 1.5 kilometres |
Summit area | 35 x 70 kilometres |
Location | |
Group | Mid-Pacific Mountains |
Coordinates | 18°16′N 179°20′E / 18.26°N 179.33°E [1] |
Geology | |
Type | Guyot |
{{Infobox seamount/sandbox | name = Allison Guyot | depth = | height = 1.5 kilometres | summit_area = 35 x 70 kilometres | location = | group = [[Mid-Pacific Mountains]] | coordinates = {{coord|18.26|N|179.33|E|display=inline,intitle}}{{sfn|Arreguín-Rodríguez|Alegret|Thomas|2016|p=348}} | country = | type = [[Guyot]] | age = | discovered = | pushpin_map = Pacific Ocean | map_size = | map_caption = Location in the Pacific Ocean | label = Allison }}
As you might see, calling {{
Location map}} from inside the infobox produces a nicely centered map, with no need to set the width of the infobox. This is consistent with the behavior of the other geographic infoboxes --= I've not encountered an off-center map, even though the |map=
or |photo=
widths are specified in px and the infobox width is specified in em. I suspect that the problem you're encountering is due some subtle order of evaluation of the templates.
The |pushpin_map=
seems to work well --- I think it's ok to promote the sandbox to the main template. What do you think? —
hike395 (
talk)
21:26, 15 February 2019 (UTC)
|coordinates=
once in the example. The right shift of a module happens because it uses a |dataN field in {{
Infobox}} which is the right-hand cell of a table. Of course it could be wrapped in a div and centred, but your approach of using an image field (which is centred by default) works just as well."Parameter names should use lower-case unless they are proper nouns."; and
"
Infoboxes using geographical coordinates should use |coordinates=
as the parameter name, with the {{
coord}} template in the parameter's value."
Sorry, but the current sandbox is a step backward in compliance with MOS. --
RexxS (
talk)
22:14, 15 February 2019 (UTC)
|coord=
, per your suggestion.|boxwidth=
, because it can take so many forms (some of which are context-dependent, like "25%"). We can bring this up at
WT:WikiProject Mountains and see if other editors have opinions/suggestions. —
hike395 (
talk)
22:40, 15 February 2019 (UTC)
hastemplate:Infobox seamount insource:/| *Name/
, which shows 132 articles with capitalised |Name=
. Let me know if you run into any problems. Cheers --
RexxS (
talk)
23:22, 15 February 2019 (UTC)
References
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Where does one have to edit the template so that it doesn't throw an "undocumented parameter" error when using |mapframe=no? Such as on Protector Shoal. Putting an edit request here since I know nothing about this particular bit of template formatting. Jo-Jo Eumerus ( talk) 07:51, 22 November 2023 (UTC)
Related to Jo-Jo Eumerus's question above, in Protector Shoal, how do we get the maplink to show inside the infobox, like it does in the example on Template:Infobox seamount? RoySmith (talk) 15:47, 22 November 2023 (UTC)
|mapframe=yes
and set other parameters (that I see are undocumented). I updated
Protector Shoal and will update the doc page. —
hike395 (
talk)
17:37, 22 November 2023 (UTC)
|map=
or |pushpin_map=
are present. You would get mapframe for Protector Shoal by default. —
hike395 (
talk)
20:03, 22 November 2023 (UTC)This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||
|
Discussion at WT:WikiProject_Seamounts#Proposed_change_to_infobox_style. — hike395 ( talk) 05:33, 16 May 2010 (UTC)
Shouldn't this be {{ Infobox seamount}}? -- Stepheng3 ( talk) 18:40, 15 August 2010 (UTC)
@
RexxS: Could you explain your latest edits? I'm not sure why |module=
is named the way it is, nor what it's supposed to do. I'm also curious why the width of the infobox needs to change from article to article? —
hike395 (
talk)
10:12, 15 February 2019 (UTC)
|module=
parameter, and I saw no reason for using a different parameter name in this case. As far as I know, it was originally called 'module' because the included templates were often a kind of module (things like the player for audio clips).|map=
to get parameters for {{
Location map}}. The infobox calls {{
Location map}} itself: each infobox exposes a set of parameters to control the look of the map. Would you mind if I updated {{
Infobox seamount}} to match the other infoboxes? I will gladly change
Allison Guyot to use those parameters.
|map=
is already taken to mean an image map (which is probably more common for seamounts). In this case, like in {{
Infobox river}}, the parameter is called |pushpin_map=
. Not the nicest name, but we may need to bow to consistency. —
hike395 (
talk)
16:29, 15 February 2019 (UTC)|boxwidth=
is used? I would prefer to control the width of the infobox within the template. Usually geographic infoboxes control their own width, for consistency and to prevent inexperienced editors from squeezing the text of the article. The width of the map and photographs are limited. Since you're not using |boxwidth=
in
Allison Guyot, may I remove the parameter?Allison Guyot | |
---|---|
| |
Height | 1.5 kilometres |
Summit area | 35 x 70 kilometres |
Location | |
Group | Mid-Pacific Mountains |
Coordinates | 18°16′N 179°20′E / 18.26°N 179.33°E |
Geology | |
Type | Guyot |
@
Hike395: Unfortunately, the documentation of this template gives no indication of how {{
location map}} can be called from this template. I can't see how it will work from inspecting
Module:Infobox, so I have to ask if you're sure that you can display it using the map
parameter? Perhaps you can use this demo infobox to show how it's done before editing a Featured Article candidate.
If an editor supplies a location map using its default width (i.e. omits the width
parameter), then they get a wide left margin on the map. That will be similar for any other embedded modules that don't have the same default width as
Template:Infobox seamount. In addition, you'll see mismatches in different skins between any embedded object whose width is in pixels and this template, which has a default width of 23.5em. Although it is generally best practice to set sizes in ems, the exception comes when you are trying to match sizes with elements that are specified in pixels (like images). In order to overcome these sort of problems, I recommend that you retain the option of allowing this infobox to have its width set on a per-article basis. I understand your desire to lock-down templates against unwarranted changes, but unfortunately an infobox width needs flexibility in the units used as well as the values. --
RexxS (
talk)
17:48, 15 February 2019 (UTC)
|pushpin_map=
, and have also added a
test case for
Allison Guyot, reproduced here:Allison Guyot | |
---|---|
Height | 1.5 kilometres |
Summit area | 35 x 70 kilometres |
Location | |
Group | Mid-Pacific Mountains |
Coordinates | 18°16′N 179°20′E / 18.26°N 179.33°E [1] |
Geology | |
Type | Guyot |
{{Infobox seamount/sandbox | name = Allison Guyot | depth = | height = 1.5 kilometres | summit_area = 35 x 70 kilometres | location = | group = [[Mid-Pacific Mountains]] | coordinates = {{coord|18.26|N|179.33|E|display=inline,intitle}}{{sfn|Arreguín-Rodríguez|Alegret|Thomas|2016|p=348}} | country = | type = [[Guyot]] | age = | discovered = | pushpin_map = Pacific Ocean | map_size = | map_caption = Location in the Pacific Ocean | label = Allison }}
As you might see, calling {{
Location map}} from inside the infobox produces a nicely centered map, with no need to set the width of the infobox. This is consistent with the behavior of the other geographic infoboxes --= I've not encountered an off-center map, even though the |map=
or |photo=
widths are specified in px and the infobox width is specified in em. I suspect that the problem you're encountering is due some subtle order of evaluation of the templates.
The |pushpin_map=
seems to work well --- I think it's ok to promote the sandbox to the main template. What do you think? —
hike395 (
talk)
21:26, 15 February 2019 (UTC)
|coordinates=
once in the example. The right shift of a module happens because it uses a |dataN field in {{
Infobox}} which is the right-hand cell of a table. Of course it could be wrapped in a div and centred, but your approach of using an image field (which is centred by default) works just as well."Parameter names should use lower-case unless they are proper nouns."; and
"
Infoboxes using geographical coordinates should use |coordinates=
as the parameter name, with the {{
coord}} template in the parameter's value."
Sorry, but the current sandbox is a step backward in compliance with MOS. --
RexxS (
talk)
22:14, 15 February 2019 (UTC)
|coord=
, per your suggestion.|boxwidth=
, because it can take so many forms (some of which are context-dependent, like "25%"). We can bring this up at
WT:WikiProject Mountains and see if other editors have opinions/suggestions. —
hike395 (
talk)
22:40, 15 February 2019 (UTC)
hastemplate:Infobox seamount insource:/| *Name/
, which shows 132 articles with capitalised |Name=
. Let me know if you run into any problems. Cheers --
RexxS (
talk)
23:22, 15 February 2019 (UTC)
References
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Where does one have to edit the template so that it doesn't throw an "undocumented parameter" error when using |mapframe=no? Such as on Protector Shoal. Putting an edit request here since I know nothing about this particular bit of template formatting. Jo-Jo Eumerus ( talk) 07:51, 22 November 2023 (UTC)
Related to Jo-Jo Eumerus's question above, in Protector Shoal, how do we get the maplink to show inside the infobox, like it does in the example on Template:Infobox seamount? RoySmith (talk) 15:47, 22 November 2023 (UTC)
|mapframe=yes
and set other parameters (that I see are undocumented). I updated
Protector Shoal and will update the doc page. —
hike395 (
talk)
17:37, 22 November 2023 (UTC)
|map=
or |pushpin_map=
are present. You would get mapframe for Protector Shoal by default. —
hike395 (
talk)
20:03, 22 November 2023 (UTC)