PHYSICAL INTELLIGENCE · GIS

Drishti: satellite change detection for unauthorized construction enforcement

A ranked, evidence-backed inspection worklist built on tiered satellite imagery, three-class change detection and a legally defensible human-in-the-loop. Built for a metropolitan development authority.

Drishti before/after/AI-result view: Sentinel baseline on the left, latest capture on the right, Cartosat-3 result with change bounding boxes below, and a ranked inspector worklist showing 24 changes detected (16 high, 7 medium, 1 low confidence) with per-case review controls
Changes per cycle
34*
Confirmed on inspection
86%*
Flag-to-confirmation
2.4 days*
Automated notices
Zero
Industry
GIS, Satellite Intelligence, Urban Governance
Client
Metropolitan development authority (anonymised)
Territory
Thousands of square kilometers of urban and peri-urban land
End users
Enforcement inspectors, ward officers, planning cell, authority leadership
The Problem

Where the pain concentrates

Authorities can usually demolish once a structure is found. The gap sits upstream: nothing systematically looks until an enforcement drive or a public tip does. By then the structure is already entrenched, surrounded by other recent construction, and politically harder to act on than it would have been three months earlier.

01

Enforcement outpaces detection

Authorities can usually demolish once a structure is found. The gap sits upstream. Nothing systematically looks until an enforcement drive or a public tip does.

02

Structures surface once entrenched

By the time a case lands on an inspector's desk, the construction is usually surrounded by other recent builds and politically harder to act on.

03

False positives are legally expensive

A notice or demolition is legally consequential. At scale, change-detection models produce false positives often enough that no notice should ever be automatic.

04

Ownership data is a compliance trapdoor

Matching flagged parcels to tax and ownership records touches personal data. That step needs a formal agreement first, not a v1 feature.

Design Decisions

What the platform says, out loud

“The platform never issues a notice. It produces a ranked worklist. The decision stays with the authority.
“Enforcement does not pause for weather. When clouds roll in, SAR keeps scanning.
“A decision taken six months ago can be reconstructed with the exact imagery and reasoning that produced it.
Our Approach

One pipeline, three satellites, a human-gated verdict

Drishti scans a metropolitan authority's full jurisdiction on a 30-day cycle, flags new construction, earthwork and sheds with a confidence score, and hands every case to a human inspector with the source imagery attached. The platform never issues a notice. It produces a ranked worklist. The decision stays with the authority.

The design decision came first: a notice or demolition order is legally consequential, and a change-detection model at scale will produce false positives. No notice should travel through an automated path. Drishti is deliberately a ranked worklist, not an auto-notice engine, and the ownership and tax-base layer sits behind a documented data-sharing agreement rather than appearing in v1.

What runs today in the pilot ward: tiered imagery triage across Sentinel-2, Sentinel-1 SAR and Cartosat-3; a three-class change classifier with confidence scoring; a monsoon-proof SAR fallback; and a full audit trail that lets a decision taken six months ago be reconstructed and defended.

Human-gated
Drishti never issues a notice

A legally consequential act never travels through an automated path. The inspector sees the imagery, the score and the context, and decides.

Sentinel-2 + Sentinel-1 wide-area triage
Cartosat-3 spent only on flagged tiles
Three-class model with confidence score
SAR fallback through monsoon cloud cover
Ranked worklist, inspector decides
Full audit trail per case
What We Built

Five building blocks, one defensible worklist

Each block carries a specific job between the imagery pipeline and the inspector. Together they make satellite change detection safe to put in front of a legally exposed enforcement workflow.

Tiered imagery triage

Sentinel-2 optical and Sentinel-1 SAR scan the whole region continuously. Cartosat-3 precision imagery, free to government entities under India Space Policy 2023, is spent only on tiles already flagged. The Cartosat-3 cost line stays flat as coverage grows.

Three-class detection with confidence

The model does not just say something changed. It classifies each change as construction, earthwork or shed, and attaches a confidence score. The inspector sees a ranked case with a probability, not a binary alert.

Monsoon-proof scanning

Optical imagery is useless under cloud cover. Sentinel-1 SAR keeps scanning through clouds. The pipeline switches to SAR-primary during cloud-heavy windows and back to optical-primary when the sky clears.

Human-gated worklist

Every detected change lands in a ranked worklist. The inspector sees the before and after imagery, the confidence score and the classification, and decides: schedule verification, close as false positive, or escalate. The platform never auto-notices.

