76 lines
4.4 KiB
Markdown
76 lines
4.4 KiB
Markdown
# Campus and Multi-Building Workflow
|
|
|
|
## Contents
|
|
|
|
1. Branch selection
|
|
2. Scope contract
|
|
3. Placement evidence
|
|
4. Site outlines and missing buildings
|
|
5. Assembly gates
|
|
6. Site context
|
|
|
|
## Branch Selection
|
|
|
|
Treat folders such as `1#厂房 / 2#厂房 / 3#辅房 / 总图` as a campus, not floors of one building. Produce one frame-detection run, config, spec, and model per delivered building drawing set. Keep site plans in their own units.
|
|
|
|
Building plans are usually millimeters; total/site plans may be meters at surveying coordinates. Never combine both in one extraction config. Convert everything to site-local meters before GLB export; raw coordinates hundreds of kilometers from origin lose float32 precision.
|
|
|
|
## Scope Contract
|
|
|
|
Before modeling, write `scope_manifest.json` from the user request and source inventory. Do not derive requested scope from whichever config or GLB happened to succeed. Minimum shape:
|
|
|
|
```json
|
|
{
|
|
"scope_version": 1,
|
|
"mode": "campus",
|
|
"requested": ["1#", "2#", "3#"],
|
|
"buildings": [
|
|
{"id": "1#", "status": "PASS", "artifacts": ["../../outputs/1/model.glb"]},
|
|
{"id": "2#", "status": "BLOCKED", "reason": "unresolved XREF", "artifacts": []}
|
|
],
|
|
"site": {"status": "PASS", "artifacts": ["../../outputs/site_top.png", "../../outputs/campus.glb"]}
|
|
}
|
|
```
|
|
|
|
Every `requested` ID must have exactly one ledger entry and there may be no unrequested extras. `PASS` requires at least one verifiable model artifact: a GLB with mesh primitives, a Blender file with a valid header, or a schema-valid `building_spec.json`; an arbitrary non-empty text/JSON file does not satisfy scope. Campus site evidence must include a valid model or readable image. Relative paths resolve from the scope manifest's directory. `BLOCKED` requires a concrete reason and makes the overall campus result `BLOCKED`, not complete. Feed the ledger to `cad_showcase.py run --scope-manifest ...` or `verify_delivery.py --scope-manifest ...`.
|
|
|
|
## Placement Evidence
|
|
|
|
Prefer anchors in this order:
|
|
|
|
1. coordinate callouts;
|
|
2. wall lines;
|
|
3. envelope rectangles whose dimensions equal the model wall bbox;
|
|
4. registered site outlines.
|
|
|
|
Use wall evidence, not roof/eave envelopes. Derive rotation from a matched edge and resolve the 180-degree ambiguity with an asymmetric feature such as entrances, machine rooms, or basement ramps. Save the source and reasoning in `site_manifest.json`.
|
|
|
|
For irregular outlines use `register_site_outlines.py`. Constrain the angle window when the building is visibly axis-aligned. Treat residuals roughly as: 0.06m excellent, 0.5-1m plausible with balconies, above 2m likely wrong outline/floors.
|
|
|
|
## Site Outlines and Missing Buildings
|
|
|
|
If a building has no delivered drawings but has a site outline and storey label, use `massing_from_outline.py`. Label every such floor/model as total-plan outline massing. Never silently fabricate detailed walls/windows.
|
|
|
|
Use multiple floor footprints for registration when upper wings/overhangs explain the site outline better than one floor.
|
|
|
|
## Assembly Gates
|
|
|
|
Use `assemble_campus.py` with per-building `rotation_deg` where needed. Require:
|
|
|
|
- no unexplained negative wall-envelope gaps;
|
|
- 0.15-0.30m joints corroborated as expansion joints;
|
|
- several-meter separations checked against fire/site evidence;
|
|
- all buildings inside the red line;
|
|
- a top-view overlay or render showing each model inside its site outline;
|
|
- numeric envelope dimensions and neighbour gaps in the notes/evidence.
|
|
|
|
Do not classify a small gap from distance alone. Corroborate a 0.15-0.30m attached-building/expansion-joint interpretation with the neighbour roof shown on the subject building's roof plan and matching floor elevations. A negative gap is always a placement error. A multi-metre hypothesis that pushes either building through the red line is also wrong.
|
|
|
|
`--allow-overlap` is for a documented shared structure or verified interlocking geometry, not a shortcut around placement bugs.
|
|
|
|
## Site Context
|
|
|
|
Use `site_context_from_dump.py` to generate ground/red-line footprints, roads, parking, fences, trees, and low-confidence context massings from one selected site-plan copy. Supply the correct per-dump unit scale, region window, origin, and exclusion quad for real modeled buildings.
|
|
|
|
Keep site context in every presentation variant. Replace context massings with real models when drawing sets exist. A campus with only boundary sticks is incomplete presentation, but visual completeness never permits fake buildings.
|