Cam IncollFieldwalker's design tools use a symbol library purpose-built for permaculture — trees, garden beds, swales, fences, zones, water features, and dense vegetation, all rendered in the illustration style used in permaculture design manuals.
There's a visual language to permaculture design. If you've studied Mollison's Designer's Manual or looked at the illustrations in Holmgren's work, you'll recognise it immediately. Trees rendered as organic canopy shapes from above. Swales drawn with the asymmetric cross-section that shows which side holds water and which side is the berm. Dense vegetation as a single amorphous blob with a scalloped edge, not a collection of individual dots. Garden beds with their planting patterns visible.
This visual language exists for a reason. It communicates. A permaculture designer can look at a well-drawn site plan and read it — understanding what's existing and what's proposed, where the water goes, how the zones relate to each other, what type of fence defines each boundary.
Fieldwalker's symbol library is built around this language. Not as an afterthought bolted onto a generic drawing app. As the foundation.
Why generic tools don't work
You can draw a permaculture design in any drawing application. People use everything from PowerPoint to Illustrator to QGIS. Some people still do it by hand on trace paper over a printed aerial, which honestly produces beautiful work.
But generic tools make you build the visual language from scratch every time. You draw a tree as a circle with some green fill. You draw a swale as a pair of parallel lines. You represent a fence as a straight line that looks the same whether it's post-and-rail or electric tape.
None of these communicate what they are to someone reading the plan. And every time you start a new design, you're rebuilding these symbols from nothing. The overhead adds up. The quality suffers. And the designs end up looking like diagrams rather than design documents.
Symbols that know what they are
In Fieldwalker, when you place a tree, it looks like a tree in a permaculture design. It has an organic canopy shape — not a perfect circle, but the natural irregular form you'd draw by hand. The trunk is visible beneath the canopy. The style matches what you'd see in a Mollison illustration.
When you place a swale, it renders with the asymmetric cross-section that communicates function. The channel side is distinct from the berm side. Hatch marks on the berm show the earthwork. A dashed centre line runs along the path. You can see at a glance which way the water flows and where the berm sits.
Dense vegetation — a forest edge, a thick hedgerow, a patch of established woodland — renders as a single canopy blob. Not individual trees scattered randomly, but the amorphous shape with a scalloped organic edge that says "this is a mass of vegetation" the way permaculture designers have always drawn it.
Fences distinguish between types, because the type matters. A post-and-rail fence — the permanent boundary, the structural element — looks different from an electric tape fence, which is temporary, moveable, part of a rotational grazing system. When you're planning paddock layouts, that distinction is the whole point.
Garden beds show their internal planting patterns. Zones render as the familiar concentric overlays. Water features look like water. Every symbol is drawn to communicate its function within a permaculture design, not just to mark a location on a map.
Scale-aware by default
One of the things that trips people up with generic tools is scale. You place a tree symbol on a suburban quarter-acre block and it covers half the property. You use the same symbol on a 50-acre farm and it's a tiny dot. You end up manually resizing everything, which takes time and breaks the visual consistency.
Fieldwalker's symbols understand the scale of the site. Place a tree on a small block and it's sized appropriately relative to the house and garden. Place one on a broadacre property and it scales accordingly. Garden beds, fences, swales — they all adapt to the working scale so the design looks proportionally right without manual adjustment.
This matters more than it sounds. When the proportions are right, you can actually read the design at a glance. You can see whether a garden bed is a realistic size for the space. You can tell whether the orchard spacing is too tight. The design becomes a tool for spatial thinking, not just a picture.
From detection to design language
The symbol library connects directly to the AI detection pipeline. When Fieldwalker detects features on your aerial image, those detections can be converted into proper design symbols.
A detected cluster of trees becomes an illustrated canopy in the permaculture style. A building becomes a building symbol. A patch of dense vegetation becomes the amorphous canopy blob. The conversion step translates raw detections into the visual language of the design.
This means your base map — with all its detected existing features — already speaks the same visual language as the new elements you'll design on top of it. The existing trees look like the proposed trees. The existing buildings match the style of the designed structures. The whole document reads as one coherent design, not a satellite image with some shapes drawn on top.
The point is communication
A permaculture design document is a communication tool. You present it to a client. You hand the earthworks section to a contractor. You pin it to the shed wall as a reference while you implement. You come back to it next season to plan the next phase.
Every one of those uses depends on the document being readable. Clear. Professional. Drawn in a visual language that communicates what's existing, what's proposed, and how the whole system fits together.
That's what the symbol library is built for. Not to be clever or decorative. To communicate — in the visual language that the permaculture community already knows and uses.