Case study

Mapping 575 km² for a lift irrigation project in 65 days

A case study from my earlier career: 10 to 15 clusters in Odisha, two drone pilot teams, a DGPS team, and maps for pipeline alignment planning.

By Naresh KaviyarasanLift irrigation · Odisha

575 km²Area mapped

The full scheme, in one project.

10–15Clusters

The scheme was spread across 10 to 15 clusters.

45 daysData capture

Two drone pilot teams and one DGPS team in the field.

≈65 daysStart to delivery

Final outputs handed over to the client.

The project

This was a lift irrigation scheme in Odisha. In lift irrigation, water is pumped up from a river or reservoir and carried through pipelines to land that sits higher than the source. Where those pipelines can run depends on the ground, so the first job was a map of the ground.

The scheme was spread over 10 to 15 clusters, about 575 km² in all. My role was to run the field side of it: mobilise the teams, plan the flights, manage the ground survey, and get the data to the processing team and the final outputs to the client.

What was delivered

The client received four outputs for the whole area, to plan the pipeline alignment on.

Orthomosaic

One georeferenced, distortion-corrected image of the whole area, stitched from the drone photos.

Shows what is on the ground.

DTM

The height of the bare ground, with trees and buildings removed.

Shows how the ground rises and falls.

Contour maps

Lines of equal elevation, drawn from the terrain model.

Makes slope readable at a glance.

Point clouds

The 3D measurements the other products are built from.

Source data for checks and re-processing.

For a pipeline, the terrain model and the contours are what show where a route climbs and where it falls.

How the work was organised

Capture was done by two drone pilot teams, with one DGPS team working alongside them. I led the work on the ground:

  • Mobilisation. I put the teams together and got them to site.
  • Flight planning. I prepared the flight plans for the pilot teams.
  • Ground control. I managed the DGPS team, who survey the control points that tie the drone images to real-world coordinates.
  • Operations. Travel, accommodation and day-to-day logistics for the teams.
  • Data and processing. I looked after data backup and coordinated with the backend team that processed the data.

The timeline

Data capture was completed in 45 days. The whole project, from start to the final outputs, took about 65 days. Averaged over the capture period, that is about 13 km² a day across the two pilot teams.

Handover

The final outputs were handed over directly to the client on a hard disk. Orthomosaics and point clouds for an area this size run to very large files, and a hard disk is a normal way to deliver them.

Why I am writing it up

Samara Geospatial processes drone and lidar data into survey-ready outputs and takes on large-area mapping. This project is the clearest picture I can give of how I run that kind of work. If you have an area to map, or data waiting to be processed, tell us about it.

Written byNaresh KaviyarasanFounder, Samara Geospatial · Chennai, India

Start a project

Have an area to map?

Tell us the area, the outputs you need and your deadline. We reply with a plan and the accuracy check we would use.