Military data arrives keyed by grid square, not latitude and longitude. The batch importer ingests CSV, TSV, and SQLite files and converts MGRS and GARS references into real geometry automatically.
Field data — checkpoint lists, target decks, sensor logs, unit locations — commonly arrives in spreadsheets keyed by MGRS or GARS. The importer scans your file, auto-detects the coordinate columns, and builds a DuckDB table with proper WGS84 geometry ready for spatial queries and map display.
| Input Format | Coordinate Types | Output |
|---|---|---|
| CSV / TSV | MGRS, GARS, lat/lon (auto-detected) | DuckDB table with WGS84 geometry |
| SQLite | MGRS, GARS, lat/lon columns | DuckDB table with WGS84 geometry |
| Any of the above | lat/lon only | Enriched with MGRS/GARS reference columns |
Higher headquarters sends a spreadsheet of named areas of interest keyed by MGRS. One import later they're geometry in DuckDB: visible on the ATAK map, joinable against your mission data, searchable in the attribute table, and servable to the map through the in-app OGC endpoints.
Imported tables flow into everything else: DuckDB spatial joins, the attribute table with search, H3 aggregation, OGC API Features serving with CQL filtering, and GeoPackage export for sharing back out.