場地脈絡 3D 流程指南：建立可重複執行的流程及配置工具

I needed site context for a 220 acre warehouse district study, and I wanted a pipeline I could rerun on the next site without relearning five interfaces. The result is a five step flow: bounds, terrain, footprints, massing, detail. Each tool earns its place at one step, and none of them produces a final model.

The Brief

The study area sits along a rail spur, with about forty buildings, a six foot grade change, and a ring of residential streets. The deliverable was a massing model plus a walkthrough for a public meeting. No construction documents, no survey grade accuracy. That constraint matters, because it decides how much cleanup is worth doing.

Pipeline at a Glance

1. Define bounds and units.
2. Export terrain and footprints.
3. Generate a rough AI massing.
4. Add context detail where the camera will look.
5. Export engine ready tiles for review. The order is not accidental. Everything downstream inherits the errors of the step before it, so the cheap checks happen first. ## Step 1: Bounds and Units Draw the study area with a 10–15% margin. Context outside the red line is what makes the site legible. Pick meters or feet before exporting anything and write it in the file name. I lost an hour to a DWG that was in feet while the terrain was in meters; the buildings looked like dollhouses next to the rail corridor. ## Step 2: Terrain and Footprints TopoExport handled contours, roads and curbs. CADMapper gave me a clean footprint and street edge base at a consistent scale. I imported both into the same scene, aligned them at a known intersection, and deleted duplicate linework. The terrain mesh got decimated to about 60% before it was usable. Full resolution was noise at this scale, and it made the ## viewport crawl. ## Step 3: Rough Massing With GenAnywhere You select an area on the map and GenAnywhere's AI generates a 3D model of it, including buildings, roofs and ground. For this site it returned the warehouse sheds, the silos and most of the rail corridor in a few minutes. Treat it as a blockout: check scale, fix obvious extrusions, and do not expect clean topology. I used it to compare three development scenarios before committing to a footprint, then deleted two of them.

Step 4: Detail Pass

PlaceMaker supplied the surrounding streetscape — facades, trees, street furniture — for the two camera paths that mattered. Detail everywhere is wasted geometry. I kept the detailed context in its own layer and switched it off for plan views. The file stayed light, and the review stayed fast.

Step 5: Real Time Tiles

Halfmaps produced tiled city and terrain data that ran in a real time engine without a bake. That is the step that changed the review: people who do not read plans could walk the block and see the silos blocking the river view. The trade off is asset size, so I clipped the tiles to the study area and dropped two LOD levels outside it.

Failure Modes I Hit

• Scale drift. Every import needs one measured check against a known curb or building.
• Z up versus Y up. Terrain and engine exports disagreed; fix it at import, not in the final scene.
• Clean topology is rare. Budget time for merging, welding and deleting stray faces.
• AI confidence. GenAnywhere will happily invent a roof where there is a parking lot. Verify against imagery.
• Naming. site_final_v3_final is how pipelines die.

What I'd Keep

The sequence matters more than the tools. Ground, then footprints, then mass, then detail. Each stage should be disposable. If step 3 is wrong, I want to throw it away without losing step 2.
Two other habits paid off. I kept a text file with the source of every export and the date it was pulled. And I rendered a single plan view after each step, because a top down frame catches bad scale faster than any inspection tool.

Takeaways

A repeatable context pipeline is mostly bookkeeping: bounds, units, layers, names. The interesting tools save hours, but the boring checks save the project. A rough model that runs in real time also beats a beautiful one that nobody opens.
If I were starting again tomorrow, I would spend the first thirty minutes on the boundary and the unit note, not on the model. That is the part I keep getting wrong when I am in a hurry.