Template:Infobox airport/doc

{{#ifeq:{{{noheader|}}}|yes||{{Documentation subpage}} {{high-use}} {{Lua|Module:Infobox|Module:InfoboxImage|Module:String|Module:Check for unknown parameters|Module:Type in location}} {{Auto short description}} {{Uses Wikidata|P625}}

Usage
}}

The following blank template includes all of the available parameter names, except for repeating names used for runways and statistics. All parameters except name are optional; however, "IATA: none – ICAO: none", along with the heading "Summary", will always appear. Any unused parameters should be omitted, but can also be left blank if preferred. The use of flag icons with this infobox is discouraged.

Parameters
All parameters except name are optional.

Airport name
These parameters specify the airport name which is displayed at the top of the infobox.


 * name
 * The name of the airport in English, such as Warsaw Chopin Airport or Beijing Capital International Airport.


 * nativename
 * Airport name in a native language using Western characters (French, German, Spanish, etc.), such as Lotnisko Chopina w Warszawie. In such cases the native name should be in italics, see Manual of Style/Text formatting. Can also be used for two different names in the same language (see Region of Waterloo International Airport).


 * nativename-a
 * Airport name in a native language with non-Western characters (Chinese, Japanese, Korean, Arabic, etc.), such as 北京首都国际机场.


 * nativename-r
 * Use in conjunction with above for Romanized name of the airport, such as Běijīng Shǒudū Guójì Jīcháng. In such cases the Romanized name should be in italics, see Manual of Style/Text formatting.

Airport image
These parameters specify an airport photograph or logo which is displayed below the title. A second image can also be displayed below the first image by using the parameter names ending with a "2".
 * ensign
 * Optional small ensign


 * image / image2
 * The name of image file, such as  or   (do not include the   or   prefix).


 * image_alt / image2_alt
 * Alternative text for the images.


 * image_size / image2_size
 * image-width / image2-width
 * The image size or width in pixels, i.e., 175 (defaults to 220 if not specified).
 * May be used for smaller images which would appear distorted when expanded to a width of 220px.


 * caption / caption2
 * Text displayed beneath the image. If left blank or omitted, a caption will not be displayed.
 * This should only be used for photographs that require an explanation; it should be omitted for airport logos and may be omitted for photographs.

Airport codes
These parameters specify airport location identifiers which are displayed below the image (or below title if there is no image):


 * IATA
 * The airport's three character IATA location identifier. If omitted or left blank it will display as IATA: none.


 * ICAO
 * The airport's four character ICAO location identifier. If omitted or left blank it will display as ICAO: none.


 * FAA
 * The three or four character FAA location identifier for airports in the United States. If omitted or left blank, nothing is displayed.


 * TC
 * The three or four character Transport Canada location identifier for airports in Canada. If omitted or left blank, nothing is displayed.


 * LID
 * A location identifier for airports outside the US or Canada, if other than ICAO or IATA codes. If omitted or left blank, nothing is displayed.


 * GPS
 * A Global Positioning System code for the airport, if other than ICAO or IATA codes. If omitted or left blank, nothing is displayed.


 * WMO
 * The World Meteorological Organization five digit code for the weather station at the airport. If omitted or left blank, nothing is displayed.

