01
Erosion intelligence
Daily soil-loss modeling, without the black box.
RUSLE2-aligned management simulation combines local soil, terrain, erosivity, vegetation, residue, and operations into traceable annual results.
TerrainLogic beta
From a field boundary to an engineering-ready decision.
Bring terrain, soils, climate, management, and field history together in one auditable desktop workflow—built for conservation planners, engineers, and land managers.
Local-first50-state testedScience-traceableField-history aware
01 / The platform
One field model.
Connected decisions.
TerrainLogic preserves the relationships between land, management, and time. Each run can be explored as a scenario or authored into the managed field’s history for the next cycle.
02
Nutrient accounting
Follow nutrients through the management cycle.
Track additions, crop uptake, biomass return, legume fixation, residue transformations, and carried field state in a dedicated nutrient report.
03
Gully risk
See where concentrated flow is likely to become a problem.
Map terrain-driven corridors on satellite imagery and trace contributing area beyond the field boundary.
04
Waterway engineering
Move from hotspot to a documented preliminary design.
Carry mapped flow paths into channel sizing, editable design constraints, survey tables, dig profiles, as-built comparisons, and inspection history.
Explore engineering →02 / Erosion modeling
Field-scale erosion, with the evidence attached.
TerrainLogic resolves the field, terrain, soils, climate, and management into a daily RUSLE2-aligned simulation. The result is shown against soil tolerance T, with R, K, LS, C, P, soil moisture, and SCI available for review.
- Draw or select the field on satellite imagery
- Model exact operations or producer-relative timing
- Inspect daily factors instead of accepting a black-box total
- Generate a standalone, auditable erosion report
03 / Nutrient tracking
See how the management cycle moves N and P.
The nutrient workspace follows fertilizer and manure additions, crop uptake and harvest export, biomass and roots returned to soil, legume fixation, environmental pathways, and carried field state from the beginning to the end of the cycle.
Planning-level accounting.Mass-balanced estimates are intended for conservation screening and scenario comparison—not fertilizer recommendations, regulatory nutrient-management plans, or soil-test interpretation.
- Works with explicit additions or modeled crop/residue movement
- Continues from a prior authored field state
- Reports starting pools, ending pools, gains, losses, and exports
- Produces a dedicated nutrient report separate from erosion
04 / Field workflow
Built around how the work actually moves.
Use authoritative local and public data where possible. Add professional judgment where it matters. Keep the evidence attached to the field.
- 01
Locate
Draw a field or select an estimated boundary. TerrainLogic resolves county, climate, soils, elevation, slope, and flow context.
- 02
Model
Select or author exact management operations. Run a new scenario or continue the field’s managed state.
- 03
Decide
Review erosion, soil condition, moisture, nutrients, gully risk, and supporting daily evidence.
- 04
Document
Generate separate erosion, nutrient, and engineering reports; save the run to field history when it becomes the plan.
05 / Engineering workspace
Follow the water.
Then size the practice.
TerrainLogic carries terrain-derived flow information from the field map into a transparent preliminary grassed-waterway workflow. Mapped geometry supplies context; the responsible professional still selects and documents the governing engineering inputs.
Start with concentrated flow.
Potential corridors are shown on satellite imagery with total and in-field contributing area, corridor slope, severity, and DEM-coverage checks.
Field-to-design handoff
The site context follows the selected corridor.
Reach length, contributing area, design grade, local rainfall context, soil erodibility, and vegetation choices are assembled in one workspace. Peak discharge remains editable and its source is recorded so a documented EFH-2, WinTR-55, NETS, or state-approved value can control the design.
- Mapped upstream area and reach geometry
- Editable 10-year, 24-hour peak discharge
- Vegetation and hydraulic-retardance selection
- Capacity, velocity, stress, and side-slope checks
Document the design basis.
Field-derived values arrive prefilled while the designer can review, replace, and recalculate the governing inputs.
Review a constructible section.
See flow and excavation dimensions, inspect the cross section, and continue into centerline and edge surveys, a dig profile, engineering documents, and as-built comparison.
Included in Beta 1
Terrace design
DEM-assisted layout, sizing, and construction survey.
TerrainLogic can propose contour-aligned terrace locations from the selected field DEM, calculate a preliminary CPS 600 planning section, and prepare stationing for a construction survey and stakeout profile. Designs must still be checked against the applicable state FOTG and verified by field survey.
06 / Local dashboard
A working portfolio of managed fields.
The desktop dashboard brings every locally managed field together without requiring a cloud account. Review current management, latest erosion, authored cycles, reports, saved waterways, and practices that need attention.
Field-centered recordsLocal-first storageOne-click reports
07 / Stateful field design
The next decision starts where the last cycle ended.
A scenario can remain a what-if. An authored run becomes field history, preserving the ending residue, biomass, water, soil-condition, and nutrient state as the starting context for the next management cycle.
Existing field state→Scenario or authored cycle→Next-cycle starting state
Future capability
08 / Watershed intelligence
From private field decisions to watershed-scale understanding.
ContourStack is developing a privacy-protected aggregation layer for HUC12 watersheds. Individual field boundaries and management records remain local; only qualified, anonymous summaries contribute to watershed research and monitoring.
USGS watershed boundaries provide national context and progressively reveal HUC12 detail as users zoom.
Published polygons can report modeled acres, average soil loss, acres meeting T, field count, and—when available—nitrogen and phosphorus movement.
Watershed erosion
See where modeled outcomes are improving.
Aggregate soil loss, acres meeting soil-loss tolerance, modeled acreage, and conservation-management coverage by HUC12 and reporting year.
Watershed nutrients
Follow nutrient movement without exposing a farm.
Summarize planning-level nitrogen and phosphorus movement across qualified watersheds while keeping identifiable field records out of the aggregate product.
Privacy by design
No single field becomes the story.
Minimum-field publication thresholds suppress small groups. Uncolored watersheds mean insufficient publishable data—not zero erosion or nutrient loss.
Planned capability: the watershed dashboard is under development and is not part of the current TerrainLogic beta. Measures will be modeled planning indicators for research and watershed monitoring, not regulatory determinations.
05 / Confidence
Designed to be challenged.
TerrainLogic separates equation verification, reference-model parity, and independent observational validation. See the evidence, metrics, source literature, applicability domains, and unresolved limitations on the dedicated science page.
749-case erosion parity benchmarkRow-level nutrient comparisonsKnown limitations documentedReproducible source manifests
Read the science & validation record ↗
09 / Report library
10 report typesEvery decision can leave with its documentation.
Open any example to see the actual TerrainLogic report format. These are generated from realistic field, management, and engineering scenarios—not marketing mockups.
Soil-Loss Analysis ReportErosion, T, factors, soil condition, and provenance
Nutrient Tracking ReportStarting and ending N and P balances and pathways
Gully Hotspot Screening ReportNumbered satellite field map, terrain corridors, contributing area, and field checks
Management Comparison ReportCurrent management compared with a proposed alternative
Managed Field Lifecycle ReportManagement years, field states, practices, and inspections
Data & Assumptions AuditInput sources, model modes, warnings, and traceability
Waterway Engineering PackageDesign basis, section, checks, survey, and dig profile
Waterway As-Built PackageDesigned versus constructed dimensions and acceptance
Terrace Engineering PackageLayout, hydraulic sizing, section, and stakeout survey
Practice Inspection ReportAs-built record, routine inspections, status, and follow-up
10 / System requirements
Low-end testedBuilt to run on an ordinary Windows field computer.
TerrainLogic does not require a workstation-class processor or a dedicated graphics card. Low-end compatibility testing covered installation, site determination, repeated erosion and nutrient runs, gully screening, waterway and terrace design, saved-field reloads, memory recovery, and clean shutdown.
Tested baseline
Verified on low-end hardware
- Processor
- Intel Core i3-10110Y @ 1.00 GHz
- Memory
- 8 GB RAM
- Graphics
- Intel UHD integrated graphics
- Storage
- 128 GB SSD
- Operating system
- Windows 11, 64-bit
Minimum supported
For normal TerrainLogic workflows
- Intel Core i3-class processor or comparable AMD processor
- 8 GB RAM
- SSD storage with at least 5 GB free
- Windows 11, 64-bit
- Reliable broadband connection for initial public-data retrieval
- No dedicated GPU required
Recommended
For faster startup and larger terrain scans
- Intel Core i5-class processor or comparable AMD processor
- 16 GB RAM
- SSD storage
- Windows 11, 64-bit
- Reliable broadband connection
Observed low-end performance: four consecutive field runs completed without error. Routine analyses used approximately 215–250 MB of application memory. A more intensive terrace DEM scan briefly peaked near 600 MB and released that memory after processing. Initial startup was the principal low-end tradeoff.
For technical teams
Bring your questions. See the workflow live.
Request a focused TerrainLogic briefing for your conservation, research, engineering, or program team. We will tailor the demonstration to the capabilities and decisions that matter to your organization.
Live platform walkthroughScience and validation discussionOrganization-specific Q&ARequest a technical briefing ↗
Private beta
Put TerrainLogic to work on real fields.
We’re inviting conservation professionals and land managers who want to test workflows, compare results, and help shape the next release.