EMO Atlas: from maritime history to a connected world view
A working local dashboard combines public feeds while keeping source times, coverage and failures visible.
Body
EMO Atlas is now the main name for the workspace that began as EMO TIDE. The change is more than a label: the existing maritime history now sits beside a searchable globe and multiple selectable data layers.
During verification, weather, wind and aircraft feeds returned current responses after the rendering service was started. The expanded build also received Caribbean AIS observations, USGS earthquake reports and a TfL catalog of public traffic cameras. A separate check retrieved an actual public camera still. These are individual integration checks, not a promise that every feed or camera is continuously available.
The dashboard keeps distinctions visible. A wind animation represents a forecast field. Aircraft positions can be delayed. Public cameras can provide still images rather than continuous video. A catalog entry does not establish successful image delivery.
One workspace, separate sources
The existing Caribbean AIS collector continues to supply ships and preserve voyage history. Atlas reads that local source without copying its credential or opening another AIS connection. The other adapters retrieve their own permitted public feeds and expose source times and availability.
Users can move the globe to a place, switch layers, search aircraft or ships, follow a public aircraft and inspect a registered public camera. The optional imagery and voice connections explain what they require rather than implying an account is already connected.
What the video taught us—and what we verified
zSecurity’s God’s Eye View walkthrough provided the starting point. We reviewed its English auto-generated captions and inspected the upstream project. God’s Eye View by Bilawal Sidhu and CesiumJS remain the credited rendering foundation; EMO’s work is the product integration and its local source boundaries.
Upstream describes road-traffic motion as simulated from aggregate data. Atlas therefore does not advertise it as tracking individual cars. A rendered cockpit perspective is also different from a camera inside an aircraft. Neither is presented as live video in this build.
Local control and practical limits
The map renderer runs on demand and has an idle shutdown. Local host/origin guards, a fixed provider allowlist, bounded requests, separate-origin message checks and safe text rendering remain in place. A dependency advisory and renderer shutdown issue found in the first build were patched. New regression checks preserve the existing mail desk, assistant path and paused worker policies.
The verified local layers need no new account or copied API key. Public endpoints still have quotas and usage terms. High-detail imagery, street imagery and paid cloud voice are separate configurations, and public or commercial deployment needs appropriate provider review. Atlas is not a navigation, emergency-response or private-surveillance product.