Chapter 2: The Planned Capital

---

In the spring of 1948, a German-Jewish architect who had fled the Nazis a decade earlier arrived in Odisha to design a city from scratch. Otto Koenigsberger was forty-one years old. He had spent the war years working for the Princely State of Mysore, designing hospitals and housing for a country that was not his own but had taken him in. He had consulted on Jamshedpur’s expansion — the Tata steel town that remains India’s most successful planned industrial city. He had been part of the early conversations about what would eventually become Chandigarh, though Le Corbusier would get that commission. Nehru recommended him for the Bhubaneswar job, and Chief Minister Harekrushna Mahtab — a man who understood that a state formed only twelve years earlier needed physical infrastructure to match its political ambitions — brought him to Odisha.

The brief was straightforward. Cuttack, the existing capital, was flood-prone, congested, and hemmed in by the confluence of the Mahanadi and Kathajodi rivers. Expansion was geographically impossible. The new state of Orissa needed a new capital, and the site chosen was near the ancient temple town of Bhubaneswar — a settlement that had existed for over two thousand years but housed barely sixteen thousand people. On April 13, 1948, Nehru laid the foundation stone.

Koenigsberger’s plan was elegant. He designed for 40,000 people, organized into six neighbourhood units — each a self-contained cluster of 5,000-6,000 residents spread across roughly 150 acres. Every unit would have a primary school within a quarter-mile walk, a health centre, a market, entertainment, places of worship, gardens. The organizing metaphor was the village transplanted into the city: walkable, human-scaled, complete. The units attached to a central spine road like branches to a tree trunk, growing northward in a linear pattern — add a new unit, extend the spine, and the city grows without disrupting what already exists. He specified seven types of roads for seven types of movement: footpaths, parkways, cycle paths, minor streets, major streets, main roads, and arteries. The primary mobility assumption was walking. The secondary was cycling. Cars did not figure into the design in any meaningful way.

Unit V was the administrative heart — Secretariat, Legislative Assembly, Raj Bhavan. The other units arranged themselves around this core. Koenigsberger, shaped by his experience as a refugee from fascism, deliberately avoided temple-inspired architecture for government buildings. He did not want the new capital to replicate the social hierarchies embedded in religious architecture. He wanted a space where “workers and their representatives, manufacturers, businessmen, scientists, officials and last but not the least politicians meet and collaborate.” He insisted the master plan be published with an appeal for public participation. It never was. The plan circulated only among government officials.

The six units were named: Bapuji Nagar, Ashok Nagar, Kharavela Nagar, Bhauma Nagar, Keshari Nagar, Ganga Nagar. They were built. They still exist. They remain the best-planned, most liveable zone in the city — the most green cover, the most open space, the most coherent street pattern.

And they were designed for 40,000 people.

Today, Bhubaneswar holds an estimated 1.3 million. That is a 32.5x overshoot. The city reached its designed capacity by 1961 — thirteen years after the plan was drawn. By 1971, it held 113,000 people, nearly three times the design load. By 1991, it was 411,542 — ten times over. By 2011, the census recorded 885,363 in the municipal corporation area alone. The urban agglomeration was larger still.

Here is the thing about a 32x load increase: no system survives it without being redesigned. Not a bridge. Not an electrical grid. Not a software application. If you built a web application to handle 40,000 concurrent users and 1.3 million showed up, the application would not slow down gracefully. It would crash. The database would choke. The load balancer would fail. Response times would degrade from milliseconds to minutes. Features that worked perfectly at the designed load — the neighbourhood school within walking distance, the market you could reach on foot, the seven-type road hierarchy that separated pedestrians from cyclists from cars — would stop functioning entirely. Users would develop workarounds: shortcuts through back alleys, informal markets in unauthorized locations, auto-rickshaws and two-wheelers flooding roads designed for feet and bicycles. The workarounds would become the system. The original design would become a ghost underneath.

That is what happened to Bhubaneswar. Koenigsberger built a brilliant minimum viable product. The city was never iterated.

---

The Koenigsberger Plan

To understand what went wrong, you first need to understand what went right.

Koenigsberger’s 1948 master plan was not naive. It was one of the most thoughtful pieces of urban design produced in post-independence India — more thoughtful, in several respects, than the more famous Chandigarh plan that Le Corbusier would produce three years later.

The difference was philosophical. Le Corbusier designed Chandigarh for automobiles and monuments. His Capitol Complex — the High Court, Secretariat, and Legislative Assembly — was deliberately monumental, set apart from the residential sectors, designed to inspire awe. The scale was superhuman. The streets were wide enough for cars that most Indian families would not own for decades. The sectors were large — 800 metres by 1,200 metres — and internally organized around a commercial strip. The vision was the machine-age city: rational, geometric, concrete.

Koenigsberger designed Bhubaneswar for pedestrians and climate. His neighbourhood units were small enough to walk across in ten minutes. His buildings incorporated forecourt gardens and rear courtyards suited to the hot-humid climate of coastal Odisha — passive cooling, cross-ventilation, shade from tropical sun. He specified protective green corridors between units. Where Le Corbusier’s Chandigarh was designed to look good from a helicopter, Koenigsberger’s Bhubaneswar was designed to feel right at ground level.

The third planned capital, Gandhinagar, came later — 1965, designed by H.K. Mewada and P.M. Apte, both trained under Le Corbusier at Chandigarh. Gandhinagar adapted the grid model with Gandhian sensibilities: thirty sectors, significant green cover (a 57% target), austere government buildings. But Gandhinagar was placed deliberately near Ahmedabad’s commercial engine. It could draw on the economic dynamism of one of India’s most entrepreneurial cities. Chandigarh sat at the edge of industrial Punjab and Haryana. Both planned capitals had commercial hinterlands.

Bhubaneswar had no hinterland. The nearest significant city was Cuttack — which was itself declining, which was in fact the city Bhubaneswar was designed to replace. The new capital would not be nourished by proximity to commercial energy. It would have to generate its own. And since it was built to house a state government, the energy it generated would be bureaucratic, not commercial.

This was the first design choice that mattered. In software terms, Koenigsberger designed the application but did not choose the deployment environment. The environment chose itself: a government town, in a state with no significant industry, surrounded by agricultural hinterland, with no commercial city to lean on. The application was sound. The infrastructure it ran on was limited.

The second design choice that mattered was the planned population. Forty thousand. Some sources say the range was 20,000 to 50,000 — Koenigsberger designed for a flexible capacity, but the core infrastructure assumed a small administrative town. This was reasonable in 1948. The state government employed a finite number of people. The plan was for those people and their families, plus the service economy they would generate: shopkeepers, cleaners, cooks, clerks. Forty thousand was a defensible estimate for a state capital that was expected to remain administrative in character.

But it was an MVP. A minimum viable product serves the initial use case well. Its value depends entirely on what happens next — on the iteration. You measure how users actually behave, identify where the design assumptions were wrong, and rebuild. The MVP is not the product. It is the hypothesis.

