aceModerate evidence
Published recordClimateProblem Space
More
Advancing climate resilience through artificial intelligence: A comprehensive review across urban and climate-sensitive sectors in Morocco
- Truvace record
- TRV-2026-2597raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Systematic review or meta-analysis
- Sources
- 1 sourcePeer-reviewed
- sha256
- f990eef39035…check it
Climate change poses significant challenges to Morocco, which is increasingly affected by desertification, recurrent droughts, rising temperatures, and water scarcity. These impacts threaten climate-sensitive sectors such as agriculture, water resources, energy, urban planning, and environmental management, highlighting the urgent need for innovative and data-driven resilience strategies. In this context, artificial intelligence has emerged as a promising tool for strengthening prediction, planning, risk managem…
The problem
A review of 80 publications from 2020–2025 found that Morocco's climate-resilience AI research is limited by sparse ground observations, restricted institutional data, limited spatial transfer testing and minimal explainable AI, constraining reproducibility and operational uptake.
What this doesn’t fix
The review found that sparse ground data, limited spatial transfer testing and minimal explainable AI constrained how reproducible and deployable the reviewed AI applications were.
Sources
1 on file- City and Environment Interactionsdoi:10.1016/j.cacint.2026.100461
Cite this record
v1Truvace Impact Record TRV-2026-2597, v1: “Advancing climate resilience through artificial intelligence: A comprehensive review across urban and climate-sensitive sectors in Morocco.” Truvace, 2026-11-12. /record/TRV-2026-2597 (accessed on the day you copy it). sha256 f990eef39035dc47…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2597 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.