How do the JSON output and object table of Aviation Edge historical schedules API function?

In this article, I will clarify the object table and JSON output of the Aviation Edge historical schedules API. Specifically, I will describe the structure of the object table and the information it contains, as well as the format of the JSON output and the data it represents. Understanding the object table and JSON output of this API is crucial for effectively accessing and utilizing the data provided by the API.

API Table

1. type: This object represents the schedule type, which can be either "departure" or "arrival".

2. status: This object represents the last recorded flight status, which can be one of the following: "landed", "active", "cancelled", "diverted" etc.

3. departure: This object is an object that contain fields related to departure airport.

4. iataCode: This object represents the IATA (International Air Transport Association) code of the departure airport.

5. icaoCode: This object represents the ICAO (International Civil Aviation Organization) code of the departure airport.

6. gate: This object represents the flight gate at the departure airport.

7. delay: This object represents the total delay of the flight.

8. scheduledTime: This object represents the originally scheduled departure time of the flight.

9. actualTime: This object represents the actual departure time of the flight.

10. estimatedRunway: This object represents the estimated runway time of the flight.

11. actualRunway: This object represents the actual runway time of the flight.

12. arrival: This object is an object that contain fields related to arrival airport.

13. iataCode: This object represents the IATA (International Air Transport Association) code of the arrival airport.

14. icaoCode: This object represents the ICAO (International Civil Aviation Organization) code of the arrival airport.

15. terminal: This object represents the terminal at the arrival airport.

16. baggage: This object represents the baggage belt of the flight in the arrival airport.

17. gate: This object represents the flight gate at the arrival airport.

18. scheduledTime: This object represents the originally scheduled arrival time of the flight.

19. estimatedTime: This object represents the estimated arrival time of the flight.

The information in the table provided is useful for a variety of purposes. The "type" object can be used to determine whether a flight is a departure or arrival, while the "status" object can be used to track the current status of a flight. The "iataCode" and "icaoCode" objects can be used to identify specific airports, and the "gate" and "terminal" objects can be used to track a flight's location within an airport. The "scheduledTime" and "actualTime" objects can be used to track flight delays and the "delay" object can be used to check the total delay of the flight. The "arrival" and "departure" objects give the user detailed information about the airports and fields related to it. This information can be used by airlines, travel companies, and other organizations to track flights, plan routes, and provide accurate information to customers. Additionally, it can be used by individuals to plan their travel itineraries and track the status of their flights. Overall, the table provides a wealth of information that can be used to make informed decisions and better understand the current state of flight schedules and airport operations.

JSON REST Output

This JSON output represents information about an airline and its arrival details at an airport. The output is an array containing a single object, which has two properties: "airline" and "arrival". The "airline" property is an object that contains information about the airline, including its IATA code ("iataCode"), ICAO code ("icaoCode"), and name ("name"). The "arrival" property is also an object, which contains detailed information about the flight arrival. It includes the actual time of flight landing on the runway ("actualRunway"), the actual time of flight landing ("actualTime"), baggage belt ("baggage"), total delay of flight ("delay"), estimated runway time ("estimatedRunway"), estimated arrival time ("estimatedTime"), flight gate at the arrival airport("gate"), the iata code of the arrival airport ("iataCode"), the icao code of the arrival airport ("icaoCode"), scheduled arrival time ("scheduledTime") and terminal at the arrival airport("terminal").

This JSON output can be used to get information about an airline and its flight details, it can be used to track the flight status, delays, and other relevant information about a flight's arrival at an airport.

[
{"airline":
{
"iataCode":"WS",
"icaoCode":"WJA",
"name":"WestJet"
},
"arrival":
{"actualRunway":"2022-01-24T23:48:00.000",
"actualTime":"2022-01-24T23:48:00.000",
"baggage":null,
"delay":"19",
"estimatedRunway":"2022-01-24T23:48:00.000",
"estimatedTime":"2022-01-24T23:29:00.000",
"gate":"A15",
"iataCode":"IAH",
"icaoCode":"KIAH",
"scheduledTime":"2022-01-24T23:29:00.000",
"terminal":"A"
}
]

Closing words

In summary, the information provided in this conversation pertains to the object table and JSON output of the Aviation Edge historical schedules API. The object table lists the different objects available in the API, including schedule type, flight status, departure and arrival airport codes, flight gates, delays, and scheduled and actual times. The JSON output, on the other hand, provides specific information about an airline and its arrival details at an airport, including airline name, IATA and ICAO codes, actual and estimated runway and arrival times, baggage belt, flight gate and terminal. Understanding the structure of the object table and the format of the JSON output is crucial for effectively accessing and utilizing the data provided by the API. This information can be used by airlines, travel companies, and individuals to track flights, plan routes, and provide accurate information.

Note

The Aviation Edge historical schedules API is a valuable resource for obtaining detailed information about flight schedules, departure and arrival airports, flight status, delays, and other relevant information. However, in order to access this data, you typically need to request access to the API through the third party data marketplace of Worldindata.

Worldindata is a data marketplace that provides access to a wide range of data sets and APIs, including the Aviation Edge historical schedules API. By signing up for an account on the Worldindata marketplace, you can request access to the API and gain access to the detailed flight information it provides. Once you have access, you will be able to use the API to retrieve data programmatically, which can then be used in your application or analysis. It is important to note that access to the API may come with usage limitations and costs, and they might require you to sign agreements.