How Global Mangrove Watch maps are made
Satellite pixels are classified as mangrove, cleaned, and compared across years to find change.
Atlas does not make these maps; it stores, measures and explains them. Understanding how they are made tells you how far to trust them.
Steps (simplified)
- Baseline extent. A reference map of where mangrove is, built by classifying satellite imagery with training samples and a mask of areas where mangrove can occur (coastal, tropical, low-lying).
- Change detection. Each year's imagery is compared with the baseline; pixels that persistently change are flagged as loss or gain.
- Time series. Yearly maps are produced by applying the changes to the baseline.
- Vectorisation. Mangrove pixels are joined into polygons; v4.1 adds a country label to each polygon.
- Validation. The authors check the maps against independent reference samples and publish accuracy results in the scientific papers. Read the paper before citing precision.
What it means for you. Errors are most likely: at forest edges; in narrow creeks; for small patches; where mangrove is mixed with other vegetation; and in cloudy regions for optical years.
In Atlas every polygon is stored with its source id, its area is recalculated on the ellipsoid, and the original archive file is kept with a checksum.
Related reading
More in Methodologies
- Geodesic area and perimeter
- How features are assigned to countries
- Carbon assumptions used in scenarios
- Why Atlas totals are 2.3% higher than the official figures
- Provenance, checksums and the archive
- Fragmentation metrics
- Net change versus gross loss and gain
- How carbon project locations are established and checked
Still have a question?
The AI analyst answers from these articles and from the data.
Ask Atlas