Walk any residential street in any Indian
city. Not the arterial roads – those have maintenance budgets and occasional
VIP motorcades to keep them presentable. The streets behind those. The ones
where your morning walk requires a working knowledge of obstacle avoidance.
You will find water running from a
premises onto the road because someone’s sump tank has no functioning outlet
valve, or because the watchman’s idea of car-washing extends approximately
three metres into public space. You will find a hedge that the compound wall
has been sponsoring, slowly, into your headroom. You will find a ramp from a
private gate that crosses the kerb and occupies a portion of the pavement it
was never entitled to. You will find a kiosk with a roof and walls and electrical
connections and a business that has been running from that particular spot for
so long that it has its own regulars, its own aesthetic, and its own implicit
understanding with parties who prefer not to be named.
All of this is documented, in the negative,
in the municipal master plan. The plan specifies what the pavement should look
like. The satellite image specifies what it actually looks like. The gap
between these two things – the compliance gap – is computable.
This is the starting point for MapMop.
The method
Municipal and planning authority records
in most Indian cities now include georeferenced road layouts – approved
cross-sections specifying carriageway width, pavement extent, setback from
property boundary, and drain placement. These are public records. They are,
increasingly, available in digital GIS formats.
Satellite imagery, updated with
sufficient frequency, shows current ground conditions from above. Street-level
photographs – whether from mapping services or citizen submissions – show ground
conditions from the human perspective. Together, they provide enough
information to identify a physical object that should not be where it is.
Computer vision can measure the footprint
of that object. Cross-referenced against the approved layout, it can compute
the variance: how many metres of right-of-way this object occupies that it is
not entitled to occupy. This computation requires no human reviewer. It runs
continuously. It timestamps its output.
The property registry – another public
document – identifies who owns the plot adjacent to the variance. The official
organisational directory identifies which municipal department holds
jurisdiction over that stretch of road, and which officer is currently listed
as responsible. The system can therefore produce: location, variance
measurement, responsible entity, responsible department, officer of record, and
date of first detection.
This is not an accusation. It is a
record.
The anonymity architecture
One of the persistent problems with civic
accountability systems is that they require someone to be the accuser. RTI
applications require a name and address. Complaint portals require
registration. Journalistic investigations require a reporter whose byline is
publicly attached to the finding.
MapMop’s community confidence layer is
designed around the opposite principle. Citizens who walk these streets and can
verify whether a computed variance is accurate or not contribute anonymous
confirmations or corrections. A thumbs-up or thumbs-down, geolocated and
timestamped, raises or lowers the AI confidence score. Nothing about the
contributor is recorded. Their local knowledge improves the system’s accuracy
without creating any personal exposure.
The foot-soldier network – citizens,
retired residents, para-surveyors who walk these streets regularly – can earn
micro-payments per verified correction. The payment is for the verification,
not for the identity. The system does not need to know who you are to pay you
for being right.
The output
The civic transparency register is not a
hall of shame. It is a structured dataset with the following fields: location,
variance from sanctioned plan (in metres), responsible entity, jurisdiction
department, officer of record, date first logged, date of most recent community
verification, and days-unresolved.
Days-unresolved is the key metric. It is
a clock. It requires no commentary. A compliance gap that has been in the
register for 847 days, verified by 34 anonymous community confirmations, under
the jurisdiction of a named department, supervised by a named officer – that is
a fact. It is available to anyone with access to the register. What they do
with it is their business.
Tiered access: open summary for general
public, fee-gated detail for institutional users – RWAs, NGOs, insurers, urban
planners, researchers, journalists who prefer to work from structural trend
data rather than individual tip-offs.
The vocabulary
Every word in this system has been chosen
carefully. The register does not have culprits; it has responsible entities. It
does not document shame; it documents compliance gaps. It does not expose
corrupt officials; it surfaces officers of record whose response is pending.
This is not softness. It is precision.
And in a legal context, precision is a form of armour.
Scale
The pilot is a city. The product is a
country. Every urban local body in India with a published master plan has the
source material for this system. The compliance gap is not a Chennai
peculiarity or a Mumbai eccentricity. It is a structural feature of any
planning system where enforcement is discretionary and influence is organised.
What is currently missing is synthesis.
MapMop is a synthesis engine.
The ramp was always visible. It was just
not on the map.
LinkedIn Newsletter Article
Slides
MapMop
by u/muralide in u_muralide
No comments:
Post a Comment