Learning Center

SURVEY

Settings Reference chapter of the Ditch Assist app manual. The same text is in the app under Manual.

In the app Manual › Settings Reference › SURVEY

Survey Interval — minimum distance between recorded survey points. Default 10 ft / ~3 m. The app ships in imperial by default, so you'll see this expressed in feet first; switch to metric in UNITS and the same setting becomes meters. Common values: 1.6 ft (0.5 m) for short detailed lines; 3 ft (1 m) for normal detail; 10 ft (3 m) default; 16 ft (5 m) for very long ditches. Smaller interval = more terrain detail, bigger files.

Blade Height — how high the cutting edge of your implement sits above the ground with the implement raised in transport (survey) position. The app subtracts it from each survey point. Critical when you survey in this app and then grade against that survey-derived design (Ditching, Simple Grading, Tiling, Terracing) — an error here puts every target off by the same amount. For imported designs (Forming, Tiling AGD), the design carries its own elevations and blade height is not part of the math as long as your benchmark is calibrated. Use Auto Measure to calibrate from the implement directly. If you Skip the Blade Height prompt, it suppresses for the rest of the session but will fire again on next app launch.

Auto Measure (button) — runs a 10-second RTK-averaged measurement at the implement's UP position, then again at the DOWN position. The difference (UP elevation − DOWN elevation) becomes the blade height. The button is in the same row as the Blade Height value.

Benchmark Offset — read-only readout of the live GPS-to-survey-frame offset, with its source label (e.g. "Manual offset (Settings)"). Shows in ft (imperial) or m (metric), or Not set in italics when no BM is active. Tap Open calibration to jump straight to the Calibrate Elevation sheet — that's where you recalibrate, type a known elevation, zero to current GPS, or clear. The offset persists across app restarts.

RTK Filter — when on, surveys only record points while RTK is fixed. Float and lower fixes are dropped. Default ON. Turn it off only for receivers that report a true RTK solution as DGPS — John Deere StarFire SF-RTK is the documented case; anything surveyed, calibrated, or graded on a non-RTK fix with the filter off is at your own risk. The filter also cannot detect satellite PPP correction services (Trimble CenterPoint RTX, Hexagon/NovAtel TerraStar-X / TerraStar-C PRO, John Deere SF3) that some receivers label with the RTK fix code — those are not true RTK and are not endorsed either.

RTK Sensitivity — how aggressively to engage Auto-Hold on GPS quality drops. Low / Mid / High. Default Mid. Low holds only when the RTK Fixed solution is lost or positions go stale, and ignores HDOP altogether — pick it when your receiver's HDOP sits at 1.0 or above all day, which happens when the base sends fewer constellations than the rover tracks. Mid and High add the HDOP band and the fix-stability window on top. (Previously listed under CONTROLLER in older builds — it lives here in the current build.)

(There is no Operator Name row in Settings — the operator name is typed in the Send Logs dialog, where it is required before sending, remembered for next time, and attached to the uploaded log package.)

Did this answer your question?

Still stuck? Talk to a product specialist. 1-833-DITCH-AS · support@ditchassist.com · Monday to Friday, 8 a.m.–5 p.m. Central.

Calling about a problem? Send your app logs first so support can see what happened.