How-To

Federal data layers for a defensible environmental screen

June 4, 2026  ·  4 min read  ·  Jacob, founder of Avow

On most projects, the slow part of a desktop environmental screen is not the analysis. It is the assembly. Before a practitioner can reach any judgment, someone has to find the right federal datasets, pull each one from the right agency, project them all into a common coordinate system, and clip them to the project area. That work repeats on every project, and it is where the time goes.

This post walks through the federal datasets a defensible screen pulls, explains why each one belongs in the record, and lays out the data hygiene that keeps the result standing up to review. A one-page version of the list is available to print or save; it arrives with the first email when you subscribe to the newsletter.

Waters, wetlands, and terrain

Start with the layers that drive the Clean Water Act and floodplain questions, because those often govern whether a project needs a federal permit.

The National Wetlands Inventory (NWI), from the U.S. Fish and Wildlife Service (USFWS), is the desktop indicator of potential wetlands and their classification. The National Hydrography Dataset (NHD), from the U.S. Geological Survey (USGS), maps streams and waterbodies and records flow permanence, which matters for Clean Water Act jurisdiction after the Sackett decision. The National Flood Hazard Layer (NFHL), from the Federal Emergency Management Agency (FEMA), shows the Special Flood Hazard Areas and the regulatory floodway. Soils come from the Soil Survey Geographic Database (SSURGO), maintained by the U.S. Department of Agriculture, where the hydric-soil rating is a primary wetland indicator and a flag for site constraints.

Species and habitat

For the Endangered Species Act (ESA), pull the official species list from the U.S. Fish and Wildlife Service Information for Planning and Consultation (IPaC) system. That list is the attachment the agency requires when a project initiates Section 7 consultation, and it changes as species are listed or delisted, so it has to be current for the action area. Add ESA critical habitat, because designated critical habitat that intersects the project area is a direct Section 7 trigger. Where a project touches a managed fishery, add Essential Fish Habitat from the National Marine Fisheries Service, which carries its own consultation requirement.

Land status, cultural resources, and context

Round out the screen with the layers that establish land status and cultural context. Protected Areas (PAD-US), from USGS, shows the federal, state, and other managed lands that intersect the site. The National Register of Historic Places, from the National Park Service, is the starting point for a National Historic Preservation Act Section 106 review of historic properties. Tribal areas, from the U.S. Census Bureau, indicate whether government-to-government consultation may be in scope. Land cover, from the National Land Cover Database, supplies the existing-conditions baseline.

The data hygiene that keeps it defensible

Pulling the layers is half the work. The discipline applied to them is what makes the result hold up under review.

  • Project every layer into one coordinate system before measuring or overlaying anything, because a mismatched projection produces silently wrong areas and distances.
  • Clip each layer to the actual project boundary rather than a bounding box, so the acreages reported in the screen describe the site and not the extent of the download.
  • Record the vintage of every source, because a reviewer will ask how current the data was, and that answer belongs in the record.
  • Resolve any layer you could not retrieve before you rely on the screen. A federal endpoint that is down makes the screen incomplete, not negative, so pull that layer from the source, an alternate dataset, or once the endpoint recovers. The mistake to avoid is letting a layer that failed to load read as proof that nothing is present, which is a different and false conclusion.

Why this is worth automating

None of this is difficult. It is simply slow, and it repeats on every project. Pulling, projecting, and clipping a dozen federal layers by hand takes several hours before any analysis begins, and every manual step is another place for an error to enter the record.

That repetition is the part worth removing. Avow pulls each layer current from its official federal source, projects and clips it to the project area, records the vintage, flags anything it could not retrieve, and returns the result in minutes, with symbology ready for QGIS and ArcGIS Pro. The judgment stays with the practitioner. The assembly does not have to.

Avow outputs and these notes are screening-grade input, not legal advice, a jurisdictional determination, or a permit. Final authority rests with the reviewing agencies and the licensed professional of record.
Newsletter

Regulatory changes that move screening, every two weeks.

Short, plain-language notes on the federal rules and court decisions that change how you screen a project area: post-Sackett wetland jurisdiction, NEPA implementation, ESA and NHPA practice. Written for working consultants, planners, and scientists. Subscribe and the first email includes a one-page federal-data checklist.

Biweekly. No spam. Unsubscribe in one click.

Avow  ·  All posts  ·  Methodology  ·  Currency Ledger  ·  Privacy  ·  Terms