Solution
Cities & Regional Airspace
Build a shared airspace model across connected geography.
Operating context
A city or a region is not one site. It is many local situations, each watched by someone, that become a regional picture only if they can be joined without erasing what each one knew.
Questions asked here
- How do local pictures combine into one regional picture, and what is lost on the way?
- Which areas are covered by sources, and which are not?
- Who may see which part, and is that written into the picture?
What is difficult today
Each site builds its own view in its own format. Joining them usually means flattening them: the region sees a single dot and loses the sources, the times and the doubt that came with each local report.
Operational flow
Where the weight falls in this environment
- Observe
- Correlate
- Verify
- Track
- Understand
- Prioritise review
- Alert
- Record
- Review
- Improve
The weight falls on delivering and scaling: nodes keep their local state, a regional layer joins them with the origin intact, and access is governed.
A worked environment state
Three moments from a synthetic scenario, in relative terms.
| Moment | What is seen | What is stated |
|---|---|---|
| 1 | Two neighbouring sites each hold a local state | Each keeps its own sources and its own confidence |
| 2 | The regional layer joins them | The joined state links back to both and shows where they disagree |
| 3 | A partner agency asks for a view | It receives only the part it is allowed to see, with the origin intact |
| Stage | Value |
|---|---|
| E0 Concept | Reached |
| E1 Architecture Defined | Reached |
| E2 Prototype Validated | Not yet reached |
| E3 Integrated Validation | Not yet reached |
| E4 Controlled Field Validation | Not yet reached |
| E5 Qualified / Operational | Not yet reached |
Twin and context view
The same state can be opened in the digital twin, where its layers, its sources and its record sit side by side.
What we can show today
This page claims nothing above the level of the projects it rests on.
- Airspace Intelligence Core PlatformEvidence level: E1 · Architecture Defined
- Distributed Passive Radar NetworkEvidence level: E0 · Concept
- City / Regional Low-Altitude Airspace NetworkEvidence level: E0 · Concept
- Airspace Data & Intelligence APIEvidence level: E0 · Concept
- Near-Ground Airspace Intelligence NetworkEvidence level: E0 · Concept
What this does not claim
- The regional picture is described as a design; no network has been built or measured.
- Scale is a goal of the architecture. No number of sites, users or objects is stated.
- Governed access is part of the design; the page describes no agreement with any authority.
Responsible positioning
AIR NEXUS describes a shared model; it does not run a city's airspace. Who may see what, and what is done with it, is set by the authorities and operators involved.
Projects behind this
- Airspace Intelligence Core PlatformTurn fragmented observations into a reviewable airspace state.
- Distributed Passive Radar NetworkMany quiet observers. One evidence-aware regional state.
- City / Regional Low-Altitude Airspace NetworkBuild a regional airspace picture from observations that were never complete on their own.
- Airspace Data & Intelligence APIDeliver airspace state without stripping away the evidence behind it.
- Near-Ground Airspace Intelligence NetworkBuild a coherent airspace state where terrain, structures and clutter make every observation harder to interpret.