Data sources and limits

Provenance is not proof

README India map

The coverage illustration uses DataMeet India community's india-composite.geojson at commit 5ed214bf77788f99066e3542cccd4a52cb042896. The source is CC0 and states that it includes disputed territories in accordance with the official Survey of India boundary. The SVG keeps the mainland territorial outline, Lakshadweep, and the Andaman and Nicobar Islands; it simplifies the geometry to 0.025 degrees only for the 320-pixel README display.

The Government of India's Geospatial Guidelines make Survey of India boundaries the standard for political maps and permit compliant publication. The illustration does not copy Survey of India's political-map artwork, logo, or emblem because its separate website copyright policy requires permission to reproduce website material. Coverage shading and annotations are Pothole Reporter content; no government endorsement is implied. Runtime routing still uses the independently versioned, checksum-pinned packs documented on this page.

Classification and complaint output

Pothole detection is a strict binary decision: Yes or No. The app does not show a detection-confidence percentage. A Yes is limited to a paved drivable surface with a localized cavity, broken edge or rim, and visible depth or material loss; an ambiguous view, unpaved damage, or speed breaker is No.

Each result records a surface type—bituminous/asphalt, cement concrete, mastic asphalt, paver blocks, unpaved/non-road, or unknown—and a strict defect type. For an accepted pothole, small/medium/large is an app visual estimate only. Length, width, and depth remain unknown unless they were field-measured; the report records measurement provenance and confidence so a visual estimate cannot be mistaken for an official municipal measurement or size class.

Authority-specific templates prepare a concise email, a short WhatsApp version, and copyable portal fields. Coordinates, map link, intake routing, road-owner status, and a contract block are mandatory in every format. The official tender reference, work title, organisation, status and dates, agreement/package/highway details, contractor when actually published, match basis, and source/detail links are preserved when available; missing facts are shown as unknown rather than inferred.

Versioned data packs

Large routing, contact, highway, and procurement datasets are not embedded in the APK. The v1.35 state-pack manifest pins 42 routing/contact/Karnataka resources, and the highway manifest pins 101 National Highway geometry tiles. Separate v1.36 catalogs pin 33 State/UT National Highway project packs, 36 PMGSY State/UT road-agreement packs, and 34 official State/UT road-notice packs. Every resource records its HTTPS URL, decoded byte length, and SHA-256 checksum; old catalogs remain immutable for existing clients.

The app downloads only a relevant pack from this project's GitHub Pages site, verifies the complete response before parsing it, and caches only verified bytes locally. Missing, malformed, truncated, or checksum-mismatched optional contract data never blocks a report; it continues without a candidate. Required routing/contact failures still fail closed. Delete all app data clears the pack cache.

The request contains no report, road photo, or exact coordinates. GitHub Pages can receive the device's IP address, standard connection metadata, and the requested URL; the URL reveals the selected state or an approximate 2° highway tile. The three catalog manifests add about 100 KB to a future build; the remote packs do not enter the APK, and the already-submitted Play closed-test binary is unchanged.

National Highways across India

The app checks National Highway geometry before any municipal route. It uses every operational NH/NE carriageway reference found in the pinned Geofabrik OpenStreetMap India extract dated 20 August 2026 (source MD5 c5e0a62a1cb00c80d8c5948bf18370d7), redistributed under the ODbL. The build accepted 142,656 source features spanning 680 distinct mapped references and published them as 101 immutable 2° tiles. Only the tile containing the reported point is requested, verified, and matched locally.

A geometric match suggests Rajmargyatra, CPGRAMS, or helpline 1033. It deliberately does not claim that NHAI maintains the road: National Highways can be maintained through NHAI, NHIDCL, BRO, or a State PWD. The user must verify the maintaining agency in the official service.

This is nationwide mapped coverage, not a legal inventory. Missing or incorrect OpenStreetMap references remain gaps. The matcher refuses GPS accuracy worse than 30 m, different nearby highway references, direction conflicts from a moving phone, missing tiles, altered checksums, and malformed data rather than falling through to a city recipient.

Optional contract context uses the official NHAI/MoRTH Data Lake current-project inventory and current NHIDCL notices. The 26 August scan read 3,258 MoRTH and 529 NHIDCL rows, normalized 1,950 current/open records (1,939 + 11), and published the 1,859 with a mapped NH/NE reference in 33 packs (1,805,723 bytes). A matching highway number, State/UT, and independent road/location evidence produce a candidate, not proof that the GPS point lies inside the package chainage. Open notices assert no award or contractor.

State and Union Territory road candidates

The official PMGSY scan read 211,007 rows and retained 17,717 recent records whose source status says In Progress. They occupy 36 State/UT packs (3,075,718 bytes); CH, DH, DL, GA, and LD currently have zero retained records. An agreement number/date verifies only that the source reports an agreement. This layer never claims an award, contractor, exact segment, warranty, or DLP.