Koenigsberger’s hypothesis was that Bhubaneswar would remain a small, walkable, government town. The hypothesis was wrong within thirteen years. And nobody iterated.

The comparison with Chandigarh is instructive in a specific way. Le Corbusier designed Chandigarh for 500,000 people. Today it holds approximately 1.2 million — a 2.4x overshoot. That is still a significant mismatch, but it is a different order of magnitude from 32.5x. Chandigarh’s larger initial capacity gave it more runway. More importantly, Chandigarh became a Union Territory in 1966, which meant its land use and development came under direct central government control. The political pressure to override the plan — to rezone residential land for commercial use, to allow unplanned extensions, to build government colonies wherever the Chief Minister wanted them — was mitigated by Union Territory governance. The plan was protected partly by accident of constitutional status.

Bhubaneswar had no such protection. The plan was under the control of the same state government it was built to house. The government that occupied the buildings Koenigsberger designed was also the government that decided what happened to the land around them. Every time a new department was created, every time a new colony was needed for transferred officers, every time a minister wanted a project in the capital, the plan got overridden by the people the plan was designed to serve. The client ate the architecture.

Gandhinagar, for its part, was planned for roughly 150,000 and has reached about 400,000 — a 2.7x overshoot. Again, a different order of magnitude. And again, proximity to Ahmedabad absorbed much of the population pressure that might otherwise have landed on the planned capital itself. People who wanted commercial opportunity went to Ahmedabad. People who wanted government jobs went to Gandhinagar. The division of labour between the two cities acted as a pressure valve. Bhubaneswar had no pressure valve.

The master plan evolution tells the story of abandoned ambition:

1948: Koenigsberger’s neighbourhood-unit plan. Organic, human-scaled, climate-adapted. 1968: A continuation with modifications — still nominally following the neighbourhood model. 1994: The shift. Neighbourhood planning abandoned in favour of zone-based rational planning. The fundamental unit of the city changed from the human-scaled neighbourhood to the administrative zone. 2010: IIT Kharagpur prepared a comprehensive development plan. Fourteen planning sub-zones. 2030 CDP: Bhubaneswar Development Authority plan. The language is managerial, not architectural. 2040 Draft CDP: The planning area expanded to 705 square kilometres — absorbing 364 surrounding villages. An acknowledgment that the city had already swallowed its surroundings and the plan needed to catch up with the sprawl it had failed to prevent.

Each plan was larger than the last. Each was outdated by the time it was implemented. The pattern is identical to what happens when you never refactor a codebase: you keep adding patches, each patch accommodating the mess the previous patch created, until the system is so layered with workarounds that nobody can tell you what the original architecture was supposed to do.

---

The Two Cities

Before Koenigsberger arrived, Bhubaneswar already existed. It had existed for over two thousand years. The new capital was not built on empty land — it was built beside one of the densest sacred landscapes in India.

Ekamra Kshetra. The Field of the Mango Tree. The name comes from the Ekamra Purana, a thirteenth-century Sanskrit text: the presiding deity Lingaraj was first worshipped under a mango tree. The area around Bindusagar Tank and Lingaraj Temple constituted the old town — a dense, organic settlement of temples, tanks, pilgrimage infrastructure, and residential lanes that had evolved over a millennium according to its own logic.

The numbers are staggering. Bhubaneswar once had an estimated 700-plus temples within a small radius, earning it the epithet “Temple City.” The surviving temples constitute, in the words of one architectural historian, “virtually a complete record of Kalinga architecture almost from its nascence to its culmination.” Parashurameshwar (7th century) through Mukteshwar (10th century, called the “Gem of Odia architecture”) through Rajarani (11th century, red-gold sandstone, exceptional sculpture) to Lingaraj (1014 CE, 128 feet tall, the largest and most important, still in active worship). And Ananta Vasudeva, the lone Vaishnava temple in a Shaiva cluster, dating to the 13th century.

Ekamra Kshetra has been on the UNESCO World Heritage Tentative List since 2014.

The old town has a medieval street pattern — narrow lanes, irregular plots, organic growth shaped by temple geography, tank placement, and pilgrimage routes. It is the kind of urban fabric that emerges from a thousand years of daily decisions by residents, priests, merchants, and pilgrims. No planner designed it. It designed itself. And it works, within its own logic: the density supports the pilgrimage economy, the narrow lanes provide shade in the brutal Odisha summer, the tanks manage water, the temples anchor community.

Koenigsberger’s new capital was placed to the north and west of this old town. Two cities, side by side, following completely different rules.

Old Town: dense, organic, medieval, sacred, pedestrian by default because no car can navigate its lanes. Economy driven by temples, pilgrimage, ritual services. Governance through temple trusts and traditional structures alongside modern municipal administration. Time measured in festival cycles: Shivaratri, Ashokastami, the thirteen-day Chandana Yatra.

New Town: grid-like, planned, modernist, administrative, designed for walking but eventually overrun by cars. Economy driven by government salaries. Governance through municipal corporation and development authority. Time measured in budget cycles, assembly sessions, transfer seasons.

Religious foot traffic flows southeast, toward Lingaraj and Bindusagar. Government traffic flows northwest, toward the Secretariat and Raj Bhavan. Commercial growth concentrated at the junction of these two flows — Saheed Nagar, Janpath, the market areas between old and new town. The money accumulated where the two gravitational fields overlapped.

This dual structure is not unique to Bhubaneswar. It is, in fact, a replication of the colonial civil lines pattern: the administrative settlement placed apart from the existing town. The British did this everywhere — a civil station with its bungalows, clubs, and parade grounds; the “native town” with its bazaars, temples, and dense residential quarters. The two coexisted but were not integrated. The civil station drew labour and services from the native town. The native town drew income from the civil station. But they operated according to different logics, different aesthetics, different social hierarchies.

Koenigsberger, who had fled fascism and explicitly rejected social hierarchy in architecture, ended up recreating a colonial spatial pattern. Not through malice or blindness, but through the structural logic of the commission itself: build an administrative city near an existing settlement. The result is always a dual city. The administrative settlement imports an external logic — whether colonial or modernist — and places it beside the indigenous logic of the existing town. The interface between the two is never designed. It emerges, awkwardly, as the two systems rub against each other.

This is the MVP insight. Koenigsberger built a functional prototype for the new town. He did not design the interface between old and new. The connection point — the zone where temple-era Bhubaneswar meets mid-century-modern Bhubaneswar — was left to emerge on its own. And what emerged was commercial chaos: the market areas, the traffic snarls, the mixed-use zones where heritage buildings sit next to concrete apartment blocks, where a 10th-century temple shares a wall with a twentieth-century shop.

In software, the interface between two systems is where most bugs live. When you connect a legacy database to a modern API, the bugs are not in either system — they are in the translation layer between them. Bhubaneswar’s old-new interface is where the city’s worst urban problems concentrate: congestion, encroachment on heritage structures, flooding (because modern drainage was never integrated with the old town’s tank-based water management), and a perpetual conflict between development pressure and heritage conservation.

