Climatic data and climate zone classification

Standard 169 holds the climatic data and classification framework that other building standards rely on. This page explains how a climate zone is derived from measured data and how a UAE project should establish which zone and which station apply.

Overview

ASHRAE Standard 90.1, published by ASHRAE, a registered mark of that society, uses climate classifications to assign energy requirements, while Standard 169-2025, titled Climatic Data for Building Design Standards, provides the climatic data and classification framework used by building standards. Keeping the climatic resource separate allows several standards to refer to a common technical basis. It also makes clear that climate classification is derived from measured conditions rather than assigned casually from a country name or a map impression.

The role of Standard 169

Standard 169 organises climatic information for use in building design standards. It brings together weather-station design data, climate classification and supporting geographical information so that other standards can apply climate-dependent provisions without recreating the climatic method inside each document. Its role is foundational: it supplies a consistent interface between measured weather records and building requirements.

The current edition is Standard 169-2025, titled Climatic Data for Building Design Standards. Its title should be used accurately because the standard is not a general weather handbook or a guarantee of conditions at every project site. It provides processed climatic information intended for defined building-design applications. The appropriate data still have to be selected and interpreted for the project.

Separation also supports coordinated revision. Climatic observations can be extended, checked and reanalysed independently of the full technical content of every dependent standard. When a referencing document identifies a particular edition, however, that edition relationship must be respected. A designer should not assume that the newest climatic dataset automatically replaces the edition frozen into a code, rating method or contract.

Why climatic data sit in a separate standard

Many building provisions need the same underlying climate description. Envelope requirements, energy models, equipment calculations and other design methods may all depend on location-specific information. Housing the common data in a separate standard reduces duplication and the risk that different documents will use inconsistent station records or classification logic.

The arrangement also distinguishes climatic evidence from the engineering response to it. Standard 169 describes and classifies the climate for standards use. Standard 90.1 then assigns energy requirements in response to that classification. A mechanical design method may use design conditions for sizing, while another standard may use related climatic information differently. The data source and the rule that consumes the data are therefore connected but not interchangeable.

This distinction helps when documents are updated on different schedules. The climatic standard may contain a newer station record, while a locally adopted energy requirement may still refer to an older energy-standard edition with its own referenced basis. The project team must establish the governing combination instead of assembling the newest available part of every document without authority.

Classification from measured conditions

A climate zone is determined from measured temperature and moisture data processed according to the classification method. It is not assigned merely because a project lies within the UAE, within a particular emirate or at a familiar latitude. The method considers the climatic record associated with a location and applies defined categories to that evidence.

Temperature classification reflects the pattern of thermal conditions across the record rather than one memorable hot day. Moisture classification distinguishes climatic regimes in which atmospheric moisture behaves differently. Together, these dimensions create a classification suitable for building-energy requirements. The exact boundary criteria belong in the purchased standard and are not reproduced here.

Because the classification is evidence-based, descriptive labels such as "desert" or "Gulf coast" are not sufficient substitutes. Such descriptions can help an engineer understand regional behaviour, but they do not establish the formal zone. A project record should identify the station or mapped classification source, the applicable standard edition and any judgement used to relate the site to that source.

How classification drives energy requirements

Standard 90.1 uses climate classification to direct a project to requirements suited to the expected environmental loads. The envelope provisions respond particularly strongly because heat flow, solar exposure and moisture conditions influence the energy needed to maintain indoor conditions. The standard's method ensures that an assembly is assessed in the climatic context in which the building will operate.

Consequently, the same building design placed in different climate zones could face different prescriptive envelope requirements. A façade, roof or opening that follows the prescriptive route in one zone cannot be assumed to do so in another. The design must be checked against the requirements associated with the project's established classification, using the selected edition and unit version.

Climate-dependent requirements do not mean that every part of the standard varies by zone. Many provisions address equipment, controls and power independently or use other classifications. The project team should therefore trace each requirement through the standard rather than treating the zone as a single label that decides compliance. No protected envelope table or requirement value needs to be reproduced to explain this relationship.

Coastal humidity and inland dryness

A hot and humid coastal climate and a hot and dry inland climate can present different design problems even when their dry-bulb temperatures appear broadly similar. Coastal air can impose a strong latent load, influence coil selection and create demanding part-load air-treatment conditions. Inland air can produce a larger daily temperature range and place different emphasis on sensible cooling and heat rejection.

For the envelope, atmospheric moisture and temperature patterns influence the direction and magnitude of heat and vapour drives, material response and the energy consequences of infiltration. For mechanical systems, the same nominal sensible condition can be accompanied by very different moisture loads. Climate classification provides a structured way for standards to recognise those distinctions rather than treating all warm locations as equivalent.

The classification is not a complete design. Local orientation, shading, building use, internal loads, operating schedule and ventilation strategy still matter. Mould, moisture and humidity as a mould driver belong to a neighbouring subject and are not explained here. The energy designer should use the climate zone as an input to the standard while retaining site-specific engineering judgement.

Projects near a zone boundary

