Template talk:Infobox airport

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Aviation / Airports (Rated Template-class)
WikiProject icon This article is within the scope of the Aviation WikiProject. If you would like to participate, please visit the project page, where you can join the project and see lists of open tasks and task forces. To use this banner, please see the full instructions.
 Template  This template does not require a rating on the project's quality scale.
Taskforce icon
This template is supported by the airport project.

Image Protocol[edit]

Is there an agreed protocol to use for the image and image2 variables? Should one be a photo of the terminal and the other should be a aerial view of the runway? Or is it more free form? I have some photos of general aviation airports and wanted to know where I should put them within the template. -Ichabod (talk) — Preceding unsigned comment added by Ichabod (talkcontribs) 03:29, 15 January 2014‎ (UTC)

Architect field in Infobox[edit]

Hi. I would like to propose adding the field of "Architect" to the infobox. For famous structures and buildings, it makes sense to cite who designed & built it. It is mentioned in most every article but not in the infobox.

For infobox_museums, it worked via embedding {{Infobox building}}, which has also got a few other architecture-related parameters, like |architectural_style= with this code:

{{Infobox museum|embedded={{Infobox building|embed=yes|architect=The architect}}}}
Infobox airport
Building details
Design and construction
Architect The architect

Can we do the same for Airports? — Preceding unsigned comment added by Nconcklin (talkcontribs) 17:11, 7 August 2015‎ (UTC)

Formal edit request[edit]

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

Done GeoffreyT2000 (talk, contribs) 01:44, 17 February 2017 (UTC)
@GeoffreyT2000: The hyperlinks are still colored white. Grapesoda22 04:09, 17 February 2017 (UTC)
@Grapesoda22: A further change by Jonesey95 was made to the template, and I also changed the color for Air Force Materiel Command from white to black in the template documentation. GeoffreyT2000 (talk, contribs) 05:16, 17 February 2017 (UTC)
Thanks! Grapesoda22 00:42, 18 February 2017 (UTC)
Grapesoda22, your signature violates WP:SIGLINK. Plastikspork ―Œ(talk) 18:01, 18 February 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── @GeoffreyT2000, @Grapesoda22: What is the specific violation of WP:COLOR? In my opinion, black on dark blue is much harder to read than white on dark blue. I don't agree with this sudden change to a template found on about 14,000 pages. — Sunnya343✈ (háblamemy work) 20:25, 18 February 2017 (UTC)

Sunnya343, we could make the background color lighter or darker. But, 669ACD/black = 7.07 is a much greater contrast than 669ACD/white = 2.97. Thanks! Plastikspork ―Œ(talk) 21:17, 18 February 2017 (UTC)
@GeoffreyT2000: The contrast ratio has to be at least 7 on this checker. Grapesoda22 (talk) 00:18, 19 February 2017 (UTC)
Sunnya343, if you want white text, the lightest alternative (ratio greater than 7) would be  3C5A78 . Thanks Plastikspork ―Œ(talk) 18:29, 19 February 2017 (UTC)
Plastikspork, the current situation still doesn't seem optimal to me. Could we try this, which has a higher contrast ratio of 13.65:  CCCCFF . This is the style for the Major US Airports template. Regards — Sunnya343✈ (háblamemy work) 03:13, 21 February 2017 (UTC)
Sunnya343, that's better, and even better would be  DDDDFF  which has a 15.86 contrast ratio. this is the secondary color used by {{navbox}} as set by MediaWiki:Common.css. Frietjes (talk) 14:53, 21 February 2017 (UTC)
Frietjes, could you try implementing your suggestion? — Sunnya343✈ (háblamemy work) 01:33, 26 February 2017 (UTC)
done, using the "Level 2 color" defined by MediaWiki:Common.css, and the "Level 3 color" in the data table. Frietjes (talk) 14:10, 26 February 2017 (UTC)
Thank you Frietjes, it looks much better now. — Sunnya343✈ (háblamemy work) 16:13, 26 February 2017 (UTC)

Improving colors once more[edit]

  • This is not good enough yet. The {{navbox}} colors were chosen and set to make a navbox recognisable as ... being a navbox (color supporting the semantics/meaning).
Let's start with a different color ('hue'), and then varying into two shades (calculations were done offline). I propose:
Hue: a different blue:      (H=140/360; it should be a skyish blue of course)
'level 2':  AAE6FF     (140-85/255-255/255). Ratio: 15.47 Green tickY (changed after OP)
'level 3':  CDF0FF     (140-50/255-255/255). Ratio: 17.5 Green tickY
OK? -DePiep (talk) 23:53, 8 March 2017 (UTC)
Now in testcases. -DePiep (talk) 01:44, 9 March 2017 (UTC)
Changed the first color into #AAE6FF (darker) to get more diff with the lighter one. -DePiep (talk) 08:55, 9 March 2017 (UTC)
  • Title bar background now the same as headers. Shall I propose a darker 'level-1' color for the title? -DePiep (talk) 08:59, 9 March 2017 (UTC)
2nd proposal: add a separate title bar color.
'level 1':  87DCFF     (140-120/255-255/255). Ratio: 13.71 Green tickY
A tile bar is something else as a header bar (semantics). -DePiep (talk) 09:17, 9 March 2017 (UTC)
Pls consider the proposal, see the testcases. -DePiep (talk) 22:04, 9 March 2017 (UTC)
Everything looks good in the test cases except the white on gray on blue of "Air Force Materiel Command". That should be the same black on blue of the other headers. – Jonesey95 (talk) 22:21, 9 March 2017 (UTC)
That "Air Force Materiel Command" (looks bad) is entered as a style if by an individual article editor. Not a useful testcase. I'll remove it. -DePiep (talk) 00:16, 10 March 2017 (UTC)
I really think the current colors are fine. That bright blue is off-putting to me. — Sunnya343✈ (háblamemy work) 22:42, 9 March 2017 (UTC)
You could ask for an other kind of blue (or purple. For airfields?), I'm just throwing a first ball.
What do you think of that new 3rd, separate color for the title background? Can you agree with me that the infobox title should be distinct from a header?
About semantics, the meaning of a color on a website. To put it straight: If I'd mention this issue on a relevant Wiki forum, this "abuse of navbox colors" would not survive. -DePiep (talk) 00:16, 10 March 2017 (UTC)
I don't see a serious issue with using the same colour more than once. this search returns several thousand. but I also don't object to using a different colour scheme. a light sky blue or a light steel blue would work for me. Frietjes (talk) 00:03, 11 March 2017 (UTC)
"More than once" is not the issue. "For multiple meanings" is. Especially since this is an infobox, confusion with a (sidebar) navbox is too easy. Hell, people were coding class="navbox" and then came complaints that the nice table did not print. Semantics. (btw, a very 'otherstuffexists' argument you made). -DePiep (talk) 01:24, 11 March 2017 (UTC)

Unknown parameters[edit]

I have just run through Category:Pages using infobox airport with unknown parameters (1) 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}}


  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)

Location map parameters[edit]

The Location map template includes a parameter outside=1 that can be used to suppress an error if the mark location is outside of the map. I would like to use this in Chkalovsky Airport. That article uses a map of Moscow to illustrate the location of the airport. A error category is created because the mark is outside the Moscow map, but I think this is fine because the mark is still visible on this map. I don't want to change the map to all of Russia. Can the outside=1 parameter be added to the airport infobox to support this? MB 22:41, 29 June 2017 (UTC)

MB added as |pushpin_outside= per template:infobox lighthouse syntax. Frietjes (talk) 23:11, 29 June 2017 (UTC)