The 2020s have seen increased heritage awareness. Ekamra Heritage Walks were launched. Heritage circuits were proposed. But the fundamental design problem has not been solved: two urban systems operating by different rules, connected by an interface that was never deliberately designed.

---

Government as City-Maker

Every city has a DNA — a founding logic that shapes everything that follows, long after the original conditions have changed. San Francisco’s DNA is the Gold Rush: speculative, risk-seeking, boom-and-bust. Detroit’s DNA is the assembly line: industrial, hierarchical, dependent on a single sector. Bhubaneswar’s DNA is the civil lines: governmental, hierarchical by pay grade, dependent on the state.

This is not a metaphor. The physical city is literally organized by government employment rank.

The housing system that Koenigsberger designed was implemented through government housing colonies, arranged by Type classification. Type I quarters for the lowest-ranked employees — peons, drivers, Group D staff. Small rooms, shared facilities, dense clusters. Type II for clerks and junior assistants. Type III for section officers and middle management. Type IV for senior officers. Type V for department heads and directors. Type VI for secretaries and the highest-ranked officials — individual bungalows with large compounds, often on the best land in the city.

The Type system is not just housing. It is spatial hierarchy. Walk through old Bhubaneswar — the planned units — and you can read the social structure of the government in the built environment. The proximity to Unit V (the Secretariat) correlates with Type rank: the most senior officers live closest to the administrative heart. The most junior live farthest away. The city is a physical org chart.

Koenigsberger explicitly rejected hierarchy in his design philosophy. He wanted an egalitarian city. But the client — the state government — had its own logic: a bureaucratic hierarchy with clear ranks, each rank entitled to a specific grade of housing, each grade physically separated from the others. The architect’s intention was overridden by the institution the architecture was built to serve. This is one of the ironies flagged in the research notes: a planner who deliberately avoided temple architecture to prevent replicating social hierarchy ended up creating a city where government quarter types became the primary social hierarchy marker.

The irony deepens. In the old town — the temple city Koenigsberger wanted to move beyond — social hierarchy was embedded in caste, which was embedded in temple service roles. In the new town, social hierarchy was embedded in pay grade, which was embedded in government quarter types. The vocabulary changed. The structure did not.

When the government is the city, certain things follow necessarily.

First, the city grows only when government grows. Between 1948 and 1991, Bhubaneswar’s population growth tracked government expansion almost perfectly. New departments created new employees who needed new colonies. The population curve was not driven by commercial opportunity or industrial growth — it was driven by administrative decisions made in the same Secretariat that Koenigsberger designed. The city was its own growth engine, in a circular way: government decided to expand, expansion required more employees, employees required more housing, housing required more land, land development required more government.

Second, the city’s rhythm is the government’s rhythm. Office hours — 10 AM to 5 PM — determined when the streets were busy and when they were quiet. Government holidays emptied the city. Transfer season (typically April-June) created a predictable cycle of arrivals and departures, rental market churn, school admission anxiety. Pay cycles — the first of every month — drove retail activity. The city’s economy pulsed with the government’s heartbeat.

Third, risk aversion becomes the default culture. Government employment is, by design, stable. Salaries are predictable. Pensions are guaranteed (or were, until the New Pension Scheme changed the calculus for post-2004 recruits). Career advancement follows a known trajectory: years of service, exams, seniority. In a city where the dominant employer operates on these terms, the culture calibrates accordingly. Savings go to children’s education and marriage. Investment goes into real estate (government employees were among the first to buy plots in the expanding city). Entrepreneurship is rare — not because Odias lack entrepreneurial instinct, but because the city’s incentive structure does not reward it.

The population numbers tell the story:

• 1951: 16,512. Barely a town. The government had just moved in.
• 1961: approximately 40,000. The plan’s designed capacity. Government departments were established, initial employees were settled.
• 1971: 113,000. A 183% decadal growth rate. Government expansion plus the first wave of service-economy migration.
• 1991: 411,542. The city had grown tenfold from 1951 in forty years — almost entirely on government momentum.
• 2001: 658,220. The IT sector was beginning to arrive. For the first time, a non-government employer was pulling people to the city.
• 2011: 885,363. Growth slowing in percentage terms (34.5% decadal) but still enormous in absolute numbers.

Compare the growth drivers of the three planned capitals:

Chandigarh: administrative capital, yes, but sitting at the boundary of Punjab and Haryana — two of India’s most commercially active states. Industrial hinterland. Agricultural surplus. Military presence (Chandimandir cantonment). The city diversified its economic base relatively early.

Gandhinagar: administrative capital of Gujarat, but placed deliberately next to Ahmedabad — India’s seventh-largest city, a textile and pharmaceutical hub, one of the most commercially dynamic cities in the country. Gandhinagar could afford to be purely administrative because Ahmedabad absorbed the commercial energy.

Bhubaneswar: administrative capital of one of India’s poorest states, placed next to Cuttack — a city that was itself in relative decline, a commercial centre without a commercial hinterland, a lawyer’s town that had lost its administrative function. The 32.5x population growth happened not because commercial dynamism attracted migrants. It happened because government employment attracted people the plan had not anticipated — and those people brought their families, who brought service workers, who brought more migrants, who built slums the plan had never imagined.

The government-as-city-maker pattern has a specific failure mode. When the anchor tenant IS the city, the city cannot diversify without the anchor tenant’s permission. Every new economic activity — IT parks, shopping malls, private hospitals, universities — requires government land allocation, government approvals, government infrastructure. The government is simultaneously the regulator, the landlord, the largest employer, and the primary customer. In market terms, this is a monopsony: a market with a single buyer. In software terms, this is vendor lock-in at the platform level. The city cannot switch providers because the provider is the platform.

---

The IT Aspiration

In 1989, the Software Technology Parks of India established a centre in Bhubaneswar — one of the first three STPI centres in India, alongside Pune and Bangalore. This early start should have been an advantage. In technology markets, first-mover advantage is often decisive: the first platform to attract developers attracts more developers, which attracts more users, which attracts more developers. Network effects compound. The early bird gets the ecosystem.

Bhubaneswar got the early start and did not get the ecosystem.

By 2001, the state had built Infocity in the Chandrasekharpur area — a dedicated IT/ITeS special economic zone. Infovalley followed near the airport, eventually housing Infosys’s major campus. Technocity added another zone. The physical infrastructure was built. TCS came. Infosys came. Wipro, Tech Mahindra, Mindtree, Capgemini, Accenture, Cognizant, IBM — the full roster of India’s IT services industry established offices. Approximately 300 small and mid-size IT companies set up operations. By FY 2024-25, STPI-Bhubaneswar reported Rs 3,840 crore (approximately $460 million) in IT/ITeS exports, up from Rs 2,589 crore in FY 2020-21 — a 48% increase in four years.

These are not trivial numbers. Thirty to forty thousand people work in Bhubaneswar’s IT sector. The city has a functioning tech industry with real companies doing real work.

