f4fcf267c6
Traffic roads come from OpenFreeMap vector tiles, or TomTom flow tiles with a key (Hybrid by default). Military areas use OpenFreeMap polygons with a bundled worldwide name index; wide views show named points. ALPR reads an hourly OpenStreetMap extract. Cockpit place context and country, state and US county outlines use bundled Natural Earth and US Census data. Overpass is used only when an operator configures their own endpoint. Also: camera arrivals no longer land below ground, keyless terrain retries on 429, bounded relation geometry for configured Overpass, one shared OpenStreetMap credit, and separate tile and API transports for embedders. Co-authored-by: theGaryLarson <[email protected]> Co-authored-by: Milan Khanal <[email protected]>
1.3 KiB
Military area names
This database is distributed under ODbL 1.0, separately from the MIT code. © OpenStreetMap contributors. Distribution: Overture Maps Foundation, base/land_use release 2026-09-23.1. OSM snapshots: 2026-09-06, with two named records from 2026-09-12.
Selected named military areas; geometry simplified to interior label points,
bounds and area, coordinates rounded and records re-encoded. Names are unchanged.
Rows: [typedOsmId, name, lon, lat, west, south, east, north, classIndex, areaM2].
Labels use five decimal places; bounds use four. Area is measured on the WGS84
ellipsoid. Class indices refer to classes. Output SHA-256: names.sha256.
Rebuild (maintainer tool; requires Python and duckdb==1.5.5):
python scripts/build-military-names.py --cache /tmp/military-names
python scripts/build-military-names.py --cache /tmp/military-names --verify
The pinned parquet file list and query are in scripts/military-names-files.json
and scripts/military-names.sql. The first build downloads DuckDB extensions and
scans source columns; subsequent builds reuse the cached selected rows.