A Reproducible Site Context Pipeline With CADMapper Shapezo PlaceMake InfraWorks and TopoExport

I have learned to treat an early 3D site model as a data pipeline, not a single file. CADMapper, Shapezo, PlaceMake, InfraWorks, and TopoExport each produce a useful artifact, but each artifact carries different assumptions. If I merge them without recording those assumptions, the final scene may look coherent while being impossible to audit.
This is the small pipeline I use when the goal is a reviewable site context model rather than a final engineering deliverable.

Step one define a coordinate contract

Before opening a modeling tool, I write down the project coordinate reference, horizontal units, vertical units, vertical datum if known, and local origin. I also record the geographic extent as a polygon or bounding box.
That contract keeps imports from becoming silent transformations. CADMapper and TopoExport may arrive with different assumptions from an InfraWorks context. Shapezo may use a map selection that needs to be aligned to the project frame. PlaceMake studies need a clear relationship to the same site boundary.
I do not rely on a screenshot of a coordinate dialog. I put the values in a text or JSON sidecar file beside the exports.

Step two create a source linked base

I use CADMapper to create an initial map-derived base when streets, footprints, contours, or other geographic layers are needed in a CAD-friendly form. The artifact record includes the source date, selected area, layer list, units, coordinate reference, and any generalization I notice.
The output is useful because it remains inspectable. I can turn a layer off, compare a footprint, or remove a source that is not appropriate for the current question. I keep the base separate from generated or conceptual geometry so its origin stays clear.

Step three export elevation as its own dependency

TopoExport has a narrow but important role in my pipeline. I use it to bring terrain or topographic information into the project, then validate contour interval, surface resolution, vertical units, datum, and geographic extent.
I keep the terrain export as a dependency instead of baking it into every downstream file. If the elevation source changes, I can update the terrain version and see which studies need to be rerun. This is less convenient than copying a surface everywhere, but it makes the change visible.

Step four add a generated selected-area context

Shapezo is useful when I need a quick model of a known place. I draw or frame a boundary on a map, and its AI generates a model for that selected area. I store the boundary, run date, visible source coverage, and status as generated context.
The status is part of the pipeline contract. A Shapezo output can help with adjacency, rough massing, and spatial discussion, but it is not silently promoted to survey data. If I use it as the background for a PlaceMake study, the study record links to the exact Shapezo version.

Step five use InfraWorks for connected systems

I bring the base and terrain into a wider InfraWorks scenario when roads, bridges, rail, water, drainage, or utility corridors shape the design. The scenario record names existing conditions, proposals, source layers, and the date of the context.
I use the scenario to test relationships: whether a driveway meets a corridor, whether a bridge approach leaves room for a path, whether a grade change affects a public space, and whether a local layout conflicts with a larger network. I keep proposed geometry visually and semantically separate from existing conditions.

Step six test arrangements in PlaceMake

PlaceMake is where I study the site arrangement. I record the site boundary, access assumptions, public-realm elements, service routes, planting or open-space intent, and the context versions used. Each option receives a small version note rather than a vague label such as final.
That note can say that an entrance moved toward the active street or that service access shifted away from a walking route. It gives the next reviewer a reason for the change without pretending the option is construction-ready.

Handoff checks I reuse

• Do all exports state units, coordinates, and extent?
• Does every generated or conceptual artifact carry a status?
• Can I trace Shapezo output to its selected boundary?
• Can I trace terrain to its TopoExport source and vertical settings?
• Are InfraWorks proposals separate from existing conditions?
• Does each PlaceMake option identify its context versions? The pipeline is intentionally plain. CADMapper provides a source-linked base, TopoExport provides elevation, Shapezo provides selected-area generated context, InfraWorks provides connected infrastructure, and PlaceMake provides site arrangement studies. The value is not that the files look identical. It is that another person can understand how each one was made and what it is allowed to answer.