Details of the Object table and JSON output of airports API of Aviation Edge

The Aviation Edge airports API provides a wealth of information on airports around the world in a structured format. One of the ways in which the data is presented is through an object table. This table is essentially a collection of data organized into rows and columns, similar to a spreadsheet. Each row represents a single airport, and each column contains specific information about that airport, such as its name, location, and IATA code. In addition to the object table, the API also provides the option to retrieve the data in JSON format. JSON, or JavaScript Object Notation, is a lightweight data-interchange format that is easy for humans to read and write and easy for machines to parse and generate. This format is commonly used in web applications and is a popular choice for developers working with APIs.

API Object Table

ObjectsDescription
airportIdAirport ID in our database
nameAirportAirport name
codeIataAirportAirport IATA code
codeIcaoAirportAirport ICAO code
latitudeAirportAirport latitude
longitudeAirportAirport longitude
geonameIdGeoname ID
timezoneAirport timezone
GMTGMT
phoneContact phone
nameCountryCountry name
codeIso2Country2-digit country code
codeIataCityCity IATA code
  1. airportId: A unique identifier assigned to an airport in the Aviation Edge database. This identifier can be used to retrieve specific information about the airport from the API.

  2. nameAirport: The official name of the airport.

  3. codeIataAirport: The IATA code assigned to the airport by the International Air Transport Association (IATA). This code is typically used for commercial air travel and is three letters long.

  4. codeIcaoAirport: The ICAO code assigned to the airport by the International Civil Aviation Organization (ICAO). This code is four letters long and is primarily used for air traffic control and flight planning.

  5. latitudeAirport: The latitude coordinate of the airport. The latitude of an airport is used to locate it on the earth's surface and to calculate flight paths.

  6. longitudeAirport: The longitude coordinate of the airport. The longitude of an airport is used to locate it on the earth's surface and to calculate flight paths.

  7. geonameId: A unique identifier assigned by GeoNames, a geographical database, to identify geographical names and features on Earth.

  8. timezone: The time zone that the airport is located in.

  9. GMT: The offset of the time zone from the Greenwich Mean Time (GMT).

  10. phone: The contact phone number of the airport.

  11. nameCountry: The name of the country where the airport is located.

  12. codeIso2Country: The ISO 3166-1 alpha-2 code for the country where the airport is located.

  13. codeIataCity: The IATA code assigned to the city where the airport is located.

The information in the table is useful for a variety of purposes. The airportId, nameAirport, codeIataAirport and codeIcaoAirport, latitudeAirport and longitudeAirport can be used to identify and locate specific airports, and are useful for flight planning and navigation. The geonameId, timezone, and GMT can be used to understand the local time and time zone of an airport, which is useful for scheduling flights and coordinating with local authorities. The phone and nameCountry and codeIso2Country can be used for contact and identification of the country where the airport is located. The codeIataCity can be used to identify the city where the airport is located and it can be used for travel purposes. All of this information can be used by airlines, travel agencies, logistics companies, flight planning software, and other organizations that rely on accurate and up-to-date information about airports.

JSON output explained

This JSON output is an example of data returned by the Aviation Edge airports API. It is an array with one object inside, which represents a single airport. The airport object has several properties, each of which contains a specific piece of information about the airport. The properties include:

  • airportId: a unique identifier assigned to the airport by the Aviation Edge database.

  • nameAirport: the official name of the airport, in this case "Aachen/Merzbruck"

  • codeIataAirport: the IATA code assigned to the airport, in this case "AAH"

  • codeIcaoAirport: the ICAO code assigned to the airport, in this case "EDKA"

  • latitudeAirport: the latitude coordinate of the airport, in this case "50.75"

  • longitudeAirport: the longitude coordinate of the airport, in this case "6.133333"

  • geonameId: a unique identifier assigned by GeoNames, in this case "3247449"

  • timezone: the time zone that the airport is located in, in this case "Europe/Berlin"

  • GMT: the offset of the time zone from the Greenwich Mean Time (GMT) in this case "1"

  • phone: the contact phone number of the airport, in this case is empty

  • nameCountry: the name of the country where the airport is located, in this case "Germany"

  • codeIso2Country: the ISO 3166-1 alpha-2 code for the country where the airport is located, in this case "DE"

  • codeIataCity: the IATA code assigned to the city where the airport is located, in this case "AAH"

[
{
"airportId": "7",
"nameAirport": "Aachen/Merzbruck",
"codeIataAirport": "AAH",
"codeIcaoAirport": "EDKA",
"latitudeAirport": "50.75",
"longitudeAirport": "6.133333",
"geonameId": "3247449",
"timezone": "Europe/Berlin",
"GMT": "1",
"phone": "",
"nameCountry": "Germany",
"codeIso2Country": "DE",
"codeIataCity": "AAH"
}
]

Closing words

Today, we've discussed the object table and JSON output provided by the Aviation Edge airports API. We've explained the structure and contents of the object table and JSON output, and provided a detailed explanation of each object in the table, including the airportId, nameAirport, codeIataAirport, codeIcaoAirport, latitudeAirport, longitudeAirport, geonameId, timezone, GMT, phone, nameCountry, codeIso2Country, and codeIataCity. We've also described how this information is useful for a variety of purposes such as flight planning, navigation, scheduling flights, and coordinating with local authorities. All of these information can be used by airlines, travel agencies, logistics companies, flight planning software, and other organizations that rely on accurate and up-to-date information about airports.

Note

The Aviation Edge airports API is a powerful tool that provides a wealth of information on airports worldwide. To access this data, you can request access to the API through the third-party data marketplace Worldindata. Worldindata is a platform that allows you to access a wide range of data sets, including the Aviation Edge airports API, with a simple and easy to use interface. To request access to the API, you will need to sign up for an account on the Worldindata platform, and then search for the Aviation Edge airports API in their marketplace. Once you find the API, you can request access by clicking on the "Get API Key" button. After that you will need to agree to the terms of service and pay for the usage of the API. With an API key, you can start using the Aviation Edge airports API to retrieve data about airports worldwide and use it for your specific needs.