EYESYNC is a data-fusion and visualisation layer over sensing data CLIICXNET does not itself capture — the same posture Google Earth held toward its imagery providers. It is not a satellite and not a submersible. Every result below is either Confirmed (computed live) or clearly marked as a source we intend to integrate but haven't yet.
Real SGP4 propagation over a live TLE resolved from a public satellite-tracking catalogue — the same category of computation ORBITSYNC already runs, here as a server-side engine for EYESYNC's fusion layer.
EYESYNC does not duplicate SPICE's earth-observation analytics — it sits alongside SPICE as the cross-domain index. For soil moisture, crop, flood, and water-quality intelligence, SPICE is the live production system.
SPICE is already live in beta on Cartosat-3, RESOURCESAT-2A, and Sentinel-1/2 data, with an active 38-district proof of concept covering roughly 72 million people.
Open SPICE →Depth resolved from the GEBCO grid via the ODB GEBCO API — a public, cloud-hosted service built specifically so users query points without downloading GEBCO's multi-gigabyte global grid. Depth is stored as negative elevation, same convention as land height.
The actual point of EYESYNC: one query resolving across two or more domains — for example, what's tracked in orbit above a point, and what the sea floor looks like offshore of it — through a shared WGS84 / ECEF / ECI / depth-datum coordinate fusion engine.
The solution: Space and Undersea are both live now (above) as independent single-domain queries. The fused version — one coordinate, both answers returned together, plus whatever named undersea feature sits nearby via the GEBCO Feature Name Gazetteer — is the next build step, not yet wired up.
The long-horizon ambition behind EYESYNC is CLIICXNET-owned physical sensing — a small-aperture space-domain-awareness payload and a purpose-built undersea platform — pursued only once this software fusion layer has proven its value. This carries the full IN-SPACe / ITU / debris-mitigation / underwater-installation regulatory weight documented in CX-TECH-EYESYNC, and is deliberately out of scope until Phase 1–2 are proven.