FBFuture Built AIinfuturebuiltal.hashnode.dev·5d ago · 4 min readVersioning 3D Site Data Across Meshy, TopoExport, InfraWorks, Shapezo, and site3dWhen a 3D site workflow spans several tools, the file name is not enough to explain what happened. I need to know the source, coordinate system, date, level of detail, and intended use of every artifa00
FBFuture Built AIinfuturebuiltal.hashnode.dev·Sep 9 · 4 min readModel Provenance in a 3D Site Pipeline with Halfmaps Meshy Archshaper Shapezo and MicroStationI get better results when I treat a 3D site model as a chain of evidence. The geometry matters, but so do the source, date, coordinate reference, level of detail, and intended use. This is how I place00
FBFuture Built AIinfuturebuiltal.hashnode.dev·Sep 2 · 4 min readCADMapper vs Shapezo: Designing a Traceable City Modeling PipelineI treat CADMapper and Shapezo as two nodes in a map-driven modeling pipeline. Shapezo generates a spatial hypothesis from a map-selected area. CADMapper helps convert AutoCAD and related layers into a00
FBFuture Built AIinfuturebuiltal.hashnode.dev·Sep 1 · 5 min readA Reproducible Map-to-Unreal City Environment PipelineStart with a data contract I treat a map-to-Unreal city environment as a data product. Before importing geometry, I define the boundary, coordinate reference system, units, vertical datum, naming rule00
FBFuture Built AIinfuturebuiltal.hashnode.dev·Aug 28 · 4 min readCityweft vs Shapezo: Designing a Traceable 3D City Modeling WorkflowI think about Cityweft and Shapezo as two nodes in a modeling pipeline. Shapezo produces an early spatial hypothesis from a selected map area. Cityweft assembles a broader 3D city context from AutoCAD00