But context destroys the narrative. Bangalore’s IT exports are in the range of $53 billion annually (FY22 data). Bhubaneswar’s $460 million is less than 1% of that. Hyderabad’s IT/ITeS sector generates approximately Rs 71,574 crore. Pune exceeds $20 billion. Even adjusting for city size and maturity, Bhubaneswar is not in the same category. It is not even in the same conversation.

The structural constraints are specific and identifiable:

The talent drain. Bhubaneswar produces IT talent at scale. KIIT enrolls 30,000 students. SOA has 15,000. IIT Bhubaneswar, though smaller, adds another stream. NIT Rourkela, 350 kilometres away, is historically the premier engineering institution in Odisha. The pipeline is strong. But the pipeline flows outward. An estimated six lakh Odias work in Bangalore’s IT sector alone. NIT Rourkela’s 2024-25 placement data shows 1,274 job offers, with the highest package at Rs 62.44 lakh per annum — virtually all placed outside Odisha. About 30% of non-metro graduates relocate to Tier 1 cities. The educational institutions are excellent at producing human capital and terrible at retaining it.

The ecosystem gap. Individual companies can be attracted with incentives — tax breaks, cheap land, subsidized office space. An ecosystem cannot be. An ecosystem requires density: not just companies, but the support infrastructure around them. Venture capital. Management consultants. Specialized legal services. Headhunters. Co-working spaces where people from different companies mix ideas. Restaurants and bars where deals happen informally. A visible career ladder that does not require leaving town. Bhubaneswar has the companies. It does not have the ecosystem. Most firms’ Bhubaneswar operations are secondary or tertiary centres supporting headquarters in Bangalore or Hyderabad. Decision-making authority, premium projects, and senior talent concentrate elsewhere.

The lifestyle gap. This sounds superficial. It is not. Mobile knowledge workers — the people a city needs to attract and retain to build a tech ecosystem — choose cities based on a bundle of factors: salary, career growth, quality of life, cultural amenity, peer community, airline connectivity. Bhubaneswar’s international flight connectivity was essentially nonexistent until 2023, when IndiGo launched routes to Bangkok, Dubai, and Singapore. The city’s entertainment, dining, and nightlife options are thin by any metro-city standard. The “nothing to do in Bhubaneswar” perception, while partially unfair, is partially accurate — not in absolute terms (the city has temples, heritage, sports events, nature) but in the specific terms that matter to a 28-year-old software engineer comparing offers from Bangalore and Bhubaneswar.

The late ecosystem effect. Bangalore had Texas Instruments in 1985. Infosys relocated there in 1983. By the time Bhubaneswar’s IT parks were functional in the early 2000s, the agglomeration effects in Bangalore, Hyderabad, and Pune were already self-reinforcing. Network effects in technology markets create winner-take-most dynamics. Once a critical mass of companies, talent, and capital concentrates in one place, it becomes extremely difficult for a competing location to attract the same elements — because each element wants to be where the other elements already are. Bhubaneswar was not late by decades. It was late by the critical five-to-seven years during which ecosystem formation happens. By the time the infrastructure was ready, the network effects had locked in elsewhere.

The state’s IT Policy 2022 attempts to address these constraints with incentives: 100% SGST reimbursement for five to seven years, recruitment assistance of Rs 10,000 per Odisha-domicile employee, additional incentives for women, SC/ST, and disabled employees. The Odisha Startup Growth Fund provides Rs 100 crore through SIDBI. O-Hub offers 1.5 lakh square feet of incubation space.

These are reasonable policy interventions. They are also, in the MVP metaphor, feature additions to a platform that has not been upgraded. The IT sector is a feature. The platform is the city — its transport, its housing stock, its cultural infrastructure, its quality of life, its career ecosystem. You can add features to a platform, but if the platform cannot support them, the features underperform. Bhubaneswar bolted an IT feature onto a government-town platform. The feature works. It works at about 1% of what it works in cities where the platform was designed for it.

[Confidence note: The 1% comparison is based on STPI Bhubaneswar’s Rs 3,840 crore vs. Bangalore’s approximately $53 billion in IT exports. These figures come from different reporting frameworks and time periods and are not precisely comparable. The order-of-magnitude difference, however, is robust.]

---

Smart City, Mo Bus, and the Partial Upgrade

In 2016, Bhubaneswar was ranked first nationally in the Smart Cities Mission challenge — the highest-scoring proposal among all Indian cities that competed. This was a genuine achievement. The proposal was well-crafted, with clear metrics and innovative ideas. It carried civic pride and raised expectations.

Total Smart City plan budget: Rs 4,537 crore. Central fund: Rs 950 crore. Projected PPP investment: Rs 2,563 crore. Nearly 90% of the funding targeted Area Based Development in the Bhubaneswar Town Centre District (BTCD), covering 985 acres — roughly 4 square kilometres. Janpath was transformed into a pedestrian-friendly corridor: 5.5 kilometres of broad pavements, bus bays, pedestrian crossings, cycle lanes, sitting areas, vending zones under the Mukta Project. Smart traffic signals went up at key junctions. Smart parking systems were installed. Project Kutumb created one-stop provision for homeless and migrant support. Project Swabhimaan incubated micro-businesses for slum dwellers.

These are not nothing. Walk down Janpath today and the difference from a decade ago is visible. The pavements exist. The bus bays function. The vending zones are organized rather than chaotic.

But 985 acres in a city of 135 square kilometres (soon to be 705 square kilometres under the CDP 2040) is 0.7% of the city’s area. The “smart” improvements concentrated in a narrow corridor. The remaining 67 wards (now 81 after expansion) — the wards where most people actually live, including the wards with the highest slum populations — were largely untouched. Critics called it a “smart part-city,” and the criticism was fair.

The monsoon exposed the reality behind the smart label. Knee-deep waterlogging flooded areas that had never flooded before. The city’s original drainage system relied on ten natural channels carrying rainwater from the Chandaka forest highlands to the rivers. Most of those channels had been encroached by construction. The stormwater drainage that remained was designed for 12-20 millimetres per hour of rainfall intensity. Actual rainfall events regularly exceeded 50 millimetres per day — eleven times in 2018-19 alone — with six events exceeding 100 millimetres. Seventy-five locations were identified as flood-vulnerable. No smart traffic signal or adaptive parking system addresses waterlogging. The platform was failing under load.

The Smart City Mission was excluded from the India Smart Cities Award in 2018 — despite having been ranked first in proposal quality. Officials explained that only cities “delivering results” were eligible. The gap between the proposal and the implementation tells its own story.

Then there is Mo Bus. And Mo Bus is a different story entirely.

Launched November 6, 2018, operated by CRUT (Capital Region Urban Transport), Mo Bus is arguably the most significant public infrastructure achievement in Bhubaneswar’s post-Koenigsberger history. The numbers: 560-plus buses including 180 electric. Eighteen-plus routes covering Bhubaneswar, Cuttack, Puri, and expanding to Rourkela, Sambalpur, and Berhampur. Peak daily ridership of 316,353 in January 2023. Average daily ridership of approximately 300,000. Ridership growth of 200% in four and a half years. Fifty-seven percent of riders shifted from private vehicles — a modal shift figure that most Indian cities would envy.

