Draft guides at 80% collection and 80% segregation, not official targets.
“Both”
Collection and segregation. Top right meets both guides, bottom left is below both.
How to read the axes and positions
Further right
More of its households had waste collected.
Higher up
More of those households segregated their waste.
A number on a dot means several ULBs sit at exactly the same position, and the ULB selector lists every one. The dashed lines stay where they are when you filter by district.
Selected ULB · source code 1136
NARSIPATNAM
Anakapalli · 17 positive-household secretariats of 17 paired · 12 Aug 2026
Segregation among collected69.5%13,817 / 19,874 collected households
What this position means
Meets the 80% collection reference and below the 80% segregation reference. This is a reported daily service position.
Inspect the paired source figures
Native ULB code 1136. Only identical secretariat/date records are collapsed. Both exports agree on native identity and household denominators. Quantities below use the same paired records; percentages are ratios of sums.
Secretariat code
Households
Collected
Segregated
Code check
21136001
929
926
564
Consistent
21136002
1,472
1,472
1,121
Consistent
21136003
1,183
1,183
605
Consistent
21136004
1,388
1,380
868
Consistent
21136005
1,209
1,204
870
Consistent
21136006
963
956
678
Consistent
21136007
950
945
761
Consistent
21136008
1,432
1,370
781
Consistent
21136009
822
814
415
Consistent
21136010
836
833
487
Consistent
21136011
1,587
1,587
1,396
Consistent
21136012
1,507
1,480
1,010
Consistent
21136013
900
898
490
Consistent
21136014
1,281
1,280
1,092
Consistent
21136015
1,275
1,263
816
Consistent
21136016
1,027
1,027
909
Consistent
21136017
1,279
1,256
954
Consistent
No cross-programme Diagnostics identity is inferred from a similar ULB name.
Outside the matrix · 11 ULBs in this district selection
Whole ULB groups are held out when any paired secretariat needs geographic-code review. Code differences can reflect geographic grain; they are not automatically source errors. Zero collection leaves the segregation ratio undefined.
References, date choice & source coverage
Draft analytical references, not approved targets. The initial 80% lines are explicit review guides. Change them to inspect sensitivity; a ULB on a line meets that reference. Positions never change when a reference changes, only categories.
Why one day? The retained window carries household denominators on 16 days, but substantial collection figures on only 12 August. The other 15 days contain mostly stored zeros; these do not establish that collection stopped. We therefore compare ULBs on the supported reference day, rather than rank their service over the whole window.
Inspect daily reporting evidence
Collection percentages below describe stored reports and changing daily populations, not a service-performance trend.
2026-08-12: 112 of 116 ULBs carry positive collection · 63.7% recorded collection / households.
2026-08-13: 5 of 106 ULBs carry positive collection · 0.4% recorded collection / households.
2026-08-14: 6 of 107 ULBs carry positive collection · 0.3% recorded collection / households.
2026-08-15: 4 of 103 ULBs carry positive collection · 0.4% recorded collection / households.
2026-08-16: 2 of 111 ULBs carry positive collection · 0.2% recorded collection / households.
2026-08-17: 7 of 111 ULBs carry positive collection · 0.4% recorded collection / households.
2026-08-18: 2 of 109 ULBs carry positive collection · 0.4% recorded collection / households.
2026-08-19: 1 of 105 ULBs carry positive collection · 0.1% recorded collection / households.
2026-08-20: 4 of 111 ULBs carry positive collection · 0.4% recorded collection / households.
2026-08-21: 5 of 102 ULBs carry positive collection · 0.2% recorded collection / households.
2026-08-22: 5 of 95 ULBs carry positive collection · 0.3% recorded collection / households.
2026-08-23: 1 of 91 ULBs carry positive collection · 0.1% recorded collection / households.
2026-08-24: 2 of 90 ULBs carry positive collection · 0.3% recorded collection / households.
2026-08-25: 4 of 90 ULBs carry positive collection · 0.5% recorded collection / households.
2026-08-26: 3 of 74 ULBs carry positive collection · 1% recorded collection / households.
2026-08-27: 1 of 34 ULBs carry positive collection · 0.5% recorded collection / households.
Definitions. Collection = summed collected households / summed total households. Segregation = summed reported segregating households / summed collected households. The application interprets garbage_segregation as households, pending departmental definition confirmation; it is not waste tonnage or an independent environmental outcome.
Retained sources. msw_door_to_door_collection_api: 64,368 raw rows, 644 pages, retrieved 2026-09-08 · waste_egregation_api: 64,368 raw rows, 644 pages, retrieved 2026-09-08. Both sources are paired by secretariat code and day, then summed by native ULB code. The builder fails closed on conflicts, missing measures, unmatched records or impossible containment. One source-reported day, not a sustained or overall performance rating. Whole ULBs with native/enriched code differences are held out; matching codes are not external master certification. Where the native district code is blank or the text NULL (Markapuram), the same row's LGD district code is used and counted in districtCodeFromLgdSecretariats. Benchmarks are draft analytical references, not departmental targets.
Requirements for formal performance classifications
Gap Radar / evidence boundary
Evidence reviews are open. Performance labels need more.
0
entities eligible for scoringUNSCORED
No performance label is assigned before every required evidence gate passes.
What is blocking activation?
01
Working crosswalk reviewed locally
82 of 82 residual names carry a local decision; formal sign-off is still required.
Local review only · formal approval pending
02
Supplied LGD mapping is not usable as identity
6 of 44 retained datasets carry LGD codes, reaching 20% of observed entities. 6 district labels map to two different LGD districts inside one source.
Required before scoring
03
Periods not aligned
Operational and outcome periods have not been aligned for comparison.
Required before scoring
04
Outcome data is older
The retained outcome evidence reports 2024. Operations are from 2026.
Required before scoring
05
Scoring policy not approved
Nobody has agreed the thresholds yet, so there is nothing to score against.
Required before scoring
Next owner actionFormal crosswalk sign-off + aligned current outcomes
Local decisions support review; they do not replace formal approval. Period, quality and policy conditions still apply.
Collection and segregation both key on a numeric secretariat code, both report the same 4,023 codes on 2026-08-12, and they agree on the household denominator for every one. No names are matched, so nothing here rests on an inference, which is why identity, period and denominator finally pass. Performance still does not.
Secretariats in cohort
4,018 2,321 reported collection
Collected of households
56% 26,40,792 of 47,09,868
Segregated of collected
73% never exceeds collection, in any secretariat
OpenEntity identity is established
Both sources key on sachivalayam_code. 4023 codes in collection, 4023 in segregation, 0 present in only one, 0 disputed. No name matching is involved.
OpenPeriods are aligned
Both measures are read from the same reported day, 2026-08-12. No period is bridged and no figure is carried forward.
OpenThe denominator is agreed
0 of 4018 secretariats disagree on total households between the two sources.
ShutA performance basis exists
One reported day. A single day describes a day; it does not establish how an entity performs, and nothing here should be read as a trend.
ShutA scoring policy is approved
No thresholds, weights or directionality have been agreed. Without an approved policy there is nothing to score against, whatever the data supports.
3 of 5 gates open · still UNSCORED
This is the closest the product has come to a scoreable cohort, and it is still not one. The two gates that remain shut are not data problems that more pulling would fix: one reported day cannot establish performance, and no scoring policy exists to score against. Positions are shown; no entity is ranked or labelled.
Positions on 2026-08-12
Two reported rates, one day
Reported collection against reported segregationOne day. 2,321 secretariats with a rate; 1,697 reported no collection and have none.
1,697 secretariats reported no collection on this day and are not plotted. They have no segregation rate because there is no denominator. That is absent evidence, not a zero, and placing them at the origin would invent a reading.
Source & reading boundary
One reported day, joined on a numeric secretariat code present in both sources. Identity, period and freshness are established; performance is not. A single day is not a basis for scoring, and no scoring policy has been approved.
Joined on sachivalayam_code: 4,023 codes in collection and 4,023 in segregation, 0 present in only one, 0 held out for disagreeing repeats, 0 disagreeing on total households. Segregated households never exceed collected households in any secretariat (0 breaches), which is the containment the two measures must obey.
Identity review and historical investigations
Identity evidence / supplied mapping
The source now states its own identity. It does not agree with itself.
Six retained datasets carry LGD district and mandal codes beside the departmental label, a mapping the source asserts rather than one this product inferred. That makes it evidence. It does not make it correct.
Entities reached
20% 52 of 265
Datasets carrying codes
6 of 44 retained
Codes disputed across sources
82
Not adopted as canonical identity
6 departmental district labels map to more than one LGD district inside a single source, and 6 district mappings pair labels that are not spelling variants of each other. The supplied mapping cannot be adopted as canonical identity until the source resolves them.
One departmental district label mapped to two different LGD districts inside a single dataset. Each of these is the source disagreeing with itself, not a naming question, so none of them can be resolved here.
Dr. B.R. Ambedkar Konaseema→DR.B.R.AMBEDKAR KONASEEMATIRUPATISwachh Survekshan
Chittoor→ANNAMAYYACHITTOORSewage plant capacity
Prakasam→MARKAPURAMPRAKASAMSewage plant capacity
Connecting ULB names across sources
Crosswalk workbench · review whether different source names refer to the same urban local body
123 anchor IDs · 0 conflicts
Local working review complete
82 of 82 residual names carry a decision
The review queue is closed in this browser. These decisions improve joinability, but they are not an authoritative state crosswalk until formally signed off.
01Formal sign-offThe crosswalk is still a local working copy.
02Aligned outcomesOperations are 2026; retained outcomes are 2024.
03Approved policyThresholds and weights remain a policy decision.
Open decision audit and transfer tools82 local decisions · inspect, revise, copy or import
Similarity ranks, it never decides. Candidates are district-scoped. Atmakur K in Kurnool scores 0.86 against ATMAKUR-N in Nellore, and is held back rather than matched. Decisions are a local working copy, not an approved crosswalk.
No queue items match this filter.
Same source · same period · reported counts
Orders issued. Vehicles supplied?
Read procurement stages together without mixing sources or years.
July 2026
75 / 83paired ULB-name candidates report work orders, but zero supplied.
83 candidates share 28 coordinate positions. Larger dots group identical counts; positions are not shifted to separate them.
Source & reading boundary
ap_citizen360.sasa_sac_machinery_e_autos_service_model_api · sasa_sac_machinery_e_autos_service_model_api · ULB grain · July 2026. Each dot uses two counts from the same source record. No name crosswalk, national-rank association, delay estimate or performance score is inferred. Overlapping names can be browsed individually.
Waste clearance against national rank
65 ULBs holding both figures · not a performance score
July 2026 vs 2024 rank · 2 years apart
A varied historical-outcome comparison. Other operational measures can be paired, but most reported IHHL completions and vehicle-supply counts are zero, not missing. The two axes here are two years apart, so position shows contrast, never cause.