Airport summary
These parameters specify airport details for the "Summary" section displayed below the airport codes.


 * type
 * Airport type should be one of the following: Public, Private, Military or Military/Public. Do not use Commercial, General or Civil.


 * owner-oper
 * If the airport is owned and operated by the same entity, use this in place of owner and operator.


 * owner
 * Name of the airport owner.


 * operator
 * Name of the airport operator, if not the owner.


 * city-served
 * If the airport is associated with a major city but actually located in a smaller town, list the major city here and the smaller town under location. This is not automatically linked, in order to allow multiple links if needed.
 * Example:
 * Result: Paris


 * location
 * Name of the town or city where the airport is located. Do not put the airport's street address in this field. This is not automatically linked, in order to allow multiple links if needed.
 * Example:
 * Result: Orly, France


 * opened
 * The date when the airport originally opened for commercial service.
 * Example:
 * Result: September 22, 1989


 * closed
 * The date when the airport closed, either temporarily or permanently, along with reason for closing (for presently closed airports only). Use.


 * passenger_services_ceased
 * The date when passenger services to the airport ceased due to conversion of the airport for another use, along with the new use for the airport. Only for airports that previously had passenger services. Use.


 * hub
 * If the airport serves as a hub, list the airlines here in alphabetical order. This is not automatically linked, in order to allow multiple links if needed. Use if the list is long.
 * Example:


 * Result:
 * British Airways
 * EasyJet
 * Virgin Atlantic


 * focus_city
 * If the airport serves as a focus city, list the airlines here in alphabetical order. See discussion at Wikipedia talk:WikiProject Airports. Use if the list is long.


 * operating_base
 * If the airport serves as an operating base for an airline, list it here in alphabetical order, unless the airline is already listed under hub or focus_city. This parameter is most commonly used for Ultra-low cost airlines which do not have hubs or focus cities. Use if the list is long.


 * timezone and utc
 * Will give the time zone that the airport is in, can be linked. A list can be found at List of time zones by country.
 * Timezone is optional, but if it is used, then utc must be used as well, can be linked. A list can be found at List of UTC time offsets.


 * summer and utcs
 * If the time zone observes daylight saving time this will give the zone that the airport is in, can be linked. A list can be found at List of time zones by country.
 * Summer is optional, but if it is used, then utcs must be used as well, can be linked. A list can be found at List of UTC time offsets.


 * elevation-f
 * Height above mean sea level, in feet.


 * elevation-m
 * Height above mean sea level, in metres.


 * website
 * External link to the airport's official website. See External links for more information.
 * Example:
 * Result: http://www.dfwairport.com/

Military airports
These optional parameters provide additional information for military airports. The parameter names are based on those used in Template:Infobox military structure. This allows the display of information from that template, without the need to include an additional infobox. See example 4 below.


 * built
 * The date when the structure was built, usually given in years.


 * used
 * The period during which the structure was in active military use, usually given in years.


 * commander
 * The current commanding officer, for structures currently in military use.


 * occupants
 * Any notable military units which occupy the structure.

Geographic coordinates
This template allows for the insertion of geographic coordinates in two different ways: you can either provide a complete template in the coordinates parameter, or you can provide the individual coordinate components (degrees, minutes, seconds, etc.) in the separate parameters described below. The latter method also allows you to insert a pushpin map with an automatically-placed airport icon and label (see below).

If you use both methods, then the coordinates parameter will be used in the infobox.


 * coordinates
 * Latitude and Longitude of airport, specified using the template. When entering the coordinates always ensure that the resultant map or image shows the airport. It is very easy to confuse "N" for "S" or "E" for "W". If used as shown below, this will also cause the airport to appear in Google Earth's Geographic Web Layer.
 * Example:
 * Result: 49.45444°N, 2.11278°W

Maps
This template provides three ways to include a map: as a simple image, or using interactive Mapframe maps, or using (with the coordinate parameters described above to automatically place a pushpin mark and label on a map).

Image map
Am image map can be displayed by providing a value for image_map. The remaining image_ parameters are optional.


 * image_map
 * The name of an image to use as a map, such as  (do not include the   or   prefix).


 * image_mapsize
 * (optional) The width to display the image map, in pixels. Just the number, no " ". If omitted or left empty, defaults to 220.


 * image_map_alt
 * (optional) Alt text for the image map. If left blank or omitted, this defaults to same text used in  (or Location of  if no caption).


 * image_map_caption
 * (optional) Caption to display below the image map. If left blank or omitted, a caption will not be displayed.

Location/pushpin map
A location map can be displayed by providing values for coordinates, and pushpin_map. The remaining pushpin_ parameters are optional.


 * pushpin_map
 * The name of a location map as per Template:Location map (e.g. Indonesia or Russia). The coordinates parameter values position a pushpin mark and label on the map automatically.


 * pushpin_mapsize
 * (optional) The width to display the pushpin map, in pixels. Just the number, without " ". If omitted or left empty, defaults to 220.


 * pushpin_map_alt
 * (optional) Alt text for the pushpin map.


 * pushpin_map_caption
 * (optional) Caption to display below the pushpin map. If left blank or omitted, a caption will not be displayed.


 * pushpin_relief
 * (optional) Any non-blank value (yes, 1, etc.) will cause the template to display a relief map image, where available (see example 1). For additional information, see Template:Location map.


 * pushpin_image
 * (optional) Name of an alternative map image, which must have the same edge coordinates as the location map template specified via pushpin_map (see example 5). Do not include the  or   prefix. For additional information, see Template:Location map.


 * pushpin_label
 * (optional) The text of the label to place next to the pushpin mark (see example 1). The default is the value of the name parameter.


 * pushpin_label_position
 * (optional) The position of the label on the pushpin map relative to the pushpin mark (see example 5). Valid values are,  ,   and  . This defaults to either   or  , depending on the coordinates of the marker and its position relative to the right border of the map image.


 * pushpin_mark
 * (optional) The name of an image to display as the pushpin mark (see example 5). The default is  ( Airplane silhouette.svg ).


 * pushpin_marksize
 * (optional) The size of the mark in pixels (see example 5). The default is 10. Do not include, for example:  , not.

