
In this five-minute demo, I walk through a map-based prototype for planning mine clearance, tracking progress, and preparing completed-area records for registration.
Over the past year, I’ve been involved in developing a Mine Clearance Planner proof of concept. I recently revisited the project and recorded a walkthrough to show how the pieces fit together, from estimating the work to reviewing a completed area.
The question behind the project is straightforward. If one team plans the work, another carries it out, and several organisations need the results, what information should travel with the map? A boundary tells you where an area is. The people working with it also need to know what was planned, how much work remains, and whether the completion record has been reviewed.
Planning for one machine or several
The planner starts with four inputs: machine count, working width, speed, and working hours per day. Together, they give the team an estimated daily capacity. That makes it easy to compare the same area under different assumptions. What could one machine cover in a working day? How does the estimate change if more machines are available?
The planner treats this as a capacity estimate. Actual progress depends on site conditions, downtime, and how the work is organised. Keeping those assumptions visible gives the team a basis for revisiting the plan as it learns more.
Once an area is drawn, the prototype divides it into segments. The operator can inspect individual segments on the map and export one or several together as GeoJSON.
Using satellite imagery to understand the area
In the video, I use a Sentinel‑2 overlay to see how a proposed work area relates to the surrounding landscape. The opacity slider lets me compare the image with the basemap, making it easier to see features such as field edges and nearby roads.
Imagery is one input to the planning process. Its date and resolution affect what you can see, and field survey and verification provide the evidence needed to establish clearance boundaries. In the prototype, the overlay helps the team understand what it’s looking at and decide what to investigate further.
Following progress and reviewing the result
As segments are marked done, the map updates the share of the area completed, the share left, and the estimated working days remaining. I make those updates manually in the demo. In a future workflow, recorded vehicle activity could help populate the progress view for the team to review alongside field evidence.
When the last segment is marked done, the full area remains visible on the map while the team starts work on the next plan. The Completion history page lets a reviewer reopen the boundary in a small map, accept the record, and export it for registration. The export includes the boundary and review details. In the prototype, that handoff is a file download.
What I wanted to show
The part I find most useful is that follow-up stays connected to the original plan. A reviewer can see the area the team worked on, return to it later, and share a record that carries more context than a polygon alone. Over time, that history makes it easier to answer what has been reported complete, what has been reviewed, and what still needs attention.