Mark finished areas on the completion grid
On a LandXML excavation job the app can't tell from the bucket where you've finished, so you mark it: tap a grid cell to turn it green, tap again (or long-press) to clear it, Clear Marks to start over. Cells are 3–30 m, 11 m by default, locked when you apply the design.
- DIG™ Kit
- Ditch Assist Lite
In the app Excavation › Import Civil Design (LandXML) › map; Settings › IMPLEMENT › Excavator Grid Cell
A scraper's coverage paints itself wherever the blade goes. An excavator swings, lifts and dumps, so the app can't tell from movement where you've actually finished. On a LandXML job you mark it yourself: the design is covered by a grid of squares, and you tap a square green when that part is done.
The grid is on LandXML jobs only; trench and level-area jobs track progress on the profile chart instead.
Before you start
- A LandXML design loaded and calibrated on the dig screen (Dig to a LandXML design)
Time: a tap per square as you finish it.
Mark and unmark
Find your square
White squares cover the design. The one the machine is in has an amber outline, so you can see which square you're about to tap. The small label at the top right of the map reads Tap a grid cell to mark complete
.
- Your square. Amber outline around your dot.
- The label. Before you've marked anything.
Tap a square you've finished
When the bottom of a square is done and checked, tap the square. It fills green. It doesn't have to be the one you're in: mark ahead, behind or to the side.
- A square. Tap it to fill it green.
The label at the top right now counts the marked squares (7 cells complete
), and a red-outlined Clear Marks button appears in the right-hand column:
- 7 cells complete. Squares marked so far.
- Clear Marks. Wipes every mark (asks first).
Tap a green square again to clear it. A long press always clears, if you're not sure what state a square is in (long-press).
To start over, tap Clear Marks
Clear Marks is in the right-hand column, under Reset. Tap it. A window asks Clear all marks?
.
- Clear Marks. Under Reset.
Tap Clear Marks in the window
Tap Clear Marks at the bottom right of the window to remove every mark; the design stays loaded. Cancel keeps your marks.
- Clear Marks. Removes them all.
- Cancel. Keeps your marks.
To clear the design as well, use Reset (it clears the whole job from the screen; saved files stay).
Cell size
- Each new LandXML job starts at the Excavator Grid Cell setting (in Settings, under IMPLEMENT): 3–30 m in 1 m steps, 11 m by default. It's in metres in every unit setting.
- You can change it for one job with Completion grid cell size in the LandXML dialog, before you tap Apply.
- Once applied, the size is locked into that job so your marks never shift. To use a different size, import the design again as a new job.
- On very large designs (over about 8,000 cells) the app only draws your marked cells and the current cell, to keep the map quick.
- Excavator Grid Cell. The starting size for new LandXML jobs.
Pick a size you can work square by square: about a bucket-swing across is a good start. Smaller squares mean more tapping but a closer record.
Saved with the job
Every mark is saved with the job (on Stop, when you leave the screen, and as you work). Open Excavation and tap Resume Job: it puts every green square back where it was, with the design. It asks Calibrate GPS?
each time: calibrate on the control point again unless it's the same day and base setup.
If something goes wrong
- No grid on the map: the grid is only on LandXML jobs, and the label at the top right hides when no design is loaded.
- A tap marked the wrong square: tap it again, or long-press it.
- Marks gone after reopening: open the job from Resume Job, not a fresh import (Save and resume jobs).
- Grid or overlay not showing on a big job: overlay doesn't fill in.
Did this answer your question?
Thanks. That tells us which pages to improve.
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.