Infobox control
These parameters control how certain fields within the infobox are displayed.


 * metric-elev
 * Set to any value to display elevation in metric units (metres) before imperial/US units (feet); leave blank to display imperial/US units first. This can be seen in example 1.


 * metric-rwy
 * Set to any value to display runway length in metric units (metres) before imperial/US units (feet); leave blank to display imperial/US units first. Examples 1 and 2 below show the runway length with metres first; example 3 and 4 show it with feet before metres.

Runways
These parameters specify details for each runway in the "Runways" section displayed below the summary. This can also be used to specify water landing areas for seaplanes (see Fairbanks International Airport). Parameters start with r1- for the first runway, r2- for the second runway, up to r8- for the eighth runway (if more are needed, leave a message on the talk page). Each airport should have at least one runway.


 * rn-number (r1-number, r2-number, ...)
 * The designation of the runway, normally two numbers like this &rarr; 02/20, 1st number is 18 lower than the 2nd. Where there are parallel runways an additional letter is added to each number, for example "L" for left, "R" for right and "C" for center. In certain cases a runway will only have one number when it can only be used in one direction. For airports in the United States the leading zero is not used and the designation should read 2/20.


 * rn-length-f (r1-length-f, r2-length-f, ...)
 * Runway length in feet.


 * rn-length-m (r1-length-m, r2-length-m, ...)
 * Runway length in metres.


 * rn-surface (r1-surface, r2-surface, ...)
 * Runway surface type, such as: Concrete, Asphalt, Gravel, Grass (or Turf), Dirt, Water, etc. Avoid the generic type "Paved" if possible.

Helipads
These parameters specify details for each helipad in the "Helipads" section displayed below the runways. Parameters start with h1- for the first helipad, h2- for the second helipad, up to h12- for the twelfth helipad (if more are needed, leave a message on the talk page). This section is optional and only appears if the h1- parameters are specified. See example 1 and example 3 below.


 * hn-number(h1-number, h2-number, ...)
 * The designation of the helipad. In the United States this is usually the letter "H" followed by a number, i.e. "H1", "H2", etc.


 * hn-length-f (h1-length-f, h2-length-f, ...)
 * Helipad length in feet.


 * hn-length-m (h1-length-m, h2-length-m, ...)
 * Helipad length in metres.


 * hn-surface (h1-surface, h2-surface, ...)
 * Helipad surface type, such as: Concrete, Asphalt, etc. Avoid the generic type "Paved" if possible.

Statistics
These parameters specify details for an optional "Statistics" section displayed below the runways and helipads. Parameters start with stat1- for the first statistic, stat2- for the second statistic, etc. This section only appears if the stat1- parameters are specified. See example 1 and example 3 below.


 * statn-header (stat1-header, stat2-header, ...)
 * A brief description of each statistic, such as Passengers or Aircraft operations.


 * statn-data (stat1-data, stat2-data, ...)
 * The data associated with the corresponding header.


 * stat-year
 * The calendar year for the statistics. This is displayed in parentheses after the word "Statistics" in the section header.

Example 1
Warsaw Chopin Airport

This example shows the appearance of the infobox without an image.

It also shows the use of the parameters for latitude, longitude, and location/pushpin map.

Note: helipad information added to illustrate function of  parameter.

Example 2
Beijing Capital International Airport

This example shows the appearance of the infobox with an image and a caption.

It also uses both the  and   parameters.

Example 3
Dallas–Fort Worth International Airport

Example 4
Wright–Patterson Air Force Base

