Template talk:Infobox airport/Archive 5

Archive 1

←

Archive 3

Archive 4

Archive 5

Archive 6

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: . 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.wiki.x.io. 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)

I agree. Currently only military airports are afforded this using the |built= and |used= fields. __meco (talk) 13:30, 25 February 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)

If you do that, there should also be a |dist-to-city_nmi= parameter, because of our dear friend GCM, which enables us to get that information too, and because a lot of AIP references list distance in nmi. - Jorgath (talk) 05:35, 15 February 2012 (UTC)

You don't need three just two. If it is thought to be a good idea then |dist-to-city and |dist-to-city_unit with nautical miles the default that converts to km and mi. With the option of km that converts to nmi/mi or mi that converts to nmi/km. CambridgeBayWeather (talk) 00:37, 16 February 2012 (UTC)

Focus city airlines listed in the hub section of an infobox

Copied from discussion at WP Airports talk page Should airlines like Southwest that do not operate on a traditional hub-and-spoke system, but rather have a larger decentralized focus-city network, up in the "Hub" section of the infobox of an airport that is listed as a focus city? Someone just recently edited the Oakland International Airport article to include Southwest Airlines as a hub tenant. Just wanted to build some kind of consensus here before I went and edited it. nf utvol (talk) 20:01, 13 February 2012 (UTC)

From the airport's perspective, if a single airline has a lot of flights to and fro, maybe several aircraft (and crew &c) based there, then it's reasonable to call it a hub (even better if a reliable source calls it a hub) even if it's not the sole focus of that airline. bobrayner (talk) 15:48, 14 February 2012 (UTC)

My thought is that we should only list actual stated hubs there. That is, airlines that operate on a true hub and spoke system that fly a substantial number of flights to non-hub airports from the city in question. For instance, even though American Airlines has a lot of flights out of Nashville, almost all of their flights are to hub airports. With airlines like Southwest that operate on a Focus City system, probably a quarter of the airports they fly to would be considered hubs, which would just clutter the infobox. Also, many airlines have crew and maintenance bases at small airports, such as Dayton or Knoxville, that are definitely not a hub. Perhaps the addition of a "Crew Base" or "Focus City" entry into the infobox could be useful? Of course, then we run the risk of including too much in the infobox. nf utvol (talk) 16:16, 14 February 2012 (UTC)

How about a compromise? If a reliable source lists a destination as a hub of an airline, it's listed as a hub in the infobox. This is regardless of whether or not the airline uses a hub-and-spoke system. Airline webpages count as a reliable source if they declare the destination a hub, but not if they use the term "focus city" or something similar. - Jorgath (talk) 21:07, 14 February 2012 (UTC)

If the definition at Airline hub is to be trusted (and that article surely needs some TLC), a hub is:

An airline hub is an airport that an airline uses as a transfer point to get passengers to their intended destination. It is part of a hub and spoke model, where travelers moving between airports not served by direct flights change planes en route to their destinations. Many hubs of the airlines are also situated at airports in the cities of the respective head offices. Some airlines may use only a single hub, while other airlines use multiple hubs. Hubs are used for both passenger flights as well as cargo flights.

Which requires transfer traffic, not flights to non-hub airports. Whether Southwest's presence at Oakland qualifies, or whether that definition is correct, I leave for others to haggle over! bobrayner (talk) 22:03, 14 February 2012 (UTC)

I don't want to get drawn into (i) what the formal definition of a "hub" is or (ii) what the difference between hubs and focus cities is, but I do want to point out the following:

Just an observation..... --RFBailey (talk) 23:42, 14 February 2012 (UTC)

Good point. Another compromise suggestion, then: have the infobox template display "hub/focus city for" rather than "hub for," and include all declared hubs and/or focus cities. - Jorgath (talk) 00:35, 15 February 2012 (UTC)

Alas, I must disagree again (don't take it personally; I'm very disagreeable). "Hub/focus city for" is slightly stilted wording, and if we want a global perspective, "focus city" is something we should be moving away from. Can't we just use the word "hub" more carefully? bobrayner (talk) 02:21, 15 February 2012 (UTC)

I'm not taking it personally, don't worry. And I agree with the wording issue. The problem is that by only using official "hubs," we're on the verge of systemic bias against airlines that don't use a hub-and-spoke system, so what we need to do is actually use "hub" less narrowly even if we use it more carefully. Maybe the solution (though I dislike it) is to entirely remove the "hub" parameter from the airport infobox, leaving that information for the airline pages alone. I don't have a better idea, but we've got to either do that or find a way to include an equivalent mention of non-hub-and-spoke airlines in the infobox (and by equivalent I mean listing airlines that make major use of that airport). Hmm...maybe try to figure out a number of airports (3? 5?) that should be considered "hubs" for this purpose, even if they are officially listed as "focus cities" or some such thing? - Jorgath (talk) 04:21, 15 February 2012 (UTC)

I'm not entirely opposed to removing it, as I fall under the flag of less-is-more in infoboxes. Does including the hub in the infobox really add anything of status to it that isn't better explained in the prose of the lead in and body? As an alternative, it could be useful to reword it and change it to "Major Airline Presence" or something along those lines. That would allow for the inclusion of smaller feeder airlines like PSA or Republic in the infoboxes of airports that they use as crew bases.nf utvol (talk) 15:53, 15 February 2012 (UTC)

Edit request on 13 May 2012: different than

Please change the two occurrences of "if different than ICAO or IATA codes" to "if other than ICAO or IATA codes" and please change "if different than the owner" to "if not the owner". —Anomalocaris (talk) 18:31, 13 May 2012 (UTC) Anomalocaris (talk) 18:31, 13 May 2012 (UTC)

