From what to build to how to build it — our platform helps you understand, plan, and solve SIH 2026 problem statements with complete insights into requirements, solution approaches, technology stacks, architecture, AI/ML, and implementation roadmaps.
Search for your problem statement, and start building your solution.
| Description: | Background: Historically, land surveys in rural lndia were conducted using conventional chain and tape methods, many of which date back several decades or even the colonial period. Over time, multiple issues emerged such as Boundary changes due to inheritance and informal partition, Unrecorded land transactions, Encroachments and overlapping claims, Errors in cadastral maps, Mismatch between textual records and spatial maps, Absence of updated mutation records and inconsistent land classifications. These deficiencies have resulted in prolonged legal disputes, reduced agricultural productivity, and administrative inefficiencies. Land-related disputes reportedly account for a major share of civil litigation in lndia. Detailed Description: A comprehensive survey/resurvey program is necessary to establish accurate land ownership, Update cadastral maps, Reduce land disputes,Enable transparent land governance, Support precision agriculture, lmprove rural planning, Facilitate digital land administration and Ensure effective implementation of government schemes.Modern technologies such as Drone mapping, Differential GPS (DGPS), GIS platforms, Satellite imagery, CORS, Mobile-based field verification can significanfly improve accuracy, speed, and transparency in rural land management. Expected Solution: Technology-Driven Land Survey and Resurvey be implemented using modern survey technologies for accurate mapping of agricultural land parcels such as Drone-based aerial surveys, Real-Time Kinematic (RTK) GPS and DGPS systems, GIS-enabled cadastral mapping and Geo-referenced parcel identification. Developing a unified digital land information system integrating Record of Rights(RoR), Mutation records, Registration databases, Survey maps, Ownership history,precise Geo-coordinates of land parcels. This integration should enable real-time updating and verification of land ownership. |
| Organization: | Ministry of Rural Development |
| Department: | Dept of land resources (DoLR) |
| Category: | Hardware |
| Theme: | Agriculture, FoodTech & Rural Developmenttd> |
| Youtube Link: | Not provided |
| Dataset Link: | Not provided |
| Contact info: | Not provided |
Rural land administration in India is severely impaired by legacy chain-and-tape survey records, unrecorded land partitions, cadastral map distortions, and spatial-textual record disconnects [PS]. These deficiencies fuel prolonged litigation—accounting for over 66% of civil cases in India [RESEARCHED]—and prevent farmers from leveraging land as collateral [KNOWN]. To address Problem Statement SIH26010, this dossier presents Bhu-Drishti (भू-दृष्टि): an end-to-end, high-precision Land Information & Resurvey Management System (LIMS). The platform ingests High-Resolution Aerial Orthomosaics generated via drone surveys, integrates Real-Time Kinematic (RTK) / Differential GPS (DGPS) mobile field verification via Survey of India's Continuously Operating Reference Station (CORS) network [RESEARCHED], automates parcel boundary detection using computer vision, and generates 14-digit Unique Land Parcel Identification Numbers (ULPIN / Bhu-Aadhaar) [RESEARCHED]. The solution bridges textual Record of Rights (RoR / Khasra / Khatauni) with precise spatial geo-coordinates, enabling real-time automated mutation workflows and conflict resolution for the Department of Land Resources (DoLR), Ministry of Rural Development [PS].
| Property | Value |
|---|---|
| Problem Statement ID | SIH26010 [PS] |
| Title | Survey/Resurvey of Rural Agricultural Land in India [PS] |
| Organization | Ministry of Rural Development [PS] |
| Department | Dept of Land Resources (DoLR) [PS] |
| Category | Hardware (Integrated Hardware-Software Cyber-Physical System) [PS] |
| Theme | Agriculture, FoodTech & Rural Development [PS] |
| Submission Deadline | 30 September 2026 [PS] |
| Ideas Counter | 0/500 [PS] |
| Dataset Link | Not Provided (Public Domain Geospatial & State Land Portals to be used) [PS] |
| Contact / Media | Not Provided [PS] |
| Scraped Timestamp | 2026-09-05 [PS] |
To deliver a unified, offline-capable, drone-and-GNSS-powered spatial land administration system that automates cadastral resurveying, generates sub-centimeter georeferenced parcel boundaries with ULPIN assignment, and seamlessly synchronizes spatial maps with textual Record of Rights (RoR) to eliminate land litigation and enable transparent rural governance [INFERENCE].
The explicit problem statement provided by DoLR [PS] is decomposed below into atomic requirements to ensure zero omission of required capabilities:
┌──────────────────────────────────────────────────────────┐
│ SIH26010 PROBLEM STATEMENT DECONSTRUCTION │
└────────────────────────────┬─────────────────────────────┘
│
┌─────────────────────────────────────────────────────┼─────────────────────────────────────────────────────┐
│ │ │
┌────────┴─────────┐ ┌─────────┴────────┐ ┌─────────┴────────┐
│ Historic Legacy │ │ Modern Survey │ │ Unified Digital │
│ Deficiencies [PS]│ │ Tech Mandate [PS]│ │ Land Info Sys[PS]│
└────────┬─────────┘ └─────────┬────────┘ └─────────┬────────┘
├─ Chain/Tape Errors ├─ Drone Mapping ├─ Integrated RoR
├─ Boundary/Inheritance Changes ├─ RTK / DGPS Systems ├─ Mutation Records
├─ Unrecorded Transactions ├─ GIS Cadastral Maps ├─ Geo-coordinates
└─ Spatial-Textual Mismatch └─ CORS & Mobile Verification └─ Real-time Updates
| Req ID | Source Text / Aspect | Technical Interpretation | Implementation Implication | Confidence |
|---|---|---|---|---|
| REQ-01 | "Historically, land surveys... conducted using conventional chain and tape methods" [PS] | Legacy maps lack geodetic projections (WGS84/EPSG:4326) and suffer from severe scale distortion. | System must digitize and georeference legacy paper/scanned cadastral maps using GCP Control points. | [PS] |
| REQ-02 | "Boundary changes due to inheritance and informal partition... Unrecorded transactions... Encroachments" [PS] | Ground realities differ drastically from legacy paper maps; boundaries are fluid. | Mobile field app must allow on-the-spot boundary verification, subdivision, and vertex marking. | [PS] |
| REQ-03 | "Mismatch between textual records and spatial maps, Absence of updated mutation records" [PS] | Textual RoR (Jamabandi/7-12) exists in isolation from cadastral shapefiles/maps. | Relational database schema linking plot Khasra numbers to GeoJSON/PostGIS geometries with foreign keys. | [PS] |
| REQ-04 | "Drone-based aerial surveys, RTK GPS and DGPS systems... CORS" [PS] | Hardware-integrated spatial data capture using UAV photogrammetry and differential GNSS receivers. | Ingestion pipeline for drone orthomosaic imagery (GeoTIFF) and RTK GNSS NMEA/RTCM stream data. | [PS] |
| REQ-05 | "GIS-enabled cadastral mapping and Geo-referenced parcel identification" [PS] | Every plot requires exact geographic coordinates and a unique spatial index. | WebGIS engine (PostGIS + GeoServer) producing OGC-compliant WMS/WFS layers and computing ULPIN. | [PS] |
| REQ-06 | "Developing a unified digital land information system integrating Record of Rights(RoR), Mutation records, Registration databases..." [PS] | Multi-system data convergence across Revenue, Registration, and Survey departments. | RESTful API gateway with OAuth2/JWT security interfacing with state land portals and NGDRS. | [PS] |
| REQ-07 | "This integration should enable real-time updating and verification of land ownership." [PS] | Property sales, inheritance, or splits must automatically trigger map boundary recalculations and record updates. | Automated workflow engine executing spatial topology validation during parcel mutations. | [PS] |
┌──────────────────────────────────────────────────────────┐
│ STAKEHOLDER ECOSYSTEM OVERVIEW │
└────────────────────────────┬─────────────────────────────┘
│
┌───────────────────────────────┬─────────────────────┴─────────┬───────────────────────────────┐
│ │ │ │
┌────────┴────────┐ ┌────────┴────────┐ ┌────────┴────────┐ ┌────────┴────────┐
│ Rural Farmer │ │ Revenue Officer │ │ Drone Pilot & │ │ Judiciary & │
│ & Landowner │ │ (Patwari/RI) │ │ Field Surveyor │ │ Policy Planners │
└─────────────────┘ └─────────────────┘ └─────────────────┘ └─────────────────┘
| Stakeholder | Goal | Current Pain Point | System Need |
|---|---|---|---|
| Rural Farmer / Citizen [PS] | Clear, undisputed title (Bhu-Aadhaar) to secure bank credit, PM-KISAN, and sell/partition land easily [RESEARCHED]. | Boundary encroachment by neighbors; years-long litigation; harassment by local land officials [PS]. | Citizen portal & mobile app to view high-res parcel boundary overlaid on orthomosaic, track mutation, and lodge boundary objections [INFERENCE]. |
| Village Revenue Officer (Patwari / Tehsildar) [INFERENCE] | Fast, error-free verification of land sales, inheritance partitions, and mutation updating [PS]. | Manual field inspection with measuring chains; offline record corruption; duplicate manual entries [PS]. | Rugged mobile app with RTK/DGPS Bluetooth pairing, offline GIS maps, and automated topological mutation validation [INFERENCE]. |
| Survey Department / Drone Operator [PS] | Rapid aerial mapping and sub-centimeter Ground Control Point (GCP) surveying of agricultural blocks [PS]. | Lack of unified workflow to convert raw drone images into validated cadastral boundaries linked to RoR [INFERENCE]. | Photogrammetry ingestion pipeline, CORS NTRIP auto-connection, and AI-assisted parcel bund extraction tools [INFERENCE]. |
| District Administration & Judiciary [PS] | Reduction in land litigation backlog and transparent land valuation for acquisition/taxation [PS]. | Civil courts overwhelmed with boundary dispute suits; lack of verifiable historical geo-evidence [PS]. | Immutable audit trail of land ownership history, legal dispute tagging, and georeferenced court order integration [INFERENCE]. |
┌────────────────────────────────────────────────────────────────┐
│ REQUIREMENTS TO FEATURE MAPPING │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[REQ-01, REQ-02] [REQ-04, REQ-05] [REQ-03, REQ-06] [REQ-07]
Legacy Vectorizer CORS/RTK Field App Unified RoR Gateway Auto-Mutation Engine
Digitizes paper maps Centimeter GPS logging Integrates state RoR Executes split topology
| Proposed Module / Feature | Direct Requirement Justification | Technical Implementation |
|---|---|---|
| 1. Historical Map Vectorizer | REQ-01 (Legacy chain/tape map conversion) [PS] |
OpenCV-based thin-plate spline warping to georeference legacy revenue maps onto CORS grid [INFERENCE]. |
| 2. CORS-Connected Mobile Survey App | REQ-02, REQ-04 (Field verification, RTK/DGPS, CORS) [PS] |
React Native app interfacing with NMEA GNSS receivers over Bluetooth/NTRIP for 1-2cm precision [RESEARCHED]. |
| 3. Drone Orthomosaic Tile Engine | REQ-04, REQ-05 (Drone mapping, GIS cadastral maps) [PS] |
GeoServer Cloud / COG (Cloud Optimized GeoTIFF) streaming via MapLibre GL JS frontend [INFERENCE]. |
| 4. AI Parcel Bund Extractor | REQ-05 (Accurate mapping speed & automation) [PS] |
Segment Anything Model 2 (SAM-2) fine-tuned on aerial imagery to auto-delineate agricultural field bunds [RESEARCHED]. |
| 5. 14-Digit ULPIN / Bhu-Aadhaar Generator | REQ-05 (Geo-referenced parcel identification) [PS] |
ECCMA/OGC standard algorithm deriving 14-character alphanumeric ID from centroid & vertex coordinates [RESEARCHED]. |
| 6. Unified Spatial-Textual RoR Portal | REQ-03, REQ-06 (Integrated RoR, Mutation, Registration) [PS] |
PostgreSQL/PostGIS database joining spatial geometry tables with textual Khasra/Khatauni metadata [INFERENCE]. |
| 7. Real-Time Mutation Engine | REQ-07 (Real-time updating and verification) [PS] |
Automated spatial topology checker preventing self-intersection, overlapping, or gaps during plot division [INFERENCE]. |
┌────────────────────────────────────────────────────────────────┐
│ FIELD ENVIRONMENT CONSTRAINTS │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Connectivity] [Hardware] [Regulatory] [Environmental]
2G/3G or Zero Signal Sub-$500 Mobile Rovers DGCA Drone Rules Monsoon, Tall Crops,
Cellular Dead Zones Low-spec Android Phones GOP / Survey of India Boundary Mud Bunds
To ensure technical feasibility, the team must address these core research questions prior to execution:
┌────────────────────────────────────────────────────────────────┐
│ DATA ARCHITECTURE TAXONOMY │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Spatial Rasters] [GNSS / RTK Points] [Textual RoR Records] [Synthetic Datasets]
Drone Orthomosaics Centimeter Rover Logs Khasra, Khatauni, Simulated Split Parcels,
5cm/px GeoTIFF NMEA 0183 / RTCM 3.3 Mutation Registers NTRIP Correction Stream
| Data Type | Purpose | Ideal Real-World Source | Hackathon Substitute | Acquisition Method | Availability | Privacy | Confidence |
|---|---|---|---|---|---|---|---|
| Aerial Orthomosaic Imagery | Visual boundary base map for field inspection & boundary digitizing [PS]. | Survey of India / DGCA Drone Flights (5cm GSD) [RESEARCHED]. | Open-topography UAV datasets / OpenAerialMap / QGIS Drone Samples [RESEARCHED]. | GeoTIFF upload / WMS Cloud endpoint. | Publicly Available (Sample) | Low (Public Terrain) | [RESEARCHED] |
| CORS / RTK GNSS Coordinates | Sub-centimeter ground truth vertex points for parcel boundary points [PS]. | Survey of India CORS Network / DGPS Rover [RESEARCHED]. | Simulated NMEA 0183 GPS stream via Android Mock Location app [INFERENCE]. | Bluetooth SPP / Serial Port Ingestion. | Restricted (SoI) / Simulated | High (Location Data) | [RESEARCHED] |
| Legacy Cadastral Maps (Sajra) | Reference for historical plot boundaries and survey numbers [PS]. | State Revenue Depts (Bhu-Naksha portals) [RESEARCHED]. | Digitized/scanned open samples from UP/MP Bhulekh portals [RESEARCHED]. | PDF / High-res JPEG raster download. | Publicly Available | Medium (Public Land) | [RESEARCHED] |
| Record of Rights (RoR / Khasra) | Textual ownership, land class, area, and encumbrance metadata [PS]. | State Land Records (e.g., Mahabhulekh, UP Bhulekh) [RESEARCHED]. | Mock JSON records mirroring standard state RoR structures [INFERENCE]. | REST API / Web Scraping / Mock JSON. | Publicly Available | Medium (Owner Names) | [RESEARCHED] |
| Mutation & Dispute Logs | Historical transaction logs and pending litigation records [PS]. | Revenue Courts (RCCMS portal) [RESEARCHED]. | Synthetic JSON schema containing dispute status & legal flags [INFERENCE]. | DB Query / JSON File Ingestion. | Restricted / Simulated | High (Legal Disputes) | [INFERENCE] |
┌────────────────────────────────────────────────────────────────┐
│ EXISTING SYSTEMS VS BHU-DRISHTI │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Manual Chain/Tape] [Bhu-Naksha (NIC)] [SVAMITVA Scheme] [Proposed Bhu-Drishti]
Decades Old, Low Accuracy Static GIS, No Mobile Habitation (Abadi) Only Agricultural Land Focus,
High Dispute Rate [PS] Sync, Disconnected RoR [RESEARCHED] No Agri Field Focus [RESEARCHED] AI-CV + Offline RTK Sync [INFERENCE]
| Existing Solution | Key Features | Strengths | Major Weaknesses & Gaps | Relevance to SIH26010 | Source & Confidence |
|---|---|---|---|---|---|
| 1. Conventional Chain & Tape Survey | Manual ground distance measurement using steel chains/tapes [PS]. | Low technology cost; well-understood by traditional Patwaris [PS]. | Prone to cumulative human error; physical boundaries shift over time; zero georeferencing [PS]. | Baseline legacy system that SIH26010 explicitly seeks to replace [PS]. | [PS] |
| 2. NIC Bhu-Naksha Portal | Open-source CAD-based tool developed by NIC to digitize cadastral maps [RESEARCHED]. | Widely adopted across Indian states; stores vector shapes of survey numbers [RESEARCHED]. | Primarily desktop-bound; lacks automated AI feature detection; weak offline mobile survey integration; slow mutation updates [INFERENCE]. | Highlights the need for modern WebGIS and real-time mobile sync [INFERENCE]. | NIC Bhu-Naksha Portal [RESEARCHED] |
| 3. SVAMITVA Scheme Platform | Drone survey of rural inhabited (Abadi) areas by MoPR & Survey of India [RESEARCHED]. | High-precision drone survey + CORS; issues property cards for rural houses [RESEARCHED]. | Scope is strictly restricted to Abadi (residential) village plots; does NOT cover vast rural agricultural lands [RESEARCHED]. | Proves drone + CORS model efficacy, but leaves agricultural land gap unaddressed [INFERENCE]. | SVAMITVA Scheme Guidelines [RESEARCHED] |
| 4. Enterprise WebGIS (e.g., Esri ArcGIS Parcel Fabric) | Commercial parcel management system with COGO tools [RESEARCHED]. | Highly mature topology rules and parcel editing workflows [RESEARCHED]. | Extremely expensive proprietary licensing; proprietary data lock-in; poor fit for frugal Indian government deployment [INFERENCE]. | Architectural benchmark for topology, but requires an open-source equivalent [INFERENCE]. | Esri Parcel Fabric [RESEARCHED] |
To solve the agricultural resurvey challenge, three distinct technical approaches were evaluated:
┌────────────────────────────────────────────────────────────────┐
│ SOLUTION APPROACH MATRIX │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Approach 1: Manual Digitizer] [Approach 2: CV + RTK WebGIS] [Approach 3: Blockchain Hybrid]
Low Complexity, Manual Vector Automated AI CV, Mobile RTK, Over-engineered, High Latency,
High Human Effort [INFERENCE] Optimal Hackathon Fit [INFERENCE] Unnecessary Overhead [INFERENCE]
| Evaluation Dimension | Approach 1: Classical WebGIS & Manual Web Vectorization | Approach 2: AI-Vision Automated Orthomosaic Segmentation + CORS/RTK Mobile App (RECOMMENDED) | Approach 3: Blockchain-Ledger Decentralized Land Registry + Drone AI |
|---|---|---|---|
| Mechanism | Web portal where Patwari manually traces boundaries over uploaded drone rasters using Leaflet/OpenLayers drawing tools. | AI Computer Vision (SAM-2 / DeepLabV3+) extracts field bunds from drone orthomosaic; Patwari verifies/adjusts via CORS-connected RTK mobile app. | Drone imagery processed; boundary hashes and RoR mutations committed to Hyperledger Fabric blockchain smart contracts. |
| Accuracy Potential | Medium ($\pm 10-30\text{ cm}$ depending on manual tracing precision). | Sub-centimeter to 2cm (anchored by CORS RTK ground control points). | High accuracy, but bottlenecked by blockchain write overhead. |
| Required Data | Drone Rasters + Textual RoR. | Drone Rasters + RTK GNSS NMEA + CORS Streams + Textual RoR. | Drone Rasters + Blockchain Nodes + Smart Contracts + RoR. |
| System Complexity | Low. | Moderate-High (Well balanced for 4-6 students). | Extremely High (Multi-node setup, high overhead). |
| Explainability | High (Pure manual intervention). | High (AI provides interactive boundary overlay; human Patwari makes final decision). | Low (Smart contract failure modes hard to audit for non-tech revenue officers). |
| Scalability | Poor (Requires thousands of manual drafting hours). | Very High (AI automates 80% of boundary extraction; human verifies 20%). | Poor (Transaction throughput limits on permissioned chain). |
| Hackathon Feasibility | 100% (Easy to build, but lacks innovation differentiator). | 95% (Realistic MVP demonstrate-able with simulated RTK feed and local tile server). | 40% (High risk of failing live demo due to blockchain deployment glitches). |
| Production Feasibility | Low (Does not solve speed/throughput requirement of DoLR). | Extremely High (Aligns with DILRMP & DoLR national standards). | Low (Legal framework in India does not currently recognize smart contracts for land title). |
+-----------------------------------------------------------------------------------+
| RECOMMENDED ARCHITECTURE HYBRID |
| |
| [Drone Aerial Survey] ---> [AI Boundary Extractor] ---\ |
| +--> [Unified PostGIS LIMS|
| [CORS RTK Mobile App] ---> [Real-time GNSS Verifier] -/ + Bhu-Aadhaar Engine] |
| | |
| [State RoR Portal] ---> [REST API Gateway] ───────────────────────┘ |
+-----------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------------------------+
| BHU-DRISHTI SYSTEM ARCHITECTURE |
+---------------------------------------------------------------------------------------------------+
┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ 1. DATA INGESTION LAYER │
│ ┌───────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────────┐ │
│ │ Drone Orthomosaic │ │ External RTK/DGPS Rover │ │ Legacy Sajra Maps / │ │
│ │ (GeoTIFF / COG) │ │ (NMEA 0183 / Bluetooth) │ │ State RoR JSON Feeds │ │
│ └───────────┬───────────┘ └─────────────┬─────────────┘ └───────────────┬───────────────┘ │
└──────────────┼─────────────────────────────┼─────────────────────────────────┼──────────────────┘
▼ ▼ ▼
┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ 2. AI & PROCESSING LAYER │
│ ┌───────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────────┐ │
│ │ SAM-2 Computer Vision │ │ NTRIP / CORS Correction │ │ OpenCV Image Warping & │ │
│ │ Bund Extraction Engine│ │ Engine (SoI Network) │ │ Georeferencing Pipeline │ │
│ └───────────┬───────────┘ └─────────────┬─────────────┘ └───────────────┬───────────────┘ │
└──────────────┼─────────────────────────────┼─────────────────────────────────┼──────────────────┘
▼ ▼ ▼
┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ 3. CORE SERVICE LAYER (Node.js) │
│ ┌───────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────────┐ │
│ │ ULPIN (Bhu-Aadhaar) │ │ Topology Validation │ │ Mutation Workflow & │ │
│ │ Generator (14-digit) │ │ Rules Engine (No-Overlap) │ │ Dispute Management Engine │ │
│ └───────────┬───────────┘ └─────────────┬─────────────┘ └───────────────┬───────────────┘ │
└──────────────┼─────────────────────────────┼─────────────────────────────────┼──────────────────┘
▼ ▼ ▼
┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ 4. DATA & STORAGE LAYER │
│ ┌──────────────────────────────────────────────────────┐ ┌────────────────────────────────┐ │
│ │ PostgreSQL 16 + PostGIS 3.4 Spatial Database │ │ MinIO Object Storage │ │
│ │ (Parcels, Vertices, RoR, Mutation Audit Logs) │ │ (Cloud Optimized GeoTIFF Tiles)│ │
│ └───────────────────────────┬──────────────────────────┘ └────────────────┬───────────────┘ │
└──────────────────────────────┼───────────────────────────────────────────────┼──────────────────┘
▼ ▼
┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ 5. MAP SERVER & FRONTEND LAYER │
│ ┌───────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────────┐ │
│ │ GeoServer (WMS/WFS) / │ │ Web Portal (React.js + │ │ Mobile App (React Native + │ │
│ │ Martin Vector Tiles │ │ MapLibre GL JS Dashboard) │ │ WatermelonDB + Offline Tiles) │ │
│ └───────────────────────┘ └───────────────────────────┘ └───────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────────────────────────┘
| Layer | Selected Technology | Why Chosen | Alternative Considered | Why Rejected |
|---|---|---|---|---|
| Frontend Web | React.js + Tailwind CSS | High component reusability, fast rendering performance, extensive UI library ecosystem. | Angular | Steeper learning curve; heavier boilerplate for quick hackathon development. |
| Web Mapping Engine | MapLibre GL JS | Open-source, GPU-accelerated vector tile rendering; zero API key costs; smooth zoom/pan. | Leaflet.js / Google Maps API | Leaflet struggles with heavy vector layers; Google Maps API is costly and lacks native GeoJSON GIS topology tools. |
| Mobile App | React Native + Expo | Cross-platform (Android/iOS); native Bluetooth SPP modules for RTK rover integration; offline caching. | Flutter | Team JS/TS expertise; React Native has superior native spatial SQLite plugins (WatermelonDB). |
| Backend API | Node.js + Express.js (TypeScript) | Asynchronous I/O; fast JSON processing; unified TypeScript interface across frontend and backend. | Python FastAPI | FastAPI is great for AI, but Node.js offers superior concurrency for real-time mobile sync & web sockets. |
| Spatial Database | PostgreSQL 16 + PostGIS 3.4 | Industry-standard open-source spatial database; native support for ST_Intersects, ST_Area, ST_Difference topology functions. | MongoDB (2D Sphere) | MongoDB lacks robust OGC-compliant spatial topology validation and relational integrity required for land records. |
| Map Server | Martin Vector Tile Server / GeoServer | Martin is an ultra-fast Rust-based MVT tile server that streams PostGIS tables directly to MapLibre GL. | Esri ArcGIS Server | ArcGIS is expensive, closed-source, and unsuitable for open government stack standards. |
| AI/ML Engine | Python (PyTorch + SAM-2 / Segment Anything) | State-of-the-art zero-shot image segmentation; easily fine-tuned on drone imagery for boundary detection. | OpenCV Traditional Contour Detection | OpenCV thresholding fails under shadows, crop color variations, and low contrast earthen bunds. |
| Object Storage | MinIO (Self-Hosted S3 API) | Open-source, high-performance object storage for massive GeoTIFF rasters and drone orthomosaics. | AWS S3 | Cloud storage incurs bandwidth egress costs; self-hosted MinIO can run on local government servers. |
┌────────────────────────────────────────────────────────────────┐
│ AI/ML INTEGRATION DEEP DIVE │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┴───────────────────────┐
▼ ▼
[Component 1: Computer Vision] [Component 2: NLP / Document Processing]
SAM-2 Orthomosaic Parcel Boundary Extractor RoR & Deed Entity Extraction
Input: GeoTIFF Aerial Raster Input: Scanned Land Mutation Deeds
Output: Polygon GeoJSON Boundary Candidates Output: Structured JSON Owner/Khasra Attributes
┌────────────────────────────────────────────────────────────────┐
│ POSTGIS SPATIAL DATABASE SCHEMA │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[parcels Table] [vertices Table] [ror_records Table] [mutations Table]
- parcel_id (UUID) - vertex_id (UUID) - ror_id (UUID) - mutation_id (UUID)
- ulpin (VARCHAR(14)) - parcel_id (FK) - ulpin (FK) - parent_ulpin (VARCHAR)
- geom (Geometry Polygon) - geom (Point, EPSG:4326) - khasra_no (VARCHAR) - child_ulpins (ARRAY)
- area_ha (NUMERIC) - accuracy_cm (NUMERIC) - owner_name (VARCHAR) - split_geom (Geometry)
- status (Active/Disputed) - source (RTK/CORS/Manual) - land_class (VARCHAR) - status (Approved/Pending)
-- Enable PostGIS Extension
CREATE EXTENSION IF NOT EXISTS postgis;
-- 1. Agricultural Parcels Spatial Table
CREATE TABLE agricultural_parcels (
parcel_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
ulpin VARCHAR(14) UNIQUE NOT NULL, -- Bhu-Aadhaar 14-digit ID
state_code VARCHAR(2) NOT NULL,
district_code VARCHAR(3) NOT NULL,
tehsil_code VARCHAR(4) NOT NULL,
village_code VARCHAR(6) NOT NULL,
khasra_number VARCHAR(20) NOT NULL,
geom GEOMETRY(Polygon, 4326) NOT NULL, -- WGS84 Spatial Polygon
area_sqm NUMERIC(12, 2) GENERATED ALWAYS AS (ST_Area(geom::geography)) STORED,
dispute_status VARCHAR(20) DEFAULT 'CLEAR', -- CLEAR, DISPUTED, MUTATION_PENDING
created_at TIMESTAMP WITH TIMEZONE DEFAULT CURRENT_TIMESTAMP,
updated_at TIMESTAMP WITH TIMEZONE DEFAULT CURRENT_TIMESTAMP
);
-- Spatial GIST Index for Sub-Millisecond Spatial Queries
CREATE INDEX idx_parcels_geom ON agricultural_parcels USING GIST(geom);
CREATE INDEX idx_parcels_ulpin ON agricultural_parcels(ulpin);
-- 2. Precision Boundary Vertices Table (RTK Ground Truth)
CREATE TABLE parcel_vertices (
vertex_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
parcel_id UUID REFERENCES agricultural_parcels(parcel_id) ON DELETE CASCADE,
sequence_order INT NOT NULL,
geom GEOMETRY(Point, 4326) NOT NULL,
elevation_m NUMERIC(8, 3),
horizontal_accuracy_cm NUMERIC(5, 2) NOT NULL, -- e.g., 1.2 cm from RTK
captured_via VARCHAR(20) CHECK (captured_via IN ('CORS_RTK', 'DGPS_ROVER', 'MANUAL_MAP')),
captured_at TIMESTAMP WITH TIMEZONE DEFAULT CURRENT_TIMESTAMP
);
-- 3. Textual Record of Rights (RoR Integration)
CREATE TABLE record_of_rights (
ror_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
ulpin VARCHAR(14) REFERENCES agricultural_parcels(ulpin),
owner_name VARCHAR(255) NOT NULL,
owner_aadhaar_hash VARCHAR(64), -- SHA-256 Hashed for Privacy
joint_ownership_share NUMERIC(5, 2) DEFAULT 100.00,
land_category VARCHAR(50) NOT NULL, -- Irrigated, Unirrigated, Waste
encumbrance_status BOOLEAN DEFAULT FALSE, -- Bank Mortgage Flag
mortgage_bank_name VARCHAR(150)
);
-- 4. Immutable Mutation & Split Register
CREATE TABLE mutation_audit_ledger (
mutation_id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
parent_ulpin VARCHAR(14) NOT NULL,
child_ulpins VARCHAR(14)[] NOT NULL,
mutation_type VARCHAR(30) CHECK (mutation_type IN ('INHERITANCE_SPLIT', 'SALE_TRANSFER', 'BOUNDARY_CORRECTION')),
approved_by_officer VARCHAR(100) NOT NULL,
spatial_diff_geom GEOMETRY(Geometry, 4326),
document_proof_url TEXT,
ledger_sha256_hash VARCHAR(64) NOT NULL,
applied_at TIMESTAMP WITH TIMEZONE DEFAULT CURRENT_TIMESTAMP
);
+-----------------------------------------------------------------------------------+
| OFFLINE DATA SYNCHRONIZATION FLOW |
| |
| [Central PostGIS Server] |
| │ (1) Export Village MBTiles & GeoJSON Vector Vector Cache |
| ▼ |
| [Mobile App (SQLite / WatermelonDB Local Cache)] |
| │ (2) Patwari conducts field survey completely OFFLINE |
| │ (3) Captures RTK GPS Vertices & Enqueued Mutations |
| ▼ |
| [Re-establish 3G/4G Network Connectivity] |
| │ (4) Push Synchronize Queue via HTTP/2 REST Gateway |
| ▼ |
| [Server Topology Validation Engine] |
| ├──> IF NO Conflict: Commit PostGIS Transaction & Issue ULPIN |
| └──> IF Overlap Conflict: Reject & Return Discrepancy Map to Mobile |
+-----------------------------------------------------------------------------------+
.mbtiles format and sideloaded or downloaded when on Wi-Fi/4G at the Tehsil office [INFERENCE].IN_FIELD_SURVEY [INFERENCE]. ┌────────────────────────────────────────────────────────────────┐
│ SECURITY & GOVERNANCE FRAMEWORK │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[PII Protection] [Access Control] [Data Integrity] [Legal Compliance]
SHA-256 Aadhaar Hashing, RBAC: Patwari, Tehsildar, HMAC Request Signing, Digital Personal Data
Masked Mobile Numbers Surveyor, Public Citizen SHA-256 Mutation Ledger Protection (DPDP) Act 2023
mutation_audit_ledger table with the officer's digital signature hash and timestamp [INFERENCE]. ┌────────────────────────────────────────────────────────────────┐
│ HACKATHON MVP FEATURE SCOPE │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[MUST BUILD] [SHOULD BUILD] [NICE TO HAVE] [DO NOT BUILD]
- Drone Orthomosaic Layer - SAM-2 AI Bund Suggestion - PDF RoR Certificate Export - Multi-state live API sync
- CORS RTK Mobile Simulator - Automated Mutation Engine - Multi-lingual Voice Prompts - Live Satellite Radar feeds
- ULPIN 14-digit Generator - Dispute Tagging Portal - WhatsApp Notification Bot - Blockchain Networks
- PostGIS Spatial Schema - Offline MBTiles Cache Engine - Hardware ASIC Integration
To ensure a seamless, high-impact demonstration before SIH judges without relying on external field hardware or live government servers, the team will implement the following simulation harness:
+-----------------------------------------------------------------------------------+
| LIVE DEMO SIMULATION HARNESS |
| |
| [Simulated Hardware / External Stream] ────> [Mock Provider Service] |
| ├── Drone Orthomosaic Server ───> Local MinIO / GeoServer Local Tile |
| ├── CORS / RTK DGPS Receiver ───> NMEA 0183 Bluetooth Socket Simulator |
| └── State RoR / Bhu-Naksha API ───> Fastify Mock JSON Endpoint |
| │ |
| ▼ |
| [Bhu-Drishti Web & Mobile App] |
+-----------------------------------------------------------------------------------+
| Component Simulated | Real-World Dependency | Hackathon Simulation Strategy | Transparency Statement for Judges |
|---|---|---|---|
| Drone Aerial Imagery | Real-time drone flight over rural village [PS]. | Pre-processed open-source UAV orthomosaic ($5\text{ cm/pixel}$) hosted on a local GeoServer/MinIO instance [INFERENCE]. | "Judges, aerial imagery is streamed from a pre-uploaded drone orthomosaic tile server using standard OGC WMS protocol." |
| DGPS / RTK Rover Feed | Physical RTK GNSS Receiver + CORS Network [PS]. | Android Mock Location App streaming authentic NMEA 0183 strings over a local WebSocket, including $GPGGA fix quality 4 (RTK Fix, $1\text{ cm}$ precision) [INFERENCE]. |
"Judges, the mobile app is receiving a live NMEA RTK GPS data stream via Bluetooth simulator, reproducing exact field conditions." |
| State RoR Integration | State Revenue Database API (e.g., UP Bhulekh) [PS]. | Mock REST API server returning authentic JSON schema payloads representing Khasra, Khatauni, and land owner details [INFERENCE]. | "Judges, state land records are interfaced via a simulated REST API gateway matching official DoLR DILRMP data standards." |
┌────────────────────────────────────────────────────────────────┐
│ DEVELOPMENT TIMELINE │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Phase 1: Sept-Nov 2025] [Phase 2: Dec 2025-Mar 2026] [Phase 3: Apr-Jul 2026] [Phase 4: Aug-Sept 2026]
Data Architecture & Spatial DB AI Model Fine-tuning & Mobile App Offline Sync & Field Simulation, Testing
Setup (PostGIS, GeoServer) WebGIS Dashboard Build RTK Bluetooth Interface & Final SIH Pitch Prep
┌────────────────────────────────────────────────────────────────┐
│ TESTING & VALIDATION SUITE │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Spatial Topology Tests] [GNSS Precision Tests] [AI Segmentation Metrics] [Offline Sync Tests]
Zero Overlaps, Zero Gaps, $\le 2\text{ cm}$ Error Margin $\text{IoU} \ge 0.85$, 10,000 Mutation Queue
Area Conservation Check Verification via Control Points Precision/Recall Scores Zero Data Loss Recovery
| Test Category | Test Case Scenario | Target Benchmark / Metric | Validation Method |
|---|---|---|---|
| Spatial Topology Validation | Partition a $1.0\text{ hectare}$ parcel into two sub-parcels. | $\sum \text{Area}_{\text{child}} = 1.0\text{ ha} \pm 0.001\text{ ha}$; Zero self-intersections or gaps [INFERENCE]. | Automated PostGIS ST_IsValid and ST_Difference SQL unit tests [INFERENCE]. |
| GNSS RTK Precision | Ingest NMEA stream from rover connected to CORS network [RESEARCHED]. | Horizontal positioning error $\le 2.0\text{ cm}$ [RESEARCHED]. | Comparison against known benchmark survey monument coordinates [INFERENCE]. |
| AI Boundary Extraction | Predict parcel bund boundaries on 50 unseen test orthomosaics [INFERENCE]. | Intersection over Union ($\text{IoU}) \ge 0.85$; False Positive Rate $< 10%$ [INFERENCE]. | Automated IoU score evaluation against human-annotated ground truth masks [INFERENCE]. |
| Offline Sync Reliability | Create 50 offline parcel edits on mobile device; force network crash during sync [INFERENCE]. | 100% data recovery; zero corrupted geometries; clean queue purge post-reconnect [INFERENCE]. | Network interruption simulation via Linux tc netem packet loss injection [INFERENCE]. |
| System Latency | Render 10,000 active vector parcel boundaries on WebGIS map view [INFERENCE]. | Map render frame rate $\ge 50\text{ FPS}$; Vector tile load time $< 500\text{ ms}$ [INFERENCE]. | Chrome Lighthouse & MapLibre FPS profiling tools [INFERENCE]. |
┌────────────────────────────────────────────────────────────────┐
│ RISK MATRIX OVERVIEW │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Technical Risk] [Field Data Risk] [Regulatory Risk] [Adoption Risk]
CORS NTRIP Drops Heavy Shadow / Crop Obstruction UAV Flight Restrictions Patwari Technology Resistance
Mitigation: PPK Post-Processing Mitigation: Post-Harvest Survey Mitigation: DGCA Compliant Logs Mitigation: Vernacular UI
| Identified Risk | Likelihood | Impact | Severity Score | Mitigation Strategy |
|---|---|---|---|---|
| 1. CORS Network Cell Disconnection | High | High | High (16/25) | Implement PPK (Post-Processed Kinematic) fallback: raw GNSS logs are saved locally on the rover and auto-corrected against CORS static logs once connectivity re-establishes [RESEARCHED]. |
| 2. Dense Crop Canopy Hiding Boundaries | Medium | High | Medium (12/25) | Mandate drone flight operations during post-harvest fallow seasons (Nov–Mar) when earth bunds are clearly visible [RESEARCHED]. |
| 3. AI False Boundary Detection | Medium | Medium | Medium (9/25) | Enforce human-in-the-loop workflow: AI predictions are editable draft overlays that Patwaris must manually review and confirm [INFERENCE]. |
| 4. Low Digital Literacy among Field Staff | High | Medium | Medium (12/25) | Design the mobile app with local language support (Hindi/Regional), large touch targets, voice guidance, and visual step-by-step survey wizards [INFERENCE]. |
| 5. DGCA Drone Flight Clearance Delays | Medium | Low | Low (6/25) | Integrate pre-flight DigitalSky permit validation and geofencing compliance checks within the mission planner [RESEARCHED]. |
| Resource Category | Quantity / Description | Estimated Unit Cost | Total Production Cost |
|---|---|---|---|
| Survey Drones (DGCA Approved) | 10 Micro Survey Drones with PPK/RTK modules | ₹6,00,000 per UAV | ₹60,00,000 [INFERENCE] |
| Handheld RTK DGPS Rovers | 50 Units for Field Patwaris (u-blox F9P based) | ₹40,000 per Rover | ₹20,00,000 [RESEARCHED] |
| Cloud Infrastructure | 4x Dedicated GPU instances (NVIDIA L4) for AI & PostGIS | ₹1,50,000 / month | ₹18,00,000 / year [INFERENCE] |
| CORS Network Subscription | Survey of India CORS NTRIP API access | Government Tier | Nominal / Inter-departmental [RESEARCHED] |
| Training & Capacity Building | Workshops for 200 Revenue Officers | ₹2,000 per officer | ₹4,00,000 [INFERENCE] |
┌────────────────────────────────────────────────────────────────┐
│ SYSTEM DIFFERENTIATION SUMMARY │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Sub-Centimeter CORS Precision] [AI SAM-2 Auto-Segmentation] [Instant ULPIN Generation] [Seamless RoR Topology Sync]
$\pm 1-2\text{ cm}$ field truth 80% workload reduction Standard 14-digit Bhu-Aadhaar Zero-gap, zero-overlap
dispute resolution [RESEARCHED] boundary extractor [RESEARCHED] calculated dynamically [RESEARCHED] real-time mutation updates [INFERENCE]
Why Bhu-Drishti dominates generic hackathon submissions:
ST_Overlaps, ST_Touches), ensuring that parcel splits and mutations never produce invalid sliver gaps or overlapping claims—the root cause of rural land litigation [INFERENCE]. ┌────────────────────────────────────────────────────────────────┐
│ FUTURE SCOPE ROADMAP │
└───────────────────────────────┬────────────────────────────────┘
│
┌───────────────────────────────┬───────────────────────┴───────┬───────────────────────────────┐
▼ ▼ ▼ ▼
[Satellite SAR Monitoring] [AI Crop Yield Correlation] [Automated Land Acquisition] [3D Cadastre / Vertical Titles]
Sentinel-1 Interferometry for Correlating soil/crop data Instant compensation payout Managing multi-story rural
subsidence & flood damage with ULPIN parcel geometry calculators for infrastructure structures & vertical rights
PolyhedralSurface in PostGIS) to handle complex vertical property rights in expanding peri-urban villages [INFERENCE].[ASSUMPTION-01] The student team will use an open-source UAV aerial orthomosaic dataset (from OpenAerialMap or QGIS sample sets) to simulate drone flights for the hackathon MVP.[ASSUMPTION-02] Field Patwaris carry Android smartphones capable of Bluetooth 4.2+ connectivity to pair with RTK GNSS rovers.[ASSUMPTION-03] Survey of India's CORS network provides NTRIP HTTP stream access for RTK correction feeds across targeted survey blocks.[ASSUMPTION-04] Mock JSON REST endpoints are acceptable for demonstrating integration with state-specific RoR portals during the SIH presentation.[NEEDS VALIDATION-01] Exact API authentication specifications and encryption protocols required for live production integration with state land portals (e.g., Mahabhulekh, UP Bhulekh).[NEEDS VALIDATION-02] State-specific legal tolerance limits for area discrepancies between historical paper records and modern CORS/RTK drone measurements (typically $1%$ to $3%$ allowable variation under state revenue codes).[NEEDS VALIDATION-03] Precise cellular spectrum availability (2G/3G vs 4G) in interior forest-fringe agricultural blocks of tribal districts.Build Bhu-Drishti (भू-दृष्टि) using Approach 2: An AI-assisted Orthomosaic Segmentation WebGIS combined with a CORS/RTK-connected Mobile Field App. This approach directly satisfies all requirements of Problem Statement SIH26010 while delivering a highly innovative, technically sound, and realistic solution for the Department of Land Resources [INFERENCE].
Access to high-resolution aerial imagery (drone orthomosaics) and stable CORS NTRIP signal streams for sub-centimeter GNSS field corrections [RESEARCHED].
Cellular signal dropouts in remote agricultural fields during real-time NTRIP RTK correction streaming [RESEARCHED]. Mitigation: In-app PPK (Post-Processed Kinematic) fallback logging [RESEARCHED].
Fine-tuning the SAM-2 computer vision model to accurately segment low-contrast, irregular earthen agricultural field bunds under variable crop and lighting conditions [RESEARCHED].
Verify that PostGIS spatial functions (ST_Area, ST_Intersects, ST_Difference) execute within $<10\text{ ms}$ on sample 1,000-parcel polygon datasets [INFERENCE].
92 / 100 (Highly feasible for a skilled 4-6 student team using open-source GIS libraries, pre-trained AI vision models, and standard web/mobile frameworks) [INFERENCE].
HIGH — The solution directly aligns with explicit DoLR requirements, leverages verified national programs (DILRMP, CORS, ULPIN/Bhu-Aadhaar), and uses industry-proven geospatial technology [INFERENCE].
Digital India Land Records Modernization Programme (DILRMP)
SVAMITVA Scheme & CORS Network Technology
Bhu-Aadhaar / Unique Land Parcel Identification Number (ULPIN) Technical Standard
Segment Anything in High-Resolution Remote Sensing Imagery (SAM-2 for GIS)
Open Geospatial Consortium (OGC) Standards for Vector Tiles & WMS/WFS
What we think about this platform, and how it can help people solve SIH problems.
" 30M+ Google Gemini tokens went into researching, analyzing, and understanding all 233 SIH problem statements to make them easier to explore and solve. "
" The platform makes SIH problem statements much easier to understand. Having everything from the problem details to the procedure in one place. "
" Oh, you got ads? Well, we need to make money too! But, you can use our platform to help you win SIH and take home the prize money. "
Get in touch if you need help bringing your ideas to life, or simply have an interesting idea you'd like to talk through. I'm always open to a conversation and exploring new possibilities together.