Understand what the land is telling you

Seven raw map layers sitting beside each other are not a site analysis. Civexa turns them into constraints with geometry, severity and evidence — and measures what they actually take off the ground.

Explore your property See the whole platform

The question

Which part of this property can realistically be developed, and what has to be verified before anyone commits money?

Union, never sum

Overlapping constraints do not each take their own land

A wetland, its buffer and a steep slope routinely occupy the same ground. Adding their areas together invents lost land and makes a viable site look marginal. Civexa unions the geometry, reports the developable remainder, and states the overlap the union removed so you can see the correction being made.

Severity decides what is deducted

“Needs a study” is not the same as “cannot be built on”

Constraints are classified as hard, conditional, soft or informational, and only a hard constraint removes ground. Conditional land stays countable with the condition attached — because calling a wetland-buffer review unbuildable is as wrong as ignoring it.

Gaps are findings too

A layer nobody screened is reported as unscreened

If the flood service is unreachable, the report says the flood layer was not screened. It does not say the parcel is outside the flood zone. A hit with no usable geometry is reported and explicitly NOT deducted, with the usable area called optimistic by an unknown amount.

This is the distinction the whole engine is built around: the difference between a clear site and an unexamined one.

Verification, as a worklist

What a professional has to settle, and why

Each unresolved item names the discipline that would settle it — a geotechnical engineer, a wetland biologist, a surveyor — and the drivers that raised it. The output is a list of what to commission, in the order the money should be spent.

In the report

What the site section reports

Measured constraint geometry, the union correction, and the layers that were not reached.

Layers screened9 of 10verified

Steep slope1,840 sfverified

Naive sum of constraints2,450 sfderived

Overlap the union removed610 sfderived

Developable remainder9,380 sfderived

Flood layerNot screenedunresolved

Illustrative figures from a real Civexa run. Run your own address for live, code-traced numbers.

What it will not do

The answers Civexa declines to give

A model that always produces a number is a model whose confident answers cannot be told apart from its guesses. These are the cases where Civexa reports a gap instead.

GIS proximity is never utility capacity. A main in the street is not a connection, and the report does not present one as the other.
A screen is never a geotechnical conclusion. Mapped landslide or liquefaction data raises a constraint and names the study that would resolve it.
No site is called safe or unsafe from mapped data. The output is a constraint model with confidence, not a verdict about the ground.
Missing data never becomes “no constraint”. Unscreened layers are counted as gaps, and enough gaps raise the site's risk band on their own.

Questions

Site & environmental intelligence, in detail

Which layers are screened?

Parcel boundary and terrain, FEMA flood, city and county critical areas, geologic hazard, soils, vegetation, existing structures, frontage and access, and utility provider coverage — with each layer's source, confidence and effective date reported.

What if a data source is down?

The layer is reported as not screened, and the developable area is flagged as optimistic by an unknown amount. Civexa never silently substitutes an absence of data for an absence of constraint.

Does this replace a critical-areas review?

No. It tells you whether one is likely to be needed and what it would be looking at, before you pay for it.