This infobox shows the use of an image and linked text over the blue background in title area. It also makes use of some of the fields used for military airports.

Example 5
Buri Ram Airport

This infobox shows the use optional parameters for the location/pushpin map.

TemplateData
{	"format": "\n", "params": { "name": { "label": "Name", "type": "string", "required": false, "description": "The name of the airport in English", "default": "" },		"nativename": { "label": "Nativename", "type": "string", "required": false, "description": "Airport name in a native language using Western characters (French, German, Spanish, etc.)" },		"nativename-a": { "label": "Nativename-a", "type": "string", "required": false, "description": "Airport name in a native language with non-Western characters (Chinese, Japanese, Korean, Arabic, etc.), such as ????????." },		"nativename-r": { "label": "Nativename-r", "type": "string", "required": false, "description": "Use in conjunction with above for Romanized name of the airport. In such cases the Romanized name should be in italics." },		"ensign": { "label": "Ensign", "type": "content", "required": false, "description": "A small ensign using image syntax.", "example": "" },		"image": { "label": "Image", "type": "wiki-file-name", "required": false, "description": "The name of image file, such as Airport.png or Logo.gif (do not include the File: or Image: prefix)." },		"image_size": { "label": "Image size or width", "aliases": ["image-width"], "type": "number", "required": false, "description": "The image size or width in pixels, e.g., 175 (defaults to 220 if not specified).", "example": "175", "default": "220" },		"image_alt": { "label": "Image alternative text", "type": "string", "required": false, "description": "Alternative text for the images." },		"caption": { "label": "Caption", "type": "string", "required": false, "description": "Text displayed beneath the image. If left blank or omitted, a caption will not be displayed. This should only be used for photographs that require an explanation; it should be omitted for airport logos and may be omitted for photographs." },		"image2": { "label": "Image2", "type": "wiki-page-name", "required": false, "description": "The name of image file, such as Airport.png or Logo.gif (do not include the File: or Image: prefix)." },		"image2_size": { "label": "Image2 size or width", "aliases": ["image2-width"], "type": "number", "required": false, "description": "The image size or width in pixels, e.g., 175 (defaults to 220 if not specified). This should only be used for smaller images which would appear distorted when expanded to a width of 220px.", "example": "175", "default": "220" },		"image2_alt": { "label": "Image2 alternative text", "type": "string", "required": false, "description": "Alternative text for the images." },		"caption2": { "label": "Caption2", "type": "string", "required": false, "description": "Text displayed beneath the image. If left blank or omitted, a caption will not be displayed. This should only be used for photographs that require an explanation; it should be omitted for airport logos and may be omitted for photographs." },		"IATA": { "label": "IATA", "type": "string", "required": false, "description": "The airport's three character IATA location identifier. If omitted or left blank it will display as IATA: none." },		"ICAO": { "label": "ICAO", "type": "string", "required": false, "description": "The airport's four character ICAO location identifier. If omitted or left blank it will display as ICAO: none." },		"FAA": { "label": "FAA", "type": "string", "required": false, "description": "The three or four character FAA location identifier for airports in the United States. If omitted or left blank, nothing is displayed." },		"TC": { "label": "TC", "type": "string", "required": false, "description": "The three or four character Transport Canada location identifier for airports in Canada. If omitted or left blank, nothing is displayed." },		"LID": { "label": "LID", "type": "string", "required": false, "description": "A location identifier for airports outside the US or Canada, if other than ICAO or IATA codes. If omitted or left blank, nothing is displayed." },		"GPS": { "label": "GPS", "type": "string", "required": false, "description": "A Global Positioning System code for the airport, if other than ICAO or IATA codes. If omitted or left blank, nothing is displayed." },		"WMO": { "label": "WMO", "type": "string", "required": false, "description": "The World Meteorological Organization five digit code for the weather station at the airport. If omitted or left blank, nothing is displayed." },		"type": { "label": "Type", "type": "string", "required": false, "description": "Airport type should be one of the following: Public, Private, Military or Military/Public. Do not use Commercial, General or Civil." },		"owner-oper": { "label": "Owner-Operator", "type": "string", "required": false, "description": "If the airport is owned and operated by the same entity, use this in place of owner and operator." },		"owner": { "label": "Owner", "type": "string", "required": false, "description": "Name of the airport owner." },		"operator": { "label": "Operator", "type": "string", "required": false, "description": "Name of the airport operator, if not the owner." },		"city-served": { "label": "city-served", "type": "string", "required": false, "description": "If the airport is associated with a major city but actually located in a smaller town, list the major city here and the smaller town under location. This is not automatically linked, in order to allow multiple links if needed.", "aliases": [ "area-served" ]		},		"location": { "label": "Location", "type": "string", "required": false, "description": "Name of the town or city where the airport is located. Do not put the airport's street address in this field. This is not automatically linked, in order to allow multiple links if needed." },		"opened": { "label": "Opened", "type": "string", "required": false, "description": "The date when the airport originally opened for commercial service." },		"closed": { "label": "Closed", "type": "string", "required": false, "description": "The date when the airport closed, either temporarily or permanently, along with reason for closing (for presently closed airports only). Use ." },		"passenger_services_ceased": { "label": "Passenger Services Ceased", "type": "string", "required": false, "description": "The date when passenger services to the airport ceased due to conversion of the airport for another use, along with the new use for the airport. Only for airports that previously had passenger services. Use ." },		"hub": { "label": "Hub", "type": "string", "required": false, "description": "If the airport serves as an hub, list the airlines here. This is not automatically linked, in order to allow multiple links if needed. Use if the list is long." },		"focus_city": { "label": "Focus City", "type": "string", "required": false, "description": "If the airport serves as a focus city" },		"built": { "label": "Built", "type": "line", "required": false, "description": "The date when the structure was built, usually given in years." },		"used": { "label": "Used", "type": "string", "required": false, "description": "The period during which the structure was in active military use, usually given in years." },		"commander": { "label": "Commander", "type": "string", "required": false, "description": "The current commanding officer, for structures currently in military use." },		"occupants": { "label": "Occupants", "type": "string", "required": false, "description": "Any notable military units which occupy the structure." },		"timezone": { "label": "Timezone", "type": "number", "required": false, "description": "Will give the time zone that the airport is in, can be linked. A list can be found at List of time zones by country. Timezone is optional, but if it is used, then utc must be used as well, can be linked. A list can be found at List of UTC time offsets." },		"utc": { "label": "UTC", "type": "number", "required": false, "description": "UTC time of the airport" },		"summer": { "label": "Summer", "type": "string", "required": false, "description": "If the time zone observes daylight saving time this will give the zone that the airport is in, can be linked. A list can be found at List of time zones by country. " },		"utcs": { "label": "UTCS", "type": "string", "required": false, "description": "Summer is optional, but if it is used, then utcs must be used as well, can be linked. A list can be found at List of UTC time offsets." },		"elevation-f": { "label": "Elevation In Feet", "type": "number", "required": false, "description": "Height above mean sea level, in feet." },		"elevation-m": { "label": "Elevation In Metres", "type": "number", "required": false, "description": "Height above mean sea level, in metres." },		"metric-elev": { "label": "Metric-elevation", "type": "number", "required": false, "description": "Set to any value to display elevation in metric units (metres) before imperial/US units (feet); leave blank to display imperial/US units first." },		"coordinates": { "label": "Coordinates", "type": "number", "required": false, "description": "Latitude and Longitude of airport, specified using the °N, °W template" },		"website": { "label": "Website", "type": "string", "required": false, "description": "External link to the airport's official website" },		"image_map": { "label": "Image Map", "type": "wiki-page-name", "required": false, "description": "The name of an image to use as a map, such as Airport_map.png (do not include the File: or Image: prefix)." },		"image_mapsize": { "label": "Image Mapsize", "type": "number", "required": false, "description": " The width to display the image map, in pixels. Just the number, no \"px\". If omitted or left empty, defaults to 220.", "default": "220" },		"image_map_alt": { "label": "Image Map Alternative", "type": "string", "required": false, "description": " Alt text for the image map. If left blank or omitted, this defaults to same text used in image_map_caption (or Location of if no caption."		},		"image_map_caption": {			"label": "Image Map Caption",			"type": "string",			"required": false,			"description": "Caption to display below the image map. If left blank or omitted, a caption will not be displayed."		},		"pushpin_map": {			"label": "Pushpin Map",			"type": "string",			"required": false,			"description": "The name of a location map as per Template:Location map (e.g. Indonesia or Russia). The coordinates field position a pushpin mark and label on the map automatically."		},		"pushpin_mapsize": {			"label": "Pushpin Mapsize",			"type": "number",			"required": false,			"description": " The width to display the pushpin map, in pixels. Just the number, without \"px\". If omitted or left empty, defaults to 220.",			"default": "220" },		"pushpin_map_alt": { "label": "Pushpin Map Alternative", "type": "string", "required": false, "description": " Alt text for the pushpin map." },		"pushpin_map_caption": { "label": "Pushpin Map Caption", "type": "string", "required": false, "description": "Caption to display below the pushpin map. If left blank or omitted, a caption will not be displayed." },		"pushpin_relief": { "label": "Pushpin Relief", "type": "string", "required": false, "description": " Any non-blank value (yes, 1, etc.) will cause the template to display a relief map image, where available (see example 1). For additional information, see Template:Location map#Relief parameter." },		"pushpin_image": { "label": "Pushpin Image", "type": "wiki-page-name", "required": false, "description": " Name of an alternative map image, which must have the same edge coordinates as the location map template specified via pushpin_map" },		"pushpin_label": { "label": "Pushpin Label", "type": "string", "required": false, "description": "The text of the label to place next to the pushpin mark. The default is the value of the name parameter." },		"pushpin_label_position": { "label": "Pushpin Label Position", "type": "string", "required": false, "description": " The position of the label on the pushpin map relative to the pushpin mark (see example 5). Valid values are left, right, top and bottom. This defaults to either left or right, depending on the coordinates of the marker and its position relative to the right border of the map image." },		"pushpin_mark": { "label": "Pushpin Mark", "type": "string", "required": false, "description": "The name of an image to display as the pushpin mark.", "default": "Airplane silhouette.svg" },		"pushpin_marksize": { "label": "Pushpin Marksize", "type": "number", "required": false, "description": " The size of the mark in pixels" },		"r1-number": { "label": "r1-Number", "type": "number", "required": false, "description": "The designation of the runway, normally two numbers like this ? 02/20, 1st number is 18 lower than the 2nd. Where there are parallel runways an additional letter is added to each number, for example \"L\" for left, \"R\" for right and \"C\" for center. In certain cases a runway will only have one number when it can only be used in one direction. For airports in the United States the leading zero is not used and the designation should read 2/20." },		"r1-length-f": { "label": "r1-Length-In Feet", "type": "number", "required": false, "description": "Runway length in feet." },		"r1-length-m": { "label": "r1-Length-In Metres", "type": "number", "required": false, "description": "Runway length in metres." },		"r1-surface": { "label": "r1-Surface", "type": "string", "required": false, "description": "Runway surface type, such as: Concrete, Asphalt, Gravel, Grass (or Turf), Dirt, Water, etc. Avoid the generic type \"Paved\" if possible." },		"metric-rwy": { "label": "Metric-runway", "type": "string", "required": false, "description": "Set to any value to display runway length in metric units (metres) before imperial/US units (feet); leave blank to display imperial/US units first" },		"h1-number": { "label": "h1-Number", "type": "number", "required": false, "description": "The designation of the helipad. In the United States this is usually the letter \"H\" followed by a number, i.e. \"H1\", \"H2\", etc." },		"h1-length-f": { "label": "h1-Length-In Feet", "type": "number", "required": false, "description": "Helipad length in feet." },		"h1-length-m": { "label": "h1-Length-Metre", "type": "number", "required": false, "description": "Helipad length in metres." },		"h1-surface": { "label": "h1-Surface", "type": "string", "required": false, "description": "Helipad surface type, such as: Concrete, Asphalt, etc. Avoid the generic type \"Paved\" if possible." },		"stat1-header": { "label": "Stat1-Header", "type": "string", "required": false, "description": "A brief description of each statistic, such as Passengers or Aircraft operations." },		"stat1-data": { "label": "Stat1-Data", "type": "string", "required": false, "description": "The data associated with the corresponding header." },		"stat-year": { "label": "Stat-Year", "type": "line", "required": false, "description": "The calendar year for the statistics. This is displayed in parentheses after the word \"Statistics\" in the section header." },		"footnotes": { "label": "Footnotes", "type": "string", "required": false, "description": "The most common use for this field is to give sources or references for the data displayed in the infobox" }	} }