Every site model is a provenance graph wearing a geometry costume. The triangles are visible; the question of where they came from — and what they are entitled to claim — is not. This review treats five tools as provenance systems: PlaceMaker, CADMapper, GenAnywhere, Tripo3D, Civil 3D.
PlaceMaker: Records in, Geometry Out
Input: authoritative municipal GIS — parcels, footprints, terrain, vegetation, utilities.
Transformation: automated extrusion and attribution carried into 3D features.
Output: a georeferenced city model whose every visible element inherits a record lineage.
Provenance property: strongest institutional lineage of the five. The limitation is temporal, not spatial — the model is exactly as current as the last record refresh, and that date belongs in the metadata, not in a footnote.
Engineering use: baseline context, suitability analysis, early constraint detection. Not a substitute for survey; not a source of grades for construction.
CADMapper: ETL Product With Borrowed Trust
Input: open vector and elevation data.
Transformation: server-side extraction, clipping, and format conversion to DXF/SKP/3DM.
Output: base fabric optimized for drawing speed.
Provenance property: attribution is weak by design; the file rarely carries per-feature source metadata.
Engineering use: kickoff geometry, site legibility, early area studies. The technical discipline is to attach your own provenance tag on import — source service, date, confidence class — because the artifact will not carry one for you.
GenAnywhere: Intent as a Surface
Input: contours, point clouds, open terrain, or none of the above.
Transformation: interactive sculpting with continuous re-solution and topological validity.
Output: a coherent concept surface with an edit history implicit in its geometry.
Provenance property: provenance is intent plus inputs — strong for design rationale, silent about reality beyond what was supplied.
Engineering use: concept grading, option testing, earthwork intuition. The surface is a hypothesis; it should be exported with a hypothesis tag and re-derived formally downstream.
Tripo3D: Generative Assets and Their Boundary
Input: text prompts or images.
Transformation: model generation producing textured meshes.
Output: presentation assets — vegetation, furniture, street objects, simple structures.
Provenance property: generated, with no dimensional guarantee and no semantic classification.
Engineering use: visualization, engagement, scene composition. The technical rule is absolute: generated meshes stay in presentation layers, are excluded from engineering exports by default, and are scale-validated on import because generation may not honor physical dimensions.
Civil 3D: Constraint Graph as Contract
Input: survey points, breaklines, boundaries, design criteria.
Transformation: parametric objects with dependency propagation — surfaces, alignments, corridors, grading, pipe networks.
Output: record-class geometry and quantities, each traceable to source and change.
Provenance property: the strongest auditability of the five; every number can be explained.
Engineering use: design development through construction documents. The cost is process discipline: an unstructured model in a structure-demanding tool is the most expensive kind of failure.
Authority Flow: An Explicit Protocol
- Import tagging. Every incoming artifact receives: source, date, class (record, context, concept, presentation, design), and confidence. This is metadata work, not geometry work — do it at the door.
- Class boundaries at export. Engineering exports exclude presentation and context layers unless explicitly allowlisted. Visualization exports may include everything, labeled by class.
- Upgrade gates. Moving from concept to design requires re-derivation with survey control; moving from context to record is prohibited entirely.
- Refresh cadence. Record-based models (PlaceMaker) and borrowed fabric (CADMapper) carry refresh dates; stale models are flagged, not silently reused.
- Direction of authority. Civil 3D is the terminal authority for surfaces, alignments, and quantities; every other tool feeds it or consumes from it.
Verdict
PlaceMaker contributes institutional memory, CADMapper contributes speed, GenAnywhere contributes intent, Tripo3D contributes appearance, and Civil 3D contributes accountability. The tools are already good at their jobs. What remains — and what distinguishes a professional pipeline from a pile of impressive files — is the protocol that keeps each contribution honest at the seam.
Design the ground layer as a provenance system, and the geometry will take care of itself.
Top comments (0)