Design a hybrid pipeline where Python handles compute-heavy stages (OSM parse, elevation triangulation, heightmap stamping, mesh geometry) and Unity handles only asset creation (Mesh, TerrainData, Prefab). Key questions: Which stages move to Python (pyosmium, scipy, numpy, shapely, triangle)? What is the interchange format (binary .bin per chunk vs JSON)? How does the Unity importer change? What is the CLI interface? Output: design.md + architecture diagram + implementation issue list.
Only proceed after #58 timing confirms compute (not AssetDatabase I/O) is the dominant bottleneck.
Discovered from #55.
Design a hybrid pipeline where Python handles compute-heavy stages (OSM parse, elevation triangulation, heightmap stamping, mesh geometry) and Unity handles only asset creation (Mesh, TerrainData, Prefab). Key questions: Which stages move to Python (pyosmium, scipy, numpy, shapely, triangle)? What is the interchange format (binary .bin per chunk vs JSON)? How does the Unity importer change? What is the CLI interface? Output: design.md + architecture diagram + implementation issue list.
Only proceed after #58 timing confirms compute (not AssetDatabase I/O) is the dominant bottleneck.
Discovered from #55.