GEO Area Pipeline · OpenTopo / OsmAnd
Local map packages and reproducible area definitions: WGS84 bounding boxes, OpenTopoMap XYZ tiles, OsmAnd SQLite and validated area import into Map Geometry.
Problem
Initial situation
Download coverage, local map containers and metric analysis areas are easily confused. Areas need reproducible definitions and imports without overwriting unrelated project objects or their provenance.
Constraints
Boundary conditions
- Strict WGS84 bounding-box/zoom validation and tile budget
- Provider rights and attribution; rate limits alone do not grant offline permission
- Separate tile and geometry outputs
- Explicit analysis origin and conservative 249 km preliminary check
- Dry run, backups, stable object identities and idempotent updates
Solution
Solution
A Python standard-library pipeline defines regions, plans raster packages and checks SQLite/PNG holdings. A separate export converts bounding boxes to geographic WGS84 polygons under the Map-geometry-v1 contract; the saved JSON is manually imported into Map Geometry. Tile packages and browser tile caches remain independent.
Architecture
Architecture
- regions.json: bounding box / zoom / tile budget
- XYZ → SQLite .sqlitedb for OsmAnd
- Resume with build contract / read-only package verification
- WGS84 polygon export with bounding-box/zoom provenance
- Map-geometry-v1 validation / stable source key
- Optional explicit auto-origin / AEQD range gate
- Atomic JSON writes / verified backups / package manifest
Result
Result
The bounding-box export and controlled origin switching are implemented locally. The October 10, 2026 auto-origin report documents 75 tests and a cross-check against the Map Geometry engine; these checks are reported here, not rerun. Map Geometry does not read .sqlitedb directly. Further Geo/ROS adapters are integration possibilities, not a proven end-to-end data pipeline; a current OsmAnd target-device test is missing.