Before Mo Bus, bus mode share in Bhubaneswar was 8%. Auto-rickshaws handled 17%. Two-wheelers and cars accounted for 62%. The city had essentially no functional public transit. It was built for walking but had outgrown walking distance. The gap between what the Koenigsberger plan assumed (pedestrian city) and what the city had become (two-wheeler city) was filled by Mo Bus.

The buses have WiFi, CCTV, online ticketing, advanced driver-assistance systems, and a smartphone app with live tracking. Mo E-Ride adds 50 e-rickshaws for last-mile connectivity, deliberately hiring women, transgender, and HIV-positive operators. Airport express routes connect BBI to Cuttack and Puri. Mo Bus won the Gupta Urban Award in 2024. It is a genuinely world-class public transport system for a city of this size.

And here is the pattern that matters: Mo Bus works because it was designed and operated as a dedicated institution. CRUT is a Special Purpose Vehicle with focused leadership, clear metrics, and operational autonomy. It is the same institutional pattern as OSDMA — the Odisha State Disaster Management Authority that transformed cyclone response from 10,000 deaths in 1999 to 64 deaths in Fani in 2019. Concentrated institutional excellence. A single problem, a single team, with authority and accountability.

But Bhubaneswar’s drainage does not have a CRUT. Its slum rehabilitation does not have a CRUT. Its heritage conservation does not have a CRUT. Each of these domains is managed through the general municipal apparatus — BMC, BDA, state departments — where responsibility is diffused, accountability is unclear, and coordination between agencies is, in the words of one analyst, nonexistent: “the BMC often doesn’t know what the BDA does and vice versa.”

The Smart City Mission illustrates the same pattern at a different scale. Rs 4,537 crore spent on specific, bounded projects. Janpath improved. Traffic signals modernized. Specific wards upgraded. But no systemic redesign. No integration of drainage with land use. No comprehensive sewerage upgrade. No metropolitan authority to coordinate Bhubaneswar and Cuttack. Each project is a standalone intervention, not a platform iteration.

In software terms, this is patching, not refactoring. A patch fixes a specific bug without changing the underlying architecture. Patching is necessary. But when the architecture itself is the problem — when the system is running at 32x its designed load, when the original assumptions about mobility, density, drainage, and governance no longer hold — patches cannot solve the structural issue. They can make specific intersections work better. They cannot make the city work.

The Capital Region Ring Road — 111 kilometres, six lanes, Rs 8,308 crore, access-controlled greenfield highway from Rameshwar to Tangi — is the largest current infrastructure project. The proposed metro rail — 26 kilometres, Rs 6,300 crore, Airport to Trisulia — would be the first mass rapid transit connecting Bhubaneswar and Cuttack. But the metro tenders were scrapped due to viability concerns. The cost comparison is stark: surface railway at approximately Rs 30 crore per kilometre versus elevated metro at approximately Rs 300 crore per kilometre. For a city of Bhubaneswar’s size and income levels, the metro may be the wrong solution — a feature designed for a different platform.

The Centre is reportedly considering Namo Bharat Rapid Rail as an alternative. The debate continues. Meanwhile, vehicle registrations increased from 25,543 in 2000-01 to 110,370 in 2019-20. Over two million vehicles added in a decade, 85% growth. Approximately 80% are two-wheelers. The roads designed for walking — Koenigsberger’s seven-type hierarchy where footpaths came first — carry motorcycles and scooters for which no road type was ever specified.

---

The Slum and the Skyline

Here is a number that should be placed next to the Smart City ranking: between 34% and 47% of Bhubaneswar’s population lives in slums.

The range reflects methodological disagreement — different surveys define “slum” differently, and the Census 2011 basis suggests the higher end. But even the lower estimate means that more than one in three residents of India’s first-ranked Smart City applicant lives in informal housing with uncertain land tenure, inadequate water, and no sewerage.

Bhubaneswar had zero slums until the 1960s. The first informal settlements appeared as construction workers and service-economy migrants arrived to build the new capital. The city needed them — it could not construct itself. But the plan had not anticipated them. Koenigsberger designed for government employees. The people who built the houses for government employees had no place in the design.

This is a pattern common to every planned city in the developing world. Brasilia, Le Corbusier’s Chandigarh, Islamabad, Abuja — all developed significant informal settlements within decades of construction. The plan accounts for the people the plan is designed for. The people who service those people — the cooks, cleaners, construction workers, drivers, vendors — are invisible in the design. They become visible in the slum.

By 2011 estimates, Bhubaneswar had approximately 436 slum clusters across 67 wards. Of these, 99 were “authorized” (13,420 households, 70,660 people) and 278 were “unauthorized” (46,706 households, 237,947 people). Total slum population: approximately 308,000 on a 2011 census basis. Given population growth since then, the current number is certainly higher.

The largest slum, Salia Sahi, has existed since the late 1970s. It is older than most of the “planned” additions to the city. It has its own internal economy, its own social structure, its own politics. It is not a temporary aberration. It is a permanent feature of the city — the shadow city that the planned city created by not planning for it.

Real estate prices tell the other half of the story. Average apartment prices in Bhubaneswar: Rs 7,000-7,500 per square foot. Saheed Nagar: Rs 7,000-9,000-plus. Chandrasekharpur: Rs 6,000-8,000. For a 1,000-square-foot apartment in a decent area, you are looking at Rs 60-90 lakh — $70,000 to $110,000. For a government peon on Type I quarters earning Rs 20,000-25,000 per month, formal housing is mathematically impossible. For a construction worker earning Rs 400-500 per day, it is absurd.

The highest price appreciation over three years (as of 2025): Ghangapatna at 123.8%, Mancheswar at 108.3%, Nakhara at 105%. Real estate is a speculative asset class in Bhubaneswar, as in every Indian city. Prices are rising faster than incomes, pushing the formal housing market further from reach for the bottom 40%.

In November 2025, 550-plus houses were demolished in one of the largest slum clearance drives in the city’s history — reportedly for the Jayadev Vihar-Nandankanan Road project. Rehabilitation required down payments that many displaced families could not afford. The bulldozer approach: destroy the existing solution (however imperfect) without providing a viable alternative at the price point the affected population can actually access.

Against this backdrop, JAGA Mission stands out.

JAGA (Jaga Abhiyaan, or Mission on Land) is one of the most innovative responses to urban informality in India. The core idea: give land rights first, then build housing. Not the other way around. In conventional slum rehabilitation — Mumbai’s SRA model, Delhi’s various schemes — the government builds housing (or partners with developers to build housing) and then relocates slum residents. The problem is that relocation breaks social networks, separates people from their livelihoods, and often moves them to distant locations with no transport links to their workplaces. Compliance rates are low. Resettlement colonies become slums themselves.

JAGA inverts the sequence. Under the mission, 2,919 slums across 114 Odisha cities (not just Bhubaneswar) were mapped using drone surveys. 175,000 families were given land rights certificates. The land they were already occupying was titled to them. Security of tenure — the base layer — was established first. Housing, services, and infrastructure are built on top of that secure base.

The programme won the World Habitat Award in 2019 and again in 2023. It is internationally recognized as a model.

In design pattern terms, JAGA gets the layer architecture right. In any layered system — software, infrastructure, social services — you build the base layer first and make it stable before adding features on top. The base layer for urban residents is land tenure. Without secure tenure, no family invests in improving their house (why improve what can be demolished?), no bank provides a loan (no collateral), no government provides permanent infrastructure (to an “unauthorized” settlement). By securing the base layer, JAGA enables every subsequent layer — housing improvement, water connection, sewerage, school enrollment, bank accounts — to function.

Compare with Delhi’s bulldozer approach: destroy the visible structure without addressing the base layer (where will these people go?). Compare with Mumbai’s SRA: build new structures in a different location without preserving the social and economic base layer (proximity to livelihoods, community networks). JAGA is the correct design pattern.

But the scale of the problem dwarfs the solution. 175,000 families across 114 cities is significant. 436 slum clusters in Bhubaneswar alone — with population growing faster than the programme can process — means that the backlog grows even as the programme advances. The structural dynamic that produces slums — a city that attracts workers it cannot formally house — has not changed. JAGA treats the symptoms with unusual intelligence. It does not cure the disease.

[Confidence note: The claim that JAGA represents the “correct” design pattern relative to Delhi’s or Mumbai’s approach is an analytical judgment, not an empirical fact. Reasonable people disagree. What is empirically established is that JAGA’s completion rates and resident satisfaction scores are higher than most relocation-based programmes. Whether this translates to long-term outcomes comparable to market-based housing solutions remains to be seen — the programme is less than a decade old.]

---

Education Hub as Identity

There is one domain where Bhubaneswar punches above its weight, and it is the domain that matters most for the long term.

The institutional cluster: KIIT (30,000 students, 200 acres across 12 campuses, NAAC A grade). SOA (15,000 students, NIRF rank 15 among universities). IIT Bhubaneswar (permanent campus still developing at Argul, 25 kilometres south of the city centre). AIIMS Bhubaneswar (premier public healthcare and medical education). NISER (National Institute of Science Education and Research, under the Department of Atomic Energy, pure sciences). XIM University (top-10 MBA nationally). Utkal University (the oldest in Odisha, 1943, 381 affiliated colleges, 400-acre campus at Vani Vihar). And NIT Rourkela, 350 kilometres away but functionally part of the same ecosystem — its graduates feed Bhubaneswar’s professional class and IT sector (or, more accurately, feed Bangalore’s).

Total estimated student population in the Bhubaneswar metro area: 100,000 to 150,000-plus. In a city of 1.3 million, students constitute roughly 8-12% of the population. That is a distinctive urban identity. Few Indian cities outside explicitly university-town contexts (Manipal, Pilani, Kharagpur) have a higher student-to-resident ratio in their core metro area.

The education cluster is reshaping the city’s geography. KIIT’s 12 campuses in the northern city have created a micro-city: 17 girls’ hostels, 22 boys’ hostels, 12,000-plus capacity, plus the commercial zones and service economy that 30,000 students generate. IIT Bhubaneswar at Argul is pulling development southward, creating a new growth corridor. NISER at Jatni anchors the southern expansion. Utkal University at Vani Vihar, in the city’s heart, provides a large green lung and generates student-oriented commercial activity radiating outward. During academic year, the student population creates a distinct sub-economy: hostels, paying-guest accommodations, food stalls, photocopying shops, coaching centres, low-cost transport corridors from each campus.

The concentration of world-class institutions within a 50-kilometre radius is genuinely unusual for an Indian city of this size. IIT, AIIMS, NISER, KIIT, SOA, XIM, Utkal — this is a stronger institutional base than most state capitals can claim. Government narratives frame the region as a future “knowledge hub” comparable to Boston or the San Francisco Bay Area.

The comparison exposes the gap.

Boston’s knowledge economy works because MIT and Harvard do not exist in isolation. They exist within an ecosystem of venture capital, technology transfer offices, startup accelerators, industry research partnerships, and a dense network of alumni who stay in the region because the career opportunities match the educational quality. Stanford generated Silicon Valley not because it produced great engineers — many universities do that — but because it actively commercialized research, encouraged faculty entrepreneurship, and was located in a region that already had defence-industry R&D (Lockheed, Fairchild, HP) creating demand for technical talent.

Bhubaneswar has the institutions. It does not have the ecosystem around them. IIT Bhubaneswar and NISER produce internationally competitive research, but there is no surrounding infrastructure of technology transfer, university-industry collaboration, or research-to-startup pipeline. KIIT and SOA produce large numbers of graduates, but most enter the service economy of IT firms in other cities. The knowledge produced in Bhubaneswar’s institutions does not primarily generate economic value in Bhubaneswar.

The talent export data is the sharpest evidence. NIT Rourkela’s 2024-25 placement record: 1,274 job offers. Highest package: Rs 62.44 lakh per annum. Virtually all placed outside Odisha. The pattern repeats across institutions. IIT Bhubaneswar graduates go to Bangalore, Hyderabad, Pune, Delhi. KIIT and SOA graduates follow the same routes. AIIMS-trained doctors take super-specialty positions in metro hospitals. XIM MBA graduates join firms headquartered in Mumbai and Gurgaon.

The city is an incubator that ships its output to competing platforms. In the language of venture capital, Bhubaneswar is the research lab, and Bangalore is the company that commercializes the research. The lab does the hard, expensive work of education and training. The returns accrue elsewhere.

This is the education hub paradox: the very quality that could anchor Bhubaneswar’s transformation — its concentration of institutions and young talent — is also the quality that most efficiently drains that talent away. The better the education, the more marketable the graduate, and the more likely they are to leave for a city with a stronger career ecosystem. The education investment is real. The retention return on that investment is close to zero for the highest-performing graduates.

Ninety percent or more of high-achieving graduates leave. The figure is not precisely measurable — no institution publishes “stayed in Odisha” as a placement metric — but placement data, alumni surveys, and anecdotal evidence all point in the same direction. The city educates the talent that other cities employ.

What would change this? Not more institutions — Bhubaneswar has enough. Not more incentives for companies — the IT Policy 2022 already offers those. What would change it is the ecosystem that makes staying a viable career choice: the density of employers, the visible career ladder, the cultural amenity, the peer community of ambitious people who chose to stay. Building an ecosystem is harder than building an IT park. It requires a critical mass of decisions — by individuals, by companies, by investors — that tip the balance from “leaving is the default” to “staying is a viable option.” That tipping point has not been reached.

---

The MVP That Was Never Iterated

Otto Koenigsberger left Bhubaneswar soon after completing the initial plan. He moved to New Delhi to join the Union Health Ministry, and later founded the Development Planning Unit at University College London, where he spent the rest of his career training planners for developing countries. His involvement in Bhubaneswar tapered off. Implementation was left to state engineers.

