Template talk:Infobox airport

Upgrading the hCard microformat

{{editprotected}}

Please make these changes: [changes redacted to save space] to add several "nickname" properties for the hCard microformat. Thank you. Andy Mabbett | Talk to Andy Mabbett 18:13, 23 August 2008 (UTC)

Y Done Happy‑melon 14:35, 24 August 2008 (UTC)

That's great; thank you. Andy Mabbett | Talk to Andy Mabbett 14:51, 24 August 2008 (UTC)

Editprotected request - Add to Category:Exclude in print

{{editprotected}} Can an admin please add this template to Category:Exclude in print? Thank you. Glacier Wolf 12:01, 27 March 2009 (UTC)

Can you not just add it to the documentation subpage in an includeonly? — Martin (MSGJ · talk) 12:54, 27 March 2009 (UTC)

Should the infobox be excluded from print? I understand nav or stub templates, but as far as I know, generally infoboxes are being included, as they contain valid summary info on the article. - Trevor MacInnis (Contribs) 16:09, 27 March 2009 (UTC)

Alternative text for images

Does this Infobox support Wikipedia:Alternative text for images ? -Optigan13 (talk) 01:49, 15 August 2009 (UTC)

It doesn't appear to, and I believe that support needs to be added, otherwise it may be difficult or even impossible for any article using this infobox to pass an FA review. Unfortunately, I don't know how to do this myself; if someone with better knowledge of template syntax than I can add it, it would be much appreciated. Ron2K (talk) 10:51, 23 December 2009 (UTC)

I've added it to the sandbox and tested on the test cases page; it appears to work. Could someone else confirm that it works, and maybe perform a sync if it does? Ron2K (talk) 11:01, 23 December 2009 (UTC)

Addition

{{editprotected}}

Hi, I have drafted a version of this which adds a parameter to list what airlines the airport is a hub or focus city for. Personally, I think this would be a useful addition. The draft is located at User:Ishwasafish/Sndbx 4 Infobox Airport. Thanks,

Ishwasafish ^{click here!!!}

22:00, 16 August 2009 (UTC)

Have you tested this thoroughly? It doesn't seem to allow both hub and focus to be used ("=yes" I presume?) at the same time, and a third parameter "airline" must be used to list the airlines, which isn't an easy way to do this. I'd also ask for some input from the Airports Project before implementing this.- Trevor MacInnis ^contribs 23:22, 16 August 2009 (UTC)

Both hub and focus city could be used, it would be similar to in Airline articles, where you would list the individual airport that was a focus city or hub for the airline. Here is an example for SFO:

Hub for	* United Airlines * Virgin America
Focus city for	* Alaska Airlines

Ishwasafish ^{click here!!!}

01:03, 17 August 2009 (UTC)

Please see this discussion. So far, two other editors have approved the additions.

Ishwasafish ^{click here!!!}

01:22, 17 August 2009 (UTC)

Y Done. I saw the mixed reactions to the focus-city but decided to add that as well. If there turns out to be a problem with that parameter it can easily be removed. Would you please update the documentation page now? — Martin (MSGJ · talk) 18:31, 17 August 2009 (UTC)

Y Done by CambridgeBayWeather (talk · contribs). Thanks a lot!

Ishwasafish ^{click here!!!}

12:50, 23 August 2009 (UTC)

Style tweaks

{{editprotected}} Requesting sync with the sandbox to bring into line with edits to other aviation infoboxes recently, and to clean the code up a bit. Comparison at test cases. Chris Cunningham (not at work) - talk 12:29, 26 September 2009 (UTC)

I've tweaked the microformat mark-up in the sandbox. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 12:37, 26 September 2009 (UTC)

Done, thanks chaps.  Skomorokh  17:42, 26 September 2009 (UTC)

{{editprotected}}

Re-sync please: missing bracket. Chris Cunningham (not at work) - talk 09:25, 29 September 2009 (UTC)

This has been done by Ynhockey. — Martin (MSGJ · talk) 13:45, 29 September 2009 (UTC)

includeonly

Why is there a bunch of things like

{{{owner<includeonly>|<includeonly>|}}}

This seems pointless to me, and causes some problems in print (click [1] to see what I mean). Headbomb {^ταλκ_{κοντριβς} – WP Physics} 22:29, 2 December 2009 (UTC)

Good question. I'm not too familiar with how this version came about, but I'll try a sandbox version without the junk and see if it still works. If it does then they should be removed. - Trevor MacInnis ^contribs 23:25, 2 December 2009 (UTC)

Hub parameter.