The official notice catalog combines 30 zero-failure GePNIC feeds with dedicated Bihar eProc2, Chhattisgarh CHiPS, Gujarat nProcure, Telangana eProcurement, and Lakshadweep adapters. The 35 feeds scanned 69,754 rows, rejected 64,358 through strict scope/current-record checks, and published 5,396 notices in 34 packs (4,296,746 bytes). Exact IDs/references, titles, organisations where published, dates, and official sources are preserved; missing facts stay null. Andhra Pradesh remains blocked because its complete table requires undocumented client-encrypted state and exposes no stable record link. KPPP remains a separate Karnataka supplement.

A candidate is considered only in the same jurisdiction and only with independent road/immediate-locality evidence. Drain-, footpath-, sewer-, utility-, consultancy-, and roadside-plantation-only work is rejected. Runtime attempts National Highway, Karnataka KPPP, PMGSY, and official State/UT notice layers nationwide, but does not guarantee every public tender or road. Open notices are not awards. Exact segment, work scope, award, contractor, warranty, and DLP require authoritative evidence.

Statewide and reviewed regional coverage

Statewide Maharashtra fallback

Every point inside OpenStreetMap relation 1950884 is eligible for a neutral Aaple Sarkar handoff after National Highway, MMR, and PMC checks. The ODbL state MultiPolygon was retrieved on 23 August 2026, and the runtime pins geometry SHA-256 1f5555fede30d19d58ffafabb7d38c8cba0af7b27f7c7129d10480351a0304ce. The state grievance-management resolution documents service across all 36 districts, evidence attachments, tracking, and district-level routing. The user still has to select and verify the responsible department; the boundary does not identify a municipality, PWD, panchayat, MSRDC, NHAI, contractor, or road owner. MahaULB is offered as an urban-area alternate. A GPS circle touching the state or a more specific local boundary fails closed.

Mumbai Metropolitan Region

Coverage targets MMRDA's current official MMR extent and its 2019 extension notification: 9 municipal corporations, 9 municipal councils, Khalapur Nagar Panchayat, and the remaining rural MMR. Rural or ambiguous locations use the neutral Aaple Sarkar fallback instead of the nearest city. Maharashtra's official grievance-management resolution documents online lodging and tracking, attachments, and district-level municipal-corporation routing; the app does not claim it has selected the exact MMR body.

The downloaded Maharashtra routing pack contains an outline made from OpenStreetMap relation 13312356 plus the Palghar, Vasai, Alibag, Pen, Panvel, and Khalapur taluka relations named by the notification. It is approximate: it measures about 6,264.9 km² versus MMRDA's published 6,328 km², and its whole-taluka polygons do not subtract the Scheduled Areas excluded by the 2019 notification. It is not a legal MMR boundary. Valid administrative polygons can suggest 11 bodies: BMC, Thane, Kalyan-Dombivli, Navi Mumbai, Ulhasnagar, Bhiwandi-Nizampur, Vasai-Virar, Mira-Bhayandar, Panvel, Ambarnath, and Kulgaon-Badlapur. The other eight bodies have no usable civic polygon in the source snapshot, so they, rural points, and overlaps use Aaple Sarkar. A Nominatim place name never selects the recipient. These are local routing aids, not proof of road ownership.

Pune Municipal Corporation

Pune coverage uses the PMC_Boundary layer published by the official PMC GIS through its GeoServer WMS and corresponding WFS GeoJSON layer. A copy is checked locally from the verified Maharashtra routing pack. It selects the current Pune Municipal Corporation route only; Pimpri-Chinchwad Municipal Corporation (PCMC) and other points outside PMC use the statewide Maharashtra fallback. Road damage uses Road Mitra; garbage and manhole reports use PMC CARE. PMC's official CARE booklet describes general civic grievances, trackable tickets, WhatsApp +91 96899 00002, and toll-free 1800 103 0222.

Statewide West Bengal fallback

Every point confidently inside OpenStreetMap relation 1960177 is covered after the National Highway and exact KMC checks. The ODbL state MultiPolygon was retrieved on 24 August 2026, and the runtime pins geometry SHA-256 aa4ab13c3064be2e168889f6eb02e87c59e01bc709d36b66bece534dfea23015. It is a routing aid, not a legal boundary or ownership record. Outside KMC, road-damage, garbage, and manhole reports are offered the Government of West Bengal's general Public Grievance Redressal System, with CMO Grievance as an alternate. The user must select and verify the district or department. The app does not infer a local body, road owner, contract, guaranteed category acceptance, or submission. A GPS circle touching the state or KMC boundary fails closed.

Kolkata Municipal Corporation

