Atlas · Mauritania
/
Methodologies
METHODOLOGIES
Versions and cumulative updates
New downloads become new dataset versions; the old ones stay, and changes are listed.
Atlas is built so that updating never destroys history.
- Check. A scheduled job asks each source whether anything changed (record counts, edit dates, checksums).
- Download. Changed layers are downloaded as a new dated snapshot; unchanged layers are reused.
- Import as version N+1. The old version stays; the new one becomes "current".
- Compare. Records are matched by source id and listed as added, changed or removed in the What Changed page.
- Re-run the analysis. Recommendations and briefs are regenerated from the new data.
Schedule. Weekly checks and monthly refreshes are planned for after go-live. Until then each source is current to the date it was downloaded, shown on its dataset page.
Global Mangrove Watch releases new years roughly annually; Atlas adds them as new epoch datasets rather than overwriting.
Limits. The scheduled jobs are not running yet.
Related reading
More in Methodologies
- How the data-quality score is calculated
- Spatial statistics: Moran's I and Getis-Ord Gi*
- Net change versus gross loss and gain
- Proximity to pressures
- How units are harmonised on import
- The rules behind recommendations
- Carbon assumptions used in scenarios
- Why Atlas totals are 2.3% higher than the official figures
Still have a question?
The AI analyst answers from these articles and from the data.
Ask Atlas