This biographical detail matters more than it appears to. In software development, the worst thing that can happen to a product after launch is for the original architect to leave. The architect carries context that no document captures — the reasoning behind trade-offs, the assumptions behind constraints, the vision for what version 2.0 should look like. When the architect leaves, the team that inherits the codebase can maintain it but cannot evolve it with the same coherence. Subsequent additions are technically functional but architecturally inconsistent. The vision degrades into maintenance.

That is what happened to Bhubaneswar. The first six units — Koenigsberger’s original design — remain the city’s most coherent zone. Units VII through IX, designed by the Public Works Department rather than following Koenigsberger’s principles, were built at larger footprints with different assumptions. The neighbourhood-unit concept was diluted. The seven-type road hierarchy was simplified. The climate-responsive design was abandoned in favour of standard reinforced-concrete construction. Each subsequent extension was functional — people could live in it — but architecturally disconnected from the original vision.

By the 1994 master plan revision, the neighbourhood concept was explicitly abandoned in favour of zone-based planning. This was not an upgrade. It was a surrender. The neighbourhood unit was Koenigsberger’s fundamental insight — the idea that a city should be organized around human-scaled communities, not administrative zones. Abandoning it meant abandoning the most distinctive feature of the original design. What replaced it was generic: zoning, floor-area ratios, land-use regulations. Important, but not architecture. Management, not design.

The plan was never published for public participation, as Koenigsberger had insisted it should be. It circulated among government officials. The citizens of Bhubaneswar — the users of the system — were never invited to contribute to its design. In participatory design methodology, this is the cardinal sin: building for users without building with them. The result is a system that meets the designer’s assumptions about user needs rather than the users’ actual needs. Koenigsberger assumed walking. The users wanted scooters. Koenigsberger assumed 40,000 people. Forty times that many showed up. The gap between assumption and reality grew wider with every decade, and no feedback mechanism existed to close it.

Here is the synthesis, and it is the claim this chapter rests on.

Koenigsberger’s 1948 plan was a genuine MVP: functional, well-designed for its constraints, appropriate for the initial load, thoughtful about climate, respectful of scale. In many ways it was a better MVP than Chandigarh — more human-scaled, less monument-driven, better adapted to tropical conditions. As a first version of a city, it was excellent.

But MVP methodology has a second part that matters more than the first. The first part is building the minimum viable product. The second part is iterating. Measure how users actually behave. Identify where the assumptions were wrong. Redesign the system for the reality you observe, not the reality you imagined. Ship version 2.0. Then 3.0. Then 4.0. Each version incorporates what you learned from the previous one. The product improves because the feedback loop is built into the process.

Bhubaneswar never iterated. The 1948 plan was never replaced by a comprehensive 2.0 redesign that accounted for the actual trajectory of growth. Instead: ad hoc extensions when government needed more housing. Unplanned growth when migrants arrived whom the plan did not anticipate. Government colonies added wherever land was available. IT parks bolted on at the periphery. Smart City patches applied to a narrow corridor. Ring roads drawn around a sprawl that had already happened. Metro proposals for a city that may not generate the ridership to justify the cost.

The city is running version 1.0 under a 32x load. Every version-1.0 feature — the neighbourhood school within walking distance, the seven-type road hierarchy, the green corridors between units, the separation of pedestrian and vehicular traffic — has either degraded or collapsed entirely.

In software, running a system at 32x its designed load produces a predictable set of pathologies:

Degraded performance. The system still works, but slowly, unreliably, with frequent failures. In Bhubaneswar: traffic congestion at every major junction, peak-hour gridlock from Jayadev Vihar to Nandankanan, from Khandagiri to Tomando, from Pahala to Rasulgarh. Roads designed for feet and bicycles carrying two million vehicles, 80% of them two-wheelers. Average commute times that would have been unimaginable in Koenigsberger’s walkable units.

Security vulnerabilities. The system exposes data and resources it was never designed to protect. In Bhubaneswar: 34-47% slum population with no secure land tenure, no sewerage, no formal water supply. The “unauthorized” settlements are not bugs — they are the system’s way of handling users it was never designed for. The vulnerability is structural: the plan did not allocate resources for these users, so they access resources informally, insecurely, and at constant risk of demolition.

Feature requests that cannot be fulfilled. Users demand capabilities the architecture cannot support. In Bhubaneswar: public transit (partially fulfilled by Mo Bus, but the metro remains stalled), comprehensive sewerage (only 17 of 47 wards fully covered by piped water — the rest rely on borewells), air quality management (PM2.5 at 47.4 annually, winter readings at 111-176), coordinated metropolitan governance (Bhubaneswar and Cuttack still governed as separate entities despite sharing a congested corridor and a 2-million-person combined population).

Users migrating to competing platforms. The most capable users leave for systems that offer better performance. In Bhubaneswar: the 90%-plus of high-achieving graduates who leave for Bangalore, Hyderabad, Pune. The six lakh Odias in Bangalore’s IT sector. The brain drain that the education hub produces with industrial efficiency. The city’s best output — its educated, ambitious young people — votes with its feet, and the vote is against Bhubaneswar.

The question this analysis raises is not “was Koenigsberger’s plan good?” It was. The question is: why was it never iterated?

Part of the answer is institutional. No institution was charged with iterating the plan. The BDA manages land use and approvals but does not redesign the city. The BMC manages services but does not plan for the future. The state government makes project-level decisions — an IT park here, a ring road there — but does not think in terms of urban system architecture. No one owns the whole. [This is arguably below 70% confidence as a complete explanation — institutional structure is a necessary but possibly not sufficient cause. Political incentives, fiscal constraints, and the sheer difficulty of redesigning a city while it is in use all contribute.]

Part of the answer is political. Redesigning a city means reallocating land — and land in an Indian state capital is the primary store of political value. Every rezoning decision, every master plan revision, every road-widening project redistributes wealth. The government that controls the capital is also the government that benefits from the status quo of land allocation. Iteration would require challenging the interests of the people who authorize the iteration. The conflict of interest is built into the governance structure.

Part of the answer is cognitive. People who live in a city rarely see the system. They see their commute, their neighbourhood, their traffic jam. The conceptual leap from “this intersection is badly designed” to “the entire urban system is running on an architecture designed for one-thirtieth of the current population” is large. It requires thinking in systems, not incidents. And systems thinking about cities is rare — among citizens, among politicians, and among the bureaucrats who manage urban governance.

But the largest part of the answer may be simpler. India does not iterate cities. Chandigarh has not been redesigned. Gandhinagar has not been redesigned. No Indian city — planned or unplanned — has undergone a comprehensive system-level redesign that accounts for actual growth trajectories rather than projected ones. The Master Plan tradition in India is a one-shot exercise: design, implement (partially), watch it get overwhelmed, draw a new plan that accommodates the sprawl that has already happened, repeat. The feedback loop is not iterative. It is reactive. The plan follows the city instead of leading it.

Koenigsberger understood this risk. He insisted on public participation. He wanted the plan to be a living document, revised with citizen input. That never happened. The plan became a historical artifact — cited in architecture journals, studied by urban planners, genuinely admired by anyone who compares it to what came after. And entirely irrelevant to the city that actually exists.

