Template talk:Airport codes

message: List "A"
*Long Beach Municipal Airport 
*L.A./Ontario International Airport , owned by the city of Los Angeles. 	
*Bob Hope Airport , formerly known as Burbank Airport 
*Long Beach Municipal Airport  	
List "B"
* Long Beach Municipal Airport 
* L.A./Ontario International Airport, owned by the city of Los Angeles. 
* Bob Hope Airport, formerly known as Burbank Airport 
* Long Beach Municipal Airport
In List "A" there's a forced line break that adds lots of extra space and makes it harder to read. When I placed the template at the beginning of the line in List "B" the bullets disappeared.  ·:· Will Beback  ·:· 08:03, 16 July 2007 (UTC)
thread_title:  Odd formatting 

message: Please delete :de:Vorlage:Flughafencode since it does not exist anymore (2007). --Scriberius (talk) 15:38, 19 October 2009 (UTC)
thread_title:  update iw (Edit protected page)

message: I wanted to add Airport API from PilotOutlook to us-airport template. You can access data for any US based airport by providing IATA or ICAO code to this API - 
http://www.pilotoutlook.com/xml/AirportLookup?IATA_CODE=KBFI&AccessKeyId=28b878cacfb84cff92f7c56b22eceddab919534d
. Introduction is at http://www.pilotoutlook.com/api/introduction. Please let me know if you can add this.
Rajatgarg79 (talk) 01:30, 11 April 2008 (UTC)
thread_title:  Adding Airport API 

message: I was thinking that it might be convenient to categorize articles that are missing IATA codes or ICAO codes. I propose something on the lines of the following changes:
()
Does anyone have any comments negative or positive? I don't know how many airports would be in the category without IATA codes, but I would think most airport articles would / should have ICAO codes.Categorization would help locate articles that needed ICAO codes added to them. Just a thought... --Dual Freq (talk) 23:47, 23 August 2008 (UTC)
replies: text: I guess the question is do all airports that are notable have either code?  If not all airport have these codes, then putting then in a maintenance category would be useless. Vegaswikian (talk) 01:53, 24 August 2008 (UTC)
replies: text: That's a valid point, not all airports would have IATA codes, but most should have an ICAO code right? --Dual Freq (talk) 02:12, 24 August 2008 (UTC)
thread_title:  Categorization of pages missing IATA or ICAO 

message: I would like to change the output of this template, to emit an hCard microformat, such that:
Emmonak Airport (IATA: EMK, ICAO: PAEM, FAA LID: ENM) is ...
is rendered as:

<span class="vcard"><span class="adr"><span class="fn org extended-address">Emmonak Airport</span></span> (IATA: <span class="nickname">EMK</span>, ICAO: <span class="nickname">PAEM</span>, FAA LID: <span class="nickname">ENM</span>)</span> is ...

Can anyone advise how this might be implemented, please? Thank you. Andy Mabbett | Talk to Andy Mabbett 23:55, 23 August 2008 (UTC)
replies: text: This template doesn't appear to deal with the name of the airport itself, but the inner spans for the different codes should be quite simple to implement; just add the 'span class=nickname' tags to this template wrapped around the template's parameters. The spans should be harmless in areas where this template is used outside of vcards so there's no need to get fancy trying to distinguish such situations. Bryan Derksen (talk) 18:05, 7 September 2008 (UTC)
replies: text: Thanks; I don't know how I misunderstood that. As the template is curently used, there seems to be no point adding microformat classes; airport codes within infoboxes, which form an hCard microformat, are already amrked up as class="nickname". I do think thugh ehret there woudl be some snese in creating a simailr temaplte, with a name field, to output the above mark-up, for pages which name airfields, with codes, but which do not have an infobaox about that airfield. Emboldening of the airfeld name could be switchable. Andy Mabbett (User:Pigsonthewing); Talk to Andy Mabbett; Andy Mabbett's contributions 20:31, 7 September 2008 (UTC)
thread_title:  hCard microformat 

message: The use of boldface in this template doesn't quite comply with MOS:BOLD, and it'd probably be appropriate to print the airport codes in a normal font weight. – Acdx (talk) 13:08, 14 August 2012 (UTC)
replies: text: Posted a link to here at Wikipedia talk:WikiProject Airports might bring in a few more comments. For me I'm not bothered either way. CambridgeBayWeather (talk) 18:11, 14 August 2012 (UTC)
replies: text: The template documentation gives examples which look like the first line of an article - where I think that it's OK to have a bold code because it's an alternate descriptor for the subject of the article (WP:MOSBOLDSYN gives an example of Sodium hydroxide, where NaOH is mentioned at the top of the article, and boldface). I think that usage is reasonable though we shouldn't make it mandatory. However, in practice it seems that this template is transcluded all over articles, in the middle of prose or even in refs - in places like that I think boldface is ugly. So, overall, I think it's best not to have boldface codes in this template. bobrayner (talk) 18:37, 14 August 2012 (UTC)

