Template talk:Infobox airport/Archive 5

message: We should add a  and probably . Any comments? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 28 January 2012 (UTC)
replies: text: I agree. Currently only military airports are afforded this using the  and  fields. __meco (talk) 13:30, 25 February 2012 (UTC)
thread_title:  Opened/ closed dates 

message: Why not include a  and a  parameter into the template? Maybe merge it with the  field? Pizza1016 (talk) 10:44, 2 February 2012 (UTC)
replies: text: If you do that, there should also be a  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)
replies: text: You don't need three just two. If it is thought to be a good idea then  and  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)
thread_title:  Distance to city 

message: 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)
replies: text: Not done:  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)
replies: text: It's at Template:Infobox airport/doc. CambridgeBayWeather (talk) 23:15, 13 May 2012 (UTC)
thread_title:  Edit request on 13 May 2012: different than 

message: 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)
replies: text: This is because  (like ,  and ) is pushed through the  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 ; no variation is provided for. --Redrose64 (talk) 20:51, 20 May 2012 (UTC)
replies: text: 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)
replies: text: Well as a workaround there is this and this. CambridgeBayWeather (talk) 00:11, 21 May 2012 (UTC)
thread_title:  Problem with presentation 

message: I propose allowing the infobox to pass a value to the relief parameter used by . This would be accomplished via the addition of a pushpin_relief parameter to .
Background: Setting pushpin_map = Chad causes  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  template will display this second image if the relief parameter is set to any value (such as "y").
Current template code:
|width = 
|AlternativeMap = 
Suggested change:
|width = 
|relief = 
|AlternativeMap = 
This has been implemented in  (diff) and an example can be seen at . 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)
replies: text: . Let me know if there are any issues with it. Best — Mr. Stradivarius (have a chat) 07:36, 15 August 2012 (UTC)
thread_title:  Edit request - enable parameter to display pushpin relief map 

message: 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)
replies: text: 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  template. Thanks — Mr. Stradivarius (have a chat) 16:49, 16 August 2012 (UTC)
thread_title:  Edit request - add focus cities 

message: 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)
thread_title:  Struck-though text 

message: I don't understand why the word Coordinates is linked in the box -  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)
thread_title:  Removal of wiki link 

message: I suggest following additional fields: 
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)
thread_title:  Additional fields? 

message: 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)
replies: text: I added  and .  Thanks! Plastikspork ―Œ(talk) 05:41, 27 November 2012 (UTC)
thread_title:  Edit request on 27 November 2012: Alt text for images 

message: The map created by  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  (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)
replies: text: Done — Mr. Stradivarius (have a chat) 10:40, 3 December 2012 (UTC)
thread_title:  Edit request: Update to fix centering of location maps 

message: 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.wikipedia.org/wiki/Template:Infobox_airport/sandbox?diff=542244869&oldid=542241077
Tholme (talk) 18:54, 5 March 2013 (UTC)
replies: text: 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)

text: Ruslik_Zero 18:59, 6 March 2013 (UTC)
thread_title:  Edit request on 5 March 2013: Frameless as default image size 

message: 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)
replies: text: 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)

text: 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 "" next to built and used be removed? Gavbadger (talk) 23:29, 10 May 2013 (UTC)

text: 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)
replies: text: I don't see any changes to Template:Infobox airport/sandbox yet? — Martin (MSGJ · talk) 19:34, 13 May 2013 (UTC)
replies: text:  Not done for now: Please reactivate the  template when you have put the relevant code in the template sandbox. Best — Mr. Stradivarius ♪ talk ♪ 11:37, 14 May 2013 (UTC)
thread_title:  Edit request on 6 May 2013: new parameter 

message: 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)
thread_title:  New edit request 

message: It appears that  and  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)
replies: text: 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)
thread_title:  Dates not showing 

message: 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)
replies: text: 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)
replies: text: 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)
thread_title:  Airport Types should have more Specific Definitions 

message: 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)
thread_title:  Airport codes and historic airfields 

message: 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)
replies: text: Frietjes I suggest we remove the extra fields from the specific infobox. -- Magioladitis (talk) 18:33, 6 September 2013 (UTC)
replies: text:  done, but someone may try to wedge it back in. Frietjes (talk) 19:17, 6 September 2013 (UTC)
thread_title:  Bantayan Airport 

message: 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)
replies: text: I think I'd asked about this before. It would be a good idea. CambridgeBayWeather (talk) 14:50, 29 August 2013 (UTC)

text: Good thinking I support the idea. We should copy the parameters from . Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:16, 29 August 2013 (UTC)
replies: text: Done. CambridgeBayWeather (talk) 05:47, 21 November 2013 (UTC)
thread_title:  Timezones 

message: When a closing date is given, this template should use the past tense. Please replace:
 ! colspan=2  Serves
with:
 ! colspan=2  Serve
Thanks!
 – Minh Nguyễn (talk, contribs) 07:20, 26 March 2014 (UTC)
replies: text: 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)

text: 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. —  (t • e • c) 15:24, 26 March 2014 (UTC)
replies: text: 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)
thread_title:  Past tense for closed airports 

message: Please copy from the current sandbox. I adjusted the  template call to invoke the  parameter instead of absolute . This allows automatic scaling of the map for narrow countries.
Paul_012 (talk) 04:44, 8 November 2014 (UTC)
replies: text: done. Frietjes (talk) 13:35, 8 November 2014 (UTC)
thread_title:  Template-protected edit request on 8 November 2014 

message: Hey  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)
thread_title:  Template-protected edit request on 30 November 2014 

message: In the code within the Heliport section
 | n8  =   | l8-m  =   | l8-f  =   | s8   = <BR>
| n9  =   | l9-m  =   | l9-f  =   | s9   = <BR>
| n10 =  | l10-m =  | l10-f =  | s10  =  
Can someone please change the "n9" to 
| n9  =   | l9-m  =   | l9-f  =   | s9   = 
Thanks. Gavbadger (talk) 22:47, 10 January 2015 (UTC)
replies: text: . SiBr4 (talk) 22:57, 10 January 2015 (UTC)
thread_title:  Heliport code fix 

message: Replace #69c with #669ACD to meet the AAA color restrictions.  Grapesoda22 (talk) 00:42, 8 December 2015 (UTC)
replies: text: changed. Frietjes (talk) 15:37, 8 December 2015 (UTC)
thread_title:  Template-protected edit request on 8 December 2015 

message: 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)
thread_title:  Runway Directions link no longer valid 

message: I  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)
replies: text: 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)

text: Done Re : 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)
replies: text:  Fair enough.  This works for now anyway.  Izkala (talk) 01:10, 27 April 2016 (UTC)
thread_title:  Accessibility 

message: Please update to my last sandbox version (diff) to track the numerous cases of location maps being embedded within the  parameter rather than the proper  parameters.
PanchoS (talk) 00:27, 16 June 2016 (UTC)
replies: text: 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  tags, but it's difficult to say without seeing an example. Best — Mr. Stradivarius ♪ talk ♪ 00:43, 16 June 2016 (UTC)
replies: text:   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)

text: 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)
replies: text:  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  parameter is actually a valid ICAO code, and add a tracking category for all other input. Something like  should do the trick - that would add the tracking category unless  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)
replies: text:  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)
replies: text:  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)
replies: text:  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)
replies: text: Right, unofficial codes. --Izno (talk) 11:47, 16 June 2016 (UTC)

text: Synced sandbox to template, feel free to add another edit request if needed. — xaosflux Talk 11:18, 16 June 2016 (UTC)
replies: text:   Thanks for syncing!  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)

text:  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)
replies: text:  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)
thread_title:  Template-protected edit request on 16 June 2016 

message: 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 ) 11:40, 17 August 2016 (UTC)
replies: text: Not done: please establish a consensus for this alteration before using the  template. Izno (talk) 12:07, 17 August 2016 (UTC)
replies: text: . 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  and  as in Acme Airport. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 05:24, 18 August 2016 (UTC)
replies: text:  But what about the articles where the closed date is unknown? Also, using  doesn't seem to be anywhere in the documentation. --MorbidEntree - (Talk to me! (っ◕‿◕)っ♥)(please reply using ) 14:05, 18 August 2016 (UTC)
replies: text: . In most cases you should be able to get the year it closed by when the  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)
thread_title:  Edit request for status parameter 

message: 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)
replies: text: You're referring to , , , ? — Andy W. (talk) 21:22, 14 November 2016 (UTC)
replies: text:  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)

text: I've doubled the number of available stat params... not anticipating needing more — Andy W. (talk) 21:50, 14 November 2016 (UTC)
thread_title:  Template-protected edit request on 14 November 2016 

message: 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   =  → | n1   = 
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)
thread_title:  Clean up? 

message: 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)
thread_title:  List markup 

message: 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)
replies: text: 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)

text: Not done: please establish a consensus for this alteration before using the  template. Based on 's concerns, I'm declining this until a consensus can be reached. Primefac (talk) 03:06, 27 January 2017 (UTC)
thread_title:  Wikidata 'plan view' item. 

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

message: I have just run through  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  = 
Notes:
# I did not remove them, because that would be a trivial edit (no article effect).
# By having them in there, non-trivial parameter errors are hidden and hard to find (if at all).
# 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)
replies: text: 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)
replies: text: 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)
thread_title:  Unknown parameters 

message: 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)
replies: text: . Good idea. Changed it. CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 21:03, 15 October 2017 (UTC)
replies: text: Thanks!John a s (talk) 12:55, 16 October 2017 (UTC)
thread_title:  Direction - edit request 

message: 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)
replies: text: Not done: please establish a consensus for this alteration before using the  template. — JJMC89 (T·C) 05:48, 13 February 2018 (UTC)
replies: text: 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)
replies: text:  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)
thread_title:  Template-protected edit request on 13 February 2018 

message: and  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 . See Template:Infobox building#Mapframe maps and Template talk:Infobox building#Change to the map parameter so Kartographer works for further information.  - Evad37 [talk] 15:35, 31 August 2018 (UTC)
replies: text: Support, I agree about this update.  angys (Talk Talk) 11:47, 1 September 2018 (UTC)
thread_title:  Mapframe maps? 

message: 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)
thread_title:  How to suppress IATA/ICAO labels 

message: 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 . 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)
replies: text: 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)
replies: text: 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)
thread_title:  Need to replace "Military airport" wording with "Military aerodrome" 

message: This template has  and  for elevation in feet and meters.  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. ? MB 18:01, 21 February 2020 (UTC)
replies: text: User:MB, should be fixed now. Frietjes (talk) 18:06, 21 February 2020 (UTC)
thread_title:  ASL elevation display error 

message: Can someone add parameters for transit and parking here? This is pretty important connection information, available in many infoboxes like , , , , and more. ɱ (talk) 17:53, 23 March 2020 (UTC)
replies: text: Support. Clarify: add , which would display "Public transit access". Vaselineeeeeeee★★★ 19:12, 23 March 2020 (UTC)
replies: text:  for this template. Please adjust the documentation. – Jonesey95 (talk) 14:48, 14 April 2020 (UTC)
thread_title:  Public transit/parking 

message: 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)
thread_title:  Frequency field in Airport Infobox 

message: 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)
thread_title:  Issue with runway conversions