Data sources · District OS

System

Data sources & provenance

Every dataset this application ships, where it came from, and how far it can be trusted.

Upstream sources

Ordered from most to least authoritative.

Government of Telangana

GODL-India

District and mandal boundary shapefiles

The authoritative boundary geometry. Imported into OpenStreetMap with source attribution, which is how it reaches this application.

Source

Census of India 2011

Public

Population, literacy, density, sex ratio, urban share

The district was constituted in 2016 from Ranga Reddy; 2011 figures are the Telangana government's recompilation for the new district boundary.

Source

OpenStreetMap contributors

ODbL 1.0

Roads, rail, facilities, water bodies, green space, land use, wards

Harvested via the Overpass API, clipped to the district relation, then normalised. Coverage is volunteer-driven, so facility counts are a lower bound.

Source

Election Commission of India

Public

Assembly constituency composition (which mandals fall in which seat)

No open geodata exists for the ECI delimitation. Constituency extents shown on the map are dissolved from the constituent mandals and are indicative only — real constituencies do cross mandal lines.

Source

Illustrative sample records

n/a

Issues, projects, events, documents, organisation, media

No public open dataset exists for these. Records are deterministic samples anchored to real coordinates, mandals and wards so the modules behave realistically. Replace the corresponding JSON files to go live.

Manifest

Shipped datasets

Loading…

Rendering

Basemap & tile providers

All keyless and free to use — the build ships no API keys and needs no signup.

OpenFreeMapVector basemap and 3D building extrusions CARTODark raster basemap tiles Esri World ImagerySatellite imagery Mapzen / AWS Open DataTerrarium elevation tiles for 3D terrain

Pipeline

Regenerating the data

The datasets are reproducible from source with two scripts.

1 · Harvest from OpenStreetMap

npm run fetch:osm

Queries the Overpass API for every layer inside the district relation, with mirror fallback and retries. Writes raw responses to scripts/.osm-cache/.

2 · Normalise into GeoJSON and statistics

npm run build:data

Stitches relation rings, computes areas and lengths on the WGS-84 sphere, performs the mandal/ward spatial joins, and emits everything under public/ together with this manifest.

3 · Regenerate the sample record sets

npm run build:records

Rebuilds the illustrative issues, projects, events, documents, organisation and media records. Deterministic — the same seed always produces the same output.

This page is generated from public/data/manifest.json, which the pipeline writes on every run — it cannot drift from what actually ships.