the_paragliding_app

OpenAIP Airspace API JSON Structure

This document describes the JSON structure returned by the OpenAIP Core API v1 airspaces endpoint.

API Response Structure

The API returns a paginated response with the following top-level structure:

{
  "items": [...],      // Array of airspace objects
  "limit": 500,        // API pagination limit
  "page": 1,          // Current page number
  "totalCount": 12,   // Total airspaces found
  "totalPages": 1     // Total pages available
}

Airspace Object Properties

Each airspace in the items array contains 22 properties:

Core Identification

ICAO Classification System

Note: icaoClass: 8 indicates the airspace has no ICAO class assigned in the OpenAIP system, not missing data.

ICAO Airspace Classifications Explanations

OpenAIP uses International Civil Aviation Organization (ICAO) classifications. THese classify airspace into seven classes (A through G) to provide different levels of air traffic services and separation. The classes range from highly controlled Class A to uncontrolled Class G:

Controlled Airspace (Classes A-E)

Uncontrolled Airspace (Classes F-G)

Special Use Airspace (SUA)

SUA areas have specific limitations or rules for safety, found on flight charts and including:

OpenAIP data includes details on the specific characteristics of each airspace, including its boundaries, altitudes, and operational times to ensure safe and efficient flight.

Altitude Limits Structure

Both lowerLimit and upperLimit are objects with identical structure:

{
  "value": 125,           // Altitude value (number)
  "unit": 6,             // Unit code (integer)
  "referenceDatum": 2    // Reference datum code (integer)
}

Unit Codes

Reference Datum Codes

Operational Status Flags

All boolean flags in the Perth dataset are false:

Administrative Fields

Implementation Notes

  1. Type Mapping: The numeric type codes need to be mapped to aviation standard abbreviations (CTR, CTA, TMA, etc.) If there isn’t a mapping, show the numerical value.

  2. Altitude Conversion: Flight levels (unit=6) represent hundreds of feet (FL125 = 12,500ft), while feet (unit=1) are direct values.

  3. Reference Datum: Ground reference (referenceDatum=0) with value=0 should display as “GND”.

  4. Sorting: For altitude-based sorting, convert all altitudes to a common unit (feet) using the conversion rules.

API Access

Airspace Types Reference

The OpenAIP /airspaces endpoint uses both numeric type codes and standard aviation abbreviations. Below are the complete airspace classifications:

ATS Airspace Types

Special Use Airspace

Sample Query

curl -H "Accept: application/json" \
  "https://api.core.openaip.net/api/airspaces?bbox=115.888,32.106,115.891,-32.100&limit=500&apiKey=YOUR_KEY"