An AI-powered Web-GIS platform that automatically extracts parcel boundaries, building footprints, and roads from drone imagery and DSM data for urban land record mapping.
Ministry of Rural Development · Dept of land resources (DoLR) · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
AI Feature Extraction Engine
Segments parcel boundaries, building footprints, roads, and land-use types from orthorectified drone imagery.
Topology and Polygon Generator
Converts predicted raster boundaries into clean vector polygons while detecting overlapping or inconsistent geometries.
Web-GIS Interactive Dashboard
Displays orthorectified imagery alongside extracted vector layers and allows users to manually inspect and edit shapes.
Ground Truthing Integration Module
Imports GNSS survey data and field ground-truthing points to validate and refine generated cadastral maps.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
Evaluators will check the automated extraction of parcel boundaries and building footprints from aerial imagery. They will also inspect the automated topology validation module for clean polygon generation and test the Web-GIS interface for interactive editing.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
What accuracy metric or target percentage counts as successful boundary extraction?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Where students can access standard sample drone imagery and DSM/DTM datasets for training?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
The exact GIS file formats required for output export compatibility?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
Each one is quoted from a gap in the brief, not a guess about your team.
Needs data you may not get
The solution requires high-resolution drone imagery, DSM/DTM datasets, and GNSS survey data, but no dataset is provided by the organizers.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for ai feature extraction engine. How would you build that?
Decoded from SIH26012 itself — Segments parcel boundaries, building footprints, roads, and land-use types from orthorectified drone imagery. The brief asks for it by name.
The brief asks for topology and polygon generator. How would you build that?
Decoded from SIH26012 itself — Converts predicted raster boundaries into clean vector polygons while detecting overlapping or inconsistent geometries. The brief asks for it by name.
The brief asks for web-gis interactive dashboard. How would you build that?
Decoded from SIH26012 itself — Displays orthorectified imagery alongside extracted vector layers and allows users to manually inspect and edit shapes. The brief asks for it by name.
The brief asks for ground truthing integration module. How would you build that?
Decoded from SIH26012 itself — Imports GNSS survey data and field ground-truthing points to validate and refine generated cadastral maps. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: evaluators will check the automated extraction of parcel boundaries and building footprints from aerial imagery.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Show me this working: they will also inspect the automated topology validation module for clean polygon generation and test the Web-GIS interface for interactive editing.
This is the evaluator read for your problem statement, decoded from the brief's own wording.