NOTAM Data APIs (v2)

This page allows you to explore the NOTAM APIs available on the Laminar Data Hub and makes it ease for you to make queries and view live data. Along with your user key, fill in the parameters for the desired API and click 'Try it out!'. If you don't have a user key, Sign Up here for a Laminar Hub Account.

There are many different types of NOTAMs in the aviation industry all of which are difficult to decipher. Some are mandatory or regulatory in nature, others advise pilots and other airspace operators, such as drone operators, of a closed airspace or runway, obstacles, or even alert airports and airlines about a nearby flock of birds.

Our Laminar Data Hub APIs make it EASY and SIMPLE to access, view and utilize NOTAMS in your applications and workflows. We also published Top 7 Things to Know About NOTAMS that describes key things you need to know about NOTAMS.

You can access our previous release here: NOTAM Data APIs (v1).

The APIs listed on this page have Global data coverage.

 

Features

The API publishes GeoJSON feature types. All features have an id that uniquely identifies the NOTAM. The following fields are currently published as feature properties:

Field Required Description
series No The series letter that identifies the NOTAM. Most US domestic NOTAMs are not issued with a series.
number Yes The incrementing number that identifies the NOTAM.
year Yes The issue year that identifies the NOTAM.
lat No The latitude of the centre point of effect of the NOTAM.
lon No The longitude of the centre point of effect of the NOTAM.
location Yes Identification of the ICAO location indicator in which the facility, airspace or condition reported on is located. Note that for some domestic NOTAM types this may be a local-specific aerodrome code rather than an ICAO location indicator.
affectedFIR No The ICAO location indicator of affected FIR or, if applicable to more than one FIR within a State, the first two letters of the ICAO location indicator of a State plus "XX".
issued No The instant at which the NOTAM was issued.
maximumFL No The overall upper limit of all volumes the NOTAM affects expressed as a flight level. Note that for many NOTAMs this limit is omitted or left to a default of `999`, which is often higher than the actual upper limit.
minimumFL No The overall lower limit of all volumes the NOTAM affects expressed as a flight level. Note that for many NOTAMs this limit is omitted or left to a default of `0`, which is often lower than the actual lower limit.
purpose No Enumerated value classifying the distribution of the NOTAM. See below.
scope No Enumerated value describing the broad aeronautical feature the NOTAM affects. See below.
qcode No The "Q-Code" summarising the content of the NOTAM. See ICAO document 8126 for more details.
traffic No Enumerated value stating the type of traffic affected by the NOTAM. See below.
type No Enumerated value of `N` for a new NOTAM, `R` for a NOTAM replacing another, `C` for a NOTAM cancelling another.
effectiveStart No The instant at which the NOTAM is applicable.
effectiveEnd No The instant at which the NOTAM ceases to be applicable.
text No The text content of the NOTAM.
publisherNOF Yes An identifier of the authority that issued the NOTAM.
translations No Expressions of the NOTAM in different formats.
translations[n]/type No The type of format in which the translation has been made.
translations[n]/language No The language of the translation.
translations[n]/simpleText No The translation content in plain text without any markup.
translations[n]/formattedText No The translation content with HTML markup.
relationship/affectedFIR No Links to the FIR object the NOTAM affects. Only applicable when apparent from the NOTAM and only one FIR is affected.
relationship/affectedFIR/id Yes The four letter designator of the FIR.
relationship/affectedFIR/href Yes A link to the canonical representation of the FIR object in the Laminar API.
relationship/reference No Details of the NOTAM that has been cancelled or replaced by this NOTAM. Only applicable when apparent from a replacement or cancellation NOTAM.
relationship/reference/series No The series of the referred NOTAM.
relationship/reference/number Yes The sequence number of the referred NOTAM.
relationship/reference/year Yes The year of the referred NOTAM.

Purpose

The possible values of the purpose field are as follows:

Scope

The possible values of the scope field are as follows:

Any combination of these codes may appear.

Traffic

The possible values of the traffic field are as follows:

Geometries

The API attempts to obtain a geometry for each NOTAM. Geometries are currently either taken from the center point and radius stated in the NOTAM Q-line, or inferred from the text content of the NOTAM.

Geometries are published in GeoJSON form. Currently, the geometry member of each Feature will either be null where a geometry is not available, or a GeoJSON geometry object of type GeometryCollection where a geometry has been obtained. The type of geometries within the GeometryCollection will be Polygon. Clients should be compliant with the full GeoJSON specification, and be prepared to accept other types of GeoJSON geometry object on the geometry member or within a GeometryCollection in the future.

Each geometry object within the collection represents a volume of space the NOTAM affects. Since there is no standard way to express a volume with upper and lower bounds in GeoJSON, the geometry objects are extended in order to encapsulate this additional information. The properties upperLimit and lowerLimit are added, which describe the maximum and minimum vertical limits respectively.

An example of this representation is shown below:

{
    "id": "2d6fb513-5512-432b-9eaf-cda8ab643e0d",
    "type": "Feature",
    "geometry": {
        "type": "Polygon",
        "coordinates": [ ... ],
        "lowerLimit": {
            "reference": "SFC"
        },
        "upperLimit": {
            "reference": "AMSL",
            "uom": "FEET",
            "value": 6000.0
        }
    },
    "properties": {
        ...
    }
}

Note that the upperLimit and lowerLimit properties are optional. As a general principle, the API does not create additional information that did not exist on the input. If the information is unavailable, you may assume the NOTAM has a surface lower limit and unlimited upper limit.

The following properties are defined under upperLimit and lowerLimit: