Landscape Site Compliance
Landscape Site Compliance reviews a landscape design against the jurisdiction’s landscape ordinance — planting setbacks, hardscape ratios, permeability, irrigation, tree-protection, native-species requirements, and shade-coverage minimums. It reads a Revit or Civil 3D landscape model plus the active rule library and outputs element-pinned citations, available now as a Labs engagement under MSA + Appendix.
- Landscape design checked against the active landscape ordinance before issue to the client or authority.
- Each non-compliant tree, planter, or hardscape element pins to a rule citation in the review report.
- Rule library calibrated per Labs engagement against the firm’s primary jurisdictions and project types.
From compliance-by-consultant to read-the-design.
Workflow today
-
01
Landscape architect ships the design
Week 0. The landscape architect issues the site package once the plant palette is locked, hardscape is laid out, and irrigation zones are defined. The Revit or Civil 3D model, plus PDF plans and planting schedules, go to the internal team and the external compliance consultant. Any late zoning clarifications trigger manual rework across the whole set.
Week 0 -
02
Compliance check by external consultant
Week 1–4. A local specialist interprets the landscape ordinance, native-species lists, and tree-protection rules. The hand-off usually goes by PDF markups and email notes, often disconnected from the Revit or Civil 3D model. Each jurisdictional nuance — like Dubai villa perimeter planting or US municipal shade-tree counts — lives in the consultant’s head, not in a reusable rule library.
Week 1–4 -
03
Issues come back with low context
Week 4+. The consultant returns a marked-up PDF package with rule references but no element IDs or coordinates. Senior staff spend hours matching notes like “insufficient permeable area in Zone B” to specific paving families, planting beds, or irrigation zones in the model. Edge cases around tree-protection distances and water-feature setbacks are easy to miss on a second pass.
Week 4+ -
04
Resubmit with revisions
Week 5+. The team revises the model and drawings, issues a new set, and waits again. New ambiguities in the landscape ordinance — such as shade-coverage minimums at different times of day or native-species percentage by planting zone — surface late. Coordination with planning and zoning checks, including Dubai Villa Code Compliance, becomes a separate manual effort.
Week 5+
Workflow with VitruAI
-
01
Run the agent on the landscape model
Day 1, ~1 hour. As part of a Labs engagement, VitruAI configures a landscape rule library for the firm’s primary jurisdictions, including overlaps with the Dubai Villa Code where villas require specific perimeter planting and permeable-area ratios. The agent reads the Revit or Civil 3D landscape model, parses planting, hardscape, permeability, and irrigation data, and loads the active ordinance profile for the project’s site.
Day 1, ~1 hour -
02
Agent flags violations
Day 1. The workflow runs a dedicated landscape compliance agent, related to the Code Compliance Agent, across the model. Each flag pins to a specific element — a tree at coordinate X, a planter at coordinate Y, a paving region with insufficient permeability, or an irrigation zone exceeding allowed density. The report cites the exact rule text, threshold values, and any cross-dependency with villa or building requirements.
Day 1 -
03
Landscape architect reviews and revises
Day 1–2. The landscape architect works directly from element-pinned flags instead of PDF markups. Planting setbacks, hardscape ratios, and permeability gaps resolve in the model, with notes tied to Revit categories or Civil 3D objects. Native-species shortfalls, tree-protection buffers, and shade-coverage minimums are addressed in context, while planning-level checks continue in parallel via urban planning and zoning compliance workflows.
Day 1–2 -
04
Re-runs on revisions
Ongoing. The team re-runs the landscape site compliance check after each revision set, diffing against the prior review to confirm that fixes hold and no new violations appear. The Labs rule library grows with each project, capturing local interpretations of Estidama, US municipal landscape codes, and villa-site requirements from Dubai Villa Code Compliance. Each Beta-style deployment ships a per-project accuracy report calibrated to the firm’s pipeline.
Ongoing
Landscape site compliance — common questions
-
Which jurisdictions are supported?
Each Labs engagement calibrates the landscape rule library to the firm’s primary jurisdictions and project types. Typical starting points include Dubai villa-site requirements aligned with the Dubai Villa Code, UAE Estidama landscape credits, US municipal landscape and tree ordinances, and UK BREEAM landscape requirements. Additional municipalities or private-community standards are added over the 4–8 week engagement as projects demand them.
-
Does it integrate with Civil 3D, Revit, or Vectorworks Landmark?
Yes, the workflow reads the firm’s authoring models, with Revit as the primary path via the VitruAI + Revit integration. Civil 3D and Vectorworks Landmark models are supported as Labs extensions, with mapping from their object types into a common landscape schema. During scoping, VitruAI documents which categories, layers, and parameters drive planting, hardscape, permeability, and irrigation checks for each tool.
-
How does this fit with planning and zoning compliance?
Planning and zoning compliance covers parcel-level controls such as use, FAR, height, and primary setbacks, as in the urban planning and zoning compliance workflow. Landscape site compliance works underneath that layer, checking planting setbacks, hardscape ratios, permeability, irrigation, and shade coverage within the approved envelope. Firms often run zoning checks first, then use landscape compliance to align detailed site design with villa or building rules, including Dubai Villa Code Compliance.
-
How does a Labs engagement work for landscape site compliance?
Landscape site compliance is available as a bespoke Labs engagement under MSA + Appendix, typically over 4–8 weeks. VitruAI works with the firm’s landscape and BIM leads to encode priority ordinances, map Revit, Civil 3D, or Vectorworks Landmark models to rule inputs, and validate outputs on one live project. At the end, the firm holds a working agent and a documented rule library that can extend to additional jurisdictions and projects.