Mapping & Site Analysis

All urban analysis stands on a base map, the accurate, scaled drawing of the physical facts of a place onto which every other layer is registered. A good base map shows at least the street network, building footprints, plot or parcel boundaries, water, open space, and contours or spot levels, all georeferenced so they line up. In India the raw material comes from several sources that rarely agree perfectly: Survey of India toposheets for terrain and the regional frame, municipal or development-authority cadastral and master-plan maps for plots and land use, and increasingly OpenStreetMap and high-resolution satellite imagery for current footprints and roads. The first discipline of analysis is therefore reconciliation: overlaying these sources, noticing where they disagree, and deciding which to trust for each feature. A map is never a neutral mirror of reality; it is a selective argument, and every base map embeds choices about scale, extent, and what counts as worth drawing. Choosing the study extent is itself an analytical act, because a site's real influences, its catchment, its watershed, its transport corridor, almost always spill beyond the red line of the plot. Draw too tight a boundary and you will miss the forces that actually govern the site; draw the base map at the scale of the question, not the scale of the property.

The most durable idea in site analysis is the layer cake, popularised by Ian McHarg in Design with Nature in 1969 and now the everyday logic of every geographic information system. Instead of one crowded drawing, you separate reality into thematic layers, one each for topography, hydrology, vegetation and ecology, land use, movement, ownership, and so on, then stack them so patterns emerge from their overlay. McHarg used this to find the least-cost, least-harm route for roads by overlaying constraint layers until the clear corridors revealed themselves, an early form of what GIS now calls suitability analysis. The power of the method is that it disaggregates a confusing whole into legible parts and then lets you recombine them deliberately. In practice you build these layers in a tool like QGIS, the leading free and open-source GIS, or a commercial platform such as Esri's ArcGIS, pulling geometry from OpenStreetMap, government open-data portals, and your own survey. The layers you choose are an argument about what matters: a flood-resilience project foregrounds hydrology and levels; a high-street revival foregrounds ground-floor uses, footfall, and frontage. Discipline yourself to keep each layer clean and single-themed, because the insight comes not from any one layer but from the moment two of them line up, when the low ground turns out to be exactly where the informal settlement sits, or the dead frontage exactly where the block is oversized.

OpenStreetMap has transformed urban analysis, especially in India, where official large-scale digital data can be patchy or costly. It is a free, editable world map built by volunteers, with tagged geometry for roads, buildings, land use, amenities, water, and much else, downloadable and usable in any GIS. For a student or a small practice it means you can assemble a credible base map of almost any Indian city in an afternoon, extracting the street network for a permeability study, the building footprints for a figure-ground, and points of interest for a land-use or amenity map. Its limits must be respected: coverage and accuracy vary from city to city and even neighbourhood to neighbourhood, footprints may be missing or dated, and informal areas are often under-mapped, so ground-truthing by walking the site remains essential. Pair OpenStreetMap with satellite imagery to check and complete footprints, with census data for population and demographics, and with your own field survey for the things no dataset holds, the smell of the drain, the shade of a tree, the informal cricket pitch, the direction people actually walk. The best analysts treat digital data as a first draft to be corrected on foot, never as the truth.

A thorough urban site reading works through several families of question. Movement: how do people and vehicles get to and through the site on foot, by cycle, by bus or metro, by car, where are the desire lines and the barriers, and what is the walking catchment, typically the area within a five-to-ten-minute walk of a station or centre? Uses and activity: what happens where, when do streets fill and empty, where is the active frontage and where the dead edge, and what is missing that people must travel far to find? Ecology and environment: where does water flow and pool, where are the trees and green, which way does the sun and the prevailing wind come, and where is it hot, noisy, or polluted? People and meaning: who uses this place, who is excluded, what do residents value, and what carries memory or sacred significance, the temple tank, the old banyan, the market that has met on the same spot for generations? Kevin Lynch's five elements, paths, edges, districts, nodes, and landmarks, give a ready vocabulary for the perceptual layer, mapping how the place is held in the mind, not just on the ground. A reading that covers movement, use, ecology, and meaning, drawn and then checked on foot, is what turns raw layers into understanding.

A frequent blind spot is treating the site as a still photograph when it is really a film. Cities pulse across the day, the week, and the year, and a layer that maps time often explains more than any static drawing. A market street that is choked and thrilling at nine in the morning may be a shuttered canyon by nine at night; a school gate is a bottleneck for twenty minutes and empty for the rest of the day; a floodplain is dry ground for eleven months and a lake in the monsoon. Mapping these rhythms, by returning to the site at different hours and seasons, or by using proxies such as transit timetables, festival calendars, and rainfall records, reveals conflicts and opportunities invisible on a single visit. Historical time matters too: comparing old toposheets, cadastral records, and past imagery against the present shows how the fabric arrived at its current state and which changes are accelerating, the tank being encroached, the orchard being subdivided, the ground floors turning from homes to shops. Overlaying yesterday on today is the site-scale version of the morphological reading you learned earlier, and it protects you from designing brilliantly for a moment that does not last. Ask always not only what is here but when, and the site becomes far harder to misread.

In the Indian setting, site analysis must also read the statutory landscape, because what you may do is as much a fact of the site as its slope. The master plan or development plan prepared under the state Town and Country Planning Act and guided by the URDPFI Guidelines assigns each parcel a land-use zone and a set of Development Control Regulations, including Floor Space Index, setbacks, and heights, which together define the development envelope. Alongside these sit special layers: coastal regulation zones near the sea, heritage listings that constrain change in a precinct, transit-oriented development zones along metro corridors that permit higher density, and mission programmes such as AMRUT and the Smart Cities Mission that may bring funds and rules to particular areas. The 74th Constitutional Amendment devolves urban planning powers to elected urban local bodies and mandates ward committees and district planning, so the institutional map, who actually decides, is part of the analysis too. Treat every statutory claim carefully and verify it with the local development authority, because zoning, FSI, and precinct rules vary by state and city and change over time. The mature analyst maps not only the physical and social site but the regulatory and institutional one, because a brilliant proposal that the plan forbids is not yet a proposal.

Analysis that stays a pile of layers is useless; its purpose is a synthesis that points to design. The classic device is the constraints-and-opportunities plan, a single drawing that distils all the layers into what must be protected or avoided, the flood line, the heritage frontage, the mature trees, the noisy edge, and what invites action, the underused plot, the missing connection, the blank frontage on a busy street, the sunny sheltered corner. A companion urban SWOT, strengths, weaknesses, opportunities, threats, can structure the narrative. The discipline is to be selective and argumentative: a synthesis diagram makes a claim about what the site is really about, and it should be legible in one glance to a client or a community. From here the leap to design is short, because a good synthesis almost proposes the scheme for you, showing where movement should be added, where the block should be broken, where density belongs and where it does not. Site analysis, done honestly, is not a hoop to jump through before the real work; it is the first act of design, the moment the designer stops imposing and starts listening to what the place, its people, and its rules are already saying.