The dimensional half of "does the parking meet code": measures each parking-stall block's drawn footprint and flags any stall smaller than the minimum for its class (Standard / ADA / Van). Sibling of
VDCPARKING in the same tool, same stall blocks, same settings file, same palette.
Stall block footprint
Meets class minimum
Under minimum → flag
Unmeasurable → warning
What it does, per run
- Classifies each stall block with the same name lists as
VDCPARKING(van → ADA → standard priority, no double-count). - Measures rotation-independently: the block definition's local bounding box × the reference's scale, a stall rotated along a curved aisle still measures true; dynamic blocks reflect their current stretched state.
- Compares width (short side) and depth (long side) to the class minimum, with a small tolerance for drafting noise.
- Flags every under-size stall with a zoomable finding; unmeasurable geometry gets a WARNING rather than a silent pass.
Settings & scope
- Per-class minimums + tolerance in the dialog (defaults Std/ADA/Van 9 × 18, tol 0.05 ft), configurable per jurisdiction, shared
settings.jsonwithVDCPARKING. - Stalls only in v1: drive-aisle and ADA access-aisle widths need the striping linework, not the stall blocks, planned addition.
- Ribbon: VDC QC tab → Parking Code, beside Parking Count.
- Output:
<drawing> - Parking Dimensions.csvplus the findings palette.
Dialog

VDCPARKINGDIMSettings file:
%APPDATA%\VDC\Parking\settings.jsonWhen to use it
- Before a site plan submittal, to catch a stall that got stretched or scaled under the ordinance minimum.
- After someone edits a dynamic stall block or scales a parking bay - the drawn size is what gets reviewed, not the nominal one.
- On an inherited or consultant drawing, to confirm the stalls are actually the size the plan claims.
How to run it
- Run VDCPARKINGDIM; the settings dialog opens with the minimum width and depth for each class (Standard / ADA / Van) and the tolerance.
- Set the minimums to the governing parking ordinance, then click OK - Check.
- Every stall block in model space is measured and compared; read the summary on the command line (measured / failed / OK) with the minimums it used.
- Work the palette - double-click a finding to zoom to that stall - and open the CSV in the drawing's VDC Reports folder for the full stall-by-stall table.
Options
- Minimum width + depth per class: Standard, ADA, and Van each get their own minimum. Width is the short side of the stall, depth the long side - measured, not assumed from the block name.
- Tolerance (ft): grace below the minimum so a stall drawn a hair under nominal is not flagged (a stall fails only when it is under the minimum by more than the tolerance).
- Stall blocks: matched by EXACT name, the same lists VDCPARKING uses; the dialog shows the current Standard / ADA / Van names as read-only hints.
- Dynamic blocks: measured in their current stretched state, then scaled by the reference's X/Y scale - what is actually drawn is what is checked.
Watch out for
- Stall blocks are matched by EXACT name - if 0 stalls are measured, your block names do not match the lists in settings.json (same names VDCPARKING uses).
- A stall whose block geometry cannot be measured is reported as a WARNING, never silently passed - check that one by hand.
- Stalls drawn as plain polylines instead of blocks are not measured here (VDCPARKING can still count polygons).
- The CSV is only written when the drawing has been saved to a real path.
- Aisles are out of scope in this version - a passing run says nothing about drive-aisle or access-aisle width.
Related: Parking · ADA Slope · Sheet Index