Project · Domain & Environmental
Port & Coastal Air-Surface Intelligence
Build a coherent picture where coastal airspace and surface activity meet.
Evidence levelE0Concept
Split-horizon timeline
Interactive view
Data status: Illustrative
Air tracks above a waterline and surface tracks below it, on one time axis. Switch cooperative reports and independent observation on and off. Threads join an air track to a surface track only when both exist, and a cooperative-only picture is flagged incomplete.
CooperativeIndependentCorrelation thread
Surface picture
Partial: independent observation only
Correlation threads: 2 / 2
The tracks and the waterline are invented and symbolic. There is no coast, route or vessel.
Why this exists
At a coast or a port the surface picture and the air picture are kept apart, and the surface picture is often built from cooperative reports that are incomplete by nature. Joining the two without saying what is missing produces a tidy picture that is wrong.
What it takes in
Each input adds something and leaves something unproven.
- Surface tracksCooperative reports and independent observation of activity on the water and at the quay, kept as separate contributions. No port, route or vessel is described here.
- Air tracksLow-altitude observations from passive and optical sensing, taken from the projects that produce them.
- Environmental contextConditions at the coast, such as sea clutter and visibility, that change what each source can support.
How it works
Three steps, in the order the state is formed.
- Builds on passive sensing, electro-optical sensing and fusion from other projects; no dedicated sea-surface sensor is claimed.
- Relates approved surface tracks to low-altitude observations through correlation threads that are drawn only when both ends exist.
- Adds environmental context, so that a degraded view is shown as degraded.
- A split horizon: surface below the waterline and air above, on one shared time axis.
- A picture built from cooperative reports alone is flagged incomplete.
- Cooperative and independent contributions are always told apart.
- An application, not a sensor.
Where it sits in the architecture
Port and coastal intelligence is an application of the core platform. It takes air observations and surface tracks that other projects supply, relates them across the waterline and presents one picture in which it is clear which contribution is cooperative and which is independent. It adds no sensing of its own.
| Stage | Value |
|---|---|
| 1 | Sources |
| 2 | Model |
| 3 | Policy |
| 4 | Interface |
| 5 | Consumer |
| 6 | Audit |
Evidence and assurance
What has been shown, to which level, and what has not.
Evidence ladder
- E0 · Concept reached
- E1 not reached
- E2 not reached
- E3 not reached
- E4 not reached
- E5 not reached
Project assurance panel
- Mission and context
- Give a coast or a port one connected picture of air and surface activity, in which incomplete cooperative data is not mistaken for a full account.
- Primary contribution
- A split-horizon timeline of air and surface tracks, cross-domain correlation threads and a visible account of what each source contributes.
- Decision value
- Lets a reviewer see where air and surface activity meet, and where the surface picture rests on cooperative reports alone.
- Evidence status
- Evidence level: E0 · Concept Concept and research direction only. No specification, prototype, test result or deployment is claimed.
- Next validation step
- Write down how surface tracks are related to air observations and what makes a picture incomplete, then specify a first review of a synthetic coast before any claim is made.
- Behaviour when degraded
- When independent observation is missing, the surface picture is flagged incomplete and no correlation thread is drawn. When sea clutter or poor visibility reduce a source, its tracks are marked as less certain.
- Role in integration
- Would take the unified state from the core platform and the fusion engine and expose it through the data API. It does not feed port or maritime control systems.
- Human review
- A person reviews every picture in which air and surface activity are joined, and the account of which contribution is cooperative and which is independent.
- Public-safe limitation
- No port, coast, route, vessel or procedure is described. The timeline on this page uses invented tracks.
- Open unknowns
- How surface and air tracks should be matched, what makes a picture incomplete and how sea conditions should be weighed are not yet known.
When inputs degrade
When independent observation is missing, the surface picture is flagged incomplete and no correlation thread is drawn. When sea clutter or poor visibility reduce a source, its tracks are marked as less certain.
- Normal
- Degraded
- Unavailable
| Time (relative) | Component 1 | Component 2 | Component 3 |
|---|---|---|---|
| 1 | Normal | Normal | Normal |
| 2 | Normal | Normal | Normal |
| 3 | Normal | Normal | Normal |
| 4 | Normal | Normal | Unavailable |
| 5 | Normal | Normal | Unavailable |
| 6 | Normal | Degraded | Normal |
| 7 | Normal | Degraded | Normal |
| 8 | Degraded | Normal | Normal |
| 9 | Degraded | Normal | Degraded |
| 10 | Normal | Normal | Normal |
| 11 | Normal | Normal | Normal |
| 12 | Normal | Normal | Normal |
Where it applies
A port that wants air and surface activity in one picture
- Why it matters here
- The two pictures are kept in different systems, and the places where they meet are the hardest to see.
- What it contributes
- A timeline with a waterline in which threads join related tracks.
- What it does not replace
- Port or maritime control systems, or the people who run them.
A coast where cooperative reports are all there is
- Why it matters here
- A tidy surface picture can hide the fact that it only shows who chose to report.
- What it contributes
- A flag that says the picture is incomplete and what independent observation would add.
- What it does not replace
- A full surface surveillance system.
Role in the data flow
Would take the unified state from the core platform and the fusion engine and expose it through the data API. It does not feed port or maritime control systems.
Validation path
Write down how surface tracks are related to air observations and what makes a picture incomplete, then specify a first review of a synthetic coast before any claim is made.
| Item | Defined | Prototype | Integrated | Field |
|---|---|---|---|---|
| Module A | Done | In progress | Not started | Not started |
| Module B | Done | Not started | Not started | Not started |
| Module C | In progress | Not started | Not started | Not started |
Limitations
- This is a concept. There is no specification, prototype or measured result behind it.
- The timeline uses invented tracks and a symbolic waterline. It shows how the two domains are kept apart and joined, not how any coast behaves.
- No dedicated sea-surface sensor is claimed. The project depends on sensing from other projects, whose evidence is at the same early stage.
- A correlation thread is a hypothesis that two tracks belong together. It is not an identification.
Related projects
Each link says why the two belong together.