Lesson 2.2Lesson 2.2 · Parametric Urbanism
Urban Parameters & Rules
The actual knobs of a parametric urban model - density, block size, street width and hierarchy, setback, height, floor area ratio, coverage and orientation - and how the planning rules that govern a city become the parameters of the model, carrying their power and their silences with them
Density, block size, street width, setback, height, FSI, coverage, orientation - a handful of numbers that a whole neighbourhood obeys. These are the knobs. Where do they come from?
A parametric model is only ever as good as the parameters you expose, so the practical heart of parametric urbanism is knowing which quantities actually govern urban form - and, just as importantly, where those quantities come from. The reassuring news is that urbanism already thinks in parameters. Long before anyone wrote a line of code, planners governed cities with numbers: a floor area ratio here, a height limit there, a minimum street width, a maximum ground coverage, a setback from the plot line. Development-control regulations are, in effect, a parametric description of what may be built - a set of numeric constraints that any conforming design must satisfy. Parametric urbanism does something almost obvious in hindsight: it takes those same numbers and makes them *live* knobs in a model, so you can see, instantly and consistently, what a given combination of rules actually produces on the ground.
That is genuinely powerful. A written rule - "maximum FSI two, height fifteen metres, coverage fifty percent" - is abstract; most people, including the officials who set it, cannot really picture the neighbourhood it will grow. Turn those clauses into parameters and the model shows you: this density, these blocks, this skyline, this much open ground. You can test a proposed by-law before a city is built to it, or reverse-engineer what density a transit corridor needs and read off the rules that would deliver it. But the same move smuggles in the field's deepest hazard, quietly. A rule becomes a parameter only if it is a measurable number. Everything a city is that the rule-book could never quantify - the mixture of uses along a street, the informal plot that fits no setback, the meaning of a route, whose neighbourhood is protected and whose is cleared - does not become a knob, and so silently drops out of the model altogether. The parameters carry the rules' power *and* their silences. This lesson names the real knobs and keeps that double inheritance in full view.
Knobs: density, block size, street width+hierarchy, setback, height, coverage, FSI/FAR, orientation. They come from the RULE-BOOK (DCR clauses = parameters). See what rules grow! But only measurable clauses jump - the silences (mixture, informal, who benefits) vanish.
The knobs of a city - the core urban parameters
A parametric urban model typically exposes a compact, recurring set of parameters, and it is worth knowing them the way a musician knows scales. Start with the ones that shape the fabric. Block size sets the grain of the city - small blocks give many streets, corners and route choices; large blocks give fewer, longer streets and superblock interiors. Street width and its companion, the street hierarchy (main roads, collectors, local lanes), set movement capacity, sunlight into the street, and the feel of the public room between buildings. Plot depth and width subdivide the block into buildable parcels. Setback - how far a building stands back from the street or plot edge - governs the street wall, privacy, light and the space for planting or parking. Building height sets the skyline, shadowing and how much floor area a plot can hold.
Then the ones that govern intensity. Ground coverage is the fraction of a plot its building footprint may occupy, controlling open space at ground level. Floor area ratio - called FSI in India and FAR elsewhere - is the ratio of total built floor area to plot area, the single most powerful intensity knob in most rule-books: it decides how much building a piece of land can carry. Density - dwellings or people per hectare - is closely related but not identical, since the same FSI can house very different numbers of people depending on unit size. Finally orientation: the angle of the grid to the sun and prevailing wind, which in a hot climate like much of India is a first-order parameter for daylight, heat gain and natural ventilation, not a cosmetic one.
What makes these a *parametric* set, rather than just a list, is that they interact. Push block size up and street count falls; push FSI up against a fixed height limit and coverage must rise, eating open space; tighten setback and the street wall closes but daylight narrows. A good model encodes these dependencies so the plan stays consistent when any one knob moves - which is exactly the associativity of the previous lesson, now populated with real urban quantities. Learn this vocabulary well, because every parametric urban model, however sophisticated, is in the end an arrangement of these few numbers and the relationships between them.
Fabric knobs: block size, street width, plot depth, setback, height. Intensity knobs: coverage, FSI/FAR, density. Plus ORIENTATION (grid angle to sun/wind - first-order in India). They interact - move one, others follow.
The network parameters - street width and hierarchy
Streets deserve their own attention, because the street network is the one urban system that outlives almost everything built on it, and it is governed by parameters that are easy to under-think. The obvious knob is street width, but width alone is meaningless without hierarchy: a healthy network is not a single width repeated but a graded system - arterials and main roads carrying distance and transit, collectors gathering local traffic, and fine local lanes serving front doors. In a parametric model this becomes a set of related parameters: how many levels of street exist, the width and spacing of each level, and the rule by which a lower street connects to a higher one. Change the spacing of arterials and you change block size, trip lengths and where intensity wants to sit; change how freely local lanes connect and you change how walkable and permeable the fabric is.
The subtler and more consequential network parameter is connectivity itself - how many route choices the grid offers between two points. A dense grid of small blocks is highly connected: many parallel routes, many corners, resilient to a blockage and friendly to walking. A tree-like network of culs-de-sac hanging off a few arterials is poorly connected: few route choices, long detours, car-dependent by geometry. This is not a matter of taste; connectivity is measurable, and Module 6 will show how space syntax and network theory quantify it. In a parametric model, connectivity is often the parameter with the largest quiet influence on how a neighbourhood actually lives, because it sets whether daily life can happen on foot.
But here the honest caution returns sharply. The network parameters capture *geometry and capacity* - widths, spacings, connections, flows. They do not capture what a street is *for* beyond movement: the doorstep conversation, the vendor's pitch, the way an Indian street is a workplace, a market and a living room as much as a route. A model can optimise a network for traffic flow or even for walkability score and still hollow out the street life those numbers were meant to protect, because the life is not in the geometry. Tune the network parameters to open up possibilities and test them - never to conclude that the best-scoring network is the best street.
From development-control rule to model parameter
The deepest idea in this lesson is that the parameters of an urban model are not invented from nothing - they are, very largely, the *planning rules themselves* turned into knobs. A development-control regulation is already a parametric specification: it says maximum FSI shall be this, front setback shall be at least that, height shall not exceed so many metres, ground coverage shall not exceed such a percentage. Each of those clauses is a number attached to a piece of urban form - which is precisely what a parameter is. Building a parametric model of a plan area is often, in practice, the act of reading the applicable regulations and wiring each numeric clause to a knob, with the rule's limit becoming the parameter's range.
This is enormously useful and worth doing well. It lets you *see the rule-book*, which almost no one can do from the text alone. You can load a real development-control regime - in India, the master-plan and development-plan provisions and the applicable DCR, alongside the relevant parts of the National Building Code - and watch the neighbourhood those rules would grow: the density they permit, the skyline they imply, the open space they leave. You can test a proposed amendment before it is enacted, or check whether a corridor's rules actually deliver the transit-supportive density a plan claims to want. Used this way, a parametric model becomes a rehearsal space for policy, making the abstract consequences of regulation legible to officials, communities and elected decision-makers before anything is built.
The hazard is exact and must be named every time. When you turn a rule-book into parameters, only the *quantifiable* clauses make the jump. FSI, setback, height and coverage become knobs; the things the rule-book is silent on - or gestures at in words no number can hold - do not. The mixture of uses that makes a street alive, the fine grain that lets small enterprise survive, the informal settlement that satisfies no plot rule, the question of who gains and who is displaced: none of these becomes a parameter, so the model quietly proceeds as if they did not exist. The regulation's power is inherited faithfully; so are its blind spots, now hardened into the very structure of the model. A parametric rule-model is therefore never a neutral picture of "what the rules produce" - it is a picture of what the *measurable* rules produce, with everything unmeasurable already erased.
A DCR clause (FSI 2.0, setback 3m, height 15m, coverage 50%) IS a parameter spec. Wire each number to a knob -> see the rule-book grow a neighbourhood. But only measurable clauses jump; the silences (mixture, informal, who benefits) vanish.
The honest edge - the parameters you can name are not the whole city
Put the two halves together and the discipline of this lesson becomes clear. The urban parameters - density, block size, street width and hierarchy, setback, height, FSI, coverage, orientation - are a genuinely powerful and legitimate vocabulary. They are how urbanism already governs form, they interact in ways a model can keep consistent, and making them live knobs lets designers, officials and communities *see* consequences that words hide. None of that is in question. What is in question is the seductive slide from "these are the parameters of the model" to "these are the parameters of the city" - as if the numbers we can name were the whole of what a place is.
They are not, and the gap is where the harm lives. A city is also its mixture and its meaning, its memory and its informal ingenuity, its patterns of belonging and its questions of justice - none of which is a knob, because none is a number. When a parametric model quietly stands in for the city, everything outside its parameters is not merely unmodelled; it is *presumed absent*, and a plan optimised against the parameters will trade it away without ever registering the loss. In the Indian context this is not abstract. A model built from formal development-control parameters can be structurally blind to the informal city where a very large share of urban life happens, representing as "vacant" or "non-conforming" the homes and livelihoods of millions - and then a clean, re-forming plan can rationalise their erasure with the false authority of geometry.
So the professional stance is to use the parameters fully while refusing to mistake them for the city. Name every parameter your model exposes, and next to it name what that parameter cannot hold. Treat the parameterised rule-book as a rehearsal of the *measurable* consequences of policy, always annotated with what the rules are silent about. And keep the binding decisions where they belong: the choice of which rules a city adopts, which densities and heights it permits, whose neighbourhoods are protected and whose are changed, is a political and democratic act for the planning authority, the participatory process, the affected communities and the governing law - informed by the parameters, never dictated by them. The knobs help you argue; they do not get to decide.
The core parameters
The recurring knobs
Block size, street width and hierarchy, plot depth, setback, height, coverage, FSI/FAR, density and orientation - a compact interacting set every urban model arranges. Learn how moving one moves the others. Modules 2.2, 4.1-4.3.
Rules become parameters
Where the knobs come from
A development-control regulation is already a parametric spec; wiring each numeric clause to a knob lets you see what a rule-book grows. In India, the master-plan/DCR process and NBC. Modules 2.2, 7.1.
The parameters carry silences
What does not become a knob
Only measurable clauses become parameters; mixture, informal fabric, meaning and equity drop out and are presumed absent. Name the silence beside every parameter. Modules 2.2, 9.4.
The binding choice is democratic
Which rules a city adopts
Choosing densities, heights and which neighbourhoods change is a political, statutory act for the planning authority, the participatory process, the communities and the law - informed by the model, never dictated by it. Modules 7.3, 9.4.
Workshop — read a real rule-book as a set of parameters, then find its silences
The fastest way to understand urban parameters is to see them hiding in a real regulation. In this workshop you take the development-control rules for a plot or area you can find, translate the rules into model parameters, sketch what they grow, and then list what the rules never quantified.
A real set of development-control rules or by-laws and graph paper. No software needed; and remember the binding choice of which rules a city adopts belongs to the planning authority, the participatory process, the affected communities and the governing law.
Goal: see a rule-book as parameters, and see what it leaves out Inputs: any accessible development-control rules or building by-laws (a city DCR summary, a plot's zoning) + graph paper Time: ~45 minutes
- 1Extract the numbers: from the rules, list every numeric clause - FSI/FAR, setbacks, height limit, ground coverage, road width, any density cap. Each is a parameter.
- 2State the ranges: for each parameter write its allowed range (the rule usually gives a max or min), so you have a knob with limits.
- 3Grow it by hand: sketch a block that obeys these parameters at their limits - the densest, tallest, most-covered version the rules permit. This is what the rule-book actually allows.
- 4Sweep one knob: halve the FSI (or the height) and redraw. Note how coverage, open space and plausible density respond - feel the parameters interact.
- 5List the silences: name five things about a good version of this neighbourhood that NONE of these parameters can express (mixture, ground-floor life, informal plots, meaning, who benefits), and note who should decide whether they matter - flagged as reasoning.
You’ll walk away with
A one-page 'rule-book as parameters': the parameter list with ranges, a hand sketch of the maximum the rules allow, one swept variant, and a list of five silences the parameters cannot hold - with the choice of rules left to the planning process. Keep it for Module 7.
Three altitudes on the same idea
Read the band that fits you — or all three.
For the architect or urban designer, fluency in the urban parameters - density, block size, street width and hierarchy, setback, height, FSI, coverage, orientation - is the practical core of parametric skill, and knowing where they come from is what keeps you honest. These are not arbitrary knobs; they are the quantities urbanism already governs form with, and most of them are lifted straight from the development-control rules of your site. Build models that wire each rule to a parameter so you can see what a regime actually produces, test amendments, and reason about how the knobs interact - push FSI and watch coverage or height respond. But annotate every parameter with what it cannot hold: mixture, informal fabric, meaning, who benefits. In India especially, treat orientation as first-order for climate, and never let a formal-parameter model present the informal city as absent. Use the parameters to explore and to make consequences legible; defer the binding choice of which rules a city adopts to the planning authority, the participatory process, the affected communities and the governing law.
For the planner or urbanist, this lesson is close to home, because the urban parameters are your own instruments - FSI, setback, height, coverage, density - and a parametric model is, at heart, your rule-book made visible. That is a real gift: you can finally show a committee or a community what a proposed FSI or height regime will grow on the ground, rather than asking them to picture it from clauses. Use it to rehearse policy, test corridors for transit-supportive density, and surface consequences before they are built. But hold the line that a parametric rule-model shows only the *measurable* consequences of regulation; the mixture, the informal city, the equity of who gains and who is displaced never became parameters and are therefore presumed absent unless you insist otherwise. Keep those silences on the table in every review. The choice of which rules the city adopts is a statutory, democratic act belonging to the process, the affected communities and the law - informed by the model, never dictated by it.
Learn the vocabulary cold: the recurring urban parameters are density, block size, street width and hierarchy, setback, building height, ground coverage, floor area ratio (FSI/FAR) and orientation - and the punchline is that these mostly come from the city's own planning rules. A development-control regulation is already a set of numbers attached to urban form, so building a parametric model is largely the act of wiring each numeric clause to a knob. That is powerful because it lets you *see* what a rule-book grows - a density, a skyline, an amount of open ground - which almost no one can read from the text. But carry the two-sided lesson that marks a real urbanist: only measurable clauses become parameters, so everything the rules cannot quantify - the mixture of a living street, the informal settlement that fits no setback, the question of who benefits - silently drops out of the model. The parameters inherit the rules' power and their blind spots together. So the knobs help you understand and argue; the binding choice of which rules a city adopts stays democratic.
“If you get all the urban parameters right - the correct density, FSI, block size, street widths, setbacks and heights - you have essentially defined a good neighbourhood. Good urban form is just the right combination of these numbers, so tuning the parameters until they are optimal gives you a good place.”
Do it yourself
No software needed — reason it through.
- 1List the core urban parameters and, for each, say in one line what part of urban form it governs.
- 2Give one example of how moving one parameter forces another to change, and explain why.
- 3Explain how a development-control rule 'becomes' a model parameter, and what is gained by seeing the rule-book that way.
- 4Why is street connectivity often the network parameter with the biggest quiet effect on daily life?
- 5Name three things a formal-parameter model cannot represent, and say why that matters especially in the Indian city.
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Floor area ratio — Wikipedia — Floor area ratio, 2026.
- 02Zoning — Wikipedia — Zoning, 2026.
- 03Density (urban) — Wikipedia — Density (urban), 2026.
- 04Street network — Wikipedia — Street network, 2026.
- 05National Building Code of India — Wikipedia — National Building Code of India, 2026.
We now have the knobs and know where they come from. The next question is architectural: how are these parameters actually wired together into a working model - the inputs, the logic, the outputs - and how can a model's hidden assumptions silently shape everything it produces?
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →