Site Conditions
Once the work area is drawn, Mastiff measures it against public survey data — USGS elevation for slope, NRCS soil survey for rock and drainage — and proposes the site-condition multipliers that fit. Nothing is ever applied behind your back: you see the evidence and decide.
Mastiff Free · $0 forever · No credit card
The problem
Steep ground slows a machine down. Rock eats teeth. Wet ground turns a two-day job into a week of ruts and a callback. Every operator knows to price for it, and almost nobody has a number — so the multiplier is a gut call made from a truck window, and it's wrong in whichever direction hurts.
Without Mastiff
With Mastiff
How it works
Site conditions measure the polygon from your satellite takeoff, so the reading covers the ground you're actually clearing rather than the whole parcel.
Mastiff queries the national elevation dataset for slope across the tract and the soil survey for surface rock fragments and drainage class. Results cache against the geometry, because terrain doesn't change.
A quiet band offers what the data supports — steep, rocky, wet — each with the measurement behind it. Nothing is applied until you tap it.
One tap applies the multipliers to the bid. Your eyes on the ground still win; the measurement is there to inform the call and to back it up afterwards.
Capabilities
Slope degrees are computed server-side across the drawn area, and both the mean and the 90th percentile are read — so a tract that's mostly flat with one brutal face is still caught.
Component-weighted surface rock fragments and the dominant drainage class come from the NRCS soil survey. Rock-outcrop components with no horizon data are imputed conservatively rather than skipped.
Each proposal carries the line that produced it, phrased as a measurement rather than an instruction. You can see why the tract read steep before you agree that it is.
When the data contradicts a condition you've set by hand, it says so — "Wet / swampy — Well drained (NRCS)". A tool that only ever agrees with you is not measuring anything.
The multipliers change what the customer pays, so they never move on their own. The band offers; one tap commits; your judgement is the last word.
Terrain doesn't change, so a successful reading is cached against the geometry and returns instantly on every later look. Failures are never cached, so a bad day for a government API doesn't poison the job.
FAQ
Two public sources: the USGS 3D Elevation Program for slope, and the USDA NRCS Soil Data Access service for surface rock fragments and drainage class. Both are free and keyless — site conditions add no subscription and no per-lookup cost.
No, and that's deliberate. Site conditions move what the customer pays, so the measurement only ever proposes. You see what was measured, you decide whether it matches the ground, and one tap applies it.
Steep fires at a 15-degree mean slope or a 25-degree 90th percentile, rocky at 25% surface rock fragments, and wet on the poorly-drained soil classes. The thresholds are named and tunable rather than buried in a formula.
Overrule it. Public survey data is coarser than a pair of boots, and it can't see a spring that showed up last winter. It exists to catch what you can't see from the road and to give you something to point at — not to bid the job for you.
Draw the tract, read what the ground actually is, and price the hill before it prices you.
1 active job + 1 active quote free forever