ASCII City Engine

Build a portable city experience in three layers: an engine, a city-provider contract, and a city pack. Keep city-specific facts out of engine code.

Workflow

1. Define the pack boundary and local meter-based CRS.
2. Acquire elevation, building, and road/path data from public sources.
3. Verify downloads, licenses, units, and provenance before conversion.
4. Reproject all geometry to local meters and emit the manifest plus world tiles.
5. Validate the pack offline:

   python3 scripts/validate-city-pack.py path/to/city-pack
   

6. Load the pack's first tile in assets/ascii-city-engine.html and test movement, grade following, and solid footprints.
7. Record data limitations and human acceptance evidence.

Required invariants