Kolkata's specific route uses the SMARTCITY:wb_municipal_boundary feature published by the Government of West Bengal Urban Development & Municipal Affairs Department through its official Nagar GIS WFS. The feature was retrieved on 21 August 2026 and has ULB_Code 250299 and MUN_ID 250299_0000001. One source self-intersection was repaired with GDAL ogr2ogr -makevalid; the RFC 7946 result was written at seven-decimal precision, validated, and not topologically simplified. The runtime pins the repaired geometry SHA-256 fa9e157d8cdc8d918dd934a77a5dcde375d3108598412cb8ca3e19ca2d916bf5 and fails closed if it changes without a reviewed release. The WFS publishes no explicit reuse licence. Only this exact polygon selects KMC; Howrah, Bidhannagar/Salt Lake, New Town, and other in-state points use the statewide PGRS route. Neither boundary proves road ownership.

Statewide Punjab fallback

Every point confidently inside OpenStreetMap relation 1942686 is eligible for a neutral Connect Punjab handoff after the National Highway check. The ODbL polygon was retrieved on 24 August 2026 and its geometry SHA-256 is e113eb774f4f353d3c7a9c98830f4b665f9bd4d166ed3b84e90855bdf38f5782. Punjab mSeva is offered for urban areas and Connect Punjab publishes helpline 1100. Chandigarh Union Territory is outside the state boundary. State containment does not identify a local body, road owner, contractor, or guaranteed category; the user must select and verify them. A GPS circle touching the state edge fails closed.

Statewide Tamil Nadu fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 96905 is eligible for a neutral Mudhalvarin Mugavari handoff after the National Highway and exact GCC checks. The ODbL state MultiPolygon was retrieved on 24 August 2026 and its geometry SHA-256 is b3034527326b1120366adaf4b7c3df4bd0b8c7aab4d82b28e3dde189b39c313e. Puducherry Union Territory, including Karaikal, is outside the Tamil Nadu boundary; a GPS circle touching the edge or an excluded enclave fails closed.

The primary service's official citizen Android package is org.tnega.cmhelpline.citizen, and its published helpline is 1100. The statewide route deliberately does not guess a secondary municipal portal. Neither the service nor the boundary establishes a department, local body, road owner, complaint category, contractor, or submission. The user must verify and complete the complaint externally; there is no complaint-write API integration or automatic filing.

Statewide Andhra Pradesh fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 2022095 is eligible for a neutral Andhra Pradesh PGRS handoff after the National Highway check. The ODbL state MultiPolygon was retrieved on 24 August 2026 and its geometry SHA-256 is 4e36d9c16fda044dceab7a5b08955cb19046bb1bddd052b7671a8311e90cd71c. Yanam is part of Puducherry Union Territory and is explicitly outside this route; a GPS circle touching Yanam, the state edge, or a neighbouring state fails closed.

PGRS is offered for road damage, garbage, and open or damaged manholes; AP CDMA/Puramithra is an urban-area alternate and the grievance helpline is 1902. The user must select and verify the district, department, local body, category, and road owner and complete the complaint externally. There is no complaint-write API, automatic filing, or ownership inference. The public AP tender list was verified, but a complete machine-readable pull requires undocumented client-encrypted state and exposes no stable record link; the app publishes no AP notice pack rather than bypassing the portal or inventing fields. National Highway and PMGSY candidates remain separate. The outline was cross-checked against Government of Andhra Pradesh APSAC administrative-boundary services and the Survey of India state map. Those official geometries are validation-only because APSAC publishes no explicit redistribution licence and Survey of India restricts reproduction without permission; only the independently licensed ODbL geometry is redistributed.

Statewide Telangana fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 3250963 is eligible for a neutral Telangana Prajavani handoff after the National Highway and exact Hyderabad CURE checks. The ODbL state polygon was retrieved on 24 August 2026 and its geometry SHA-256 is 77183815e4b698ec1e823f4a94a6f213d1d827ea35de8fec8c0ab3b6a9d15175. A GPS circle touching the state edge fails closed rather than inheriting a route from a place name.

The Government of Telangana's Prajavani portal is offered for road damage, garbage, and open or damaged manholes as a neutral statewide handoff. The Centre for Good Governance project record describes state-level rollout and routing to district or department officers by category and location. Citizen Buddy Telangana is an urban alternate only for municipalities and corporations outside Hyderabad. The user must select and verify the district, department, local body, category, and road owner and complete the complaint externally. No stable public prefill or documented third-party complaint-write API is available; Pothole Reporter does not log in, bypass OTP, submit, or read status.

Inside Hyderabad, a successful official CURE and Cantonment check keeps the more specific My Cure route. A CURE-service failure or an accuracy envelope intersecting Secunderabad Cantonment blocks My Cure but can still fall back to neutral Prajavani when the checksum-pinned state polygon contains the complete accuracy circle. The fallback does not claim that a Telangana department owns a Cantonment road. The ODbL outline was cross-checked against TGRAC's official State Boundary layer 29. TGRAC publishes no explicit redistribution licence for that layer, so it is validation evidence only; only the independently licensed OpenStreetMap geometry is redistributed.