Not done: {{edit protected}} is usually not required for edits to the documentation, categories, or interlanguage links of templates using a documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage. --Redrose64 (talk) 23:11, 13 May 2012 (UTC)

It's at Template:Infobox airport/doc. CambridgeBayWeather (talk) 23:15, 13 May 2012 (UTC)

Problem with presentation

G'day, I have just noticed a problem with the Infobox in the Sydney Airport article. There is a year given in brackets for the freight tonnage total; when I view it, it says "(2,009)" instead of "(2009)" but it has been typed correctly. YSSYguy (talk) 08:02, 20 May 2012 (UTC)

This is because |stat3-data= (like |stat1-data=, |stat2-data= and |stat4-data=) is pushed through the {{formatnum:}} parser function, which expects a pure integer with no other information. The information in these four parameters should be for the same year as is given in |stat-year=; no variation is provided for. --Redrose64 (talk) 20:51, 20 May 2012 (UTC)

I've noticed this on Edmonton International Airport, as well, I don't know what a fix could be. 117Avenue (talk) 23:29, 20 May 2012 (UTC)

Well as a workaround there is this and this. CambridgeBayWeather (talk) 00:11, 21 May 2012 (UTC)

Edit request - enable parameter to display pushpin relief map

I propose allowing the infobox to pass a value to the relief parameter used by {{Location map}}. This would be accomplished via the addition of a pushpin_relief parameter to {{Infobox airport}}.

Background: Setting pushpin_map = Chad causes {{Infobox airport}} to use the map definitions specified in Template:Location map Chad, including the default map image (in this example, File:Chad location map.svg). However, many of the map definition templates specify a second image that is usually a relief map (such as File:Chad relief location map.jpg). The {{Location map}} template will display this second image if the relief parameter is set to any value (such as "y").

Current template code:

