Bhu-Suraksha
How it works

From field survey to a tamper-proof registration record

One system, three linked outputs — a GPS-tagged boundary, a hash-secured record, and a QR code — built into the registration workflow, not bolted on after.

  1. Step 1

    Field survey

    A certified surveyor (or the citizen themselves, for self-service registration) captures the plot's boundary as GPS coordinates — walked corner to corner, or drawn against satellite imagery.

    Try a boundary capture

  2. Step 2

    Record created

    The boundary and its metadata (area, centroid, capture method, timestamp) are stored as a parcel record and cryptographically signed with SHA-256 — any later edit to the row is detectable.

    How the signature works

  3. Step 3

    QR generated

    A compact Geo ID and matching QR code are issued for the parcel — scannable on the printed deed, and resolvable by anyone without logging in.

    Enter a demo Geo ID

  4. Step 4

    Registrar scans

    At submission, geometry is auto-checked against every neighboring registered plot, and the survey number is checked against other active records for the same village — overlaps and duplicate registrations are flagged before approval, not after.

    See flagged plots on the map

  5. Step 5

    Locked to deed

    The verified boundary is embedded in the registration certificate. Every future transaction on this parcel references the same locked boundary record — the chain never breaks.

See the whole chain end to end on a real demo plot — Survey No. 123/A, Beeramguda.

View its public record

Built to plug into the existing registration workflow

This proof of concept implements every stage below against a self-contained SQLite database so it runs anywhere with no external services — a production pilot would swap the spatial-data layer for PostgreSQL + PostGIS without changing anything upstream or downstream of it.

Field Capture

GPS walk-capture or satellite-image tracing, standing in for DGPS/drone survey at pilot scale.

Spatial Data

Every parcel stored as a real polygon; geometry math via Turf.js. A production pilot would move this to PostgreSQL + PostGIS.

Hash & Signature

SHA-256 record signing over each capture's immutable fields — tamper-evident by design.

QR Generation

Compact Geo ID plus a scannable QR, generated on demand for any registered plot.

Registrar Workflow

SRO review queue auto-fills the computed extent and surfaces conflicts and duplicate-survey warnings inline.

Public Verification

Anyone — buyer, bank, department — can scan and confirm a plot's boundary, ownership, and signature validity.

See the whole system in action

Explore all plots on the mapOfficial / Citizen Login