Statewide Karnataka fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 2019939 is eligible for neutral Janaspandana iPGRS after National Highway and verified Karnataka urban-body checks. The ODbL state MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is 9d7fe3f01a80cb41712c09139efcd43e0e11a644849d5f3bffe125cc0bc1c5ad. A GPS circle touching the state edge fails closed.

Janaspandana's current official page says 41 departments and 270 line departments are onboarded and publishes grievance helpline 1902. Janahitha is offered only as an urban-local-body alternate. Existing verified municipal-recipient and Bengaluru civic routes remain more specific. The user must select and verify the department, body, category, and road owner and finish the grievance externally. The statewide fallback does not call a complaint-write API or claim submission; Karnataka's separate contract snapshot remains candidate-only.

Statewide Kerala fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 2018151 is eligible for neutral Kerala CMO Public Grievance Redressal after the National Highway check. The ODbL state MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is 51e226750b1d6c08a5030e6074e2641282e01c328f46d8aee741de664bef705c. Mahe is part of Puducherry Union Territory and is outside this boundary; a GPS circle touching Mahe or the state edge fails closed.

The Kerala CMO portal provides online grievances and docket-based status. Its toll-free 1076 line provides help and status information; the official FAQ says a complaint cannot be lodged by phone. Official Local Self Government Department service K-SMART is an alternate for local-body issues. The user must select and verify the department, local body, category, and road owner and finish the grievance externally. Neither service proves ownership or category acceptance, and there is no complaint-write API integration or automatic filing. A same-State open notice can appear only as an unawarded candidate. The seven Kerala entries retained in the immutable top-50 pack are compatibility data only; current routing uses the exact state boundary.

Statewide Uttar Pradesh fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 1942587 is eligible for a neutral UP Jansunwai–Samadhan handoff after the National Highway and exact Delhi NCT checks. The ODbL state MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is 2dbb5237cab5eb029f517c1d79451663c1fc49affe0e0789b11f0565180db015. Delhi NCT is outside the state boundary and keeps its own route; a GPS circle touching Delhi, the state edge, or a neighbouring state fails closed.

The official citizen Android package is in.nic.up.jansunwai.upjansunwai, and the Chief Minister Helpline is 1076. The interactive public flow can require mobile verification and CAPTCHA. The user must select and verify the district, department, local body, category, and road owner and complete the grievance externally. There is no complaint-write API integration, automatic filing, or ownership inference; a same-State open notice can appear only as an unawarded candidate. The seven Uttar Pradesh entries retained in the immutable top-50 pack are compatibility data only; current routing uses the exact state boundary.

Statewide Chhattisgarh fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 1972004 is eligible for a neutral Chhattisgarh CM Helpline handoff after the National Highway check. The ODbL state polygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is 827e89a598571ade84db77390bca5daf98c9f67fbae716b17193f4ccdc2876eb. A GPS circle touching the state edge or a neighbouring state fails closed.

The statewide service publishes helpline 1076. NIDAAN 1100 is offered only as an urban civic-issue alternate. The user must select and verify the district, department, local body, category, and road owner and complete the grievance externally. Neither service proves responsibility or category acceptance; there is no complaint-write API integration, automatic filing, or ownership inference. The dedicated CHiPS adapter preserves official open-notice IDs/NIT references, titles, organisation hierarchy, deadlines/opening dates, and source locators without inferring an award or contractor. The Raipur and Durg–Bhilai entries retained in the immutable top-50 pack are compatibility data only; current routing uses the exact state boundary.

Statewide Rajasthan fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 1942920 is eligible for a neutral Rajasthan Sampark 2.0 handoff after the National Highway check. The ODbL state MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is dcde670675d0fc50e292c6b306b1f80d9d68a1323250c29d6eddc97992491a36. A GPS circle touching the state edge, a neighbouring state, or the international border fails closed.

Rajasthan Sampark publishes toll-free helpline 181; its current official Android package is com.rajsampark.versiontwo. The user must select and verify the district, department, local body, category, and road owner and complete the grievance externally. Containment does not prove those details, and there is no complaint-write API integration, automatic filing, or ownership inference; a same-State open notice can appear only as an unawarded candidate. Jaipur and Jodhpur remain in the immutable top-50 pack only for saved-report compatibility; current routing uses the exact state boundary.

Statewide Goa fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 11251493 is eligible for neutral CM Helpline Goa after the National Highway check. The ODbL MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is f4c47a79a3671d333d47f66a597d66b6295a78b1cd7cd3cba7bc2db472190e4f. A GPS circle touching the coast, state edge, or a neighbouring state fails closed. Relation 1997192, found in older references, is obsolete and is not used.

The Directorate of Public Grievances says its jurisdiction covers the entire state. Its current portal accepts infrastructure/road and health/sanitation grievances, offers uploads and tracking, and publishes the 24/7 toll-free helpline 1905. The official citizen Android package is in.gov.dpg.cmhelpline. The user must complete the mobile-OTP flow and verify the department, local body, category, and road owner. There is no documented public complaint-write API integration, automatic filing, or ownership inference; a same-State open notice can appear only as an unawarded candidate.

Statewide Madhya Pradesh fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 1950071 is eligible for the neutral Madhya Pradesh CM Helpline after the National Highway check. The ODbL MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is 24f0c93ed8bd40c4c6b4e1f650c3b9870b1e65ccd5d7b00ea0193a8a5aedc357. A GPS circle touching the state edge or a neighbouring state fails closed.

The official portal requires mobile OTP and provides complaint registration and tracking. Its citizen Android package is com.magnum.helpline, and the service uses helpline 181. The user must verify the district, department, local body, category, and road owner and finish externally. There is no documented public complaint-write API integration, automatic filing, or ownership inference; a same-State open notice can appear only as an unawarded candidate. Indore, Bhopal, Jabalpur, and Gwalior remain in the immutable top-50 pack only for saved-report compatibility; current routing uses the exact state boundary.

Statewide Bihar fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 1958982 is eligible for neutral Bihar Lok Shikayat after the National Highway check. The ODbL MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is 3d846e20cfee28a656d6dd808c4dad37a4f1c95852f9f292b0acefde708f4b24. A GPS circle touching Nepal, the state edge, or a neighbouring state fails closed.

The official portal supports new grievances, appeals, status lookup, and toll-free helpline 1800 345 6284. Its official Android package is com.bpsms.jansamadhan. Lok Shikayat applies to eligible state schemes, programmes, services, and public authorities; containment does not guarantee a civic category is accepted. The user must select and verify the public authority, local body, category, and road owner. There is no documented public complaint-write API integration, automatic filing, or ownership inference. The dedicated Bihar eProc2 adapter contributes strict current road-surface notices with official IDs/references, titles, dates, and source locators; missing organisation names remain official numeric IDs instead of being guessed. Patna remains in the immutable top-50 pack only for saved-report compatibility.

Statewide Odisha fallback

Every point whose complete GPS-accuracy circle is confidently inside OpenStreetMap relation 1984022 is eligible for neutral Odisha Jana Sunani after the National Highway check. The ODbL MultiPolygon was retrieved on 25 August 2026 at seven-decimal precision, and its geometry SHA-256 is af0fe4941b6cdd2abe5dc5717db8875bec6b68a2d6671002d2afc9c7d37d5179. A GPS circle touching the coast, state edge, or a neighbouring state fails closed.

The Government of Odisha portal accepts grievances through web, mobile app, WhatsApp, email, letter, and in-person channels and routes them to selected districts, departments, or offices. The official Android package is com.sociomatic.janasunani, its WhatsApp chatbot is +91 63709 51930, and the Government of Odisha publishes Sanjog helpline 155335. Even the skip-login form requires mobile OTP and interactive locality and recipient choices. The user must verify those choices and finish externally; there is no documented public complaint-write API integration, automatic filing, or ownership inference. A same-State open notice can appear only as an unawarded candidate.

Nationwide completion boundaries and handoffs

Twenty separate checksum-pinned packs add or expand the 13 states and 7 Union Territories below, completing coordinate-based civic routing for all 28 states and all 8 Union Territories. Each ODbL administrative relation was retrieved through OpenStreetMap Nominatim on 26 August 2026 at seven-decimal precision. The build pins its relation ID, source bounding box, geometry SHA-256, test points, and official handoff metadata and refuses a changed object or geometry.

National Highway matching runs first, and existing exact municipal, metropolitan, and authority-specific routes remain preferred. A fallback is eligible only when the complete GPS-accuracy circle is inside one pinned state/UT polygon; coast, enclave, and border ambiguity fails closed. Containment selects a neutral starting channel only: it does not identify a municipality or road owner, guarantee category acceptance, call a complaint-write API, or submit anything. The citizen must choose and verify the recipient and retain the official reference ID.

National Capital Territory of Delhi

Delhi coverage uses OpenStreetMap relation 1942586 under the ODbL, checked against the official Delhi State GIS scope. The 21 August 2026 routing data measures 1,483.885 km² and the runtime pins geometry SHA-256 3462ba68bdbbc1fdebc99403aa9e1f9db5e0b78e30ca138b2d25df7463506ab3. Only the full Delhi NCT receives the Delhi route; Noida, Gurugram, Ghaziabad, and Faridabad cannot inherit it. Noida and Ghaziabad may qualify independently through the exact Uttar Pradesh route, while Faridabad retains its conservative top-50 neutral route. The NCT polygon cannot establish whether PWD, MCD, NDMC, Cantonment, DDA, NHAI, or another agency maintains a road.

External channels