|width = {{#if:{{{pushpin_mapsize|}}}|{{{pushpin_mapsize|}}} | 220 }}
|AlternativeMap = {{{pushpin_image|}}}

Suggested change:

|width = {{#if:{{{pushpin_mapsize|}}}|{{{pushpin_mapsize|}}} | 220 }}
|relief = {{{pushpin_relief|}}}
|AlternativeMap = {{{pushpin_image|}}}

This has been implemented in {{Infobox airport/sandbox}} (diff) and an example can be seen at {{Infobox airport/testcases#Test case 12: New parameter: pushpin_relief}}. The change will not affect any existing airport infobox, because the template will use the default map image when pushpin_relief is not included or is blank.
-- Zyxw (talk) 18:21, 14 August 2012 (UTC)

 Done. Let me know if there are any issues with it. Best — Mr. Stradivarius ^{(have a chat)} 07:36, 15 August 2012 (UTC)

Edit request - add focus cities

As discussed at WikiProject Airports, focus cities will be a positive for airport pages, similar to airline pages. Kairportflier (talk) 22:29, 15 August 2012 (UTC)

Please add below Hub but above Built, Thanks! Kairportflier (talk) 16:26, 16 August 2012 (UTC)

|- style="text-align: left"
{{#if: {{{focus_city<includeonly>|</includeonly>|}}}|
! colspan=2 {{!}} [[Focus city|Focus city]] for
{{!}} colspan=2 {{!}} {{{focus_city}}}

 Done I've tested your edit in the sandbox and fixed the code (the code above was missing the closing }}). Next time, please test out your edits in the sandbox and use an {{edit protected}} template. Thanks — Mr. Stradivarius ^{(have a chat)} 16:49, 16 August 2012 (UTC)

Struck-though text

There's a discussion of use of this infobox, at Talk:Nanjing Dajiaochang Airport#Struck-through content. Your views would be welcome. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:02, 19 September 2012 (UTC)

Removal of wiki link

I don't understand why the word Coordinates is linked in the box - [[Geographic coordinate system|Coordinates]]. It looks bizarre to me, and I think it should be unlinked. John of Cromer in China (talk) mytime= Wed 08:12, wikitime= 00:12, 21 November 2012 (UTC)

Additional fields?

I suggest following additional fields:

• f(n)-runway-width-f
• f(n)-runway-width-m
• largest-handling-capacity
• airport-manager

Further, there are a number of parameters described in runway which it may be useful to consider here. These include Declared distances, flare path, and an extended description of runway surface. There are other more technical parameters whose inclusion could be discussed here.

00:28, 21 November 2012 (UTC)

Oops, wrong button John of Cromer in China (talk) mytime= Wed 08:35, wikitime= 00:35, 21 November 2012 (UTC)

Edit request on 27 November 2012: Alt text for images

Add alt text parameter to the template for images as per MOS:IMAGES and WP:ACCESS. Thank you.

TBrandley 02:28, 27 November 2012 (UTC)

I added |image_alt= and |image2_alt=. Thanks! Plastikspork _―Œ^(talk) 05:41, 27 November 2012 (UTC)

Edit request on 27 November 2012: Runway width and other information

1. Remove linking from the word 'coordinates' as it serves no useful purpose. line 94
2. Add parameter 'manager' after parameter 'owner' - lines 35 - 44
3. Add parameter 'r[n]-width-f / r[n]-width-m after lines 152/153, 159/160, 166/167, 173/174, 180/181, 187/188, 194/195, 201/202
4. Before line 323 start a new heading 'Other information", then also add processing for further parameters 'largest-handling-capacity' which refers to aircraft size, and 'fuel-availability' which can be Yes or No.

John of Cromer in China (talk) mytime= Tue 11:13, wikitime= 03:13, 27 November 2012 (UTC)

I support your proposed changes. TBrandley 03:16, 27 November 2012 (UTC)

I thought I'd get everything done at once, while they have the box open! John of Cromer in China (talk) mytime= Tue 11:32, wikitime= 03:32, 27 November 2012 (UTC)

There are quite a lot of changes here. Could you add them to the template sandbox? It will be a lot less likely for me to make a mistake that way. Also, you can view the changes against the main template at the test cases page. If you have any difficulty with the coding, just let me know, and I can try and add what I think you are getting at to the sandbox. :) Best — Mr. Stradivarius ^{(have a chat)} 11:57, 27 November 2012 (UTC)

I'll have a crack John of Cromer in China (talk) mytime= Tue 21:03, wikitime= 13:03, 27 November 2012 (UTC)

Curious about the "largest handling capacity" line. Is that to be for the largest possible aircraft or the largest and most commonly used aircraft at an airport? For example Cambridge Bay Airport has had a Boeing 727 on several occasions but the aircraft can't use the airport when it is fully loaded. However, the largest most common aircraft is the Boeing 737. CambridgeBayWeather (talk) 12:37, 27 November 2012 (UTC)

The airport I have in mind has a GRE runway and the biggest it can handle is a Dash-7. And no fuel. John of Cromer in China (talk) mytime= Tue 21:03, wikitime= 13:03, 27 November 2012 (UTC)

 Administrator note I have disabled the request. Please reactivate when the required changes have been made to /sandbox and it is fully tested. — Martin (MSGJ · talk) 14:04, 27 November 2012 (UTC)

Example 1
IATA: none ICAO: none
Summary
Runways
Direction Length Surface m ft 10L/28R 4,000 13,123 Asphalt/Concrete

Example 2
IATA: none ICAO: none
Summary
Runways
Direction Length Surface m ft 10L/28R 4,000 × 45 13,123 × 148 Asphalt/Concrete

Example 3
IATA: none ICAO: none
Summary
Runways
Direction Length Surface m ft  10L/28R   4,000 × 45   13,123 × 148   Asphalt/Concrete

I think we need to be careful that the infobox doesn't start getting too large with additional information that might be better placed in the body of the article. Here are my comments on the suggestions above:

1. Runway widths: I have experimented with adding these manually to the infobox in the past. I found that it made the infobox appear cluttered and more difficult to read (Example 2), but that can be resolved by including additional white space (Example 3). Also, the "Length" header text should only include " × Width" if width parameters are displayed. These changes increase the infobox width (Example 1 vs. Example 3), but please do not hardcode anything wider than the current default so as not to affect all the existing infoboxes.
2. Coordinates: No problem with removing the link from the word (it is the same link you'll find with coordinates displayed in the upper right title area on many pages). We should also consider removing the link for "Runway", since the blue text on blue background isn't easily readable (as seen in examples to right).
3. Manager: Is the name of the individual who manages an airport notable enough to even be added to the article, much less the infobox? I read and edit a lot of airport articles and I rarely see the manager mentioned.
4. Other information: Again I think most of these are better placed into the article instead of the infobox. If this new section is added, please try to keep the added parameters to a minimum. "Largest handling capacity" I can see since it is of general interest, "fuel availability" perhaps less so.

-- Zyxw (talk) 13:09, 2 December 2012 (UTC)

All those curly braces are making my eyes go funny! It's a very laborious process, because I have to save the sandbox changes each time I make a change, before I can cycle the testcase. What I intend is have × actual-width (if present) on the line below length, so that box is longer rather than wider. Problem now is that somewhere in the meta-parsing process that part gets wrapped in <p> </p> which means it doesn't align with the others.

All info is optional, so if it is not of consequence it doesn't get included. Part-time grass feeder airfields are different from international ones. I don't see how the name of an AFB commander is actually different from that of a manager.

There are several pointless wikilinks. Runway would be white otherwise, ditto Helipad. Others: tonnes. And have you ever clicked on the actual coordinates or the globe next to them? One page I'm familiar with, they lead to two different maps, one of which includes sunken World War II warships (clickable). John of Cromer in China (talk) mytime= Sun 22:05, wikitime= 14:05, 2 December 2012 (UTC)

I often click the actual coordinates link and use the resulting "GeoHack" page to view Google Maps (hybrid satellite view), Bing Maps (for its unique Bird's Eye view), Wikimapia (shows places not labelled on other maps including details within some airports), MapQuest (at a certain zoom level it has nice view showing U.S. county borders), and SkyVector (aeronautical charts for articles missing a direct SkyVector link). Very rarely use the globe link, but it is automatically added to coordinate links in infoboxes and in the page's title area at top right (for more on that see Template talk:Coord#Globe icon, Template talk:Coord#Globe icon not showing, Template talk:Coord/Archive 10#Make icon display optional, and meta:Talk:WikiMiniAtlas). -- Zyxw (talk) 19:20, 2 December 2012 (UTC)

I'm still not sure that "largest handling capacity" is workable. There is too much of a difference between the largest possible and the normal largest. The Antonov An-225 Mriya has landed at Paris–Le Bourget Airport which means that it could be listed at any airport with an elevation of 220 ft (67 m) or less and a runway 3,000 metres (9,800 ft) or longer. Of course that would also depend on the type of runway surface and its load capacity. It would be better in the body where it could be explained properly or make the line something like common aircraft. In that case Iqaluit Airport which has seen the Airbus A380 would actually have Boeing 737. CambridgeBayWeather (talk) 12:06, 3 December 2012 (UTC)

OK I have now made the changes in the sandbox. I can usually spot spelling mistakes and punctuation errors at 1000 feet, but this typographical language, those curly brackets, just make my eyes go funny!

Basically I have set it up so no change = no change, i.e. box width hasn't changed but obviously length will. If a runway width is added, it will appear after the length, as × width. Depending on the length, it might all fit on the same line, or wrap to the next. HTML seemed to have a mind of its own regarding column widths, so ft and m may not always be balanced, I couldn't figure out why not, but that's always happened. See for instance Wright-Patterson AFB.

I have applied this change to helipads as well as runways.

Specify runway widths as R[n]-width-[d] where n = 1 to 8 and d = m or f Specify helipad widths as H[n]-width-[d] where n = 1 to 12 and d = m or f

As regards the info such as airport manager, handling capability, etc., rather than introduce specific items, I have introduced 10 other fields similar to current for stats, specified as other[n]-header and other[n]-data. n=1 to 10; if you specify other[n>1] without other[1] then you won't see it. Data is passed through unchanged. (i.e. text)

There is a subpage /dim currently sitting below sandbox. That needs to be copied to be a subpage of the main infobox. This also entails editing the changed code so it points to infobox airport/dim and not infobox airport/sandbox/dim

I removed wikilinking of coordinates, runway and helipad.

Sorry, I don't know about <includeonly> etc. I presume it's for documentation purposes. Needs to be addressed. John of Cromer in China (talk) mytime= Sun 20:11, wikitime= 12:11, 9 December 2012 (UTC)

I made the following updates to the sandbox template:

• fixed placement of <includeonly> – its purpose is to display header text and parameter names when viewing the template page, which is useful for documentation and to allow previewing of changes while editing the template
• replaced {{!}} with | where former not required since not inside #if
• removed the empty row above airport name and moved widths back to runway/helipad headers – the empty row created extra white space above the airport name when viewed in the current version of Mozilla Firefox
• updated runway and helipad "Length" headers to only display "× Width" when a width is defined – for header including "× Width" see Template:Infobox airport/testcases#Test case 1: Public airport
• updated runway and helipad "m" and "ft" headers to replace {{pad|2.7em}} with "text-align:right" – it has same effect & matches alignment of data in Template:Infobox airport/sandbox/dim

Other issues that should be fixed before going live (not changed pending additional discussion):

• The live template centers data in all four runway/helipad columns (number, length/width in m & ft, surface) but the sandbox displays left-aligned for number/surface and right-aligned for length/width. I would suggest keeping this data centered.
• Wrapping of runway/helipad data when the template displays widths: as shown in Template:Infobox airport/testcases#Test case 1: Public airport it can wrap differently on different lines within the same infobox, which looks somewhat ugly. Possible solutions include preventing it from wrapping with style="white-space:nowrap" (which will slightly increase the infobox width, but only when needed) or forcing it to wrap by including <br/> before "× (width)".

The difference in the output of the live template vs. the sandbox version can be seen at Template:Infobox airport/testcases. The differences in the actual template code can be seen here. -- Zyxw (talk) 10:49, 11 December 2012 (UTC)

The reason for the {{pad|2.7em}} was to try to get the width columns approximately equal. I really don't understand why they vary, and sometimes they're unbalanced too - look at Wright-Paterson AFB, look at Helsinki. I couldn't see any reason for the imbalance, and it's always the first one narrower than second - particularly silly if feet come first, as that's a wider field than m. As regards alignment, the length needs to be left-aligned and the width right-aligned. John of Cromer in China (talk) mytime= Tue 19:39, wikitime= 11:39, 11 December 2012 (UTC)

Also, I made the headings so that the name of the unit (ft or m) lined up with the unit position of the value. Not easy if the value wanders about because centred (which incidentally looks pretty ghastly when you have a case such as DFW where the digit length of the runways differs, so they're not aligned at all). John of Cromer in China (talk) mytime= Fri 20:51, wikitime= 12:51, 14 December 2012 (UTC)

Edit request: Update to fix centering of location maps

{{editprotected}}

{{Infobox airport}}	{{Infobox airport/sandbox2}}
Example 1 IATA: none ICAO: none Summary Coordinates 56°04′14″N 23°33′29″E Map Example 1	Example 2 IATA: none – ICAO: none Summary Coordinates 56°04′14″N 23°33′29″E Map

The map created by {{Location map}} is no longer centered when displayed in this infobox. I reviewed both templates but could not find the exact cause. In any case, it can easily be resolved by changing line # 131 from |float = none to |float = center. To the right, Example 1 uses the current template and Example 2 uses an updated version implemented in {{Infobox airport/sandbox2}} (diff). I created the new sandbox so as not to disrupt ongoing edits in the usual sandbox. -- Zyxw (talk) 22:25, 2 December 2012 (UTC)

Done — Mr. Stradivarius ^{(have a chat)} 10:40, 3 December 2012 (UTC)

Edit request on 5 March 2013: Frameless as default image size

Please change the template to use frameless as default image size instead of hard coding 220px. This won't force images smaller than 220px to be blown up, and also allows users to set their preferred image size.

See sandbox edit: http://en.wiki.x.io/wiki/Template:Infobox_airport/sandbox?diff=542244869&oldid=542241077

Tholme (talk) 18:54, 5 March 2013 (UTC)

NB previous request still waiting to go live (since November)) John of Cromer in Philippines (talk) mytime= Wed 06:10, wikitime= 22:10, 5 March 2013 (UTC)

 Done Ruslik_Zero 18:59, 6 March 2013 (UTC)

Edit request on 6 May 2013: new parameter

Add a parameter to the infobox for the airport's opening date. There is a "built" parameter that is similar but only for military airports. Similarly, we would need a parameter for the closing date for the airport or date when passenger services ceased in cases where the airport has been converted for some other use. Thank you. BigJolly9 (talk) 19:09, 5 May 2013 (UTC)

User:BigJolly9, would you mind updating the code at Template:Infobox airport/sandbox and then reactivating this request? — Martin (MSGJ · talk) 12:01, 10 May 2013 (UTC)

Since Infobox Military Structure is currently being transformed into Template:Infobox military installation/sandbox (with the addition of runway information) and a lot of military airports will be changed to this "new" infobox. Why cannot the wording which says "<!-- military airports -->" next to built and used be removed? Gavbadger (talk) 23:29, 10 May 2013 (UTC)

I've added 3 parameters - opened, closed, and passenger_services_ceased. We could also use Gavbadger's idea. Instead of the "opened" parameter, extend "built" to cover all airports, not just military. That would save us one parameter. BigJolly9 (talk) 17:32, 13 May 2013 (UTC)

I don't see any changes to Template:Infobox airport/sandbox yet? — Martin (MSGJ · talk) 19:34, 13 May 2013 (UTC)

Not done for now: Please reactivate the {{edit protected}} template when you have put the relevant code in the template sandbox. Best — Mr. Stradivarius ^{♪ talk ♪} 11:37, 14 May 2013 (UTC)

Done CambridgeBayWeather (talk) 09:50, 21 May 2013 (UTC)

New edit request

In light of many airports in SE Asia not having relevant safety equipment, among other locations, and the recent crash of airliner Lion Air flight 904, I would like to include a section for ILS, LLWAS 1,2&3, etc. I think its important often overlooked info. Doseiai2 (talk) 22:25, 10 May 2013 (UTC)

Dates not showing

It appears that |opened= and |closed= are not showing. See Walsall Aerodrome, and the template's documentation for example. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:57, 19 May 2013 (UTC)

That's because it was added to the documentation but not to the actual template. It should be fixed now. CambridgeBayWeather (talk) 09:46, 21 May 2013 (UTC)

Airport Types should have more Specific Definitions

The Template:Airports_in_Russia seems to present the right idea when it comes to designating Airport Types.

• Major International
• Minor International
• Domestic
• Defunct

These additional types will help to add more clarification instead of just using Public, Private, Military, and Military/Public by themselves. --Arima (talk) 07:01, 18 August 2013 (UTC)

For example, Osaka International Airport changed from being an International Airport to a Domestic Airport. Therefore, simply calling it a Public Airport is ambiguous. --Arima (talk) 05:08, 31 August 2013 (UTC)

What reliable source(s) are we going to refer to when determining the appropriate category? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:56, 31 August 2013 (UTC)

Airport codes and historic airfields

Displaying "IATA: none – ICAO: none" on articles about airfields which pre-date such schemes, such as Trafford Park Aerodrome (Manchester), which closed in 1918, is redundant. We need to make the display optional. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:14, 31 August 2013 (UTC)

Bantayan Airport

Bantayan Airport is currently using some hacks to wedge in additional fields (airport manager, fuel availability, Largest handling capability, and runway width). should any of these be added here? should these fields be in the infobox at all? Frietjes (talk) 16:41, 6 September 2013 (UTC)

Frietjes I suggest we remove the extra fields from the specific infobox. -- Magioladitis (talk) 18:33, 6 September 2013 (UTC)

done, but someone may try to wedge it back in. Frietjes (talk) 19:17, 6 September 2013 (UTC)

Timezones

It would be useful to be able to tell what timezone an airport is in just by looking at the infobox. —Gordon P. Hemsley→✉ 01:43, 29 August 2013 (UTC)

I think I'd asked about this before. It would be a good idea. CambridgeBayWeather (talk) 14:50, 29 August 2013 (UTC)

Good thinking I support the idea. We should copy the parameters from {{Infobox settlement}}. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:16, 29 August 2013 (UTC)

Done. CambridgeBayWeather (talk) 05:47, 21 November 2013 (UTC)

Past tense for closed airports

When a closing date is given, this template should use the past tense. Please replace:

! colspan=2 {{!}} Serves

with:

! colspan=2 {{!}} Serve{{#if: {{{closed|}}} | d | s }}

Thanks!

 – Minh Nguyễn (talk, contribs) 07:20, 26 March 2014 (UTC)

Still Open Airport
IATA: none ICAO: none
Summary
Serves	London

Now Closed Airport
IATA: none ICAO: none
Summary
Serves	London
Closed	January 2, 1985 (1985-01-02)

@Mxn: I think this change will usually be good, but I see that the "closed" parameter says it can be used to describe a temporary closure. In that case "Serves" may still be appropriate - "Airport X serves London, but is temporarily closed for repairs". What do you think? -- John of Reading (talk) 15:12, 26 March 2014 (UTC)

Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. If it is just closed for repairs, then the airport is still open to the repairers and therefor is not closed. I would think in such cases the "closed" parameter would not be set although a note may be added to the article saying it is currently "closed to the public due to repairs" or some such. Either way, this should be thrown in the sandbox with a full set of testcases to see how it would play out in various instances. — {{U|Technical 13}} ^{(t • e • c)} 15:24, 26 March 2014 (UTC)

Ah, I didn't notice that it should be used for temporary repairs. Thanks, I'll consider implementing a more explicit way to indicate permanent closure on the sandbox. – Minh Nguyễn (talk, contribs) 19:40, 26 March 2014 (UTC)

Template-protected edit request on 8 November 2014

Please copy from the current sandbox[1]. I adjusted the {{location map}} template call to invoke the {{{default_width}}} parameter instead of absolute {{{width}}}. This allows automatic scaling of the map for narrow countries. Paul_012 (talk) 04:44, 8 November 2014 (UTC)

done. Frietjes (talk) 13:35, 8 November 2014 (UTC)

Template-protected edit request on 30 November 2014

Hey @Frietjes: and all others:
Template:Infobox airport/sandbox seems to be quite ready for prime time, see Template:Infobox airport/testcases. I fixed the remaining problems regarding the Owner/Operator variables and the column widths. What remains are some minor style differences. The more compact Runways and Helipads tables are even an improvement. The all-white captions just as well. All further optimizations should be done in incrementally followups IMHO. So I'd propose to launch the new template now.
Regards, --PanchoS (talk) 22:28, 30 November 2014 (UTC)

• Hey, what's up? Some feedback would be really nice... --PanchoS (talk) 14:20, 5 December 2014 (UTC)
  • now updated. I left the old version temporarily in the sandbox for comparison if there are problems. Frietjes (talk) 21:24, 9 December 2014 (UTC)

Heliport code fix

In the code within the Heliport section

| n8 = {{{h8-number|}}} | l8-m = {{{h8-length-m|}}} | l8-f = {{{h8-length-f|}}} | s8 = {{{h8-surface|}}}
| n9 = {{{h5-number|}}} | l9-m = {{{h5-length-m|}}} | l9-f = {{{h5-length-f|}}} | s9 = {{{h5-surface|}}}
| n10 = {{{h10-number|}}} | l10-m = {{{h10-length-m|}}} | l10-f = {{{h10-length-f|}}} | s10 = {{{h10-surface|}}}

Can someone please change the "n9" to

| n9 = {{{h9-number|}}} | l9-m = {{{h9-length-m|}}} | l9-f = {{{h9-length-f|}}} | s9 = {{{h9-surface|}}}

Thanks. Gavbadger (talk) 22:47, 10 January 2015 (UTC)

 Done. SiBr₄ (talk) 22:57, 10 January 2015 (UTC)

Template-protected edit request on 8 December 2015

Replace #69c with #669ACD to meet the AAA color restrictions. [2][3] Grapesoda22 (talk) 00:42, 8 December 2015 (UTC) Grapesoda22 (talk) 00:42, 8 December 2015 (UTC)

changed. Frietjes (talk) 15:37, 8 December 2015 (UTC)

Runway Directions link no longer valid

The link to Direction is no longer valid. Not sure if a section should be re-added on the Runway page or the link here should be changed, just calling attention to it Phil (talk) 06:35, 28 March 2016 (UTC)

• It looks like the section previously called Orientation and direction is now called Naming, so possibly it is appropriate to just change the existing link on this template to that? Phil (talk) 06:54, 28 March 2016 (UTC)

Accessibility

I updated the sandbox with a proposal for keeping the background color explicit even when it should cascade from elsewhere. The change should not be visible to most users (see testcases), but ensures the content visible for everyone. —LLarson (said & done) 19:22, 24 April 2016 (UTC)

I'd rather we used a paler header background and didn't overwrite link colours. Alternatively, we could unlink 'helipads' and 'runways'; they're edging on WP:OLINK. Izkala (talk) 01:04, 27 April 2016 (UTC)

Done Re Izkala: Implemented just as you posted; those seem to be concerns that at issue prior to this change being made. Izno (talk) 01:08, 27 April 2016 (UTC)

Fair enough. This works for now anyway. Izkala (talk) 01:10, 27 April 2016 (UTC)

Template-protected edit request on 16 June 2016

Please update to my last sandbox version (diff) to track the numerous cases of location maps being embedded within the |ICAO= parameter rather than the proper |pushpin_*= parameters.

PanchoS (talk) 00:27, 16 June 2016 (UTC)

@PanchoS: Could you point me to a page where this is being done? I'm wondering if there is a better way of finding this error than checking for closing </center> tags, but it's difficult to say without seeing an example. Best — Mr. Stradivarius ^{♪ talk ♪} 00:43, 16 June 2016 (UTC)

@Mr. Stradivarius: Sure, just take a look at Bandundu Airport, Bangoka International Airport, or Basankusu Airport. I guess searching for more complex substrings in the middle of the parameter wouldn't be better, so I figured the closing tag might be the best way. But see yourself. Cheers, PanchoS (talk) 00:53, 16 June 2016 (UTC)

I was in the middle of syncing this in when I saw this response - it didn't look like it would cause any harm - but if there is a better way then I'm all for it; I undid my sync in. — xaosflux ^Talk 03:18, 16 June 2016 (UTC)

@Xaosflux and PanchoS: Ok, I see the problem. If the goal here is to just check for that specific error and then remove the tracking-category code once all the articles are cleaned up, then I think this solution is fine. If this is going to be a permanent thing, however, I would check that the value of the |ICAO= parameter is actually a valid ICAO code, and add a tracking category for all other input. Something like {{#if: {{#invoke:String|match|s={{{ICAO|}}}|pattern=^%w%w%w%w%w?%w?$|plain=false|nomatch=}} || [[Category:Some tracking category]] }} should do the trick - that would add the tracking category unless |ICAO= contains only 4-6 letters or numbers. (Or to be exact, 4-6 characters in the Unicode categories of "letter" or "decimal number".) This check could be made more rigorous as well, if you don't want to accept codes starting with a number, etc. — Mr. Stradivarius ^{♪ talk ♪} 10:40, 16 June 2016 (UTC)

@Mr. Stradivarius: Where are there codes with more than 4 alphanumerics? The current constraint on Wikidata for airport code is 4 alphanumerics, and I want to verify your claim. --Izno (talk) 11:34, 16 June 2016 (UTC)

I just verified with our own article at International Civil Aviation Organization airport code; these are 4 alphanumerics, not any larger than that. Wikidata actually has a more rigorous constraint of ([A-Z]{2}|[CKY][A-Z0-9])[A-Z0-9]{2}. Speaking of which, why isn't this field at least using Wikidata? --Izno (talk) 11:39, 16 June 2016 (UTC)

@Izno: I was going by International Civil Aviation Organization airport code#Pseudo ICAO-codes, which says that France assigns codes up to six characters. But the six-character codes aren't official, so maybe we should ignore them. I suppose it depends on what is used in actual articles. — Mr. Stradivarius ^{♪ talk ♪} 11:45, 16 June 2016 (UTC)

Right, unofficial codes. --Izno (talk) 11:47, 16 June 2016 (UTC)

 Done Synced sandbox to template, feel free to add another edit request if needed. — xaosflux ^Talk 11:18, 16 June 2016 (UTC)

@Xaosflux: Thanks for syncing! @Mr. Stradivarius: This is of course only to fix the 170 articles (possibly more, let's see once all pages are recached), and immediately remove the tracking code. Your proposal may still be a good permanent solution to follow up with. Cheers, PanchoS (talk) 11:27, 16 June 2016 (UTC)

Wow, the number is steadily growing. Might be a good use case for a bot. Do you have an idea which bot could do that task? --PanchoS (talk) 11:30, 16 June 2016 (UTC)

I think a BRFA is warranted due to the thousands of pages in the category. You can try WP:BOTREQ and let someone else look into it. — Andy W. (talk · ctb) 17:54, 16 June 2016 (UTC)

Edit request for status parameter

I think that it would be useful to have a status parameter to indicate whether the airport is open/operational or closed/defunct. --MorbidEntree - _{(Talk to me! (っ◕‿◕)っ♥)}(please reply using {{ping}}) 11:40, 17 August 2016 (UTC)

Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. Izno (talk) 12:07, 17 August 2016 (UTC)

MorbidEntree. That's not required. If the closing date is known then "closed =" can be used as in Edmonton City Centre (Blatchford Field) Airport box. If not then just use the <s> and </s> as in Acme Airport. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 05:24, 18 August 2016 (UTC)

@CambridgeBayWeather: But what about the articles where the closed date is unknown? Also, using <s></s> doesn't seem to be anywhere in the documentation. --MorbidEntree - _{(Talk to me! (っ◕‿◕)っ♥)}(please reply using {{ping}}) 14:05, 18 August 2016 (UTC)

MorbidEntree. In most cases you should be able to get the year it closed by when the <s></s> was added. It's not in the documentation because it is one of those things that some people do and others don't. Another way is to change the "type = " to say closed. Like at Manston Airport. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 15:15, 18 August 2016 (UTC)

Template-protected edit request on 14 November 2016

Can someone add more fields to the statistics section? Wilmington International Airport has 6 statistics fields and this template can only currently display 4 of them. Always possible that ILM just has too many statistics but I didn't add them...

EoRdE6^{(Come Talk to Me!)} 18:11, 14 November 2016 (UTC)

@EoRdE6: You're referring to |stat5-header=, |stat5-data=, |stat6-header=, |stat6-data=? — Andy W. (talk) 21:22, 14 November 2016 (UTC)

@Andy M. Wang: Yes that's what I'm referring to. Edit and preview Wilmington International Airport, those error messages is what I'm trying to get fixed. Thanks! EoRdE6^{(Come Talk to Me!)} 21:49, 14 November 2016 (UTC)

I've doubled the number of available stat params... not anticipating needing more — Andy W. (talk) 21:50, 14 November 2016 (UTC)

Clean up?

I was going to clean up the code for the template a little by eliminating the display of params on the template page. So, for example, I would replace:

• | n1 = {{{r1-number<includeonly>|</includeonly>}}} → | n1 = {{{r1-number|}}}

Personally I think the code is just cleaner that way and it wouldn't affect the end result at all. Anyone have any big concerns with that? Happy to do it in the sandbox first. --Zackmann08 (^{Talk to me}/_{What I been doing}) 00:03, 25 November 2016 (UTC)

List markup

I changed the top pseudo-list to use list markup. let me know if there is a problem. thank you. Frietjes (talk) 23:15, 23 December 2016 (UTC)

Wikidata 'plan view' item.

The image_map parameter can now use d:Property:P3311 to point to a runway or plan diagram if one is available. See here for ORD. Please add this to the infobox template appropriately. grendel|khan 01:11, 21 January 2017 (UTC)

That diagram looks like it would be completely unreadable in an infobox. It would look roughly like this. – Jonesey95 (talk) 20:26, 26 January 2017 (UTC)

Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. Based on Jonesey95's concerns, I'm declining this until a consensus can be reached. Primefac (talk) 03:06, 27 January 2017 (UTC)

Color of the text

Please change the color of the text from white to black on Template:Infobox airport, becasue the current color scheme violates WP:COLOR. [4]Grapesoda22 03:58, 16 February 2017 (UTC)

Unknown parameters

I have just run through Category:Pages using infobox airport with unknown parameters (4) with AWB. I saw that now all articles in there still have this set of deprecated parameters:

| latd  =  35 | latm  = 09 | lats  = 13 | latNS  = N
| longd = 087 | longm = 03 | longs = 25 | longEW = W
| coordinates_region     = US-TN_scale:10000

while the current accepted form is:

 | coordinates  = {{coord|35|09|13|N|087|03|25|W|region:US-TN_type:airport_scale:10000}}

Notes:

1. I did not remove them, because that would be a trivial edit (no article effect).
2. By having them in there, non-trivial parameter errors are hidden and hard to find (if at all).
3. We could 'legalise' them in the parameter check (while keeping them deprecated; piggybag edits could move them out).

-DePiep (talk) 00:07, 9 March 2017 (UTC)

We could also do a separate parameter check for these parameters and categorize them under a non-alphanumeric symbol. This is commonly done for tracking, though I don't have an example at my fingertips at the moment. If nobody here knows how to do it, I'll dig up an example. – Jonesey95 (talk) 03:49, 9 March 2017 (UTC)

Even better: in a dedicated subcategory? Would be good. Maybe module:Check for unknown parameters/doc can help. As it happens, today they are sorted under "L" because of "latd", but that may become polluted. To be clear, I have no aim to clean this further. -DePiep (talk) 08:06, 9 March 2017 (UTC)

•  Done by User:Frietjes. See Category:Pages using infobox airport with historic coordinate parameters (0). -DePiep (talk) 01:11, 11 March 2017 (UTC)

Direction - edit request

When used in a page eg London Stansted Airport under the Runways section there is a header labelled Direction. This is currently a link to Runway#Orientation_and_dimensions which is a section that no longer exists, so link should be changed to to Runway#Naming. Hope someone can kindly make the edit, thanks! John a s (talk) 09:26, 14 October 2017 (UTC)

John a s. Good idea. Changed it. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 21:03, 15 October 2017 (UTC)

Thanks!John a s (talk) 12:55, 16 October 2017 (UTC)

Template-protected edit request on 13 February 2018

I would like add to the template a field for official Twitter handle of the airport, titled "twitter", similar to official websites in the "website" field. This would help users quickly identify an airport's official social media presence in which airports officially reply to travelers' requests and post updates, similar to an official website page. Please let me know your thoughts. Thanks for your consideration. Subbupedia95 (talk) 04:21, 13 February 2018 (UTC)

 Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. — JJMC89 (T·C) 05:48, 13 February 2018 (UTC)

I'm not sure if I've understood correctly - but isn't this the place to discuss and to establish consensus? If not, where can I do so? Thanks for the help.Subbupedia95 (talk) 18:03, 13 February 2018 (UTC)

@Subbupedia95: When you get that answer, typically the best thing you can do is solicit feedback from any number of places. Given that this is an infobox, about airports, and you are trying to include a new kind of external link, those places might reasonably be WP:ELN/WT:EL, WT:TRANSPORT, and WT:INFOBOX in this case: leave a neutral request to comment at those places regarding the discussion here, and you may see some consensus-building. --Izno (talk) 19:48, 13 February 2018 (UTC)

Mapframe maps?

{{Infobox building}} and {{Infobox shopping mall}} have both recently been updated to automatically show dynamic mapframe maps by default. I am proposing to similarly show such maps by default for this template, with the same optional parameters to adjust the size, frame center point, initial zoom level, and marker icon; and to similarly allow the mapframe map to be turned off using |mapframe=no. See Template:Infobox building#Mapframe maps and Template talk:Infobox building#Change to the map parameter so Kartographer works for further information. (FYI: I'm making similar proposal for other buildings infobox templates) - Evad37 [talk] 15:35, 31 August 2018 (UTC)

Support, I agree about this update. angys (Talk Talk) 11:47, 1 September 2018 (UTC)

How to suppress IATA/ICAO labels

How can I suppress the IATA/ICAO labels completely, on articles for old airfields, like Clairmarais aerodrome, which closed before those identifiers came into use? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:28, 6 November 2018 (UTC)

Need to replace "Military airport" wording with "Military aerodrome"

There is no military "airports" by the "airport" definition in aviation terminology and particularly here Airport (for the military case only "aerodromes", "air bases", "airfields", etc.). Best solution is to introduce separate {{Infobox aerodrome}}. At least, within this template all wording "Military airport" can be easily replaced with "Military aerodrome" (I'm not authorised to do this) Apetrov09703 (talk) 05:36, 15 February 2019 (UTC)

No, we do not need to fork an entire infobox for this. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:15, 15 February 2019 (UTC)

I'm sympathetic to the concern raised, however. Don't stress over the suggested solution to the problem. --Izno (talk) 16:02, 15 February 2019 (UTC)

• Thanks for comments, folks. After additional consideration I feel there may be no need at all for that part of the template where "military airport" wording exists because other template - "Infobox military installation" - has two dedicated optional sections: "airfield information" and "test site information". For example you may wish to have a look at this stub Salka Aerodrome. Apetrov09703 (talk) 18:00, 16 February 2019 (UTC)

ASL elevation display error

This template has |elevation-f= and |elevation-m= for elevation in feet and meters. |metric-elev= forces the metric value to be displayed first. If only one elevation is provided, the template does an automatic conversion to get the other. If converted value is displayed last, there is no problem. However, if the converted value is displayed first, you just see the unit (m or ft) without the number (e.g. Elevation AMSL m / 411 ft). Example here. Frietjes? MB 18:01, 21 February 2020 (UTC)

User:MB, should be fixed now. Frietjes (talk) 18:06, 21 February 2020 (UTC)

Public transit/parking

Can someone add parameters for transit and parking here? This is pretty important connection information, available in many infoboxes like {{Infobox station}}, {{Infobox shopping mall}}, {{Infobox museum}}, {{Infobox park}}, and more. ɱ (talk) 17:53, 23 March 2020 (UTC)

Support. Clarify: add |publictransit=, which would display "Public transit access". Vaselineeeeeeee^★★★ 19:12, 23 March 2020 (UTC)

 Done for this template. Please adjust the documentation. – Jonesey95 (talk) 14:48, 14 April 2020 (UTC)

Frequency field in Airport Infobox

I highly recommend the addition of a frequency field in the airport infobox as it is really helpful for people who like aviation and have a tuner for airports.YashPratap1912(CONT.) 17:18, 31 July 2020 (UTC)

Issue with runway conversions

If only the imperial/US customary values are given for runway lengths, but the metric-rwy option is enabled, then conversions do not happen and the metric column is blank. This needs to be fixed. This issue seems like it's related to the elevation AMSL issue above, but with runway lengths instead. Getsnoopy (talk) 00:58, 18 November 2020 (UTC)