A full geospatial stack — analytical database, attribute table, OGC API server, and GL rendering engine — embedded directly inside ATAK on your Android device.
At the core of the plugin is DuckDB with its spatial extension — an embedded, columnar analytical database purpose-built for fast aggregations and complex spatial queries. Run SQL against millions of features with sub-second performance, entirely offline.
The plugin runs a loopback-only HTTP server inside ATAK that turns local data into standards-compliant map services — the serving stack that normally lives in a data center, running in your pocket:
| Service | Sources | Output | Filtering |
|---|---|---|---|
| OGC API Features | GeoPackage vector features, DuckDB tables | GeoJSON (KML / Shapefile export) | CQL |
| OGC API Tiles — Dynamic Vector Tiles | DuckDB, GeoPackage vector layers | MVT generated on demand | CQL / BBox |
| GeoPackage Vector Tiles | GPKG tile pyramids | MVT / raster tiles | Zoom / BBox |
| PMTiles Vector Tiles | Single-file cloud-optimized archives | MVT | Zoom / BBox |
| MBTiles OSM Vector Tiles | Offline OSM basemap archives (OpenMapTiles schema) | MVT → styled PNG via GL renderer | Zoom / BBox |
| GL Style Renderer | GL JSON stylesheets over any vector tile source | Dynamic PNG raster tiles (XYZ) | Style layers |
ATAK does not support GL JSON styles, sprites, or glyphs natively — its map view consumes raster tile sources. That's the gap this pipeline closes: the plugin uses MapLibre GL Native as an off-screen renderer, applying any GL JSON stylesheet — with its sprites and glyphs — against local vector tiles and serving the result as dynamic PNG raster tiles, registered with ATAK as a standard XYZ map source.
Pre-load a GeoPackage with terrain, infrastructure, and threat layers plus a PMTiles basemap of the AO. In the field, DuckDB answers "every bridge within 5 km of the route" with a spatial join, the attribute table pins down the specific feature by name, and the GL renderer serves the styled basemap to ATAK — all without a single network packet leaving the device.
Before going offline, discover and stage data through the unified catalog search — OGC API Records, CSW, STAC, CKAN, Socrata, and THREDDS endpoints (USGS, NOAA, NASA, EuroGEOSS and more), plus AOI-clipped downloads from ESRI FeatureServer / MapServer / ImageServer and OGC services. Results export to GeoPackage for the offline serving stack. API-key-gated sources (such as USGS EarthExplorer M2M) clearly indicate when a key is required.