Data Viz
In Development

Battlefield Overview.

A common operating picture on real ground — BLUEFOR and OPFOR maneuvering across the JMRC training area at Hohenfels, Germany. Real terrain, real roads, rendered entirely in the browser with nothing streamed.

Canvas 2D SRTM Terrain OpenStreetMap Offline Vanilla JS
Demo only, not final product

Marketing Slop.

100%

Offline

Terrain and roads are baked at build time into the page itself. No tile servers, no API keys, no network at runtime — it runs on an air-gapped laptop.

REAL

Ground Truth

Elevation from SRTM and the road network from OpenStreetMap — the actual Hohenfels terrain and trace, not a stylized stand-in.

2

Two Forces

BLUEFOR and OPFOR move as convoys along the road net, hold in assembly areas, and screen key terrain — the shape of a rotation at a glance.

0

Dependencies

Pure Canvas 2D. No Three.js, no map library, no framework — one file, a few hundred lines, drops into any page.

3D

Oblique View

A slow drone-angle camera over slope-shaded terrain — the operational picture reads as ground, not a flat map.

Any AO

Swap the bbox and re-bake — the same engine renders any training area or operating environment on Earth.

Nerd Out.

The takeaway.

A rotation at the JMRC is thousands of moving parts across forty square kilometers of Bavarian hills. The picture that ties it together — who is where, moving which way — usually lives on a streamed tactical map that needs connectivity, licensing, and a server behind it.

This is the opposite bet: bake the ground truth once, ship it inside a single file, and let it run anywhere — a planning laptop, a kiosk, a briefing screen with no network at all. The engine started as an aircraft showcase; pointing it at Hohenfels showed the same offline-first approach scales straight from one airfield to a whole maneuver box.