Bhubaneswar in 2026 is three cities overlaid on the same geography. The temple city — Ekamra Kshetra, 2,000 years of sacred landscape, Lingaraj rising 128 feet over the old town, narrow lanes, pilgrimage economy. The planned city — Koenigsberger’s six units, government colonies, Secretariat, Type I through Type VI quarters, the ghost of an egalitarian modernist vision. And the unplanned city — IT parks at the periphery, apartment blocks replacing plotted housing, slums in every gap the plan left empty, two million vehicles on roads designed for pedestrians, Mo Bus trying to stitch together what was never designed to be stitched.

The question for the next chapter is: if Bhubaneswar is the MVP that was never iterated, what happened to the city it was supposed to replace? Cuttack — the older, denser, commercially-oriented twin — did not disappear when the capital moved. It adapted. And the story of how two cities that should function as one metro region instead compete, overlap, and fail to coordinate tells you something specific about why Odisha’s urbanization has produced scale without system.

---

Sources

Koenigsberger Plan and Bhubaneswar History:

• The Wire, “Unwelcoming Spaces: How the Architectural Vision for Bhubaneswar Has Blurred Over 75 Years”
• Borderless Journal, “Bhubaneswar@75: Perspectives”
• Question of Cities, “A Compendium on Odisha’s Planned City and Its Transformation”
• Question of Cities, “How Bhubaneswar’s Master Plan Was Overtaken by Unsustainable Development”
• Daily Pioneer, “Koenigsberger’s Guidelines Not Followed in Today’s Planning” (2013)
• RTF, “Indian Cities: Bhubaneswar, Odisha”

Chandigarh and Gandhinagar Comparisons:

• Chandigarh Administration, “Le Corbusier’s Master Plan”
• Hello Gandhinagar, “Who Planned Gandhinagar City”
• Question of Cities, “Lessons from Independent India’s Urbanisation”

Census and Population Data:

• Census of India 2011, Bhubaneswar City (census2011.co.in)
• MacroTrends, Bhubaneswar Metro Area Population
• CEIC Data, Census Population Odisha: Bhubaneswar

Temple Heritage:

• UNESCO World Heritage Centre, “Ekamra Kshetra — The Temple City, Bhubaneswar” (Tentative List, 2014)
• Wikipedia, “Ekamra Kshetra”

IT Sector:

• STPI Bhubaneswar official data (FY 2020-21, FY 2024-25 exports)
• Invest Odisha, “IT Policy 2022”
• India Briefing, “Bengaluru vs Hyderabad: India’s Tech Hubs”
• Supersourcing, “Emerging Tier 2 Cities for GCC Setup”

Smart City and Mo Bus:

• Citizen Matters, “Smart City Bhubaneswar Assessment”
• Bhubaneswar Smart City Limited, interventions data
• Daily Pioneer, Smart City project execution reporting
• PIB, “10 Years of Smart Cities Mission” (May 2025)
• Down to Earth, “How India Moves: Bhubaneswar”
• CRUT / Mo Bus operational data (fleet, ridership, modal shift)
• Gupta Urban Award 2024

Infrastructure:

• PIB, NHAI Capital Region Ring Road (Rs 8,308 crore, 111 km)
• Wikipedia, Bhubaneswar Metro (viability concerns, tender scrapping)
• Metro Rail News, viability analysis
• Down to Earth, metro cost-benefit analysis
• PHEO Bhubaneswar, water supply data (19.5 MGD from Kuakhai, ward coverage)
• Citizen Matters, stormwater drainage analysis
• ORF, storm water infrastructure assessment

Real Estate and Slums:

• 99acres, property rates and trends in Bhubaneswar
• Square Loop Estates, market scenario June 2025
• ResearchGate, “Slum Growth in Bhubaneswar: A Problem or Solution”
• IIHS, “Planning, Violations, and Urban Inclusion: Bhubaneswar”
• Odisha.plus, slum demolition reporting (November 2025)

JAGA Mission:

• World Habitat Award 2019, 2023
• State programme data (2,919 slums, 114 cities, 175,000 families)

Education:

• KIIT University (Wikipedia, official data: 30,000 students, NAAC A 3.48)
• SOA University (Wikipedia: NIRF rank 15, 15,000 students)
• IIT Bhubaneswar (Wikipedia)
• NISER (Wikipedia)
• Utkal University (official: 381 affiliated colleges, NAAC A+)
• NIT Rourkela placement data 2024-25 (1,274 offers, Rs 62.44 LPA highest)
• Invest Odisha, major institutes of higher learning

Airport:

• News on Air, BBI passenger records 2025
• OrissaPOST, 51.5 lakh passengers 2025, 13th national rank

Environmental:

• Elephants Now, Chandaka Forest and Elephant Sanctuary encroachment
• Wikipedia, Chandaka Elephant Sanctuary (forest cover decline 90.27% to 62.72%)

---

Cross-References

The Leaving (full_read/the-leaving/): The brain drain data in this chapter — NIT Rourkela placements, 6 lakh Odias in Bangalore, 90%+ high-achieving graduates leaving — directly extends Chapter 4 (“The Skilled Departure”) and Chapter 7 (“The Diaspora Mind”). The education hub paradox identified here is the urban-scale version of the talent export pattern documented in that series.

Political Landscape (full_read/political-landscape/): Government as dominant employer and city-maker connects to the analysis of how political power operates through administrative control. The Smart City ranking as political achievement, Mo Bus as governance success story, and the metro viability debate as political economy all draw on the institutional analysis in that series.

The Churning Fire (full_read/the-churning-fire/): The OSDMA exception pattern — concentrated institutional excellence in a single domain coexisting with systemic failure elsewhere — directly applies to Mo Bus/CRUT. Chapter 4 (“The Inner Fortress”) identified this pattern in disaster management; this chapter identifies it in urban transport. JAGA Mission as a positive institutional design pattern extends Chapter 8’s analysis of institutional architecture.

The Long Arc (full_read/the-long-arc/): The 1948 capital shift decision connects to Chapter 1 (“The Inherited Order”) and the post-independence state-building project. Government colony culture as spatial hierarchy connects to Chapter 5 (“The Extraction Equilibrium”) — the same government that runs the extraction-welfare cycle also runs the city as its own colony.

Culture of Odisha: The Old Town temple heritage — Ekamra Kshetra, Lingaraj, the dual-city identity — connects to the Jagannath series (full_read/the-lord-of-the-blue-mountain/) in exploring how sacred geography shapes political and economic geography. The temple city is not merely heritage to be preserved — it is an operating system that has run for 2,000 years, now coexisting with a 75-year-old modernist overlay.

Environmental Odisha (full_read/environmental-odisha/): Chandaka-Dampara Wildlife Sanctuary encroachment — forest cover declining from 90.27% (1970) to 62.72% (2005) — is the ecological cost of unplanned growth beyond the Koenigsberger plan. The drainage channel encroachment and waterlogging connect to Chapter 3 (“The River That Divides”) on water system mismanagement.