{{editprotected}}

Hi, just a small request to change the hub parameter from hub for to Hub/Base for, as there are quite a number of airlines which have -hub-like- operations, yet dont refer them to hubs, but they refer to them as bases. A few examples are Ryanair, Spirit Airlines, JetBlue Airways, V Australia and Regional Express Airlines, just to mention a few.

Sb617 (contribs) 00:07, 26 December 2009 (UTC)

I think Spirit, JetBlue, and Ryanair]] is already listed in the hub parameter that their bases. I think I would go for changing it to "Hub/Base for". Snoozlepet (talk) 16:22, 28 December 2009 (UTC)

Many airlines uses bases to indicate that they have a crew base there so adding that term could be confusing. Vegaswikian (talk) 00:17, 29 December 2009 (UTC)

This is a continuing concern. Many airlines do not use a hub system. Home base and focus city are just as important as hubs due to the increase of airlines using the alternative model. The percentage of traffic on these is huge now. The only argument I have seen against including additional parameters is that editors are worried that it will cause edit wars since some people get all bent out of shape when an airline isn't noted. A simple fix to that is making sure we stay make sure there is verifiability from reliable sources (kind of a big part of Wikipeida :) ) In regards to confusion, a Wikilink can take care of that. Cptnono (talk) 00:41, 29 December 2009 (UTC)

My only concern with this is the same as using "focus city". Are we going to end up with a large amount of airlines in the infobox? Enter CambridgeBayWeather, waits for audience applause, not a sausage 08:23, 29 December 2009 (UTC)

Bases and focus cities are just as important as hubs and generate a good amount of traffic as the industry has changed and airlines have not used the hub system. Maybe no parameter at all would be appropriate if the length is a concern.Cptnono (talk) 08:42, 29 December 2009 (UTC)

Just curious but are people thinking in terms of major passenger scheduled airlines only? An airline includes passengers and freight and could be made up of one aircraft doing skeds and/or charters. For an example look at Yellowknife Airport. It currently has five listed but adding bases would then include North-Wright Airways, Adlair Aviation, Buffalo Airways, Great Slave Helicopters, Nunasi Helicopters, Summit Air and there appears to be some others that I'm not sure of right now. So for a smaller regional airport we now have at least 11 and I would suspect that larger airports are going to have a few more. By the way how is "base" defined for use in Wikipedia? Enter CambridgeBayWeather, waits for audience applause, not a sausage 15:40, 29 December 2009 (UTC)

Again the encyclopedic nature of the information needs to be established. Hubs are definable. Bases is ambiguous. If we expand to what is being requested, I can see major confusing problems with helicopter airlines. Vegaswikian (talk) 18:54, 29 December 2009 (UTC)

If a source calls it a focus city or home base than it is definable. If a source doesn't say it then it can't be included per Wikipedia's standards. Hubs are still important but their prominence in the industry has diminished.Cptnono (talk) 21:52, 29 December 2009 (UTC)

All the ones I listed have sources. However, I see that you are now saying "home base" which is different to "base". As an example the home base for Adlair Aviation is Cambridge Bay Airport but Yellowknife Airport is a secondary base. That's why I asked for base to be defined. Enter CambridgeBayWeather, waits for audience applause, not a sausage 23:52, 29 December 2009 (UTC)

One suggestion is Airline hub/base for, as to make it clear the infobox is for Airlines only, and to prevent listing General Aviation/Helicopter companies in the infobox. Sb617 (contribs) 02:20, 30 December 2009 (UTC)

I don't see why airlines like Air Transat and Skyservice can be counted in the hub parameter of Canadian airports but WestJet is not. Although WestJet doesn't technically use the term "hub" it transfers passengers at these airports and base all their crews and planes out of them. Whereas Air Transat has no connecting passengers, just point-to-point service, how is that a hub? Thankyoubaby (talk) 22:46, 9 January 2010 (UTC)

Request

{{editprotected}} Could we add in the GPS identifier to the template, as I've already seen it used on a few pages. Thanks. Kevin Rutherford (talk) 01:29, 17 March 2010 (UTC)

Adding parameters to infoboxes is often considered controversial, so I would ask you to leave this request for a few days to see if anyone has any comments. — Martin (MSGJ · talk) 07:40, 17 March 2010 (UTC)

It's been two weeks, so it doesn't seem controversial. Kevin Rutherford (talk) 23:46, 31 March 2010 (UTC)

Okay fine, can you be more specific about what needs to be changed? — Martin (MSGJ · talk) 08:51, 1 April 2010 (UTC)

