CivicDataForge block-level follow-up package
Generated: 2026-09-02T06:04:48.039929Z

WHAT IS INCLUDED
- jammu-development-block-geometry-2017.*: 20 official Jammu block polygons from the Government of India Map Service, exported to WGS84 GeoJSON and Shapefile.
- jammu-current-lgd-block-directory.csv: the 20 blocks currently returned by the Ministry of Panchayati Raj LGD API for Jammu district.
- delhi-subdistrict-boundaries-nwic-2025.*: 36 official Delhi subdistrict polygons from the National Water Data Portal / Geological Survey of India layer.
- delhi-current-lgd-district-directory.csv: current Delhi district directory rows from LGD.
- reconciliation.json: machine-readable source, count, and freshness reconciliation.

IMPORTANT BOUNDARIES
- Delhi: LGD currently returns zero development blocks. The Delhi file is therefore subdistrict-level and is not relabeled as a block file.
- Jammu: 18 of the 20 current LGD block codes have matching polygons in the official LGD-2017 geometry service. Maira Mandrian (6864) and Chowki Choura (6865) have no matching polygon there. Sumb (6935) and Ramgarh (6937) exist in the 2017 geometry but are absent from the current Jammu LGD block directory.
- This package preserves those differences explicitly. It does not invent or silently rename geometry.

PRIMARY SOURCES
- Current LGD directory: https://lgdirectory.gov.in/webservices/lgdws/blockList?districtCode=5
- Official block polygon layer: https://mapservice.gov.in/mapserviceserv176/rest/services/Panchayat/AdminGPHierarchy/MapServer/2
- NWDP subdistrict dataset: https://nwdp.nwic.gov.in/api/3/action/package_show?id=sub-district-boundary

USE
Open the .shp file with its .shx, .dbf, .prj, and .cpg sidecars in the same directory. Review reconciliation.json before treating the Jammu geometry as a current administrative source.
