Climate Analysis Basics

A climate, for a designer, is a small set of measurable variables and the way they behave over a typical day and a typical year. The core ones are: air temperature (the daily maximum and minimum, and how they swing across the year); the diurnal range (the gap between day and night temperature, which in dry climates can be huge and in humid ones is small); humidity (how much water the air carries, usually read as relative humidity, which decides whether heat feels bearable and whether sweat can cool you); solar radiation (how much sun energy falls on the site, and from which directions through the seasons); wind (its prevailing direction, speed and seasonality, which drives natural ventilation and also cold exposure); and precipitation (how much rain or snow, and its timing - the monsoon being the defining example). Add sky conditions (clear versus overcast) and you have the working picture.

The skill is reading these together, not one at a time, because comfort and building response come from their combination. Thirty-five degrees in dry desert air with a large night-time drop is a different design problem from thirty-two degrees in saturated coastal air that barely cools at night - the first invites heavy mass that soaks up day heat and releases it to a cold night sky; the second makes mass a trap and demands relentless cross-ventilation instead. A place with fierce sun but cool air (a high-altitude town) wants to catch solar gain; a place with the same sun but hot air wants to reject it. Wind that is a welcome coolant in a humid summer is a punishing heat-loss in a mountain winter.

Two practical cautions frame this reading. First, averages hide the design problem: a gentle mean annual temperature can conceal both scorching afternoons and cold nights, and it is the extremes and the swings, not the average, that a building must handle. Second, the numbers you read are usually from a weather station that may be some distance away and, as earlier modules stressed, from the historical past - so treat them as a starting portrait, adjust for the site's own microclimate (a valley, a dense city, a coast, a hilltop each bend the regional climate locally), and remember the climate you are reading is already shifting. Reading well means holding the whole pattern, the extremes and the trend in mind at once.

Once you can read the variables, the next move is to place the site in a climate classification - a shorthand that groups places with similar design problems. Global schemes like the Koppen classification sort climates by temperature and rainfall patterns; for buildings, most countries use a simpler design-oriented set of climate zones. India is the clearest example: national practice recognises broad zones - hot and dry (much of the north-west, like Jaipur or Ahmedabad), warm and humid (the coasts and the north-east, like Mumbai, Chennai, Kolkata), composite (the interior plains, like Delhi, that are hot-dry for part of the year and humid in the monsoon), temperate or moderate (parts of the Deccan, like Bangalore or Pune), and cold (the Himalayas, like Shimla or Leh). The National Building Code of India and the energy code (ECBC) both use such zones to steer design and set requirements.

The value of a label is that it is a design shortcut, not just a name. 'Warm and humid' immediately implies a family of responses - reject solar gain, keep buildings light and open, maximise cross-ventilation, protect from driving rain, avoid heavy mass that stores heat - and a family of risks - overheating, mould, corrosion, monsoon flooding. 'Hot and dry' implies the near-opposite for some of these - heavy mass, small shaded openings, courtyards, evaporative cooling, protection from dust and glare. 'Cold' flips the whole logic toward catching and keeping heat. So classifying a site is really loading a checklist of what usually works and what usually fails there.

But a label is a starting point, never the finish. Composite climates exist precisely because many places refuse to sit in one box - Delhi genuinely needs hot-dry strategies in May and humid strategies in August, and a design that commits fully to either fails half the year. Boundaries between zones are fuzzy, microclimates can push a site toward a neighbour's category, and the classifications themselves were drawn from historical data and describe a climate that is warming - a place near a zone boundary may be drifting across it. Use the classification to load the right instincts and risks fast, then verify against the site's actual read variables and its likely future, rather than designing to the label alone.

Above every other reading sits one question that reorganises the whole design: across the year, does the building mostly need to be kept warm (heating-dominated) or mostly kept cool (cooling-dominated)? This is the hinge because heating and cooling pull design in opposite directions. A heating-dominated building (a Himalayan home, a cold-country house) wants to catch and hold energy - orient to the sun, use glazing to trap solar gain, insulate heavily, reduce ventilation heat loss, use thermal mass to store warmth. A cooling-dominated building (most of India, most of the tropics) wants to reject and shed - shade ruthlessly, minimise solar gain, ventilate to carry heat away, and in dry climates use mass and night cooling, in humid climates stay light and open. A strategy that is a virtue in one is a fault in the other: south-facing glass that is a solar collector in Shimla is an overheating liability in Chennai.

The honest, urgent point for India and the warming world is that this balance is shifting toward cooling. Places that once needed a little winter heating increasingly need far more summer cooling; composite climates are tilting hotter; and cooling demand is surging just as heat becomes dangerous. A building designed decades ago as mildly heating-sensitive may spend its later life firmly cooling-dominated - which is exactly the stale-baseline problem from Module 0 playing out in the most basic design decision of all. Reading a site today and assuming its heating-versus-cooling balance is fixed for the building's life is a mistake; the balance itself is a moving target.

So the first analytical output of a climate study is not a number but an orientation: which fight is this building's main fight, now and across its life? Everything downstream - degree-days, comfort targets, sun and shading strategy, ventilation, the whole climate study - refines the answer to that question. Getting it right is mostly about honest reading and judgement; getting the *binding* consequences right - how much cooling capacity, what glazing performance, what the energy and comfort outcomes actually are - is engineering that belongs with qualified building-physics and energy specialists, verified data and the codes. Your job here is to frame the fight correctly and design its direction; theirs is to quantify and certify it.

A climate analysis earns its place only when it changes the design, so the final step is translating the read climate into two lists: opportunities (what this climate offers that the building can harvest for free) and risks (what it threatens the building and its occupants with). Every climate offers both. A hot-dry climate offers cool night air, clear skies for night-sky cooling, and reliable sun for daylight and drying - and threatens with fierce afternoon heat, glare, dust and a huge diurnal swing. A warm-humid climate offers steady breezes to harvest for cross-ventilation and diffuse light - and threatens overheating that will not relent at night, mould, corrosion, driving monsoon rain and, most seriously, dangerous humid heat. A cold climate offers valuable winter sun to catch - and threatens heat loss, frost and snow load.

Framed this way, design becomes a set of moves that maximise the opportunities and defend against the risks particular to that place: orient and shade for the sun as it actually tracks; open to the useful wind and shelter from the harmful one; use or avoid thermal mass depending on the diurnal swing; lift, protect and drain for the rain that actually falls; and, in cooling-dominated hot climates, above all provide a passive fallback so the building stays survivable when active cooling fails. This is the bridge from analysis into the rest of the course: degree-days and comfort quantify the demand (Lesson 4.2), the sun-wind-humidity drivers get their own detailed reading (Lesson 4.3), and it all gathers into a climate study that frames the brief (Lesson 4.4).

Two disciplines keep this honest. First, carry the future, not just the historical read: the opportunities and risks of a place shift as it warms - cooling risks grow, some heating opportunities fade - so a climate analysis for a building being designed now should look at the climate of its life, not only its past (the method for that comes in Module 3 and returns in Lesson 4.4). Second, stay in your lane: reading a climate and setting design direction is design judgement and yours to own, but the binding thermal-comfort, energy and climate-risk results - how the building actually performs, what it must be sized for, whether it complies - defer to qualified specialists, validated tools and the governing codes. Analysis frames the problem; engineering settles it.