Full audit trail by design

COG tiles for imagery. A STAC catalog for discovery. PostGIS for parcel geometry and change records. Every case keeps its source imagery, score and disposition, so a decision taken six months ago can be reconstructed and defended.

Aerial view of a peri-urban enforcement perimeter: planned housing on the left, an active mid-rise construction site in the centre, open parcels under earthwork on the right, with mountains in the distance
FIG · WHAT DRISTI IS LOOKING AT · PERI-URBAN ENFORCEMENT PERIMETER
01

Scan

Sentinel-2 and Sentinel-1 run continuous wide-area triage on a 30-day cycle.

02

Triage

Change detection on the free layer identifies tiles with potential change against the baseline.

03

Zoom

Cartosat-3 precision imagery is pulled only for the flagged tiles, under India Space Policy 2023 access.

04

Classify

The three-class model labels each change as construction, earthwork or shed, with a confidence score.

05

Rank

Changes are ranked by confidence and policy relevance into the inspector worklist for the ward.

06

Inspect

The inspector reviews each case with before/after imagery, score and surrounding context.

07

Decide

Schedule field verification, close as false positive, or escalate. The platform never auto-notices.

08

Audit

Every decision is kept with its source imagery, score and disposition for later audit.

FIG · SCAN-TO-AUDIT FLOW
Sentinel-2 opticalSentinel-1 SARCartosat-3COG tilesSTAC catalogPostGISChange-detection modelConfidence scoringInspector worklist UIImmutable audit layer
Measured Outcome · Pilot Ward

Before, after, change

DimensionBeforePhase 1Change
Detection methodManual patrol, public tipsAutomated 30-day scanSystematic
New changes flagged per cycleNot tracked34*Visible
Confirmed correct on inspectionn/a86%*Measured
Flag-to-confirmation timeWeeks to months2.4 days*Collapsed
Automated notices issuedn/aZeroBy design
34*
Changes flagged per 30-day cycle
86%*
Confirmed correct on field inspection
2.4 days*
Avg. flag-to-confirmation time
Zero
Automated notices
34 changes flagged per 30-day cycle. 86% confirmed correct on field inspection. Flag-to-confirmation down from weeks and months to 2.4 days. Zero automated notices. Every decision keeps its source imagery and confidence score, so the enforcement action can be defended.

*Pilot ward numbers, measured on the first operational cycle. Confidence intervals widen with scale and will be re-baselined as the platform rolls out ward by ward.

On the Roadmap

Scaling the enforcement surface

01

Multi-ward scale

Roll out from the pilot ward to the authority's full jurisdiction, keeping the Cartosat-3 cost line flat through the triage design.

02

Historical baseline reconstruction

Backfill scans against archived imagery to anchor a starting point for tax-base reconciliation and long-run trend reporting.

03

Ownership and tax base module

Launched behind a formal data-sharing agreement. Match flagged parcels to tax and ownership records inside the compliance boundary that work requires.

04

Authority leadership dashboard

Ward-level enforcement coverage, flag conversion rates, recoverable assessment value and trend over time, for authority leadership and planning cells.

05

Mobile inspector interface

Field verification without a desktop. Ground-truth evidence captured back into the case record on the spot.

06

Multi-authority tenancy

Package the platform for other metropolitan development authorities with per-authority tenancy and audit isolation.

What We Learned

Three principles we are taking into the next engagement

01

A legally consequential act never travels an automated path

The platform is deliberately a ranked worklist, not an auto-notice engine. For a buyer in an enforcement role, this is the sentence that unlocks procurement. Automated notices would be a liability. A human-gated worklist is a tool.

02

Spend precision imagery only where cheap imagery flagged it

Sentinel-2 and Sentinel-1 cover the whole jurisdiction continuously and free. Cartosat-3 gets spent only on tiles already flagged. The economics scale across thousands of square kilometers without a runaway cost line.

03

Audit is a product feature, not a log file

Enforcement decisions get challenged. Keeping every flagged case with its source imagery, confidence score and inspector decision is what lets the authority defend the action six months later.

Managing thousands of square kilometers of urban and peri-urban territory?

ScroBits builds the imagery pipeline, the detection model, the inspector worklist and the audit layer. Talk to us about scoping a pilot ward for your authority.

Start a conversation