The offered service depends on the issue and suggested route: an official app or portal, a published municipal email address, or a state grievance service. Mapped National Highways use Rajmargyatra, CPGRAMS, or 1033 before any municipal route. Greater Mumbai road damage can use BMC Pothole QuickFix; garbage and manhole reports use BMC's MyBMC MARG grievance portal and official app, with helpline 1916. Kolkata uses KMC Grievance 2.0, with the official KMC app as an alternate, WhatsApp at +91 83359 88888, and helpline 1800 345 3375; other West Bengal points use PGRS with CMO Grievance as an alternate. Karnataka uses Janaspandana statewide, with Janahitha for urban issues and verified local routes retained; Kerala uses the CMO grievance portal statewide, with K-SMART for local-body issues. Outside GCC, Tamil Nadu uses Mudhalvarin Mugavari. Andhra Pradesh uses PGRS, with Puramithra for urban areas and helpline 1902. Telangana uses neutral Prajavani statewide, Citizen Buddy as an urban alternate outside Hyderabad, and verified Hyderabad CURE keeps My Cure. Uttar Pradesh uses Jansunwai–Samadhan and helpline 1076. Chhattisgarh uses the CM Helpline and helpline 1076, with NIDAAN 1100 only as an urban civic alternate. Rajasthan uses Rajasthan Sampark 2.0/181; Goa uses CM Helpline Goa/1905; Madhya Pradesh uses CM Helpline/181; Bihar uses Lok Shikayat/1800 345 6284; and Odisha uses Jana Sunani, WhatsApp +91 63709 51930, and 155335. Delhi road damage uses PWD Sewa; garbage and manhole reports use GNCTD/NIC's cross-department CM JanSunwai and JanMitra app, with Delhi PGMS as an alternate and helpline 1902. The user must review and complete the complaint in the external service. Public pre-login pages do not expose every category taxonomy, so these are general civic handoffs, not guaranteed category acceptance.

Authority profiles and ownership

Specific intake profiles cover BMC and the Bengaluru Central, East, North, South, and West city corporations. These profiles select the recipient and complaint wording; they do not establish who owns or maintains the road. Intake authority and road owner are kept as separate fields, and an unknown owner stays unknown. The separate BDA profile is available only when cited responsibility evidence identifies Bangalore Development Authority for that road; a Bengaluru address, nearby BDA work, or municipal boundary match is not sufficient.

Bengaluru general civic handoff

Garbage and manhole reports inside any of the five configured Bengaluru city corporations use Namma Bengaluru (Sahaaya 2.0). The current Greater Bengaluru Authority site lists all five corporations, Sahaaya 2.0 as a public-grievance service, Namma Bengaluru under mobile apps, and helpline 1533. BBMP's official app directory says citizens can file complaints and check status; its administrative review documents the unified platform and photo/video evidence. The exact Android package is com.nammabengaluruNew.org. Outside those verified Bengaluru routes, exact state containment can offer neutral Janaspandana, with Janahitha as an urban alternate; neither assigns a municipal recipient or guarantees category acceptance.

Optional candidate matching is independent of complaint routing. Current National Highway, PMGSY, official State/UT notice, and Karnataka KPPP packs can add reviewable road-title/location candidates where their strict evidence rules pass; they cannot guarantee every tender, identify the road owner, or prove the responsible contractor. No nationwide authoritative road-linked award and defect-liability feed is claimed.

Census top-50 city routes

The selection list is the 50 largest serial-numbered Urban Agglomeration/City entries by population in the Office of the Registrar General & Census Commissioner's official Census 2011 A-04(I) table and workbook. Census rank is selection metadata, not jurisdiction geometry; historical and current names are kept as aliases.

Forty-two entries already use reviewed or statewide routes. For the other 8, an immutable national pack stores conservative relevance envelopes, structured city/state aliases, source receipts, and neutral official grievance contacts. For saved-report compatibility, that pack still physically contains twenty-seven entries now covered statewide: Coimbatore and Madurai in Tamil Nadu; Visakhapatnam and Vijayawada in Andhra Pradesh; Kochi, Kozhikode, Thrissur, Malappuram, Thiruvananthapuram, Kannur, and Kollam in Kerala; Kanpur, Lucknow, Ghaziabad, Agra, Varanasi, Meerut, and Prayagraj in Uttar Pradesh; Raipur and Durg–Bhilai in Chhattisgarh; Jaipur and Jodhpur in Rajasthan; Indore, Bhopal, Jabalpur, and Gwalior in Madhya Pradesh; and Patna in Bihar. It keeps the v1.25 checksum; current routing checks exact state polygons first, so those entries do not override statewide coverage. A route is offered only when GPS accuracy is at most 30 m, the complete accuracy circle stays inside the envelope, and Nominatim returns an exact configured city or municipality alias plus the correct state. Missing, stale, broad, or ambiguous fields fail closed. National Highway routing remains first.

The 8 additions are Surat, Vadodara, Faridabad, Rajkot, Jamshedpur, Srinagar, Dhanbad, and Ranchi.

