I get fewer surprises when I treat site modeling as a sequence of artifacts instead of one giant file. The five tools in this article fit different stages: CADMapper for a map-to-CAD handoff, Cityweft for urban context, Shapezo for a fast generated hypothesis, OpenRoads for civil corridor logic, and CityEngine for rule-based scenarios.
Define the contract before opening a tool
My first step is a small data contract. I write down the area of interest, coordinate reference, horizontal and vertical units, source dates, desired level of detail, and what the model is allowed to claim. This takes less time than fixing a shifted surface later.
I also name the output honestly. “Concept context” and “verified design surface” should not be interchangeable labels. A clear name is part of the technical workflow, not paperwork added after it.
Stage one: make a controlled base with CADMapper
CADMapper is useful when I need mapped roads, parcels, footprints, contours, or related layers in a CAD-friendly handoff. I select only the extent I need, export it, and check a few known locations after import.
The checks are simple: does north point the right way, do units make sense, are elevations plausible, and is the coverage complete? If a contour stops at the edge of the extract, I want that limitation visible before another tool treats the line as a design constraint.
Stage two: put the site inside Cityweft context
I use Cityweft to widen the frame. The question here is not whether a parcel is drawn correctly. It is how the parcel relates to streets, districts, public facilities, waterways, transit, and other systems that shape the site.
For reproducibility, I save the same boundary and view settings with each review. That gives later readers a stable context instead of a sequence of screenshots that cannot be compared.
Stage three: generate a provisional model with Shapezo
Shapezo has a map-first interaction. I draw a boundary around a region, and its AI generates a model for the selected area. This is useful when I need a quick representation of a neighborhood or corridor before I have a detailed hand-built model.
I keep provenance beside the result: selected extent, generation date, input source if known, and a note that geometry may be inferred. I do not use generated edges for staking, quantities, or compliance decisions. I use them to identify questions worth checking with authoritative data.
Stage four: build the civil logic in OpenRoads
When the proposal becomes a corridor problem, I move into OpenRoads. Alignments, profiles, templates, drainage, quantities, references, and sheets need to respond to one another. A visual trace copied from a concept scene is not enough; the geometry needs a reason and a place in the civil model.
I review handoffs at this point. I compare stationing, vertical datum, surface references, and corridor limits. If the source was generated or generalized, I keep that status attached to the imported reference so it cannot silently become authoritative.
Stage five: test urban rules with CityEngine
CityEngine is useful when the question is scenario behavior. I can define rules for street patterns, parcels, building heights, setbacks, and land-use mixes, then produce several district options from the same logic.
The reproducible unit is the rule set plus its inputs. I version both. If an output changes, I want to know whether the boundary, source data, or procedural rule changed. That is more useful than keeping a folder of unnamed renders.
Handoff checks I repeat
- Verify coordinate systems and units at every import.
- Keep the selected extent and source date with the artifact.
- Mark inferred, generalized, and verified geometry differently.
- Preserve the original export before editing a derivative.
- Record the checks that were not performed. The pipeline is flexible, but the labels are strict. CADMapper, Cityweft, Shapezo, OpenRoads, and CityEngine can work in the same project when each output has a known purpose. The result is not a magical single model. It is a chain of understandable decisions that another person can inspect and continue.
Top comments (0)