GBGenerate Buildingeneratebuild.hashnode.dev·2d ago · 4 min readHow I Version Object Site Infrastructure Building and City Models Across Five 3D ToolsThe files in a 3D workflow usually fail long before they disappear. They fail when someone opens a model months later and cannot answer where it came from, what it includes, or whether it is safe to r00
GBGenerate Buildingeneratebuild.hashnode.dev·4d ago · 4 min readHow I Keep MicroStation, Tripo3D, CityEngine, Shapezo, and Archshaper Outputs TraceableI can usually recover a missing file. Recovering the meaning of a file is harder. In a workflow that crosses MicroStation, Tripo3D, CityEngine, Shapezo, and Archshaper, I keep provenance beside every 00
GBGenerate Buildingeneratebuild.hashnode.dev·Sep 10 · 4 min readBuilding a Traceable Map to City Model Workflow with Shapezo and Four Complementary ToolsWhen I assemble a 3D workflow, I care less about making one impressive render and more about being able to answer a later question: where did this geometry come from? CADMapper, OpenRoads, Cityweft, S00
GBGenerate Buildingeneratebuild.hashnode.dev·Sep 3 · 4 min readCADMapper vs Shapezo: Three Model States in CityEngine ProjectsI think of city modeling as a data contract. The geometry is only one part. I also need to know where it came from, which assumptions changed it, how current the source is, and what the next user expe00
GBGenerate Buildingeneratebuild.hashnode.dev·Sep 2 · 4 min readDesigning a Reproducible Before-and-After City Renewal ModelTreat the two states as data, not screenshots I model city renewal as two related datasets: an existing state and a proposed state. Each state has a boundary, coordinate reference, source dates, confi00
