Overview

In God's Eye View, selection defines the center and scope of an investigation rather than the subject's significance. Contacts uses a 250-kilometer air and sea proximity window, while mapped installations remain viewport-bounded; counts name their scope and distinguish zero, unknown, stale, and unavailable. Aircraft tracking, one-time framing, Cockpit, and Space Missions are camera-owning modes with different entry, cancellation, and restoration rules. Contacts and voice share one aircraft-proximity computation, but this consistency does not make the underlying coverage complete. Mission replay can use supplied trajectory samples or a labeled RECONSTRUCTED ESTIMATE, and a retained planned orbit does not prove a failed launch reached orbit. These modes make relationships easier to inspect without turning proximity into threat or replay into telemetry.

Learning outcomes

A 250-kilometer Contacts window answers a defined proximity question; it is not a radar range, sensor footprint, or tactical assessment.
Camera modes own different transitions: tracking follows an aircraft, framing returns control after one move, and Cockpit or replay must be exited and restored deliberately.
Mission replay explains launch geometry with supplied or reconstructed paths, but reconstruction and planned orbits do not establish telemetry or successful insertion.

Keywords

God's Eye ViewSelectionContactsCockpitReplayTracking

Giving the Globe a Point of View

In God's Eye View, selecting an object does more than make it brighter. Selection can define the center of a 250-kilometer context window, change which counts appear, assign a camera owner, and open a mode with its own allowed data. This chapter follows those transitions through Contacts, aircraft tracking, Cockpit, and Space Missions. The practical judgment is important: a focused view can make relationships easier to investigate, but it must not turn proximity into threat, coverage into certainty, or a replay into telemetry.

A selected subject defines scope, not significance

The Context system begins with a subject and a radius. Around a selected aircraft, vessel, or mapped installation, God's Eye View builds cohorts of nearby flights, military flights, AIS vessels, and mapped installations. It reports counts, nearby examples, source labels, freshness, and reasons for uncertainty. The radius is 250 kilometers for the air and sea proximity cohorts. It is a window for navigation and comparison, not a radar range, a sensor footprint, a weapon envelope, or an assessment of what matters operationally.

The installation cohort has an additional boundary. Mapped installations come from viewport-bounded OpenStreetMap context, so the panel labels that result as current viewport only. It does not silently expand a local map query into a complete regional survey. A site omitted from the loaded map may be unmapped, outside the request, or unavailable from the source. The absence is not evidence that the site does not exist.

The interface also distinguishes an answer from the absence of an answer. A source that is still loading and has never produced a usable record is not presented as zero. It is unknown. A previously accepted source whose freshness has degraded can remain visible as stale. A source that cannot currently support the request is unavailable. Those states matter because “zero vessels nearby” and “the vessel source has not answered yet” lead to different decisions.

The count itself is carefully shared. The Contacts panel and the voice analyst's entity-centered “how many nearby?” question use one aircraft-proximity computation. Earlier, two paths could answer from different collections: the panel used a broad live-position set while the analyst used a smaller slice of last-fix records. Both numbers could be internally defensible and still disagree badly for the same subject. Routing both surfaces through the same engine makes their aircraft count identical by construction.

That shared computation does not make every count in the application identical. God's Eye View has several legitimate scopes. The Contacts window counts contacts in the fixed radius around its subject. An analyst query can count currently loaded records for a requested view or place. A layer can also report its loaded total. The flights layer loads according to where the camera looks, so a view-scoped loaded count may be lower than a full proximity-window count after the user dives to a new location. The interface therefore names the scope in words instead of offering a bare number.

A selected subject can also move.

Published by DeepMox

FAQ

What does the 250-kilometer Contacts window mean in God's Eye View?

It is a fixed proximity window around the selected subject for comparing nearby flights, vessels, and other cohorts; it is not a radar range or tactical assessment. Mapped installations are separately identified as viewport-bounded context.

Why can a camera action be refused in God's Eye View?

A camera action can be refused or deferred when another mode or tracker currently owns the camera. Cockpit, aircraft follow, and Space Missions each impose ownership and dependency rules so a late or competing action cannot silently take control.

Does God's Eye View replay show an actual launch path?

Only where the source supplies trajectory samples; otherwise the application shows a labeled RECONSTRUCTED ESTIMATE. The replay can explain launch geometry, but reconstructed motion is not continuous ascent telemetry, and a planned orbit does not prove successful insertion after a failed launch.

Previous9 minGod's Eye View: Keeping Labels Readable

Next11 minGod's Eye View: Voice and Map Annotations

God's Eye View: Selection and Camera Modes

Giving the Globe a Point of View

A selected subject defines scope, not significance

FAQ