Soil & Water
Conservation Monitor

A field data platform supporting water organizations across the Great Lakes region — designed around Lake Erie basin monitoring objectives and Ohio EPA assessment protocols.

Ohio EPA Protocols NHD Integration Multi-watershed Role-based Access
Program Photo
500+
LEBAF Observations
200+
QHEI Assessments
12+
Active Watersheds
180+
Reaches Defined

Field Protocols

Monitoring Programs

Add Photo
Biological & Chemical

LEBAF

Lake Erie Basin Assessment Framework — a comprehensive biological and water quality monitoring protocol for Lake Erie tributary streams.

Add Photo
Physical Habitat

QHEI

Qualitative Habitat Evaluation Index — Ohio EPA protocol for assessing instream and riparian habitat quality.

Add Photo
Headwater Habitat

HHEI

Headwater Habitat Evaluation Index — rapid assessment protocol for small, intermittent, and headwater streams.

Add Photo
Headwater Macroinvertebrate

HMFEI

Headwater Macroinvertebrate Field Evaluation Index — Ohio EPA rapid bioassessment protocol for headwater and small stream macroinvertebrate communities.

Platform Technology

Automated datasets, connected to every form

Every reach definition, QHEI assessment, and watershed boundary pulls from federal geospatial datasets automatically — so field teams collect data, not coordinates.

Mode:
Select stream
Two-point
Draw
Clear
Done drawing
✓ Reach measured — ready to save 7.8 ft/mi 2.31 mi Drop: 94.6 ft Moderate gradient ↑ 1,187 ft  ↓ 1,092 ft
🔒 Demo view

Hover the labels — each explains what the platform resolves automatically

Two-point reach definition

Click any two points near a stream. The platform snaps both to the nearest NHD vertex, traces the hydrographic path between them, queries 3DEP elevation at each endpoint, and returns gradient, distance, and drop — automatically.

NHD vertex snap — both points lock to the nearest National Hydrography Dataset feature, ensuring reach boundaries conform to the national stream network
BFS path tracing — the platform searches the connected NHD graph between your two points, assembling the correct reach geometry even across multiple NHD features
3DEP gradient — USGS 1/3 arc-second elevation at upstream and downstream endpoints gives geodetically accurate slope in ft/mile
QHEI pre-fill — gradient category and distance auto-populate Section G of the QHEI form when this reach is selected
USGS · NHD

National Hydrography Dataset

The USGS NHD is the authoritative stream network for the United States — every named stream, tributary, and artificial path, with FCode classification (perennial, intermittent, canal, etc.) and ReachCode identifiers.

What this means: Reach boundaries defined in the platform conform to the national standard. Stream names, lengths, and FCode classifications are imported automatically. Data is compatible with EPA STORET, ATTAINS, and other federal water quality databases.
USGS · WBD

Watershed Boundary Dataset

USGS HUC-8, HUC-10, and HUC-12 watershed delineations provide the geographic container for every monitoring site. Boundaries are fetched by HUC code and stored as GeoJSON.

What this means: Administrators enter a HUC code and the watershed boundary polygon is automatically retrieved, displayed on all maps, and used to validate that reach definitions stay within bounds (≤10% outside enforced). No manual GeoJSON upload required for HUC-defined watersheds.
USGS · 3DEP

3D Elevation Program

The USGS National Map 3DEP service provides 1/3 arc-second (~10m) elevation data across the contiguous US. Elevation is queried at individual coordinates using the EPQS point-elevation API.

What this means: Every defined reach gets upstream and downstream elevation automatically. Gradient in ft/mile is computed geodetically and stored with the reach. QHEI Section G (gradient category and score) is pre-filled without any manual calculation.
USDA · NRCS

Web Soil Survey

The USDA NRCS Soil Data Access (SDA) service provides soil map unit polygons, series names, hydrologic soil groups, and land capability classes for any geographic extent via WFS and tabular queries.

What this means: On the QHEI map, field teams can toggle a soil survey overlay showing dominant soil series and hydrologic groups within the study watershed. This context informs riparian zone interpretation and helps explain substrate conditions observed in Sections A–D.
OSM · USGS Topo

Basemap Layers

All field forms and the Explore map support multiple basemap layers: OpenStreetMap streets, USGS National Map topo (with elevation contours and stream labeling), and OpenTopoMap. Layers are switchable in the field.

What this means: Field teams can switch to the USGS Topo basemap to see named streams, contours, and survey marks while on site — the same reference data used by USGS for stream characterization.
Platform · Reporting

Structured Data Export

Every LEBAF and QHEI observation is stored with its reach GeoJSON, HUC code, NHD ReachCode, watershed area, and observer metadata — ready for spatial analysis or submission to state and federal databases.

What this means: Full edit audit trails, approval workflows, and reach-linked observations give program coordinators a complete data provenance chain — from field collection to final approved record — with automatic gradient and soil context attached.
Watershed Photo

About the Program

Protecting the
Lake Erie Watershed

The Soil & Water Conservation Monitor is built for water organizations and conservation districts working across the Lake Erie watershed. The platform connects field teams to standardized assessment protocols, supporting tributary health monitoring and Lake Erie water quality objectives.

Lake Erie Focus
Designed around tributary monitoring objectives in the Lake Erie basin and Great Lakes region.
Multi-Watershed Teams
Role-based access across multiple watersheds and field teams.