Gods Eye View Roadmap: Upcoming Features and Development Plans Revealed

The Gods Eye View roadmap centers on four engineering priorities: native follow-camera implementation, new data probes including tracked-orbit and fly_route, bundled dataset error surfacing, and a public hosted version—tracked via GitHub issues and inline code comments.

This live-globe visualization platform continues to evolve through incremental improvements documented across its codebase. Rather than a static planning document, the Gods Eye View roadmap lives in source comments, dedicated documentation files, and the repository's issue tracker. Here's what the development team has committed to building next, directly from the source code analysis.

Native Follow Camera Implementation

The most significant camera system improvement planned is true native follow-camera support. Currently, camera tracking relies on workarounds that will be replaced with proper attachment logic.

In src/cameraVerbs.js, line 1036 contains an explicit roadmap marker:

// from src/cameraVerbs.js around line 1036
// until tracked-orbit rides the follow camera natively (roadmap).

This comment indicates that the tracked-orbit camera mode needs to depend on follow-camera infrastructure before it can function as designed. The planned API will allow seamless camera attachment to moving targets such as aircraft or vessels without frame-by-frame manual updates.

Related groundwork appears in src/data/meshFloorSampler.js at line 159, where the fly_route probe is marked for bundling with this follow-camera system:

// from src/data/meshFloorSampler.js around line 159
// the project roadmap, which bundles it with the fly_route probe so

These two files demonstrate how camera and data sampling improvements are being architected together rather than as isolated features.

Tracked-Orbit and Fly_Route Probes

The L7 roadmap items reference specific probe implementations that extend the platform's data interrogation capabilities:

Probe	Purpose	Implementation Status
tracked-orbit	Camera that maintains orbital perspective while locked to a moving target	Commented in src/cameraVerbs.js, awaiting follow-camera foundation
fly_route	Path-based sampling probe for corridor analysis	Referenced in src/data/meshFloorSampler.js as bundled deliverable

These probes represent a shift from static camera positions toward dynamic, target-relative visualization modes essential for tracking time-series data across the globe.

Bundled Dataset Failure Surfacing

A concrete quality-of-life improvement appears in src/data/localGeojson.test.mjs at line 461:

// Bundled-dataset failure surfacing (roadmap L7)

This roadmap item addresses error handling for static bundled datasets—including datacenters, dams, and other infrastructure layers currently shipped with the application. Rather than failing silently, future versions will surface these failures as user-visible errors, improving debugging and operational transparency.

The test file location suggests this feature includes comprehensive test coverage before implementation, indicating a test-driven approach to this roadmap milestone.

Performance Optimization Targets

The docs/PERFORMANCE.md file establishes measurable targets for upcoming releases. While specific metrics aren't extracted as roadmap items, the document structure implies continuous performance work across:

• Startup latency reduction
• Cache efficiency improvements
• Budget governor tightening for rendering and data fetching

Unlike discrete roadmap features, performance work is treated as an ongoing engineering priority with documented baselines.

Voice and AI System Extensions

The src/voice/ directory contains the current OpenAI Realtime integration, but source comments and documentation hint at broader provider support. Future roadmap work includes:

• Alternative LLM provider support (beyond OpenAI to potential Gemini integration)
• Cost metering UI improvements for voice-controlled operations
• Expanded voice command vocabulary for hands-free globe navigation

These enhancements target the platform's accessibility and operational cost transparency.

Public Hosted Version

The README.md contains an explicit commitment in its "What's Next" section: a hosted version is coming. This represents a strategic shift from the current self-hosted model toward a zero-install web service, dramatically lowering the barrier to entry for new users.

This hosted offering will likely necessitate infrastructure work across authentication (already partially implemented per docs/opensky-auth.md), rate limiting, and session management.

Definitive Roadmap Location: GitHub Issues

The docs/KNOWN-ISSUES.md file explicitly redirects roadmap inquiries:

For the roadmap and open backlog, see the repository issue tracker.

This establishes the GitHub issue tracker as the single source of truth for upcoming work. The inline code comments and documentation references analyzed here represent committed engineering direction, but priorities and timelines are managed through the issue workflow.

Summary

• Native follow-camera support is the foundational architecture change enabling multiple dependent features
• Tracked-orbit and fly_route probes extends dynamic camera and data sampling capabilities
• Bundled dataset error surfacing (L7) improves operational reliability for static data layers
• Performance targets are established in dedicated documentation with measurable baselines
• Voice/AI expansion includes provider flexibility and cost transparency improvements
• Hosted version represents the major distribution model shift currently in development
• GitHub issue tracker serves as the authoritative, up-to-date backlog beyond static documentation

Frequently Asked Questions

Where is the official Gods Eye View roadmap documented?

The official roadmap lives in the GitHub issue tracker, as explicitly stated in docs/KNOWN-ISSUES.md. Engineering direction also appears in inline source code comments—particularly in src/cameraVerbs.js, src/data/meshFloorSampler.js, and src/data/localGeojson.test.mjs—which mark specific features as "roadmap" or "L7" items. No single static roadmap file exists; the project uses distributed documentation plus issue tracking.

What does "L7" mean in the Gods Eye View roadmap comments?

"L7" appears as a milestone or priority marker in roadmap comments, notably in src/data/meshFloorSampler.js and src/data/localGeojson.test.mjs. While the exact meaning isn't documented in analyzed files, it likely represents a release level or tier within the project's planning system—possibly indicating features scheduled for a seventh iteration or layer of functionality.

Is there a public timeline for the hosted version of Gods Eye View?

The README.md confirms a hosted version is planned with the statement "a hosted version is coming," but no specific date or quarter is provided in available documentation. Given the project's use of GitHub issues for roadmap management, timeline information would appear there rather than in committed source files.

How can I contribute to roadmap features like the follow camera?

Contributors should start with the code comments marking roadmap items—particularly the follow-camera reference in src/cameraVerbs.js line 1036 and the fly_route probe bundling note in src/data/meshFloorSampler.js line 159. These comments indicate architectural dependencies that must be respected. Opening or reviewing related GitHub issues before starting work ensures alignment with maintainer priorities.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}