A project near a mapped or calculated zone boundary deserves explicit review. Small geographical separation does not automatically imply a meaningful climatic difference, but the formal classification can still place neighbouring locations on different sides of a threshold. The designer should avoid selecting a preferred zone merely because it produces less demanding requirements.

The appropriate response is to examine the governing standard's location information, station metadata and classification method, together with any direction issued by the applicable authority. If the site is not directly represented, the team may need to compare nearby stations and assess elevation, coastal exposure and terrain. The reasoning should be recorded so that the selected classification is reproducible.

Where uncertainty remains, the project should obtain a determination through the route established by the governing authority or contract rather than invent a hybrid classification. The UAE compliance route, including which building is in scope and who verifies evidence, is a separate subject. From the standard's perspective, the essential point is that one documented classification must direct the applicable requirements.

Establishing the relevant UAE station

The first task is to locate the project accurately and identify candidate stations or published classifications in the applicable edition of Standard 169. Station names alone may be misleading if an observation site has moved or if several records exist around a metropolitan area. Metadata should be checked for coordinates, elevation, record quality and the character of the surrounding setting.

The designer should then compare the project with each candidate station. Distance from the coast, terrain, elevation and urban exposure can be more informative than straight-line distance alone. A coastal development should not automatically adopt an inland station because it is administratively nearby, and an inland project should not inherit a maritime classification solely because the best-known station lies on the coast.

The selected station should be identified consistently across the energy model, load calculations and basis of design unless a documented technical reason requires different datasets for different purposes. Apparent inconsistencies should be resolved rather than hidden. Ambient and outdoor air monitoring methods, equipment and limit values belong to a neighbouring subject and do not establish the climatic classification used by the energy standard.

Edition control and project documentation

Edition control is essential because climate data and classifications can change as observation records and methods are updated. Standard 169-2025 is the current climatic standard, but a project may be governed by a document that freezes an earlier edition or embeds its own mapping. The team should distinguish current technical information from the edition contractually or administratively required.

Project documentation should state the site, selected station or mapped location, climate classification, source edition and reason for selection. It should also identify the version of Standard 90.1 used for energy requirements. This creates a traceable chain from measured climatic evidence to classification and from classification to the project's technical checks.

Al Sa'fat, the Dubai Green Building System, 2nd edition of January 2023, clause 401.01 requires the latest edition of Standards 62.1, 62.2 and 170 without attaching edition years; Al Sa'fat has not been identified as referencing Standard 90.1. That example illustrates why designers must read the actual UAE programme document rather than infer an energy-standard reference from its use of other building-services standards, and its mandatory tier is Silver.

Edition references in UAE instruments

Edition years matter here more than they usually do, because UAE instruments reference these standards in two incompatible ways. Al Sa'fat, Dubai's green building system, whose Silver Sa'fa requirements are mandatory for new buildings, requires the latest edition of Standards 62.1, 62.2 and 170 and deliberately attaches no year, so the applicable requirements move as the standards are revised. Estidama's Pearl Building Rating System, Version 1.0 of April 2010, does the opposite: it names specific editions — the 2007 edition of Standard 62.1, the 2007 edition of Standard 62.2, the 2004 edition of Standard 55 and the 2007 edition of Standard 90.1 — so the requirements it imposes are frozen at those editions regardless of what has been published since. Dubai Municipality's Technical Guidelines for Indoor Air Quality for Healthy Life, Version 4 of 11 December 2024, references Standard 62.1 without giving an edition year. Anyone reading a requirement should therefore establish which instrument imposes it and whether that instrument names a year, before establishing what the current edition says.

Al Sa'fat §401.01 (2nd edition, January 2023) requires the latest edition and attaches no year — Estidama PBRS Version 1.0 (April 2010) names fixed editions

Is the whole UAE assigned one climate zone?

That should not be assumed. Formal classification follows measured temperature and moisture data under the applicable method, not national borders. Coastal influence, inland conditions, elevation and local geography can affect the relevant evidence. Each project should establish its classification from the recognised source and document the selection.

Does the nearest weather station always govern?

Not necessarily. Proximity is one consideration, but a nearby station may have a different elevation, coastal exposure or terrain context. The designer should compare station metadata with the project site and select the most representative source under the governing method, recording the reasoning where the choice is not self-evident.

Why can the same building need a different envelope in another zone?

Envelope performance interacts with outdoor temperature, solar conditions and atmospheric moisture. Standard 90.1 therefore directs projects to climate-dependent requirements. A design meeting the prescriptive provisions in one classification cannot be transferred elsewhere without checking the requirements associated with the new location.

What should happen if a site lies close to a boundary?

The project should examine the applicable mapping, station data, classification method and any authority direction. It should not choose whichever classification is more convenient. The adopted conclusion and its evidence should be recorded in the basis of design so that the energy-standard requirements can be applied consistently.

This is an independent information resource. It is not affiliated with, endorsed by, or connected to ASHRAE. ASHRAE and the names of its standards are the trademarks of their respective owners and are used here only to identify the standards described.