The reviewed neutral handoffs for those 8 routes are Gujarat eNagar, Haryana Nagar Darshan, Jharkhand Municipal Grievance, and JK Samadhan.

Chennai, Hyderabad, and Ahmedabad

Greater Chennai Corporation

The Tamil Nadu pack contains OpenStreetMap relation 1766358, retrieved through Nominatim on 21 August 2026 and redistributed under the ODbL. The local polygon measures about 433.098 km². It was reviewed against GCC's official 2025 EDP_zoneBoundary_2025 layer. That service publishes no explicit reuse licence, so its geometry is validation evidence only and is not redistributed.

The specific GCC route ends at GCC limits; it does not cover the wider Chennai Metropolitan Area or adjacent urban bodies. Those areas can use the neutral statewide Tamil Nadu route when confidently inside the state boundary. GCC points retain GCC Public Grievance, Android package com.ceedeev.grivenancev2, WhatsApp at +91 94450 61913, and helpline 1913.

Hyderabad CURE official point query

The exact Hyderabad pack contains query metadata but no CURE polygon; a separate Telangana pack contains the ODbL state polygon. On Android, My Cure is selected only when TGRAC's official Proposed Core Urban Area -2053 Sq.Km layer 22 reports that the complete GPS-accuracy envelope is within CURE and TGRAC's exact official Cantonment Boundary layer 1 reports no intersection. No government CURE polygon is redistributed.

Both official responses are required for My Cure. Browser/PWA use, a service failure, or a Cantonment intersection cannot select that specific route, but a point confidently inside the local state polygon can use neutral Prajavani instead. G.O.Ms.No.292 reorganised the expanded area into 12 zones and 60 circles, and G.O.Ms.No.55 later constituted Greater Hyderabad, Cyberabad, and Malkajgiri as three corporations. The app does not infer which corporation or road maintainer owns a point; verified CURE offers shared My Cure and its OTP-bound web flow. Opening either service is not submission, and the web flow is not a public complaint-write API.

Ahmedabad Municipal Corporation

The Gujarat pack contains a dissolved union of the 48 AMC ward polygons from OpenCity / Oorvani Foundation via Bharatlas under the ODbL 1.0. The source snapshot is dated 26 May 2026 and was retrieved on 23 August 2026. The build validates ward codes 1–48, corrects the reviewed source axis order, removes internal ward edges, and pins geometry SHA-256 48de18a521d2ece507ebda91976064353b477283a251bf45d271fdd0c7b82cb7. The union measures about 439.397 km². AMC's official corporation page independently states seven zones and 48 wards.

AMC materials publish larger total areas after outer-city mergers, so this snapshot cannot prove that every current expansion is included. It excludes the wider AUDA planning area and is a reviewed routing aid, not a legal survey or proof of road ownership. A contained point offers the official AMC CCRS, Android package com.amplvb.ccrs, WhatsApp at +91 75678 55303, and helpline 155303. AMC also publishes ccrs@ahmedabadcity.gov.in; this app does not currently offer that email handoff.

These routes prepare editable evidence only. Their coverage checks and handoffs do not prove road ownership; optional project/notice candidates remain separate and unverified.

What comes from where

Current coverage and data limits

