Skip to content

Map and reference time

The map can run in 2D or Globe mode and follows the same reference-time controller as intelligence workspaces.

Live mode

Live shows aircraft and other entities within the selected freshness window. For example, Last 5 minutes retains every aircraft observed within five minutes and removes it only after it crosses that boundary. A per-second counter update must not blink markers, labels, stems, or trails.

Aircraft markers interpolate between decoded positions. The trail remains the authoritative observed route. Selecting an aircraft shows its full retained trail; Flight Trails shows all, while Military Paths independently shows confident government/military paths.

Historical mode

Selecting 24 hours or an explicit reference time issues bounded indexed queries. It may take more work than Live, but returning to Live invalidates the historical generation, drops its presentation cache, and resumes current keyed deltas promptly.

Future state cannot leak into the selected time. Product issue/validity/ expiration, aircraft observation time, orbital time, celestial scene, and terminator all follow the reference model appropriate to their data.

The active lane's capture/timeshift clock owns map time. Playing history advances at its reference-time rate; pausing keeps the inspected moment fixed. Changing lanes or seeking changes that reference explicitly. Map animation ticks are presentation opportunities, not observations or a replacement clock. For missing-clock behavior, see the architecture caveat.

Globe navigation

Left-drag pans; ordinary right-drag orbits/tilts; Shift+right-drag provides a pan alternative. A focused aircraft is a point/vertical volume in 3D, not a surface pin. Focus zoom solves the camera so the aircraft and ground anchor remain intelligible without changing true altitude or clamping a marker to the screen.

Layers and identifiers

Ground Identifiers and aircraft-attached labels are independent. Labels choose the strongest qualified identity and use collision/offset behavior while remaining associated with their marker. Satellite tracks retain orbital altitude. Celestial sky brightness and background color are presentation preferences; star/Sun/Moon positions follow reference time.

Globe's Celestial sky uses local stars and Moon imagery. Exposure and backdrop controls affect presentation, not source positions or solar/lunar measurement. Rewinding IQ also rewinds the sky, terminator and greyline; it does not leave today's Sun above yesterday's capture.

Local and online basemaps

Local light/dark geographic styles, boundaries, labels, map runtime, geocoding and orbital/celestial references are appliance-served. Optional Online vector, Online vector dark and photographic satellite imagery are explicitly selected Internet-backed alternatives. They are geographic reference imagery, not received RF evidence. Choosing them does not enable external RF-data uploads. The online-provider allowance stays narrow; it must not disable browser isolation.

Hidden surfaces

Minimizing or hiding the map suspends presentation conversion and drawing while ingestion and persistence continue. Reopening catches up from versions/current state rather than reconstructing the archive on the main thread.

A visible pop-out schedules through its own document, so hiding the tuner window must not freeze the map clock. On focus, visibility restoration or pageshow, the view catches up to the current reference and refreshes relevant samples/pass countdowns without replaying missed ticks. Paused history remains at its selected time even though the live edge continues to move.

Acceptance context

The map substrate and later celestial extension have separate dated accepted checkpoints in docs/roadmap/intelligence-maps.md; see map qualification. Remaining protocol/geographic extensions are not implied by a working Globe or a passing documentation build.