text: When this was first created, it was intended to standardize the display of these codes in the first sentence of articles.  If this is being used in other places, may I suggest that we add bold=off as an optional parameter when this is used in other places if we need to stop the bolding?  That way, the original intent will be retained and other uses would be able to conform to the MoS.  If we do this, would it make sense to also change the LID to keywords, say lid code= and lid=name? Vegaswikian (talk) 19:35, 14 August 2012 (UTC)
replies: text: That looks reasonable to me. bobrayner (talk) 19:38, 14 August 2012 (UTC)
replies: text: That sounds great to me, I suppose the documentation should then be changed to indicate that this flag be always set when the template is used outside the lead sentence? – Acdx (talk) 01:32, 15 August 2012 (UTC)
replies: text: I dont think it should be used in the lead as the information is in the infobox, this template was created very earlier on before the i/box was developed so we should really stop using it. MilborneOne (talk) 21:22, 18 August 2012 (UTC)
thread_title:  Airport codes in boldface 

message: Looking at the above section I don't think a consensus was reached. So I am looking to get more comments as to the use of bolding in the template. So should bold be the default or not? CambridgeBayWeather (talk) 20:57, 16 February 2014 (UTC)
thread_title:  RfC: Should the codes be in bold by default? 

message: Although this template's primary use is in airport articles it is used in others. Examples of this include hospital infoboxes, Royal Victoria Regional Health Centre, and the body of certain articles, Whistler, British Columbia#Transportation. According to Wikipedia:Manual of Style/Text formatting#Boldface the use of bolding is discouraged except "to highlight the article title, and often synonyms". So in the case of hospital infoboxes and the body of articles there should be no bolding. The use in airport articles is usually after the name of the article as part of the first sentence. In this case it could be bold as a possible synonym.
If bold is to be the default then, as per Wikipedia:Help desk#Template:Airport codes,  and all the others would be replaced by . This would leave all current uses of the template as is and the bolding could be removed in other articles by the use of "b=n". The other option is to remove the bold from the template and use  when bolding was required. The first option would leave all articles as is but would increase the size of the template. The second option would not increase the template size but would change every single article. CambridgeBayWeather (talk) 20:57, 16 February 2014 (UTC)
thread_title: Threaded discussion

message: Requested update action: Change entire template's content to this (please click edit source when copy/viewing the code in order to achieve proper formatting):

Reason for the request for change is that Changsha airport have a different CAAC code (HHA) compared to IATA (CSX) with source: http://cssinglewindow.com/WebSite/PortIntroduction/airPort.html C933103 (talk) 00:46, 4 January 2018 (UTC)
replies: text: There were a couple of errors. I think the lines}}{{#if: 
 | CAAC LID: . Without that the China code will not appear. Test it using User:CambridgeBayWeather/sandbox where I pasted the code. Then let me know. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 16:50, 6 January 2018 (UTC)
replies: text:  Yeah forgot about editing that. Seems like itis now working properly. C933103 (talk) 02:40, 7 January 2018 (UTC)

text: Done  please update the documentation now — Martin (MSGJ · talk) 09:18, 9 January 2018 (UTC)
replies: text: Edited the documentation, but not the example page, is there any real need to list out all the examples like this? C933103 (talk) 10:03, 9 January 2018 (UTC)
thread_title:  Update request 

message: Two of the piped links are in fact redirects, unnecessarily. Please correct them to go directly to the target.
*IATA → IATA
*ICAO → ICAO Colonies Chris (talk) 10:49, 30 March 2018 (UTC)
replies: text: Done Galobtter (pingó mió) 13:32, 30 March 2018 (UTC)
thread_title:  Template-protected edit request on 30 March 2018 

message: Are they really existent ? I couldn't find any of them on airports in China. Besides, the template could host FAA(Argentina) code@P6120, Transport Canada code@P5699, Russian code@P5851, DGAC Mexico airport code @P5746, Greece airport code@P7667 and perhaps other nation airport codes...--Bouzinac (talk) 05:51, 15 April 2020 (UTC)
thread_title: CAAC codes (parameter 6)

message: At Ronald Reagan Washington National Airport, this template currently displays . It's redundant to have "DCA" listed and bolded twice; a more elegant presentation would be . Would it be possible to improve this template such that, when certain codes are the same, it automatically combines them in the display like this?  talk 19:06, 15 June 2023 (UTC)
thread_title:  Combining codes that are the same