[Feature] Toggle Space Station Display: Static Icons vs Orbital Overlays #51
Description
Summary
Add a user-configurable toggle (e.g. in the settings panel or map controls) that lets users switch how space stations / orbital objects (from the CelesTrak space watch integration) are visualized on the globe and flat map: either as static point markers/icons (current/default behavior) or as simplified orbital path overlays (curved lines or ground tracks showing approximate/current orbits).
Why This Matters
When many event markers are active (fires, conflicts, air traffic, OSINT events, etc.), the map can become visually cluttered — especially in regions with dense activity. Static icons for space stations (ISS, military constellations, recent launches, etc.) add to this clutter because they represent persistent objects of note rather than transient events. Switching to orbital overlays would:
- Reduce icon density and visual noise on the map
- Make it immediately clear which points are dynamic events vs. fixed/ongoing objects (space assets)
- Provide more context about space objects (showing their orbital paths instead of just a dot)
- Improve clarity and usability during high-event-load scenarios without needing to disable the entire space watch layer
This would make the dashboard more readable and professional for users monitoring multiple sources simultaneously.
Scope
- Dashboard/UI change:
- New source: (minor — leverages existing CelesTrak data, but changes visualization)
Proposed Behavior
- Add a toggle switch labeled something like "Space Stations: Icons / Orbits" (or separate checkboxes: "Show space station icons", "Show orbital paths").
- When "Icons" mode is selected → current behavior: static markers/icons at current positions for ISS, Starlink count aggregations, military sats, etc.
- When "Orbits" mode is selected → replace static icons with distinct orbital overlays:
- Render simplified orbital lines/ground tracks (using current ephemeris from CelesTrak)
- Use unique visual styling to distinguish from flight corridor arcs: e.g. different line color (perhaps cyan/white), dashed/dotted hatching pattern, lower opacity (e.g. 0.4–0.6), thinner line width
- Optionally include a small label or tooltip on hover/click showing object name, NORAD ID, or basic info
- Orbits update on the same refresh interval as other space data
- The toggle should persist across sessions (save in localStorage or user settings if implemented)
- Bonus: allow both modes at once as an advanced option, but default to exclusive (one or the other) to avoid clutter
Maintenance Impact
- Relies on existing CelesTrak integration → no new API keys, rate limits, or paid services
- Adds minor frontend complexity (additional Globe.gl or D3 rendering logic for paths/lines)
- Potential new dependency or increased usage of a globe library method for drawing orbits (but Globe.gl already supports arcs/lines/paths, so likely no new deps)
- Ongoing upkeep: minimal — mostly keeping visualization in sync if CelesTrak schema changes, but same as current space watch maintenance
Additional Context
- Current map often shows dense clusters of event markers (e.g. Middle East conflicts + fires + air traffic); space station dots get lost or contribute to overload.
- Similar projects (e.g. satellite tracking sites like stuffin.space or in-the-sky.org) use orbital ground tracks or 3D paths very effectively to convey motion without clutter.
- Globe.gl docs show support for custom arcs, paths, and polygons — should be feasible to draw approximate orbital curves or ground tracks.
- Example visual distinction idea: flight corridors = solid orange/red arcs; orbital overlays = dashed cyan lines with lower opacity.
Thanks for considering — this small UI enhancement could significantly improve map readability for space + events monitoring!