This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 |
I propose to link the text "Category x" to IUCN protected area categories. -- Gerrit C U T E D H 14:19, 2 March 2013 (UTC)
Way back in 2011 {{ Infobox protected area of Australia}} was nominated for deletion but this was not possible as this infobox was not compatible. Droll did some work towards making it compatible, but work on this eventually went nowhere. Recently I looked at updating Infobox protected area of Australia but it's really not as well written as this template so I see some merit in replacing the template instead. In order to do this, as far as I can see, there are two things required. First, implement Droll's changes, which I've restored to the sandbox. [1] Secondly, rewrite Infobox protected area of Australia as a wrapper for this template that can be substed. [2] I haven't done a lot of testing yet, but this solution works in the articles that I've tested. -- AussieLegend ( ✉) 12:28, 13 December 2013 (UTC)
I have just removed the deletion notice from this template, as it resulted in an ugly message being left at Sawtooth National Forest, today's featured article. While I understand the utility of such notices, having these kind of template messages at the top of today's featured article does not give a good first impression of Wikipedia. J Milburn ( talk) 23:15, 29 May 2014 (UTC)
The long official URL seems to be pushing out the width of the infobox on Kasha-Katuwe Tent Rocks National Monument, and the notice about the proposed merge is too narrow at the top, creating a mess. Is there any way to fix this? - Gorthian ( talk) 06:51, 12 June 2014 (UTC)
http://www.blm.gov/kasha_katuwe_tent_rocks
or even http://www.blm.gov/kktr
instead of the current http://www.blm.gov/nm/st/en/prog/recreation/rio_puerco/kasha_katuwe_tent_rocks.html
. Any competent web manager will know how to do this; a good one would have done it as a matter of course.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 10:00, 12 June 2014 (UTC)This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I have added a line to the sandbox so it uses any supplied coordinates in a location map, as well as any latitude/longitude. See the testcase here: Template:Infobox protected area/testcases#Dry Island Buffalo Jump Provincial Park and the report by Deor here: Help talk:Coordinates in infoboxes, with some background. Please update the main template from the sandbox with this change.-- JohnBlackburne words deeds 19:40, 17 November 2016 (UTC)
{{{name}}} | |
---|---|
Coordinates | 0°N 0°E / 0°N 0°E |
Area | 1,234.5 ha (4.766 sq mi) |
Frietjes added |dimension=
to the infobox, which I thought was a good idea. I went ahead and added |length=
, |length_mi=
, |length_km=
, |width=
, |width_mi=
, |width_km=
to the infobox. I also hooked up these (and the area parameters) to {{
Infobox dim}} so that the Geohack map can produce the correct scale (see, e.g.,
Dry Island Buffalo Jump Provincial Park).
I would recommend using the unit-specific length and width parameters, instead of the general dimension parameters, so that the map autoscales.
Let me know if anyone sees any problems. — hike395 ( talk) 18:23, 23 December 2016 (UTC)
{{formatnum: ... |R}}
in {{
infobox dim}} so we don't have to decomma before passing the values? thank you.
Frietjes (
talk) 13:43, 24 December 2016 (UTC)
Hike395, yesterday you added a bit to the documentation regarding units. In addition to the length/width parameters discessed above, you added documentation about unit-specific autoconverting area parameters. To the 'Parameter descriptions' table, the following was added regarding these parameters: "Area of the protected area, with autoconversion to metric/imperial units. Preferred to using bare
". You are now going page-to-page to 'fix' these parameters.|area=
I would like to know how an editor can control the output units with these new parameters. For example, I typically use {{ convert}} to express very large acreages in both km2 and sqmi, as I had here. Now it outputs hectares only, which doesn't seem as helpful from a reader perspective. At the very least, conversion of large acreages to km2, rather than ha, seemed common practice when I was getting a feel for things, and it's something I've adopted as habit, maybe that's problematic? I've never seen actual guidelines on this.
What is the advantage of using these unit-specific parameters, such that they are 'preferred' over |area=
with {{
convert}}? I'm happy to lose some control over output if there are good back-end reasons for it. Thanks -
Antepenultimate (
talk) 13:29, 24 December 2016 (UTC)
|area=
, I don't know how to parse the convert template. Without the unit-ed parameters, I believe that the map defaults to 1 km across, which is often too small.|area=
, and manually select the |dim=
or |scale=
parameter in the call to {{
coord}}.@ Antepenultimate: I went ahead and changed the thresholds to be 4.0 km2 and 4.0 mi2, which is very close to your suggested threshold of 1000. It sounds like English-speaking metric-using readers aren't very familiar with hectares. I figure that if you have a protected area that's larger than 2 kilometers (or miles) on a side, then it makes sense to use square kilometers (or miles), rather than a smaller unit.
The template is live now. As usual, if anyone sees any problem, I can revert. If a problems occurs (or if consensus changes) while I'm on wikibreak, please feel free to edit or revert. — hike395 ( talk) 20:21, 25 December 2016 (UTC)
Hi, I'd like the template to be able to handle the following additional parameters, not least so we don't lose information as we import articles from other Wikis. I'd like to propose that we add:
Thanks folks. Bermicourt ( talk) 18:43, 27 April 2017 (UTC)
I stripped out the non-standard extra label and data padding. I noticed it when I embedded this template inside of {{ infobox mountain}} in Sapphire Mountains. hopefully, this didn't cause any other problems. thank you. Frietjes ( talk) 20:50, 3 July 2017 (UTC)
Frietjes, could these edits be modified so that a {{{width}}} parameter is not passed to the Location map template unless mapsize/map_size/map_width is explicitly specified? The default width preferred by the infobox (284 or 300? Currently seems inconsistent) should be passed to {{{default_width}}}, so that it may be modified by a scaling factor for maps which are vertically elongated. For example, see the following comparison between the current code and the sandbox (where I've reverted the change) for Alerce Costero National Park. -- Paul_012 ( talk) 21:12, 2 December 2017 (UTC)
{{ Infobox protected area}} | {{ Infobox protected area/sandbox}} | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
References
Would someone please add one or both of these. I want to add the date the provincial park designation was rescinded at Sylvan Lake Provincial Park. The designation was rescinded yesterday. Cheers, Hwy43 ( talk) 07:53, 19 January 2018 (UTC)
Could someone please add the ability to add a reference for the iucn category. Possibly another parameter "iucn_ref"? — Preceding unsigned comment added by 107.77.209.233 ( talk) 22:10, 12 June 2018 (UTC)
This
edit request to
Template:Infobox protected area has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change "World Heritage Site" to lowercase site: "World Heritage site" for consistency with MOS:CAPS and recent discussions and article moves. Dicklyon ( talk) 14:56, 15 October 2018 (UTC)
Can someone add the "Iucn_ref" to the {{
Infobox Australian place}}
?
Please see:
Template_talk:Infobox_Australian_place#iucn_ref
-- David Tornheim ( talk) 01:23, 30 December 2018 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 |
I propose to link the text "Category x" to IUCN protected area categories. -- Gerrit C U T E D H 14:19, 2 March 2013 (UTC)
Way back in 2011 {{ Infobox protected area of Australia}} was nominated for deletion but this was not possible as this infobox was not compatible. Droll did some work towards making it compatible, but work on this eventually went nowhere. Recently I looked at updating Infobox protected area of Australia but it's really not as well written as this template so I see some merit in replacing the template instead. In order to do this, as far as I can see, there are two things required. First, implement Droll's changes, which I've restored to the sandbox. [1] Secondly, rewrite Infobox protected area of Australia as a wrapper for this template that can be substed. [2] I haven't done a lot of testing yet, but this solution works in the articles that I've tested. -- AussieLegend ( ✉) 12:28, 13 December 2013 (UTC)
I have just removed the deletion notice from this template, as it resulted in an ugly message being left at Sawtooth National Forest, today's featured article. While I understand the utility of such notices, having these kind of template messages at the top of today's featured article does not give a good first impression of Wikipedia. J Milburn ( talk) 23:15, 29 May 2014 (UTC)
The long official URL seems to be pushing out the width of the infobox on Kasha-Katuwe Tent Rocks National Monument, and the notice about the proposed merge is too narrow at the top, creating a mess. Is there any way to fix this? - Gorthian ( talk) 06:51, 12 June 2014 (UTC)
http://www.blm.gov/kasha_katuwe_tent_rocks
or even http://www.blm.gov/kktr
instead of the current http://www.blm.gov/nm/st/en/prog/recreation/rio_puerco/kasha_katuwe_tent_rocks.html
. Any competent web manager will know how to do this; a good one would have done it as a matter of course.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits 10:00, 12 June 2014 (UTC)This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I have added a line to the sandbox so it uses any supplied coordinates in a location map, as well as any latitude/longitude. See the testcase here: Template:Infobox protected area/testcases#Dry Island Buffalo Jump Provincial Park and the report by Deor here: Help talk:Coordinates in infoboxes, with some background. Please update the main template from the sandbox with this change.-- JohnBlackburne words deeds 19:40, 17 November 2016 (UTC)
{{{name}}} | |
---|---|
Coordinates | 0°N 0°E / 0°N 0°E |
Area | 1,234.5 ha (4.766 sq mi) |
Frietjes added |dimension=
to the infobox, which I thought was a good idea. I went ahead and added |length=
, |length_mi=
, |length_km=
, |width=
, |width_mi=
, |width_km=
to the infobox. I also hooked up these (and the area parameters) to {{
Infobox dim}} so that the Geohack map can produce the correct scale (see, e.g.,
Dry Island Buffalo Jump Provincial Park).
I would recommend using the unit-specific length and width parameters, instead of the general dimension parameters, so that the map autoscales.
Let me know if anyone sees any problems. — hike395 ( talk) 18:23, 23 December 2016 (UTC)
{{formatnum: ... |R}}
in {{
infobox dim}} so we don't have to decomma before passing the values? thank you.
Frietjes (
talk) 13:43, 24 December 2016 (UTC)
Hike395, yesterday you added a bit to the documentation regarding units. In addition to the length/width parameters discessed above, you added documentation about unit-specific autoconverting area parameters. To the 'Parameter descriptions' table, the following was added regarding these parameters: "Area of the protected area, with autoconversion to metric/imperial units. Preferred to using bare
". You are now going page-to-page to 'fix' these parameters.|area=
I would like to know how an editor can control the output units with these new parameters. For example, I typically use {{ convert}} to express very large acreages in both km2 and sqmi, as I had here. Now it outputs hectares only, which doesn't seem as helpful from a reader perspective. At the very least, conversion of large acreages to km2, rather than ha, seemed common practice when I was getting a feel for things, and it's something I've adopted as habit, maybe that's problematic? I've never seen actual guidelines on this.
What is the advantage of using these unit-specific parameters, such that they are 'preferred' over |area=
with {{
convert}}? I'm happy to lose some control over output if there are good back-end reasons for it. Thanks -
Antepenultimate (
talk) 13:29, 24 December 2016 (UTC)
|area=
, I don't know how to parse the convert template. Without the unit-ed parameters, I believe that the map defaults to 1 km across, which is often too small.|area=
, and manually select the |dim=
or |scale=
parameter in the call to {{
coord}}.@ Antepenultimate: I went ahead and changed the thresholds to be 4.0 km2 and 4.0 mi2, which is very close to your suggested threshold of 1000. It sounds like English-speaking metric-using readers aren't very familiar with hectares. I figure that if you have a protected area that's larger than 2 kilometers (or miles) on a side, then it makes sense to use square kilometers (or miles), rather than a smaller unit.
The template is live now. As usual, if anyone sees any problem, I can revert. If a problems occurs (or if consensus changes) while I'm on wikibreak, please feel free to edit or revert. — hike395 ( talk) 20:21, 25 December 2016 (UTC)
Hi, I'd like the template to be able to handle the following additional parameters, not least so we don't lose information as we import articles from other Wikis. I'd like to propose that we add:
Thanks folks. Bermicourt ( talk) 18:43, 27 April 2017 (UTC)
I stripped out the non-standard extra label and data padding. I noticed it when I embedded this template inside of {{ infobox mountain}} in Sapphire Mountains. hopefully, this didn't cause any other problems. thank you. Frietjes ( talk) 20:50, 3 July 2017 (UTC)
Frietjes, could these edits be modified so that a {{{width}}} parameter is not passed to the Location map template unless mapsize/map_size/map_width is explicitly specified? The default width preferred by the infobox (284 or 300? Currently seems inconsistent) should be passed to {{{default_width}}}, so that it may be modified by a scaling factor for maps which are vertically elongated. For example, see the following comparison between the current code and the sandbox (where I've reverted the change) for Alerce Costero National Park. -- Paul_012 ( talk) 21:12, 2 December 2017 (UTC)
{{ Infobox protected area}} | {{ Infobox protected area/sandbox}} | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
References
Would someone please add one or both of these. I want to add the date the provincial park designation was rescinded at Sylvan Lake Provincial Park. The designation was rescinded yesterday. Cheers, Hwy43 ( talk) 07:53, 19 January 2018 (UTC)
Could someone please add the ability to add a reference for the iucn category. Possibly another parameter "iucn_ref"? — Preceding unsigned comment added by 107.77.209.233 ( talk) 22:10, 12 June 2018 (UTC)
This
edit request to
Template:Infobox protected area has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change "World Heritage Site" to lowercase site: "World Heritage site" for consistency with MOS:CAPS and recent discussions and article moves. Dicklyon ( talk) 14:56, 15 October 2018 (UTC)
Can someone add the "Iucn_ref" to the {{
Infobox Australian place}}
?
Please see:
Template_talk:Infobox_Australian_place#iucn_ref
-- David Tornheim ( talk) 01:23, 30 December 2018 (UTC)