NEW ROOTS DEVELOPMENT

Home›Tool Guide›VDC QC›Site QC

Tree / Utility Clearance QC

Tree vs utility clearance QC: the spec everyone has and nobody checks.

Command VDCTREECLEAR · VDC QC tab › Site QC panel

Tree vs utility clearance QC: the spec everyone has and nobody checks.

What it does

Every tree-survey point (code in your per-firm tree-code list) checked against EVERY gravity and pressure pipe for minimum horizontal separation.
Required distance from your rule matrix (NETWORK PATTERN,FEET): first match wins, 0 exempts, unmatched networks use the dialog default.
CSV + findings palette; each finding zooms to the tree/pipe pair.

Worth knowing

Shipped rule values are schema samples marked (verify), enter the governing utility's real numbers.
Horizontal separation only; root-zone/vertical questions stay with the engineer.
Data: tree-codes.csv (env VDC_TREECLEAR_CODES) + clearance-rules.csv (env VDC_TREECLEAR_RULES).

Dialog

Tree / Utility Clearance QC dialog — Tree / Utility Clearance QC, VDCTREECLEAR

Settings file: %APPDATA%\VDC\TreeClear\settings.json

When to use it

Utility design review on a wooded site - which trees crowd which mains.
Landscape plan coordination - trees drawn over the water line get caught here.

How to run it

Confirm the tree-code list and clearance rules (user-editable CSVs; env-redirectable).
Run VDCTREECLEAR, set the default clearance, and OK.
Work the findings palette - each finding zooms to the tree/pipe pair.

Options

Tree codes: %APPDATA%\VDC\TreeClear\tree-codes.csv (env VDC_TREECLEAR_CODES).
Rule matrix: clearance-rules.csv (env VDC_TREECLEAR_RULES): NETWORK PATTERN,FEET; first match wins; 0 exempts.

Watch out for

Shipped rule values are schema samples marked (verify) - enter the utility's real numbers.
Horizontal separation only - vertical/root-zone conflicts still need engineering judgment.
Compares against criteria you configure - not a compliance determination.

Related: Tree Table · Pipe Clash · Easement Widths