Zoning, FSI & Setback Overlays

A statutory master plan (or Development Plan / CDP, by state) divides a city into zones - residential, commercial, industrial, public/semi-public, green, and so on - each with rules about what may be built. When that plan is a GIS layer, your plot is not just coloured; it carries the zone as an attribute. Click it and you read its category and the rules attached to it, exactly as you clicked a plot and read its row back in Module 0.

India's planning is actively moving to this form. The AMRUT sub-scheme for GIS-based master plans and the older National Urban Information System (NUIS) exist precisely to turn drawn master plans into queryable geodatabases at scales like 1:4,000 and 1:2,000. Where that data exists, reading permitted use is a click; where it does not, you still have a scanned plan you must georeference (Module 3) before you can overlay your plot on it - a common, honest first step in Indian practice.

Floor Space Index (FSI) - called Floor Area Ratio (FAR) in many countries and increasingly in Indian codes too - is the single most consequential number on the plan. It is the ratio of total permitted built-up floor area to plot area. An FSI of 2.0 on a 500 m2 plot permits 1,000 m2 of floor area, however you stack it - four floors of 250 m2, or two of 500 m2. It is the volume budget for the whole design.

In a GIS this becomes arithmetic on attributes: multiply each plot's area by the FSI its zone allows and you have its permitted built-up area, mapped across a street or a whole sector. That is powerful for planners testing capacity and for architects sanity-checking a brief on day one. Two honest cautions: FSI definitions and exclusions (what counts as floor area, balconies, basements, premium/purchasable FSI) vary by city and change over time - so treat the GIS number as the reasoning tool and the current local Development Control Regulations as the binding authority.

FSI caps floor area; setbacks and height limits decide the shape it can take. A setback is the mandatory clear distance from each plot boundary - front, sides and rear - within which you may not build. Subtract the setbacks from the plot and what remains is the buildable footprint; extrude that by the permitted height and you have the building envelope - the invisible box the design must live inside.

In a GIS, setbacks are a negative buffer (an inward offset) of the plot boundary, and the buildable footprint is the difference between the plot and that offset. Do it for one plot to brief a design; do it across a block and you can see, at a glance, how much ground the rules actually free up - and how a generous-looking plot can become a tight footprint once front, side and rear margins are honoured. The envelope, not the plot, is the true canvas.

Put the three together and the plot's real capacity appears: the zone says what you may build, FSI says how much, setbacks and height say what shape. Overlaid on the constraints composite from lesson one, you get the intersection of the legal envelope and the physical buildable area - the ground that is both permitted and sensible.

The honesty here is about data provenance. Statutory lines are legally binding, and a GIS layer is only as current and correct as its source. Confirm you have the adopted plan, not a draft; check the revision date; and remember that zone boundaries drawn at 1:4,000 carry real positional uncertainty at the scale of a single plot. Use the GIS to reason, scope and argue - then verify the binding numbers against the current Development Control Regulations and the planning authority. That discipline is what separates a defensible feasibility from a hopeful one.