Template talk:Infobox protected area

  1. Home
  2. Wiki

Second map (interactive)

[edit]

I am adding zoomable interactive maps to articles (like this edit). These maps would be better in infobox. What about adding the option to add a second map to the infobox? In maximum configuration that would be then three items - photo, static map and dynamic map. An option would be to put both maps next to each other.--Kozuch (talk) 15:43, 5 August 2019 (UTC)[reply]

I think that would be fine. Having the national map as the default with the option to switch to the detailed map like here. Fredlyfish4 (talk) 17:57, 5 August 2019 (UTC)[reply]
I happened to come across this issue as well. This template's handling of multiple maps is way less friendly to {{infobox mapframe}} than the typical infobox. This should be fixed. --Joy (talk) 21:54, 1 July 2023 (UTC)[reply]

Template-protected edit request on 8 August 2022

[edit]

Please add a “disestablished” label and parameter, for parks that no longer exist. This will avoid the awkward wording of Established 1954 – 2014 as is sometimes used. — HTGS (talk) 02:59, 8 August 2022 (UTC)[reply]

 Done. P.I. Ellsworth , ed. put'r there 02:55, 13 August 2022 (UTC)[reply]

Logo inclusion

[edit]

I believe there should be an option to include a logo in the infobox as many national parks have their own logos. Kj1595 (talk) 16:34, 24 March 2023 (UTC)[reply]

Agreed, please add this ASAP Mark999 (talk) 17:28, 24 February 2024 (UTC)[reply]

Park Codes

[edit]

The National Park Service in the US assigns every national park/monument/etc a four-letter "Park Code." It may be useful to include this somewhere in the infobox. As of now, the easiest place to find these is an Excel file provided by the NPS. Being on Wikipedia provides additional visibility to these codes, and would selfishly assist my partner in working with the NPS API.


I'm not sure how/if other countries do this, so the text should likely be generalized, maybe we call it an identifier. Jaidenstar (talk) 16:44, 31 January 2024 (UTC)[reply]

Are these codes actually useful for general readers? It sounds like they’re a bit of a niche database reference if they’re so hard to find otherwise. Not outright, but I am leaning opposed to including them. Worth considering WP:NOTDATABASE. — HTGS (talk) 03:26, 5 February 2024 (UTC)[reply]
Good point, thanks for the feedback. I personally believe it is helpful to have these codes next to the rest of the information but you are likely right about policy here. Jaidenstar (talk) 17:00, 3 April 2024 (UTC)[reply]

Template-protected edit request on 24 February 2024

[edit]

I would like a logo section added as UK national Parks and landscapes have logos that would be useful to add. Mark999 (talk) 17:27, 24 February 2024 (UTC)[reply]

 Done SWinxy (talk) 03:03, 25 February 2024 (UTC)[reply]

Map problem

[edit]

I'm hoping someone can fix the errors shown in the infoboxes at Booderee National Park and Botanic Gardens and South West Woodland Nature Reserve. Thanks. Johnuniq (talk) 06:23, 6 October 2025 (UTC)[reply]

Photo vs Image

[edit]

Is there a reason that this template uses |photo= when literally every other infobox I've ever used uses |image=? Is there any objection to changing this? (would deprecate the old, not just delete it). Zackmann (Talk to me/What I been doing) 18:38, 13 October 2025 (UTC)[reply]

Random maps

[edit]

Why do the 'With photograph only' and 'With no photograph or map' examples have maps that don't seem to add anything to the information being imparted? YorkshireExpat (talk) 10:14, 16 November 2025 (UTC)[reply]

You mean in the documentation?
Mapframes were added to the template by Joy in November, 2024. In the current infobox, the mapframe is on by default if no other map is given. Per WP:Mapframe maps in infoboxes, we can discuss whether the mapframes should be included. What do editors think? — hike395 (talk) 12:37, 16 November 2025 (UTC)[reply]
The thumbnail in the first example, Yosemite, wasn't great because all the labels were cut off and it wasn't immediately obvious where this was. I zoomed it out by one level now (7->6), and it shows major cities, coastline and a border. Though it should be noted that even in the original form it was actually adding something to the information - the button to zoom in and out, pan, see links to other articles, etc. But it does make sense to improve the thumbnail if we can, too.
The default zoom for that thumbnail is set either the various dimensions parameters, in that case would have been based on area_acre = 761266. In that example, there's also the scale = 300000 parameter, but I'm not sure offhand what it does, it's not actually documented.
Maybe in case of protected areas we should assume they're a bit further away from other landmarks that would provide useful labels, and get that zoomed out by default a bit more?
In the second example, Harz, the zoom is likewise set after area_ha = 8900, and we have a visible label of Braunlage, but that's a relatively small place. If we zoom out by 1 (10->9), there's many more labels, but also relatively small places. If we zoom out by 1 more (8), we almost get a full label for Göttingen, which is 20x the size of Braunlage. If we zoom by 1 more (7), we get a full label for Hanover, which is 90x the size of Braunlage.
This happens in these examples - it may well vary for other protected areas in other parts of the globe. --Joy (talk) 13:15, 16 November 2025 (UTC)[reply]
Oh, good point. It could be that YorkshireExpat is objecting to the content of the maps, not the existence of the maps. — hike395 (talk) 14:09, 16 November 2025 (UTC)[reply]
I can experiment to see if we can zoom out if an area is provided. — hike395 (talk) 14:09, 16 November 2025 (UTC)[reply]
For example, the one in The Broads has no context so I tried to remove it, but turns out it's just a part of the template. It really adds nothing in that article and is probably just confusing to most readers. YorkshireExpat (talk) 21:51, 16 November 2025 (UTC)[reply]
Ah, the problem there was this part:
area = 303 square kilometres (117 sq mi)
When this conversion of dimensions is entered manually, the infobox code doesn't understand it for its own purposes. I changed it to:
area_km2 = 303
This is shorter to type, doesn't require doing the conversion by hand, and has the helpful side effect of allowing the map code to change the default map zoom accordingly.
And now we can see that the map of the intricate shape of the area showed up. If you want to tune it further, the mapframe-zoom parameter is available. --Joy (talk) 23:05, 16 November 2025 (UTC)[reply]
@Joy Awesome, thanks! YorkshireExpat (talk) 19:41, 18 November 2025 (UTC)[reply]

scale parameter

[edit]

Why doesn't the example with |scale= not trigger {{Check for unknown parameters}} here? --Joy (talk) 13:27, 16 November 2025 (UTC)[reply]

You mean here? It's because |scale= is not actually used in the template call, only in the display. It's a bug in the documentation. — hike395 (talk) 13:58, 16 November 2025 (UTC)[reply]
Oh, nice, phew, I figured I was missing something. --Joy (talk) 17:19, 16 November 2025 (UTC)[reply]
BTW followed up on this at Template talk:Syntaxhighlight#potential use in template documentation. --Joy (talk) 23:10, 16 November 2025 (UTC)[reply]