Skip to main content

SiteAI Can't Pull Wetland Data — How to Work Around It

What to do when SiteAI is unable to retrieve wetland data for a site and won't generate a layout.

Written by Mikaila McLane

In some cases, SiteAI may be unable to automatically retrieve wetland data for a parcel and will pause layout generation until the issue is resolved. If you encounter this, you can work around it by manually drawing a custom avoidance area in place of the missing wetland data.

How to Add a Custom Avoidance Area

SiteAI allows you to define custom avoidance zones for anything not automatically detected — easements, utility corridors, areas flagged during due diligence, or in this case, known wetlands. Manually designating the wetland area as a custom avoidance zone excludes it from the developable area and allows layout generation to proceed.

This approach gives you direct control over what the engine treats as unbuildable, and is also useful any time you have site-specific knowledge that isn't captured in the automatic data pull.

When to Use This

  • Wetland data fails to load for the parcel

  • You have a surveyed wetland boundary that differs from the automated data

  • Any known constraint on the site isn't being detected automatically

If you're unsure where to find the custom avoidance area settings within the SiteAI workflow, reach out to support and we can walk you through it.

Did this answer your question?