Stage 07
A detection is a fact. Cross-referencing it, watching it recur, fusing it with an independent data stream — that is where a fact becomes something you can act on. Every signal on this page is described for exactly what it proves, and what it does not.
Atmospheric fusion
Two independent, real data streams over the same footprint — a gas concentration and the wind that moves it — rendered as one map layer instead of two datasets you have to align yourself.
SO2 column density from the Sentinel-5P TROPOMI instrument, regridded onto a regular lat/lon grid and rendered as a six-stop heat ramp (blue through red). NOAA GFS 10 m wind is sampled on a 13×13 grid over the same footprint and drawn as directional arrows — so concentration and drift direction read as one picture, for volcanic SO2, refinery and industrial plumes, or cross-border pollution events.
Both sources are queried live for the AOI and date requested — the SO2 swath via Copernicus' Data Space Ecosystem (CDSE), the wind field from NOAA's public GFS archive. The source granule is cached once per scene, shared across jobs, so re-rendering the same footprint does not re-download it.
Atmospheric Fusion · SO2 column density + wind vectors, Sunda Strait
Correlation & tracking
No new sensor, no new provider — these cross-reference detections, orbital data and tasking history that SatView already collects.
A ship detection is checked against real AIS broadcast positions within 3 km and ±30 minutes. A match narrows down which vessel it likely is; no match flags it as a dark-vessel candidate. AIS history only goes back as far as SatView has been watching an area — never backfilled.
Vehicle, ship and aircraft detections are clustered by position (150 m) across repeated passes. One sighting is just that; two or more at the same spot is surfaced as recurring activity worth watching over time.
Every TLE update is compared against the satellite's previous one. A mean-motion jump past 0.005 rev/day, or an inclination change past 0.05°, is logged as a maneuver candidate — a lead to verify, not a confirmed burn.
Give SatView an AOI and it answers a different question: which satellites, across the full 500+ catalog, will pass over it in the next few days — not just the ones you already selected. A quick way to know who else might be watching the same ground.
Before a fresh tasking order goes out, SatView checks the last 30 days of archive across your connected providers for the same footprint and cloud constraint. A hit surfaces as a pre-filled shortcut into catalog search — archive imagery typically runs 30-50% cheaper than tasking, a sector rule of thumb SatView surfaces rather than a quoted price.
A detection's popup does not collapse everything into one invented percentage. It shows the model's own detection score, an AIS-correlation confidence tier where it applies, and a recurrence count — three real signals, kept separate.
Detection popup · model score and inference method shown per object
Every one of these can trigger a monitoring rule and a notification, not just a map marker.
Tell us about your mission — we will get back to you.