Template talk:Infobox airport

Template:Infobox airport is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.

Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.

This is the talk page for discussing improvements to the Infobox airport template.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Archives: 1, 2, 3, 4, 5, 6: 30 days

Aviation: Airports

	Aviation portal This template is within the scope of the Aviation WikiProject. If you would like to participate, please visit the project page, where you can join the project and see lists of open tasks and task forces. To use this banner, please see the full instructions.AviationWikipedia:WikiProject AviationTemplate:WikiProject Aviationaviation
	This template is supported by the airport project.

Infoboxes

This template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes

Edit request 2 November 2024

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Description of suggested change: addition of parameter "Purpose", for infoboxes like Mactan–Cebu, missing indication that only one runway is in active use.

example preview (ofc. making the infobox about 3 or 5 pixels wider to the ):

Diff:

} D4n2016 (talk) 17:44, 2 November 2024 (UTC)[reply]

Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. The code below appears to be TemplateData code for the documentation page, not template code. This suggestion also needs consensus. – Jonesey95 (talk) 06:19, 5 November 2024 (UTC)[reply]

I used {{efn}} to give the information. I'm not sure that a change to the infobox is needed to do something that isn't going to be used often. CambridgeBayWeather (solidly non-human), Uqaqtuq (talk), Huliva 04:51, 8 November 2024 (UTC)[reply]

Former names

Template:Infobox hospital has a line for "former-names." Would this be a reasonable line to include for airports? Alpacaaviator (talk) 13:34, 2 March 2025 (UTC)[reply]

Edit request 10 March 2025

It is requested that an edit be made to the template-protected template at Template:Infobox airport.
(edit · history · last · links · sandbox · edit sandbox · sandbox history · sandbox last edit · sandbox diff · test cases · transclusion count · protection log)

This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.

Edit requests to template-protected pages should only be used for edits that are either uncontroversial or supported by consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the template's sandbox and test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a protection request. When the request has been completed or denied, please add the |answered=yes parameter to deactivate the template.

As it is now, the image, pushpin map, and mapframe all have different default sizes. Therefore they all jog in or out, and the infobox is unsightly. By making all default sizes 250px, the images and maps line up and the infobox is consistent with other infoboxes (see sandbox and testcases for comparisons). The code to change is as follows:

Thanks. -- P 1 9 9 ✉ 14:19, 10 March 2025 (UTC)[reply]

If there is any way to use the viewer's thumb size preference instead, that would be preferable, per MOS:IMGSIZE: Except with very good reason, a fixed width in pixels (e.g. 17px) should not be specified, because it ignores the user's base width setting. Thus upright=scaling factor is preferred when it is desired to present an image at other than the default width. I have asked at Module talk:Location map and Template talk:Infobox mapframe to see if there is a way to make this happen. – Jonesey95 (talk) 03:13, 14 March 2025 (UTC)[reply]

Edit request 12 March 2025

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Description of suggested change: Hello! This suggestion aims to allow more technical data about airports and aerodromes to be added to the template.

The suggestion is that, new parameters are added to include the ability to add an airport plate (such as an Approach plate or, more likely, a ground overview plate) as well as the ability to add frequencies for Air Traffic Control (aiming mainly at the most important frequencies - tower, ATIS, approach and ground, plus an additional parameter for extras (eg. UNICOM or for other less common frequencies) .

Let me know your thoughts! Moonbloom (talk) 03:58, 12 March 2025 (UTC)[reply]

Diff:

Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. – Jonesey95 (talk) 04:34, 12 March 2025 (UTC)[reply]

I can try, but I find CSS editing really hard. Is there a reference manual for this somewhere? Moonbloom (talk) 05:33, 12 March 2025 (UTC)[reply]

General information about how infoboxes work is at Template:Infobox. – Jonesey95 (talk) 06:24, 12 March 2025 (UTC)[reply]