Climate Analysis for Design

Before you draw a wall, the site has already handed you a set of demands: how hot the afternoons run, how cold the nights fall, how much moisture hangs in the air, where the sun sits at noon in June and December, which way the wind comes in the season you most want it. Reading that brief is climate analysis, and it is the first real act of building performance simulation - because every later number, from an energy model to a comfort study, is only the climate acting on your design.

The raw material is simple: long-run records of dry-bulb temperature, relative humidity, solar radiation, wind and rainfall for the location, usually distilled into monthly means and daily swings. What matters is not memorising figures but learning to read a shape. Is the annual temperature range wide (big day-night and summer-winter swings) or narrow and steady? Does humidity stay high all year, or spike only in a monsoon? Is there a lot of clear-sky sun to harvest or to hide from? These few readings already tell you whether the building's main job is to shed heat, trap heat, dry the air, or simply stay out of the way.

The Koppen-Geiger classification is the most widely used way to name a climate in a few letters, built from temperature and precipitation patterns. Its top groups - A tropical, B arid, C temperate, D continental, E polar - split further, so a place reads as, say, Aw (tropical with a dry winter), BSh (hot semi-arid) or Cwa (humid subtropical, dry winter, hot summer). Much of India falls into Aw, BSh/BWh and Cwa; London is Cfb, Phoenix BWh, Singapore Af.

Koppen is a useful first handshake - it lets you compare your site to buildings and precedents anywhere on Earth in one code - but it was built for vegetation, not comfort. Two places sharing a Koppen label can still demand different envelopes. So treat it as orientation, not instruction: it tells you roughly what family of climate you are in, and points you to precedents worth studying, but the design decision still needs the local numbers and, better, the hourly weather file you will meet in the next lesson.

For design in India, the more directly useful map is the National Building Code (NBC, published as SP 7) five-zone classification, echoed by the Eco Niwas Samhita and ECBC. Each zone converts directly into a passive strategy:

Hot-dry (Jaipur, Ahmedabad): fierce sun, big day-night swing, low humidity. Goal - keep heat out and use the cool night. Heavy thermal mass, small shaded openings, light external colours, courtyards, and evaporative cooling (the dry air can absorb moisture, so it cools well).

Warm-humid (Chennai, Mumbai, Kochi): hot, sticky, small temperature swing, little relief at night. Goal - move air across skin. Cross-ventilation is king; deep shade, light construction that does not store heat, raised openings, and dehumidification where sealed. Evaporative cooling fails here - the air is already saturated.

Composite (Delhi, Nagpur): a hot-dry summer, a humid monsoon and a genuinely cold winter in one place. Goal - switch modes. You need mass and shade for summer, ventilation for the monsoon, and solar gain in winter, so the design must do more than one thing.

Temperate (Bengaluru, Pune): mild and forgiving year-round. Goal - light touch. Modest shading and good ventilation carry comfort for most hours with little energy.

Cold (Leh, Shimla, high Himalaya): the opposite problem - keep heat in. Compact form, high insulation, south glazing to catch winter sun, minimal exposed surface. Here the sun is a friend, not a threat.

Notice how the goal reverses across the country: in Chennai you fight to reject heat, in Leh you fight to keep it. Same physics, opposite sign - which is exactly why a single 'good design' rule cannot travel.

Climate analysis pays off only when it changes a decision, so end every read with a so-what. A wide day-night swing (hot-dry) says thermal mass will work, because the structure can soak up heat by day and dump it to the cool night sky. A flat, humid profile (warm-humid) says mass will just trap heat and hold you hot all night - go light and ventilate instead. A big winter heating demand says orient and glaze for the low winter sun; a big cooling demand says shade the summer sun and cut west-facing glass.

The fastest way to do this rigorously is a free tool called Climate Consultant (UCLA), which reads a location's weather file and plots temperature, humidity, sun and wind, then runs the data through a bioclimatic model to suggest which passive strategies suit - the subject of lesson 1.4. You point it at your city, and in minutes it ranks design strategies by how many hours they would deliver comfort. It is not a verdict, but it is a superb, evidence-based starting brief - and it turns 'I think this site is hot' into 'shading plus night ventilation would cover 61% of hours here.'

Work one read end to end to feel the habit. Take Delhi, a composite climate. The temperature curves show a scorching May-June (mean daily max near 40 degrees C), a warm humid monsoon, and a genuinely cold December-January (nights near 7 degrees C). The so-what writes itself: you need summer shading and thermal mass to survive the pre-monsoon heat, openable windows to flush the humid monsoon, and south-facing glass to catch the low winter sun for free warmth - three different jobs from one climate, which is exactly what 'composite' means and exactly why a single-strategy building fails here. Now contrast Chennai: the curves barely dip, humidity stays high all year, and there is no cold season at all. The so-what is singular and relentless - move air, shade hard, stay light - and any mass or winter-sun thinking borrowed from Delhi would actively harm it. Same country, same tools, opposite briefs.

There is one more layer beneath the regional zone, and it can quietly overturn your read: the micro-climate - the actual conditions on this plot, which can differ sharply from the city average. A dense urban core traps heat and runs several degrees warmer at night than the open outskirts (the urban heat island); a west-facing slope bakes in the afternoon while a north-facing one stays cool; a nearby lake or the sea moderates the swing and adds humidity; a stand of mature trees drops the local temperature and filters the wind; a narrow street can either funnel a breeze or choke it. None of this shows up in the regional climate label, yet all of it lands on your building.

So a complete climate read moves from the general to the specific: name the zone, then walk (or study) the site for what modifies it. Which way does the prevailing seasonal wind come, and does anything block it? Where does the plot fall in shade from neighbours or hills? Is there vegetation or water to exploit, or hard paving and traffic that will heat and dry the air? These observations refine - and sometimes contradict - the zone-level strategy. A warm-humid site with a reliable sea breeze may lean even harder on ventilation; a hot-dry plot hemmed in by tall neighbours may lose the night-sky cooling that mass relies on. Climate analysis, done well, is this two-scale habit: the regional zone sets the broad goal, and the micro-climate tunes it to the ground you are actually building on. It is also the bridge to the next lesson, because the weather file you will simulate against describes a distant station, not your street - and knowing your micro-climate is how you judge whether that file can be trusted.