LIVE COVERAGE DEMO · API-BACKED

A fully-modeled city core: Times Square, NYC

In Midtown Manhattan the story flips. A dense urban core reads as uniformly drone-sensitive, so augmented reality becomes the active preference layer — coloured here across Broadway theatres, transit hubs, public plazas, and ~1,150 buildings.

Raleigh, NCTimes Square, NYCSoFi Stadium, LA
Demonstration dataset — All values are the registry's own informational preferences, time windows, and advisory notes. Individual location preferences shown here are illustrative examples only and do not represent actual property-owner submissions, and are kept separate from the live community registry.

Loading live demo data…

Why this matters for UTM / drone / AR operators

A planning tool queries one endpoint and gets machine-readable preferences for an entire area — each footprint with a drone and AR preference, optional activity categories, an advisory note, and optional time windows. The same contract scales from one place to the whole registry.

GET https://airspaceregistry.org/api/v1/demo/preferences?region=times_squareView raw GeoJSON ↗

These are live endpoints, not screenshots — no key required. This area query returns a GeoJSON FeatureCollection; the same dataset also answers a single point (/api/v1/demo/resolve?lat=&lon=) and a point in time (&datetime=), returning the governing record — a preference or a reference to an existing rule — as informational metadata, not a go/no-go. See the API docs for all three.

Preferences are informational and voluntary — a metadata layer. They are not enforceable and are not permissions.