Please specify the exact code change required. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 22:15, 1 April 2010 (UTC)

Sorry about the delay. If possible, could "GPS: {{{GPS}}} –" be added. Most airports have a GPS identifier as they are now becomming more popular on newer planes. Thanks. Kevin Rutherford (talk) 18:49, 4 April 2010 (UTC)

Which position should this new field be placed at? — Martin (MSGJ · talk) 09:11, 5 April 2010 (UTC)

Y Done something lame from CBW 15:38, 5 April 2010 (UTC)

Request - year opened and year closed

Wikipedia is an encyclopaedia and not a catalogue, and so it seems strange not to have any historical information in the infobox apart from the parameters built and used which are, according to the documentation, only for military airports. Many public and private airport articles include the date or year the airport was opened, and most defunct public and private airport articles include the date or year it was closed. These two parameters (opened and closed) are included in the template Infobox station, and the information is just as valid and important for airports as it is for stations. Coyets (talk) 11:12, 18 May 2010 (UTC)

I checked the archives, and discovered that the parameter 'opened' was added and deleted again twice in 2005, and was proposed again in 2007 but rejected because the year that an airport was opened is not always clear. However, when I look at airport articles, the fact that no historical information is included in the infobox makes the articles, especially the shorter ones, seem like catalogue entries which sometimes have a 'History' section tacked on. Reading through the history sections, it seems that the year the airport was opened is very often clear, and the articles are often included in an establishments by year category. The fact that many airports do not have a clear year of opening does not make this information any less important. Coyets (talk) 11:37, 18 May 2010 (UTC)

The parameter would be optional, so the fact that it's available for all airports shouldn't stop it being used for those where the date is unambiguously known. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 11:42, 18 May 2010 (UTC)

It should be available and it should be done in the same style as {{Infobox settlement}} in that there is the option for multiple dates along with the title. Then you could have things like the following;

| operational_title = Construction started

| operational_date = 2000

| operational1_title = First flight

| operational1_date = 1 January 2005

| operational2_title = Official opening

| operational2_date = 1 February 2005

| operational3_title = Construction complete

| operational3_date = 2006

As Andy Mabbett points out these would all be optional so if some/all dates are not known then they won't appear. It should be clear though that these are for the airport and not for the construction of a new terminal at an existing airport. Enter CBW, waits for audience applause, not a sausage. 15:02, 19 May 2010 (UTC)

I had a look at the source of {{Infobox settlement}}, but I do not consider that I have sufficient experience in editing infobox templates to be able to add anything like that. So, would it be possible for someone who is more familiar with the syntax to add such optional parameters? Coyets (talk) 12:01, 6 July 2011 (UTC)

Request to add WMO number

Many airports also report meteorological synoptic observations, I would suggest that it would be useful to add the WMO station identifier (e.g. RAF Leeming is 03257, Newark is 72502 etc) to the infobox, somewhere near the IATA/ICAO? yorkshiresky (talk) 14:20, 19 May 2010 (UTC)

Support. Good idea. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 15:10, 19 May 2010 (UTC)

Y Done Enter CBW, waits for audience applause, not a sausage. 17:31, 24 May 2010 (UTC)

Have some from Ernest Borgnine, thanks.

Ernest Borgnine applauding

yorkshiresky (talk) 17:55, 24 May 2010 (UTC)

Edit request - conditional line break

{{editprotected}} The recent addition of a line break before the recently added GPS and WMO airport codes creates a blank line in the infobox on some airport pages. This can be fixed by replacing:

<br>{{#if:{{{GPS|}}}| – [[Global Positioning System|GPS]]: <span class="nickname">{{{GPS}}}</span>|}} {{#if:{{{WMO|}}}| – [[Location identifier#WMO station identifiers|WMO]]: <span class="nickname">{{{WMO}}}</span>|}}

with:

{{#if:{{{GPS|}}}{{{WMO|}}}|<br/>}} {{#if:{{{GPS|}}}| – [[Global Positioning System|GPS]]: <span class="nickname">{{{GPS}}}</span>|}} {{#if:{{{WMO|}}}| – [[Location identifier#WMO station identifiers|WMO]]: <span class="nickname">{{{WMO}}}</span>|}}

-- Zyxw (talk) 21:34, 24 May 2010 (UTC)

Done. I was just thinking the same thing. Thanks! Plastikspork _―Œ^(talk) 22:07, 24 May 2010 (UTC)

Sorry about that. Enter CBW, waits for audience applause, not a sausage. 22:41, 24 May 2010 (UTC)

No problem at all. The first step was the more complicated one, this follow-up was somewhat minor. Thanks! Plastikspork _―Œ^(talk) 22:59, 24 May 2010 (UTC)

Edit request - units of measurement

{{editprotected}} that:

1. all instances of [[metre|m]] be changed to m; and
2. all instances of [[Foot (length)|ft]] be changed to ft

in accordance with WP:OVERLINK. These well known units of measurement, especially in terms of the context, are never likely to be unfamiliar nor ambiguous, and should be removed. Ohconfucius ^¡digame! 08:50, 4 July 2010 (UTC)

Y Done HJ Mitchell | Penny for your thoughts? 19:21, 4 July 2010 (UTC)

This template still has some. Please edit:

1. all instances of [[metre|m]] be changed to m; and
2. all instances of [[Foot (length)|ft]] be changed to ft

Regards Lightmouse (talk) 13:05, 23 August 2010 (UTC)

Hopefully that did it. Plastikspork _―Œ^(talk) 19:07, 23 August 2010 (UTC)

Thanks. Lightmouse (talk) 13:19, 24 August 2010 (UTC)

Edit request from Yunchie, 29 September 2010

{{edit protected}} Is it possible to add the following fields: owner-contact (displaying the contact's name) owner-telephone (displaying the contact's telephone number) operator-contact (displaying the contact's name) operator-telephone (displaying the contact's telephone number)

These would be sub-fields of the current owner & operator fields, and data should display only if those fields are occupied, and then without a field label.

Example (current operator field with additional data)

Airport Flying Service
John Smith - Manager
555-555-5555

Or, can you suggest a work-around to display this information beneath the existing owner and/or operator fields?

Yunchie (talk) 12:39, 29 September 2010 (UTC)

I really don't think that we should be providing the phone number for airports. I'm sure that the owner of Essex/Billing Airstrip would not really want his phone number published in Wikipedia. Also I'm not convinced that there is any encyclopaedic value in providing the numbers. I checked a few and while some numbers may lead you directly to the airport authority others do not. For the most part there is a link to the airport website and contact information can usually be found there. I looked at Edmonton International Airport, their contact page and Canada Flight Supplement (CFS). The phone number for Edmonton Airports in the CFS is different from any listed on the contact page. Enter CBW, waits for audience applause, not a sausage. 13:17, 29 September 2010 (UTC)

I don't agree that owners would not want a number published, but I can understand its lack of encyclopedic value, somewhat. I do see it as an 'Information Box', which probably should provide some information rather than make the viewer search for it. Regarding an airport, often the owner is a government entity, and there probably is a pertinent contact person that has a number. In the case of smaller, public airports, the owner and operator may be one and the same, also having a specific contact person. My request was only to offer these options in the template for the wide variety of situations found. Yunchie (talk) 13:51, 29 September 2010 (UTC)

I am disabling the edit request for now, but please continue to discuss. I would say that Wikipedia:NOTDIRECTORY is reason enough to discuss this before implementation. Thanks! Plastikspork _―Œ^(talk) 00:33, 30 September 2010 (UTC)

OK, I can see the point of the 'no phone number' in the reference that you provided. As it doesn't specifically prohibit a 'Contact Name', I can change my request to just that. I can offer support for this with the example that a school might list the name of its principal. Perhaps, instead of the phone number, a separate field for the title would be more appropriate instead of the method that I used as an example above. Yunchie (talk) 01:36, 30 September 2010 (UTC)

I have no problem with the manager/contact person being listed if known. Enter CBW, waits for audience applause, not a sausage. 05:26, 30 September 2010 (UTC)

hCard microformat improvement

{{editprotected}}

Please change:

|- class="note" style="text-align: left"
{{#if: {{{type<includeonly>|</includeonly>|}}}|
! colspan=2 {{!}} Airport type
{{!}} colspan=2 {{!}} {{{type}}}

to:

|- style="text-align: left"
{{#if: {{{type<includeonly>|</includeonly>|}}}|
! colspan=2 {{!}} Airport type
{{!}} colspan=2 class="category" {{!}} {{{type}}}

So that the "type" value is coded as an hCard microformat "category" (nothing to do with Wikipedia categories), and not the more generic "note". Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 14:50, 29 December 2010 (UTC)

I was going to do this but I was unsure about something. What is the purpose of the <code>, </code> as the don't seem to appear on the page? Also I noticed that the other sections below this one also use the first style. Do they need updating as well? Enter CBW, waits for audience applause, not a sausage. 15:49, 29 December 2010 (UTC)

Included in error; now removed, thanks. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 16:22, 29 December 2010 (UTC)

Y Done. Enter CBW, waits for audience applause, not a sausage. 19:10, 29 December 2010 (UTC)

That's great, thank you. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 21:46, 29 December 2010 (UTC)

Including a location map

A lot of airport article infoboxes have a {{Location map}} included via the rather hacky method of putting it in one of the airport code fields - see for example the Heathrow or JFK articles. I suggest that we add code to the template to do it properly, as it is done in {{Infobox settlement}}. This would mean having separate parameters for longitude and latitude which would generate the {{coord}} template, rather than putting the {{coord}} template in a single coordinates parameter. (Although the code would be set up so that the coordinates parameter continues to work as it does now, so nothing would break.) I am willing to do the wikicode for this if we agree that it is a good idea - we would also need to decide where in the template the map would be most suitably placed. - htonl (talk) 11:33, 8 January 2011 (UTC)

Sounds like a good idea. I would say either right above the summary section would be a good place for it. Or, right before the the runways section. Plastikspork _―Œ^(talk) 15:59, 8 January 2011 (UTC)

Yes, writing it into the parameter would be much better.♦ Dr. Blofeld 16:01, 8 January 2011 (UTC)

Sounds fine. Would it be possible to do in such a way that the two lines in the {{Infobox settlement}}, "coordinates_type = airport" and "coordinates_display = inline,title", would not be required but would be the automatic default? Enter CBW, waits for audience applause, not a sausage. 18:39, 8 January 2011 (UTC)

Sure, we could make "title" display the default, unless it is specified otherwise. As far as the type goes, we could use "coordinates_region", and have "type:airport" appended by default. Plastikspork _―Œ^(talk) 18:42, 8 January 2011 (UTC)

Well, I'm going to start working on it then. - htonl (talk) 10:22, 9 January 2011 (UTC)

OK, so I've got an initial attempt sorted out in the sandbox. It allows for a {{Location map}} as well as a map that is just a plain image. I've updated the test cases accordingly, and there are some other examples in my sandbox.

The new parameters are as follows:

Coordinates

• latd, latm, lats, latNS: latitude - degrees, minutes, seconds, and north/south. You can also use just latd with decimal degrees.
• longd, longm, longs, longEW: longitude - degrees, minutes, seconds, and east/west. You can also use just longd with decimal degrees.
• coordinates_type: type coordinate parameter. Defaults to airport. (You shouldn't need to set this.)
• coordinates_region: region coordinate parameter.
• coordinates_notitle: By default the coordinates are displayed in the infobox and in the title. If this parameter is set to a non-null value then they are displayed only in the infobox.

Pushpin map

• pushpin_map: Name of a map definition template used by {{Location map}}. If, for example, you set this to Spain it will use the map defined by {{Location map Spain}}. The coordinate fields (eg. latd and longd) position a pushpin coordinate marker and label on the map automatically.
• pushpin_label_position: The position of the label on the pushpin map relative to the pushpin coordinate marker. Valid options are {left, right, top, bottom, none}.
• pushpin_label: The label to use on the pushpin map. Defaults to the name parameter.
• pushpin_map_alt: Alt text for the pushpin map.
• pushpin_mapsize: Width of the pushpin map, in pixels. Number only, do not include "px". Defaults to 220.
• pushpin_image: Alternative map image, see Template:Location map#Using Alternative Map for details.
• pushpin_map_caption: Caption to appear below the pushpin map.

Image map

• image_map: Name of an image file - do not include the File: prefix.
• image_mapsize: Width of the image map, in pixels. Number only, do not include "px". Defaults to 220.
• image_map_alt: Alt text for the image map.
• image_map_caption: Caption to appear below the image map.

- htonl (talk) 18:00, 9 January 2011 (UTC)

{{Edit protected}} Request that this template be synced with the sandbox to introduce the above-described additions. - htonl (talk) 16:25, 11 January 2011 (UTC)

Done but the documentation needs doing as well. Enter CBW, waits for audience applause, not a sausage. 16:35, 11 January 2011 (UTC)

Yes, I'll do that now. - htonl (talk) 18:02, 11 January 2011 (UTC)

Used it here and here for now. Enter CBW, waits for audience applause, not a sausage. 18:11, 11 January 2011 (UTC)

Great! I hope the documentation is satisfactory. In the examples I removed the stuff about using {{coord}} inside the infobox creating too-small coordinates in the title, since that doesn't seem to happen any more as far as I can see. I didn't add a map to the Beijing example since there isn't a suitable {{Location map}} (other than the whole-of-China map), and it can also serve as an example of using the old-style coordinates parameter. - htonl (talk) 19:18, 11 January 2011 (UTC)

Additional military parameter

Hi, just comparing this template to the military unit infobox, it'd be nice to borrow the "notable commanders" parameter from the unit one for air bases. The existing "commander" parameter is fine for the current commander, and the unit infobox has that as well, but for past commanders the "notable commanders" one works well. There are other parameters from military units that would also be of value, such as "aircraft flown", but that's not particluarly vital when the "occupants" parameter can point you to units, which will generally include the aircraft. Really like to see "notable commanders" though... ;-) Cheers, Ian Rose (talk) 08:34, 13 January 2011 (UTC)

Any response to this? Cheers, Ian Rose (talk) 01:20, 1 February 2011 (UTC)

Do you have examples of air bases where "notable commanders" in an infobox (presumably duplicating info in the article) would help readers of an airport article ? Listing previous commander(s) in infobox might be useful for military units, but I think we should draw the line at air bases. DexDor (talk) 20:46, 18 April 2011 (UTC)

Past notable commanders (which, in WP terms, effectively means past commanders who have their own article) are just as worthwhile for air bases as they are for any other military unit. This may be where we hit a bit of an impasse, aviation people see them simply as airfields whereas military people see them also as (static) units. There has been discussion elsewhere of simply creating a new and separate template for military airbases, and perhaps that will be the better course. I just felt it was a bit a shame to have something separate when there are military air bases that share facilities (at least a runway) with civilian airports, and one infobox could make things tidier. Cheers, Ian Rose (talk) 21:57, 18 April 2011 (UTC)

Text alignment in statistics data area

The statX-data items are numbers and should be aligned to the right to flush with the right side of the table. It always looks odd looking at passenger statistics when they are flushed left as they are today, especially when there are multiple stat numbers - they don't line up right one below the other. Thanks, Wikiliki (talk) 16:51, 10 February 2011 (UTC).

Seems reasonable. I will leave this open for a bit and see if there are any objections. Plastikspork _―Œ^(talk) 01:47, 11 February 2011 (UTC)

Pushpin map alignment - edit request

{{Edit protected}} Please sync with the current revision of the template sandbox. Somewhere in the recent series of layout edits, something was changed so that the pushpin map is no longer centered in the template. My edit to the sandbox fixes that. You can see the difference in the testcases. - htonl (talk) 15:05, 13 March 2011 (UTC)

Done. If I recall, we even had to add some explicit <center> tags at {{Infobox settlement}} to make the centering work in all browsers. Plastikspork _―Œ^(talk) 17:20, 13 March 2011 (UTC)

Wright-Patterson AFB

I just noticed that the Infobox on the Wright-Patterson Air Force Base page is different than the example given in Example 4. Is this intentional due to guidelines or does one need to be updated? It would probably be beneficial if the Example and the page matched. Evan.oltmanns (talk) 00:17, 20 March 2011 (UTC)

Feel free to update the documentation and/or the article. I don't think anyone bothers to keep them in sync. Frequently examples are made more generic to avoid this issue. Thanks! Plastikspork _―Œ^(talk) 02:44, 28 March 2011 (UTC)

Italics for foreign Native Names?

Forgive me if this has been raised before, but I would have thought that when the 'nativename' in the infobox is in a foreign language, then this should be in italics. Overall guidance on the use of italics is at MOS:Ety, and articles do seem to use italics in the body of the article (see Gran Canaria Airport). However this style is not carried forward into the infobox.

Previous discussion at archives in 2006 raised the point, but it was not addressed. I've tried italics in the infobox at Lanzarote Airport - to me it looks clearer and more consistent with Wikipedia atyle. What do people think? Carbonix (talk) 18:16, 29 July 2011 (UTC)

Any views anyone? or shall I just go ahead? Carbonix (talk) 15:16, 16 August 2011 (UTC)

I don't think that you can change the "native_name=" field to always be in italics. The field is not always used to give a non-English name but sometimes an alternate English name. See Region of Waterloo International Airport or John C. Munro Hamilton International Airport for example. CambridgeBayWeather (talk) 11:56, 17 August 2011 (UTC)

Ah, good point. Thank you.

• This would suggest that italics for a non-English 'nativename' should not be a standard requirement, embedded in the template, but used only on a case by case basis, that is, for foreign language alternate names. Indeed, the use of italics helps distinguish that the 'nativename' is the local language version, not an alternative English-language appellation. A reminder about italics could be included in the Parameters section on the Template page.
• Also, there are inconsistencies in how the "native_name=" field is used; to me, it is intended for materially different names, not just where there are shortened versions of the full name; thus, London Heathrow and Toronto airports have alternative names in the article but don't need a 'nativename', but Hong Kong and Region of Waterloo do because they have alternative names not simply derived from the full name. Again, a consistent solution needs clarification in the Parameters section rather than a change in the template.

Agreed?! If these points are valid, how do we agree and amend the Parameters notes for them? Many thanks for people's guidance on this process! Carbonix (talk) 22:00, 19 August 2011 (UTC)

I've been bold and updated the documentation. Please make changes if it doesn't look correct. CambridgeBayWeather (talk) 17:30, 20 August 2011 (UTC)

Great - thank you. Carbonix (talk) 18:18, 23 August 2011 (UTC)

Edit request from RaymondSutanto, 30 July 2011

Please add an interwiki: id:Infobox Bandara. Thanks. RaymondSutanto (talk) 05:05, 30 July 2011 (UTC)

Interwikis are added to the unprotected documentation. 117Avenue (talk) 05:08, 30 July 2011 (UTC)

{{formatnum: }} and {{Convert}}?

Would it be possible to add {{formatnum: }} magic word to runway length, elevation and statistical data fields to automatically add thousand separators etc.? And would it be possible to use {{Convert}} to automatically convert elevations and runway lengths from metres to feet and vice versa? ––Apalsola ^{t • c} 18:31, 30 July 2011 (UTC)

You would also want it added to the elevation section. As for the second it's not that easy see Template talk:Infobox airport/Archive 4#Automatic conversions. CambridgeBayWeather (talk) 07:05, 31 July 2011 (UTC)

Sure, code can be prepared in Template:Infobox_airport/sandbox. —TheDJ (talk • contribs) 21:52, 31 July 2011 (UTC)

I've prepared the code in Template:Infobox_airport/sandbox and made a few more test cases in Template:Infobox airport/testcases. The differences are:

• For elevation, runway length and helipad information: if only the primary value (i.e. metric, if "metric-rwy/elev=y", otherwise feet) is given, it is autoconverted to the secondary value with {{convert}}. If only the secondary value (i.e. feet, if "metric-rwy/elev=y", otherwise metric) is given, it is not autoconverted.
• If both the metric- and feet-values are given, no autoconvert is done.
• Elevation, runway length, helipad length and statistical data are automatically formatted with {{formatnum: }}. So, no thousand separator commas needed anymore (but they don't do any harm, either).
• Elevation values and unit symbols are separated with a non-breaking space per Wikipedia:Manual of Style (dates and numbers)#Unit names and symbols.

The sandbox template passes all the test cases in Template:Infobox airport/testcases. ––Apalsola ^{t • c} 12:13, 3 August 2011 (UTC) –– (edit) Apalsola ^{t • c} 12:19, 3 August 2011 (UTC)

Not done as there are errors showing up in test cases 1, 4, 5 and 6.

In #1 runway 18L/36R is given as

| r6-length-f  = 13,400 | r6-length-m  = 4,084

but displays as

18L/36R     13,401     4,084

. Test #2 is similar in that runway 18L/36R is given as

| r6-length-f  = 13400 | r6-length-m  = 

but displays as

18L/36R     13,401     4,084

. Test #5 and 6 are the same the runways are given as

| r1-number    = 04R/22L | r1-length-f  = | r1-length-m  = 3440 | r1-surface   = [[Asphalt]] |  2-number    = 04L/22R | r2-length-f  =
| r2-length-m  = 3060

but display as

04R/22L     3,440     11,286     Asphalt
04L/22R     3,060     11,286

CambridgeBayWeather (talk) 09:54, 4 August 2011 (UTC)

There were some wrong parameters. I fixed them. ––Apalsola ^{t • c} 09:16, 5 August 2011 (UTC)

Done. CambridgeBayWeather (talk) 15:59, 5 August 2011 (UTC)

I had to revert due to a couple of problems pointed out at User talk:CambridgeBayWeather#Infobox airport. Check out test cases 9 & 10 Template:Infobox airport/testcases. Also test 8. I don't think that it will happen but you never know. That's what happens when you remove the "r1-length-f" and "elevation-f" lines. It would be a nice tweak but I don't think that it is really important. CambridgeBayWeather (talk) 20:54, 5 August 2011 (UTC)

Fixed the problems pointed out at test cases 8 and 9. About the test case 10, the reference is in a wrong place. I think we just have to fix them manually article by article. For example {{Infobox settlement}} – a very widely used template – behaves exactly the same way if you put the reference in the wrong place. (See the demo here.) The footnotes parameter is the right place for references. Or we could also have parameters such as elevation_footnotes, coordinates_footnotes, runway_footnotes, stat1_footnotes etc. (similar to the Infobox settlement template) for placing inline references. ––Apalsola ^{t • c} 22:30, 5 August 2011 (UTC)

Done. CambridgeBayWeather (talk) 04:10, 6 August 2011 (UTC)

The elevation rounding problem pointed out at User talk:Apalsola#Infobox airport is fixed in Template:Infobox airport/sandbox. See also: Template:Infobox airport/testcases#Test case 11: Elevation rounding. ––Apalsola ^{t • c} 22:43, 12 August 2011 (UTC) –– (edit) Apalsola ^{t • c} 22:45, 12 August 2011 (UTC)

Done. CambridgeBayWeather (talk) 10:23, 13 August 2011 (UTC)

Edit request - enable parameters to specify pushpin map marker image and size

The pushpin maps as enabled in {{Infobox airport}} use a default image and size for the marker (). I propose allowing a non-default image and size for instances where a location map image is too dark to allow easy viewing of the black airplane marker. This would be accomplished via the addition of two parameters: pushpin_mark and pushpin_marksize (passed through to {{Location map}} via its parameters mark and marksize). This will not affect any existing airport infobox, because the template will use the current defaults if the new parameters are not included or are blank.

Current template code:

|mark = Airplane silhouette.svg
|marksize = 10

Suggested change:

|mark = {{#if: {{{pushpin_mark|}}} | {{{pushpin_mark}}} | Airplane silhouette.svg }}
|marksize = {{#if: {{{pushpin_marksize|}}} | {{{pushpin_marksize}}} | 10 }} 

This has been implemented in {{Infobox airport/sandbox}} (diff) and an example can be seen at {{Infobox airport/testcases#Test case 3: New parameters: pushpin_mark, pushpin_marksize}}. -- Zyxw (talk) 08:29, 2 August 2011 (UTC)

Some kind of bug

Not sure why it generates "+UNIQ72be792a556,627f8-ref-00,000,000-QINU" stuff at Robert Mueller Municipal Airport... AnonMoos (talk) 12:28, 16 August 2011 (UTC)

The |statn-data= fields are formatted with ​formatnum:​ magic word. This causes the references to bork and expose the strip markers that you are seeing; example: UNIQ697,726d274aec623-ref-00,000,066-QINU. The only way to fix this is to:

• Not include <ref> tags
• Update the template to not use ​formatnum:​
• Update the template to add parameters for references

---— Gadget850 (Ed) ^talk 11:30, 16 October 2011 (UTC)

You could add parameters like |stat1-dataref=:

From

|- style="text-align: left"
{{#if: {{{stat1-header<includeonly>|</includeonly>}}} {{{stat1-data|}}}|
! colspan=3 {{!}} {{{stat1-header<includeonly>|</includeonly>}}}
{{!}} {{formatnum: {{{stat1-data<includeonly>|</includeonly>}}} }}
}}

To

|- style="text-align: left"
{{#if: {{{stat1-header<includeonly>|</includeonly>}}} {{{stat1-data|}}}|
! colspan=3 {{!}} {{{stat1-header<includeonly>|</includeonly>}}}
{{!}} {{formatnum: {{{stat1-data<includeonly>|</includeonly>}}}{{{stat1-dataref|}}} }}
}}

There are several formatted fields, so a ref parameter would need to be added to all of them. This template would be a lot easier to maintain if it were updated to {{Infobox}}. ---— Gadget850 (Ed) ^talk 12:16, 16 October 2011 (UTC)

The general response to this issue has been to use the "footnotes" section. I don't think {{infobox}} is going to fix that. Especially if you consider this template uses four columns. Thanks! Plastikspork _―Œ^(talk) 16:04, 16 October 2011 (UTC)

This is still an issue in several uses of this template; see qinu airport site:en.wikipedia.org. See Help:Strip markers for details on this issue. ---— Gadget850 (Ed) ^talk 21:25, 4 February 2012 (UTC)

Opened/ closed dates

We should add a |date_opened= and probably |date_closed=. Any comments? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 28 January 2012 (UTC)

Distance to city

Why not include a |dist-to-city_mile and a |dist-to-city_km parameter into the template? Maybe merge it with the |city-served field? Pizza1016 (talk) 10:44, 2 February 2012 (UTC)