District rows
1
One row per district in the active Lakshadweep publication.
CSV AND API
Download exactly what the public site is showing.
Use these downloads when you need the exact rows behind the public site. They stay pinned to the active publication until a newer run is reviewed and published.
CSV/API parity
Aligned
The territory-wide CSV mirrors the same fields exposed by the JSON endpoints.
Source snapshot
25 April 2026
Every download carries this date and the methodology version so a citation stays valid.
Publish boundary
Published only
If a newer run is incomplete, the downloads remain pinned to the last safe publication.
Available files
District-specific history CSVs are linked from each district's permalink page so every download is one click from its narrative context.
Territory-wide district table
One row per district with rank, pending cases, cases filed and cleared last month, cases cleared per 100 filed, typical wait, old-case burden, file-clear gap, backlog movement, repeat signal, and flag reason. Includes the source snapshot date, methodology version, freshness, and source attribution as columns so the download is self-describing.
Public JSON endpoints
Three endpoints cover territory-wide stats, district rows, and the territory-wide trend series. Same fields as the CSV, fetched as machine-readable JSON for dashboards, notebooks, or downstream tooling.
What these files contain, and what they don't
What is in the CSV
Normalized snapshot fields only: the same numbers, labels, derived pressure signals, and flag reasons that appear on the public pages.
Each row references the source snapshot date and methodology version so a published number is always citeable.
What is not in the CSV
Raw capture bundles and operator evidence artifacts stay outside the public download boundary. Those belong to the review trail, not to the reader product.
For formula details, see the methodology page. For narrative context, start from a district's permalink.