Survey/Resurvey of Rural Agricultural Land in lndia

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   SVAMITVA is already doing exactly this at national scale with drone surveys and property cards, and 'how is this different from SVAMITVA' is a question you must have a real answer to, not a deflection

2. It gets worse

   Survey-grade positioning hardware costs more than most teams' entire budget, and a consumer GPS with metre-level error produces boundaries that are useless for a cadastre and obviously so

3. Still reading?

   RoR, mutation and registration databases are held by state revenue departments and are not accessible, so the unified system at the heart of the statement can only ever be demonstrated on mock data

4. And the finisher

   The statement has no defined output at all, which sounds freeing but means judges will each measure you against a different imagined deliverable

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  2/5

  You have picked a fight with physics, procurement, or both. One of them always wins.

  Survey-grade RTK/DGPS receivers start around a lakh and a photogrammetry drone with RTK several times that, the CORS network needs authorised access, and the RoR, mutation and registration databases the unified system is supposed to integrate are state-controlled and simply will not be opened to a student team.

• Innovation scope

  3/5

  Mildly interesting. The novelty will not carry the room; the build has to.

  The expected solution names the technologies to use and the records to integrate but never defines the artifact, so paradoxically you have wide latitude in what you actually build — though every direction runs into the same access wall.

• Clarity

  2/5

  Nobody is sure what is being asked, quite possibly including the people who asked it.

  The background is a well-written policy note and the expected solution is a list of technologies and databases with no deliverable attached — no accuracy target, no scale, no output format — so nothing here tells you what a correct submission looks like.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  SVAMITVA has already drone-surveyed lakhs of villages and Bhu-Naksha already links cadastral maps to RoR, so you are proposing something the government is actively executing at national scale, and the equipment that would let you compete on accuracy is out of reach.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  Field survey capture, photogrammetric or RTK processing, cadastral GIS production, a field verification app and a unified land information system integrating five separate record types is a multi-year government programme compressed into a problem statement.

• Demo-ability

  Hard

  Near impossible to show working in five minutes, which is roughly five minutes more than you get.

  The defining act is surveying real agricultural parcels against real ownership records, and you can do neither — a campus plot with mock records demonstrates the tooling but not the thing the statement is about.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 50–120 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The problem is real and universally understood, so you never have to justify why land record accuracy matters
• If your college already owns an RTK rover or a survey drone through a civil engineering department, the single biggest barrier disappears and you become one of very few teams who can show real centimetre-accurate capture
• The absence of a defined deliverable means a team that proposes a sharp, narrow artifact — say, a boundary dispute resolution tool over surveyed parcels — can define the evaluation on its own terms