NEW ROOTS DEVELOPMENT
Home›Tool Guide›VDC Plans›Plans

Cover Sheet Fill

Fills the PROJECT SUMMARY cover-sheet block in place: acreages, the impervious/pervious breakdown with percentages, CL road length, and lot counts, tallied live from the drawing, by matching each label line's wording and replacing only the number tokens , so the template text never restructures.

Command VDCCOVERFILL · VDC Plans tab › Plans panel
Fills the PROJECT SUMMARY cover-sheet block in place: acreages, the impervious/pervious breakdown with percentages, CL road length, and lot counts, tallied live from the drawing, by matching each label line's wording and replacing only the number tokens, so the template text never restructures.
Quantities tallied from the drawing land in the existing summary text, placeholders first run, refresh after. TALLIED FROM THE DRAWING hatches (SF) parcels / polys alignments (CL LF) token match by layer / parcel name / style, editable in settings.json REVIEW GRID computed vs. what the sheet says, per field PROJECT SUMMARY TOTAL PROJECT AREA = 45.06 ACRES LAND DISTURBANCE AREA = 38.20 ACRES CL LENGTH OF ROAD = 4,120 LF # OF SINGLE FAMILY LOTS = 84 RES. LOTS IMPERVIOUS AREAS = 3.21 AC (38%) ROADS AND DRAINAGE : CITY OF M.B. PARCEL PIN #'(S) : XXX-XX-XX green = filled by the tool (recolored to the label) yellow = manual fields, left alone, still standing out re-run to refresh, written numbers are tokens too

What it does

  • Label-keyed: each summary line is found by its label wording (TOTAL PROJECT AREA =) anywhere in the drawing, the cover block's definition, paper space, or model space; both inline and two-column (label + value as separate MText) layouts.
  • Token replacement: only XX.XX placeholders / previously written numbers swap; units, words ("RESIDENTIAL LOTS"), underlines, and colors around them survive.
  • Sources per field: hatches + closed polylines by layer token, parcels by name/style token (lot count + lot area), alignments for CL length, practice mixes all three.
  • Rollups: impervious = building + asphalt + concrete; pervious = its sources or (option) total − impervious; percentages against total project area.
  • Recolor on fill: a filled two-column value takes its label's color, templates often leave fields yellow until set, so filled = back to normal.

Notes & settings

  • Review before write: rows missing a label line or a matched quantity start unchecked / greyed, nothing is written blind; skipped lines are itemized on the command line.
  • Manual fields stay manual: PIN, zoning, permits, benchmark, authorities are not touched (PIN/zoning from county GIS is the planned v2).
  • Watch the [n obj] counts in the grid, overlapping hatches double-count; the funnel line says what was scanned.
  • Field catalog (labels + tokens) is editable at %APPDATA%\VDC\CoverFill\settings.json (env override VDC_COVERFILL_SETTINGS), other firms' conventions work without a code change.
  • Every written value is stamped (VDC_COVERFILL ext-dictionary) with the field, value, and date.

Dialog

Cover Sheet Fill dialog
Cover Sheet Fill, VDCCOVERFILL

When to use it

  • Setting up or updating a cover sheet whose summary still says XX.XX ACRES.
  • The design changed (lots added, disturbance limits moved) and the summary must catch up.

How to run it

  1. Open the cover sheet drawing and run VDCCOVERFILL.
  2. Read the review grid: computed value vs. what the sheet currently says, per field.
  3. Uncheck anything you don't want written and click OK - fill cover sheet.
  4. Re-run any time to refresh - the numbers it wrote are themselves replaceable tokens.

Options

  • Recolor filled values: a filled two-column value takes its label's color, clearing the stand-out yellow.
  • Pervious = remainder: compute pervious as total project minus impervious instead of summing pervious sources.
  • Field catalog: labels + layer/parcel/alignment tokens are editable in settings.json for other conventions.

Watch out for

  • A field only fills when its label line exists on the sheet AND a quantity source matched - the grid greys out anything unmatched.
  • Areas come from what the tokens match (mostly hatches; parcels and bare polylines too) - overlapping objects double-count, check the [n obj] counts.
  • Manual fields (PIN, zoning, permits, benchmark, authorities) are left alone - this fills the computable numbers only.
  • The summary must live in THIS drawing (block or space) - an xref'd summary is read-only and skipped.

Related: FIRM Note · Quantity Takeoff · Lot Table · Erosion Control