Evidence Vault

The research that makes KWIN's story credible.

Seven curated datasets from OpenCity and Karnataka State — each one carefully mapped to what it can and cannot prove about KWIN City. This is how responsible urban research looks.

Referenced sources

Source basis

S3Contextual source

Bengaluru Aviation Traffic Data

Government of India via OpenCity

Contextual source showing airport-linked regional demand and access patterns relevant to North Bengaluru growth narratives.

Open source

S5Contextual source

Bengaluru STRR Via Bannerughatta National Park Documents

Government of Karnataka via OpenCity

Project-adjacent source demonstrating that orbital road planning around Bengaluru is institutionally real and documented.

Open source

S6Contextual source

BDA Intermidiate Ring Road(IRR) Documents

BDA via OpenCity

Contextual source for the broader network logic connecting peripheral towns around Bengaluru.

Open source

S4Contextual source

Economic Survey of Karnataka 2025-26

Government of Karnataka via OpenCity

Contextual source for Karnataka’s macroeconomic and industrial capacity; it supports state-level growth arguments, not KWIN-specific projections.

Open source

S7Contextual source

Karnataka Annual Rainfall - Districts, Taluks and Hoblis

KSNDMC via OpenCity

Contextual hydrology source supporting climate-aware planning, stormwater design, and water resilience arguments.

Open source

S8Contextual source

Karnataka - Talukwise GroundWater Depth

Government of Karnataka via OpenCity

Contextual source showing why groundwater accountability and recycling matter for large developments in the region.

Open source

S9Contextual source

Bengaluru Lakes and Their Maintainers

Government of Karnataka via OpenCity

Contextual source on lake governance and blue-green infrastructure traditions in the Bengaluru region.

Open source

Evidence Vault

OpenCity is useful for defending the regional logic behind KWIN City. It helps us talk responsibly about corridor growth, connectivity, water planning, and Karnataka's economic capacity without overstating what those datasets prove about KWIN itself.

How To Use These Sources

Use OpenCity as regional context, not as proof of KWIN-specific commitments.
Prefer claims about corridor readiness, mobility, hydrology, and state economic capacity.
Keep acreage, investment, jobs, MoUs, and delivery timelines tied to KIADB or other primary records.
Treat sustainability datasets as benchmarks for good planning, not confirmation of KWIN implementation.

Safe Narrative Frame

KWIN City should be presented as a proposed node within larger patterns that are already visible in Karnataka and the Bengaluru region: airport-led growth, corridor-based mobility planning, measurable water constraints, and state-level industrial ambition. That is a strong case. It is also a much more credible case than treating contextual datasets as if they validate every KWIN project claim.

Bengaluru Aviation Traffic Data

Government of India via OpenCity

Contextual evidence

Airport demand and regional connectivity from 2015 onward

Aviation traffic is one of the strongest contextual arguments for North Bengaluru as a long-horizon growth geography tied to national and global access.

Useful for saying

+North Bengaluru has credible airport-linked growth logic.
+KWIN can be framed within a wider access and logistics narrative.
+Regional mobility advantages are not purely speculative marketing.

Not enough to prove

-That KWIN will capture a specific share of airport-driven growth.
-That any promised investment or tenancy will materialize.

OpenCity datasetView source

Bengaluru STRR Via Bannerughatta National Park Documents

Government of Karnataka via OpenCity

Project-adjacent evidence

Formal documentation around the Satellite Town Ring Road

This dataset supports the reality of orbital road planning around Bengaluru and helps explain why corridor-led urban development is a defensible proposition.

Useful for saying

+STRR is a real planning object with official documentation.
+A node-based metropolitan expansion model is institutionally grounded.
+Connectivity language around KWIN can be framed as part of a larger regional transport strategy.

Not enough to prove

-That KWIN has the exact connectivity profile described in promotional material.
-That STRR timelines or alignments directly validate KWIN delivery dates.

OpenCity datasetView source

BDA Intermidiate Ring Road(IRR) Documents

Bangalore Development Authority via OpenCity

Contextual evidence

Peripheral road-planning logic connecting towns around Bengaluru

The IRR material strengthens the argument that Bengaluru is being planned as a networked region rather than a single urban core.

Useful for saying

+Peripheral towns are part of formal mobility thinking.
+Satellite urban nodes are consistent with metropolitan planning patterns.
+KWIN can be presented as part of a regional network, not an isolated township.

Not enough to prove

-That KWIN is already integrated into all proposed corridors.
-That planned transport projects automatically convert into economic success.

OpenCity datasetView source

Economic Survey of Karnataka 2025-26

Government of Karnataka via OpenCity

Contextual evidence

Macroeconomic and sectoral context for Karnataka

The economic survey is useful for showing that KWIN is being proposed inside a state with industrial depth, policy ambition, and ongoing economic expansion.

Useful for saying

+Karnataka has the macroeconomic capacity to host large-scale urban-industrial projects.
+A knowledge-and-innovation-led narrative is aligned with broader state growth strategy.
+KWIN can be discussed as part of a wider development ecosystem.

Not enough to prove

-That KWIN-specific investment figures are correct.
-That KWIN will achieve any exact employment projections.

OpenCity datasetView source

Karnataka Annual Rainfall - Districts, Taluks and Hoblis

KSNDMC via OpenCity

Contextual evidence

Rainfall variability and hydrological context from 2020 to 2024

This dataset helps turn sustainability language into something measurable by emphasizing the importance of rainfall-aware stormwater, recharge, and storage systems.

Useful for saying

+Large townships in Karnataka need climate-aware water planning.
+Water-sensitive design is a serious planning requirement, not a decorative add-on.
+A research-oriented sustainability section for KWIN is justified.

Not enough to prove

-That KWIN has already engineered adequate water infrastructure.
-That the proposed lake system is hydrologically validated.

OpenCity datasetView source

Karnataka - Talukwise GroundWater Depth

Government of Karnataka via OpenCity

Contextual evidence

Groundwater depth and resource stress context

Groundwater datasets are valuable because they force the KWIN story to be assessed through resilience, recharge, and water accountability rather than pure aspiration.

Useful for saying

+Water governance is central to the credibility of any township in the region.
+Recycling, recharge, and lake-linked design should be core to the KWIN story.
+Sustainability claims should be benchmarked against measurable resource realities.

Not enough to prove

-That KWIN has solved local groundwater constraints.
-That proposed water systems are already approved or technically sufficient.

OpenCity datasetView source

Bengaluru Lakes and Their Maintainers

Government of Karnataka via OpenCity

Contextual evidence

Lake governance and maintenance context for Bengaluru

Lake governance data is useful because it places KWIN’s wellbeing and resilience narrative inside Bengaluru’s longer environmental history of water bodies and stewardship.

Useful for saying

+Lake systems are a serious regional planning concern.
+Blue-green infrastructure is a credible design language for KWIN.
+Waterbody restoration can be discussed as part of metropolitan ecological practice.

Not enough to prove

-That KWIN already has ten interconnected lakes as described.
-That the KWIN waterbody network is operational or ecologically validated.

OpenCity datasetView source