Bodies, fields and feature graphs

Bodies and surfaces

An implicit body describes which points in space are inside or outside a volume. Its boundary is a level surface of that description. You work with the body through operations such as union, subtraction, shelling and transformation; a preview makes the resulting boundary visible.

A field assigns a value to a position in space. A distance field, for example, can drive a gradual change in wall thickness or lattice scale. A surface display samples a body for viewing. Increasing display resolution improves what you can see, but does not itself prove manufacturing or simulation accuracy.

Typed inputs and outputs

Type

Meaning

Example use

Body

A volume

Housing, coolant, lattice envelope

Field

A spatially varying value

Thickness or offset distribution

Length

A dimensional scalar

Radius, shell thickness

Number / integer

Dimensionless value / count

Scale factor, pattern count

Vector / points

Spatial coordinates or directions, as declared by the operation

Position, curve control points

Curve / profile

A path or section

Sweep, extrusion, revolution

Each operation declares its accepted inputs and output types. Use the live feature catalogue rather than guessing whether a number, field or body is accepted by an input. A body cannot be substituted for a field simply because both can be displayed.

The editable graph

A gd.design/v1 document contains stable feature IDs, operation names, typed inputs and references, named outputs, and optional parameters and constraints. A reference connects one feature’s output to another feature’s input. Keep IDs stable during edits so dependent features and downstream selections remain traceable.

Documents declare mm or m. Explicit typed quantities can carry units; follow the schema for that input. Changing a unit label is not an instruction to resize existing geometry. Confirm bounds after any conversion and before meshing.

Keep three questions separate: does the graph validate, does its evaluated geometry meet the requirement, and is its exported representation suitable for the next operation? See constraints and import/export.