• All 28 states and 8 Union Territories have checksum-pinned ODbL boundary containment and a conservative official grievance handoff. The complete GPS-accuracy circle must stay inside one jurisdiction; border ambiguity fails closed. National Highway and exact city/authority routes retain precedence. Containment does not prove road ownership, identify the responsible local body, guarantee category acceptance, or submit anything.
• Maharashtra-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Outside exact MMR and PMC routes, Aaple Sarkar is neutral and the user must select and verify the responsible department.
• MMR coverage targets all 19 urban local bodies and the remaining rural extent. The outer OSM outline is approximate and not a legal boundary. Eleven valid civic polygons can select a specific body; the rest use Aaple Sarkar. No suggestion determines road ownership.
• PMC-specific routing is limited to the current official PMC GIS boundary. PCMC remains in statewide Maharashtra coverage but is not routed as PMC.
• West Bengal-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Only the exact KMC polygon selects KMC; other in-state points use neutral PGRS and require the user to select and verify the district or department.
• Punjab-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Chandigarh is outside it; Connect Punjab remains a neutral route requiring department/local-body selection.
• Tamil Nadu-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Puducherry and Karaikal are outside it; the exact GCC route stays preferred, while other in-state points use neutral Mudhalvarin Mugavari and must verify the recipient.
• Andhra Pradesh-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Yanam is outside it; PGRS and the urban Puramithra alternate are neutral handoffs requiring the user to select and verify the recipient.
• Telangana-wide evidence and official-handoff coverage uses a pinned ODbL state boundary checked against TGRAC's official state layer. Prajavani is neutral, and Citizen Buddy is only an urban alternate outside Hyderabad; the user must select and verify the recipient.
• Karnataka-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Verified municipal and Bengaluru routes remain preferred; other contained points use neutral Janaspandana, with Janahitha only as an urban alternate.
• Kerala-wide evidence and official-handoff coverage uses a pinned ODbL state boundary and excludes Mahe. Kerala CMO is neutral and K-SMART is a local-body alternate; the user must select and verify the recipient.
• Uttar Pradesh-wide evidence and official-handoff coverage uses a pinned ODbL state boundary and excludes Delhi NCT. Jansunwai–Samadhan is neutral; the user must select and verify the recipient.
• Chhattisgarh-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. The CM Helpline is neutral and NIDAAN 1100 is only an urban civic alternate; the user must select and verify the recipient.
• Rajasthan-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Rajasthan Sampark 2.0 is neutral; the user must select and verify the recipient.
• Goa-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. CM Helpline Goa is neutral; the user must select and verify the recipient.
• Madhya Pradesh-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. CM Helpline is neutral; the user must select and verify the recipient.
• Bihar-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Lok Shikayat is neutral and its statutory service scope must be verified.
• Odisha-wide evidence and official-handoff coverage uses a pinned ODbL state boundary. Jana Sunani is neutral; the user must select and verify the district, locality, and recipient office.
• All 50 largest Census 2011 population centres have a route. Eight additions require both a conservative coordinate envelope and exact structured city/municipality plus state fields; markers and envelopes do not claim complete Urban Agglomeration boundaries.
• Delhi-specific coverage is the full NCT only. Other NCR places cannot inherit the Delhi recipient; Noida and Ghaziabad may use the separate Uttar Pradesh route, while Faridabad retains its top-50 neutral route.
• The Chennai-specific route is GCC only. Its ODbL polygon was validated against, but is not copied from, GCC's official 2025 layer; other confidently contained Tamil Nadu points use the statewide route.
• Hyderabad's specific My Cure route uses TGRAC's official 2,053 km² CURE point-query service on Android. The complete GPS-accuracy envelope must be within CURE and must not intersect the exact official Secunderabad Cantonment layer. Browser/PWA use, service failure, and Cantonment intersection cannot select My Cure, but a verified in-state point can use neutral Prajavani. Neither handoff assigns one of the three 2026 corporations.
• Ahmedabad coverage uses the pinned 439.397 km² ODbL union of 48 AMC wards. AMC materials publish larger post-merger areas, so complete current outer-expansion coverage is not proven. The wider AUDA area is excluded.
• The project has no complaint-write API, status sync, or cross-user report database. Evidence stays local until the user deliberately opens an external handoff.
• Optional National Highway, PMGSY, official State/UT notice, and Karnataka KPPP candidates never establish road ownership, exact segment, an award, contractor responsibility, warranty, or DLP without authoritative evidence. Open notices are not awards, and nationwide candidate coverage is not a guarantee for every tender or road.
• Of 319 urban local bodies in the roster used to build the Karnataka routing/contact pack, 182 have a supported directory entry and 137 do not. A missing directory entry prevents a specific municipal recipient, not the neutral statewide Janaspandana fallback.
• Of 42,283 title-matched source candidates, 18,972 are DMA or legacy BBMP records. Of those, 7,473 explicitly include carriageway work and the downloadable pack retains the 5,351 indexed to a supported body.
• The full source has 41,159 records without a winning bidder. The filtered 5,351-row pack has 4,825 without one and 526 with one.
• Mapped National Highways and National Expressways across India are checked before municipal routes and offered a neutral Rajmargyatra/1033 handoff. Unmapped stretches and unsafe matches are not guessed.
• For Karnataka, rural roads, unknown road classes, and unsupported bodies are not routed to a municipal recipient; exact state containment can offer neutral Janaspandana instead. Elsewhere, a confidently contained state/UT point can use the conservative official handoff even when no more specific city route exists.
• All counts describe the repository snapshot above, not the current contents of an external portal.
• The public Nominatim endpoint is cached on an approximately 11 m grid and requests are serialized below one per second. A large deployment needs a policy-compliant managed or self-hosted service. The 8 additional city routes depend on exact Nominatim structured fields. All state/UT and other downloaded polygon routing remains local; Android's specific Hyderabad CURE route sends the GPS-accuracy envelope to TGRAC's official CURE and Cantonment query services.

How to audit it

1. Use the photo and printed coordinates to check the event itself.
2. For every supported region, verify the suggested route and road owner in the official service and keep any grievance/reference ID it returns.
3. For Karnataka, follow the address and GIS sources above to check location and routing.
4. Use the cited official portal root and record identifiers to verify every candidate's exact segment, carriageway scope, award, contractor, and DLP terms. For Karnataka KPPP rows, search KPPP by tender number. Never infer DLP from publication date.
5. Inspect the open-source build scripts and detailed provenance note for filtering and indexing logic.

Found stale or incorrect source data? Open a GitHub issue with a public source link. Do not include an API key, private personal data, or an unredacted road photo.