Dominio Morfoclimatico Do Brasil

Working with Domínio Morfoclimático in Real Projects

The morphoclimatic domain concept was developed by Aziz Ab'Saber in the late 1960s as a way to group Brazil's territories by the interaction between climate, relief, and vegetation. It is not a legal boundary. It is a synthetic classification meant for large-scale regional analysis. When you pick up a morphoclimatic map and try to use it for something practical, you quickly find that the lines on the paper do not match what exists on the ground. I ran into this problem last year while mapping a property in central Goiás. The official morphoclimatic chart placed the entire parcel inside the tropical continental domain, which carries a specific set of assumptions about lateritic crust formation and fluvial incision patterns. But the northern third of the property sat on a paleodrainage system with dense colluvial deposits that behaved nothing like the domain's typical regime. I spent two days in the field confirming that the domain boundary had shifted due to Quaternary neotectonic activity, which the published map simply did not reflect at that scale.

What the domínio morfoclimático do brasil actually covers

There are five main domains in Ab'Saber's framework. The equatorial domain covers the Amazon basin and parts of the Guiana Shield, characterized by deep weathering profiles, high precipitation, and dense humid forest. The tropical Atlantic domain runs along the eastern coast from Rio Grande do Norte to Rio Grande do Sul, with high rainfall, pronounced dry seasons in the north, and residual mountains shaped by ancient tectonic cycles. The tropical continental domain occupies the Brazilian Plateau interior, where the Cerrado dominates and lateritic crusts are widespread. The semiárido domain covers the inner Northeast, defined by erratic rainfall, xerophytic vegetation, and ephemeral drainage. The pampa domain is restricted to southern Rio Grande do Sul, with gentle relief, grassland ecosystems, and podzolized soils. Each domain carries implicit assumptions about erosion rates, sediment transport, and landscape stability. That is why geotechnical and environmental engineers still reference them, even though the concept is over fifty years old.

How I actually use it in practice

I start with the morphoclimatic domain as an initial filter, not as a final answer. The typical workflow involves pulling a domain map at 1:250,000 scale or larger, then cross-referencing it with IBGE soil maps and DEM-derived relief energy indices. If the domain classification and the soil data contradict each other, I treat the soil data as the more reliable indicator for on-the-ground conditions. This usually cuts the initial site assessment from three or four days down to about half a day, assuming you have the base maps loaded into QGIS. The tricky part is the transition zones. The eastern Amazon-Cerrado ecotone, for example, does not follow a clean domain line. Vegetation types interdigitate at the microscale, and the domain boundary drawn on a published map can be tens of kilometers away from where the actual climatic and pedological shift occurs. I learned this the hard way when a drainage design for a rural property near Marabá failed because the engineer assumed stable domain conditions throughout the project area. The reality was a shifting mosaic of wet-season swamps and dry-season lateritic pavements that the domain map completely smoothed over.

Pitfalls that beginners keep running into

The biggest mistake is treating morphoclimatic domains as predictive tools for local-scale engineering. They were designed for regional synthesis, not for designing a retaining wall or sizing a stormwater channel. The second mistake is ignoring the altitudinal variable. Ab'Saber himself emphasized that altitude modifies every domain, but most published versions of the map flatten that dimension into a single horizontal layer. A Cerrado area at 1,200 meters in the Chapada dos Veadeiros behaves differently from a Cerrado area at 600 meters near Brasília, and the domain label alone does not capture that difference. Another issue is that the semiárido domain includes areas with radically different water availability. The deep sertão near Campina Grande has a different hydrological regime than the agreste zone further south, yet both fall under the same domain classification. If you are doing water resource planning, you need to go beyond the domain label and look at actual rainfall distribution data from INMET stations, usually spanning at least thirty years to smooth out interannual variability.

When the concept stops working

Morphoclimatic domains break down in urbanized areas where the original landscape has been completely reworked. In Greater São Paulo or the greater Belo Horizonte area, the natural domain signature is largely obscured by anthropogenic modification. Using the domain classification there gives you a false sense of precision. I recommend switching to direct geomorphological mapping with recent satellite imagery and LiDAR data in those contexts. The domain framework is also unreliable in the Pantanal, which does not fit cleanly into any single domain due to its unique fluvial dynamics and annual flooding regime. If you need a operational tool for the Pantanal or highly urbanized regions, the morphological domains approach by Nilton Campos or the geomorphological mapping at 1:100,000 scale from CPRM will give you results you can actually use on a project.

Getting the base maps

The morphoclimatic domain maps are publicly available through IBGE and CPRM. The CPRM website offers downloadable shapefiles at various scales, and the basic domain map is also included in the IBGE geographic reference databases. For field verification, I pair the digital map with printed 1:250,000 sheets from the DNPM collection, which sometimes show slight variations due to different revision cycles. The digital versions are fine for initial screening. The printed sheets are worth keeping when you need to mark up field observations directly. The underlying data for these maps comes from a combination of Landsat imagery interpretation, field verification campaigns from the 1960s through the 1980s, and subsequent revisions. The coverage is solid for broad regional work but uneven in remote areas of the northern Amazon, where field verification was limited. If your project falls in those zones, plan for additional field time rather than trusting the domain boundaries without ground truthing.