NOTAMs

Core NOTAM data structure containing event metadata, the NOTAM detail, and any translations.

Core NOTAM detail fields per NMS API specification. Classification values: INTERNATIONAL, MILITARY, LOCAL_MILITARY, DOMESTIC, FDC Feature values: RWY, TWY, APRON, AD, OBST, NAV, COM, SVC, AIRSPACE, ODP, SID, STAR, CHART, DATA, DVA, IAP, VFP, ROUTE, SPECIAL, SECURITY Series values: A, B, C, D, E, G, H, I, J, K, N, R, V, Z

Represents a NOTAM as a GeoJSON Feature from the NMS API. See nms-api.yaml NmsNotamData schema for full specification.

NOTAM event metadata

Optional filters for narrowing NOTAM query results. All filters are combinable — when multiple filters are provided, results must match all of them (AND logic).

GeoJSON geometry - can be Point, Polygon, or GeometryCollection

Properties of a NOTAM GeoJSON Feature containing the core NOTAM data.

Request body for querying NOTAMs along a flight route. Provide either AirportIdentifiers (simple airport-only routes) or RoutePoints (mixed airports and waypoints). If both are provided, RoutePoints is used and AirportIdentifiers is ignored. NOTAMs from all route points are combined and deduplicated in the response.

Response containing NOTAMs (Notices to Air Missions) matching a query. Each NOTAM is a GeoJSON Feature with geographic geometry and detailed properties. Used by the airport, radius, and route endpoints. The search endpoint uses cursor-based pagination instead.

NOTAM translation in various formats. Type values: LOCAL_FORMAT, ICAO

Cursor-based paginated response wrapper. To retrieve subsequent pages, pass the pagination.nextCursor value as the cursor query parameter in your next request. Continue until pagination.hasMore is false.

A single point along a flight route. Each point is either an airport or a geographic waypoint: Airport point: Set AirportIdentifier. NOTAMs are queried by identifier match (not spatial). Waypoint: Set Latitude and Longitude. NOTAMs are queried by spatial radius search.