Workflows

Workflows

The cut/fill loop

[existing terrain mesh] ─▶ [gh_02_grade_pad] ─▶ proposed_mesh
          │                                          │
          └────────────▶ [gh_01_cut_fill_cartogram] ◀┘   (bake = true → drawing layers)

1. Start with a 2.5D existing terrain mesh and a closed site boundary.
2. Author the proposed surface — either edit the mesh directly, or use gh_02_grade_pad for a flat building pad, and/or gh_16_grading for design spot elevations.
3. Feed both meshes + the boundary into gh_01_cut_fill_cartogram for the cartogram, per-cell volumes, totals and the quantity table.

Set the country once with gh_00_standard. Each component reads the model unit itself, so make sure the Rhino document units are set (mm/cm/m/inch/foot) before you trust a volume — the volume components warn on a unitless document.

Baking to drawing layers

Most drawing components have a bake boolean. Set it to true and the component writes its in-memory geometry straight onto the active standard's named SPDS layer group (parent layer + styled child layers), replacing the previous bake so it is idempotent. Baking happens inside each component (rather than a separate node) because some Rhino builds will not give script inputs list access.

Sheet production: bake → Make2D → layout → print.

Assembling a genplan / organization-of-relief (ПОР) sheet

The components compose into a sheet rather than needing a single "assemble" node:

0. Pick the standard once with gh_00_standard.
1. Author the proposed grades with gh_16_grading and tune ±0.000 with gh_19_mass_haul to balance cut/fill.
2. Add detail: gh_17_blind_area, gh_18_driveway, the ditch (gh_12) and foundation drain (gh_21), and relief reading — slope arrows, contours and drainage in one pass with gh_09.
3. Quantities: feed the cut/fill (gh_01 or the serial mode of gh_04), topsoil (gh_06), backfill (gh_08) and ditch (gh_12) volumes into gh_14 for the bill + balance; gh_22 for the ТЭП.
4. Bake everything onto the SPDS layer groups, drop a gh_23 frame + title block, then Make2D + layout + print.

Each component bakes to its own named layer group, so the layers compose into one coherent, print-ready drawing tree.

Exchanging terrain with Revit

gh_13_revit_points writes terrain points as a comma-delimited X,Y,Z file in metres. In Revit, import it as a Toposurface (Create from Import → Specify Points File) or a Toposolid, choosing Meters in the import dialog. The same export is the basis for setting-out coordinates.