USDA SSURGO Soil Maps by Address: Map Units, Components, and Property-Level Limits
Learn how an address becomes a USDA SSURGO soil profile, why map units contain multiple components, how horizons relate to components, and where survey data stops short of a field soil test.
A soil map can offer valuable context about a property, but it does not reveal a laboratory-tested column of earth beneath an exact foundation. USDA SSURGO data describes surveyed map units, their expected soil components, and the properties reported for those components. Understanding that hierarchy is the key to using an address-based lookup responsibly.
1. What SSURGO Actually Maps
The Soil Survey Geographic Database (SSURGO) combines mapped soil boundaries with a relational database of survey information. The geographic layer is divided into polygons. Each polygon references a map unit, and the map unit can contain more than one named soil component.
A boundary is a survey interpretation at the published mapping scale, not a fence around perfectly uniform material. Natural transitions, small inclusions, past grading, imported fill, and local disturbance can all create conditions that differ from the representative survey description.
confirmed coordinate → SSURGO polygon → map unit → components → horizons and attributes
2. From Address to Map Unit
An address-based soil lookup is a sequence of separate operations:
- Geocode the search. A street address is converted to longitude and latitude. Broad searches such as a city or ZIP resolve only to an approximate center.
- Confirm the point. The user checks the result on a map and moves the marker when necessary.
- Intersect the soil layer. The confirmed WGS84 point is tested against USDA soil polygons.
- Retrieve related records. The resulting map-unit key connects to the tabular SSURGO records needed for a readable profile.
This is why “soil by ZIP code” is usually the wrong model. A ZIP can cross many landscapes and map units. The relevant question is which polygon contains the selected coordinate.
3. Components and Horizons
Map-unit components describe the soils expected within the mapped area. Their reported percentages help explain composition, but they are not probabilities that prove what sits beneath one point. A dominant component may cover much of a map unit while minor components occur in depressions, slopes, or other landscape positions.
Horizons belong to a component. They describe vertical layers with reported upper and lower depths and may include texture, sand/silt/clay percentages, organic matter, pH, available water capacity, Ksat, or other properties. Avoid mixing an attribute from one component with the horizons of another; the component relationship supplies essential context.
4. Missing Data and Uncertainty
A blank survey value is not zero. It may be unreported, not applicable, outside the scope of the survey, or unavailable for that record. A trustworthy interface keeps “not reported” distinct from a measured zero and retains source identifiers such as survey area and map-unit key.
Precision also matters. A geocoder may place a point at a parcel entrance, street centerline, rooftop estimate, or locality center. Confirming the marker before the soil query prevents address precision from being confused with soil-survey precision.
5. Appropriate Uses and Limits
SSURGO profiles can support:
- early property and landscape research;
- questions to raise with a landscaper, engineer, soil scientist, or local authority;
- preliminary context about mapped drainage, texture, wetness, and restrictive layers;
- comparison of the survey context around multiple confirmed points.
They do not replace a soil boring, laboratory analysis, septic perc test, wetland delineation, groundwater measurement, foundation assessment, or geotechnical investigation. Use Subsurface Atlas to inspect the mapped evidence, then obtain site-specific expertise when a decision affects construction, safety, permitting, or significant expense.