Thanks for your interest in the Allen Coral Atlas! Here you will find helpful resource material for using the Atlas, technical documents and explanations, an FAQ section, and contact information for the Atlas team.
Materials on how to use our datasets, learning about our data, and other relevant information related to remotely sensed coral reef data.
Resources on how you can use the Atlas and its products, and how to collect supporting data that will aid our initiative
Allen Coral Atlas Tutorial
Allen Coral Atlas Mapping Class Descriptions
Comparison of the Atlas to UNEP WCMC's global coral reef data set
Provide benthic verification data
Overview of Allen Coral Atlas Photo Transect Protocol
Have data you want to share? Get in touch at firstname.lastname@example.org
Detailed explanation of how to download Allen Coral Atlas data
Tutorials for more technology-savvy users of our data
Third-party resources for furthering your knowledge of remote sensing, Geographic Information Systems (GIS), use cases for Allen Coral Atlas data, and other habitat data sets.
Introduction to Mapping and Remote Sensing for Coral Reef Conservation. Developed by the Nature Conservancy and the National Geographic Society
USAID's Sustainable Ecosystems Advanced (SEA) Project review of the Atlas's uses in Indonesia
GIS external resources
National Geographic Society's Mapping and Data Resources (55KB download)
University of Queensland Remote Sensing Research Centre's Remote Sensing Toolkit
Overview of how the Allen Coral Atlas supports the Sustainable Development Goals (SDGs)
A sampling of webinars and trainings about the Allen Coral Atlas, presented to varying audiences
Coral Triangle Initiative Allen Coral Atlas Presentation August 2020
Joint Nature Conservation Committee presentation September 2020
SPREP October 2020
Literature written about the methodologies used and products created for the Atlas
Are you using data from the Allen Coral Atlas as part of your scientific research, report, spatial planning or similar? Fabulous! Please make sure to cite us with the following information.
For media, data publications, WMS, API, web-based stories, screenshots, and quoting directly from the website please use the following citation:
Allen Coral Atlas maps, bathymetry and map statistics are © 2018-2022 Allen Coral Atlas Partnership and Arizona State University and licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
For research publications:
Allen Coral Atlas (2022). Imagery, maps and monitoring of the world's tropical coral reefs. doi.org/10.5281/zenodo.3833242
For satellite images obtained from the Allen Coral Atlas website at www.allencoralatlas.org, use the following citation:
The Satellite Coral Reef Mosaic is © 2022 Planet Labs and licensed CC BY-SA-NC 4.0 (https://creativecommons.org/licenses/by-nc-sa/4.0/)
For screenshots of the Allen Coral Atlas, use the following citation:
Image credit: Allen Coral Atlas
NOAA Coral Reef Watch has specific recommendations for Coral Reef Watch Data and Product Citation, described in more detail in our Science & Methods section.
Protected Planet’s marine protected area data should be cited as:
UNEP-WCMC and IUCN (2022), Protected Planet: The World Database on Protected Areas (WDPA), February 2022, Cambridge, UK: UNEP-WCMC and IUCN. Available at: www.protectedplanet.net.
Marine Regions' national maritime boundary data should be cited as:
Flanders Marine Institute (2022): MarineRegions.org. Available online at www.marineregions.org. Consulted February 2022.
Some other data on the Atlas website is copyright by the data providers (e.g., Open Street Map) and requires proper attribution if reused.
We created the Allen Coral Atlas to fill data gaps in coral reef mapping, to help better inform reef management and research, and to help people take conservation action, following Paul G. Allen’s dream.
Paul G. Allen was an avid diver, traveling the world to explore new areas and sea life. While planning a dive at one of his favorite reef diving spots, his team informed him that the reef had recently died and he should no longer dive there. As a technology leader and philanthropist, Mr. Allen assembled some of the best scientists, advocates and remote sensing technologists to build a tool that would do three things:
He knew that only by filling data gaps about existing coral would scientists, NGOs and lawmakers be able to make those necessary decisions to giving coral reefs a fighting chance.
The Allen Coral Atlas was conceived and funded by the late Paul Allen’s Vulcan Inc. and is managed by the Arizona State University Center for Global Discovery and Conservation Science. Along with partners from Planet, the University of Queensland, and the National Geographic Society, the Atlas utilizes high-resolution satellite imagery and advanced analytics to map and monitor the world’s coral reefs in unprecedented detail. These products support coral reef science, management, conservation, and policy across the planet.
Please don’t! We wouldn’t want you to run aground.
The benthic layer includes areas <10m in depth. The geomorphic layer includes areas <15m in depth.
No, the Atlas does not have the spatial and spectral image resolution nor the mapping method to accurately make these types of classifications or assessments. Other data layers would be needed to make determinations about coral health, and a much higher resolution would be necessary to identify species of corals.
Consider using other web-based platforms such as DataMERMAID that hosts the Atlas’ data layers, as well as other relevant datasets that may address these features in your area of interest.
With the download feature available on the Atlas, you can combine our data layers with other geospatial data in your own GIS platform.
There are a few possible reasons your area of interest isn’t mapped. It is possible that your area of interest is outside of the scope of the Atlas, above 30degrees North or below 30degrees south latitude, or in deeper water.
If your area is within the latitude and longitude bounds and within the depth abilities of the Atlas but is not mapped, your area of interest may have been too turbid, or otherwise obscured, for the mapping process. Try looking at the satellite imagery with data layers turned off to see if the reef area is turbid. You can also switch the satellite imagery to “Analytic Mosaic” - it can show what may have been obscuring your area of interest, because the analytical mosaic has been used for the actual mapping.
In the type of satellite imagery currently being used for mapping, coral and the algal forms growing on reefs “look” highly similar and it is difficult to separate them, hence the combined class, especially at a regional scale mapping approach. The microscopic algae that lives inside the living coral has similar concentrations of chlorophyll-A that fleshy algae, growing on top of dead corals, has. This gives them similar spectral reflectance signatures, making them difficult, if not impossible, to differentiate with the technologies we are using for the Atlas project. We’re investigating routes to differentiate these in the future.
Follow our step-by-step guide for data downloads.
You can either draw a polygon around your country manually, or upload an EEZ boundary. To do this, download the EEZ boundary for the country you're interested in (we recommend Marine Ecoregions) as a KML or geojson. After logging into your account on the Atlas, go to the “My Areas” section and find the “Upload” button. Upload your EEZ boundary file. You will see it form a polygon around the country. Save this area to “My Areas” then follow the steps to download the data from an area of interest.
During the download process you have options of which data layers to include. You can opt for:
Download size will depend on the size of the polygon and the layers you have opted to include. The Southwest Pacific region map (20,000 km2) and depth download is about 100GB, and is 300GB with satellite imagery.
Downloads are available for 30 days after they are created.
Yes. Find the upload button under “My Areas.” Here you can upload a geojson or KML file that will bring up a polygon onto the Atlas platform. It will be saved under your “My Areas” section.
You can! To save an area this large, or download data of any size, you need to create a free login. Follow the prompt to log in, and then click "Don't have an account? Register for free" if you don't already have one. Large datasets may take some time to generate, therefore with a free account, we will notify you via email when your dataset is ready. Most files take between a few minutes and a few hours to generate, but may take up to a day for very large requests.
Yes! All of our habitat map data and global statistics are available in a single ZIP archive. Note that this archive represents the habitat map data as of October 6th, 2021 and does not reflect any map updates we have published since then. Be aware that the archive is nearly 14 gigabytes in size.
The Atlas does not include maps of mangroves. However, Global Mangrove Watch is an excellent resource available for global spatial data of mangroves.
Seagrass is a class included in the benthic map on the Atlas, but is only included when the feature is part of a coral reef.
Yes. Bathymetry data is available for download only.
Reproduction or publication of the entire global dataset of habitat maps is prohibited without the prior written consent of the Allen Coral Atlas leadership team at Arizona State University.
Tips for using these services can be found here.
There is also an API endpoint to return metadata about the habitat maps:
When you use the search feature in the Atlas, we build your results from three sources.
The overall map accuracy is between 60-90% and varies per region mapped. Accuracy is influenced by environmental characteristics (e.g. habitat complexity, water depth, turbidity) and the quality of the analytical image mosaic, satellite derived water depth, and reference data set used for training and validation.
The accuracy is calculated by comparing the mapped classes for many small areas with a validation data set for the same area (see Roelfsema et al 2013). The validation data set is different from the training data as the latter is only used for the classifier to create the map. Validation data and training data are derived from a reference sample set create with the help of expert knowledge, image interpretation existing field data and maps (See Roelfsema et al 2021).
Roelfsema C.M. and S.R. Phinn (2013) Validation Chapter 14, In: Coral Reef Remote Sensing: A Guide for Multi-level Sensing Mapping and Assessment. Goodman, J., Purkis, S. and Phinn, S.R. Springer Publishing pp375-365 ISBN 978-90-481-9291-5
Roelfsema, C. M., M. Lyons, N. Murray, K. E., E. Kennedy, K. Markey, R. Borrego-Acevedo, A. Ordonez Alvarez, C. Say, P. Tudman, M. Roe, J. Wolff, D. Traganos, G. Asner, B. Bambic, B. Free, Z. Lieb, H. E. Fox and R. S. Phinn (2021 soon to be published). "Workflow for the generation of expert-derived training and validation data: A view to global scale habitat mapping." Frontiers in marine Science: Special Issue Remote Sensing for Applied Coral Reef Science and Management.
Errors may be due to cloud cover or turbidity blocking the image, a masking issue, or because of the limitations of the semi-automated machine learning algorithm.
First, turn off the benthic or geomorphic map layer and turn on the “Analytic Mosaic” satellite imagery layer to see the imagery used for the actual mapping. Look for what features may be obscuring your area of interest. Turbidity or cloud cover visible in the imagery may be obscuring the reef area, or another artifact may be blocking the image.
Additionally, some areas may have an issue with land masking or deep water masking. If you see map classifications appearing on land or in very deep water, this is likely due to an issue with the land or deep water mask.
Quality of analytical low tide image mosaic used for mapping
Other artifacts could be present that are natural such as thin cloud cover or rough seas, or artificially created through in the preprocessing step of the low tide image mosaic. The mosaic used is a composition of many small scenes captured at the lowest tide and cloud free, that are then stitched together almost seamlessly.
Quality of satellite derived depth
The depth is derived from a composite of best available satellite imagery. This is predominantly Sentinel 2 and Landsat 8 imagery due to their high signal-to-noise ratio, with some remote regions of the world filled in with Planet Dove imagery. The depth is best derived for clear waters where bottom feature can be differentiated. Hence, when water is not as clear, or has disturbances (artifacts), errors in depth will occur that can have an effect on the ability to distinguish classes.
Limitations of the semi-automated mapping algorithm
It is important to bear in mind that the maps are created with a semi-automated machine learning algorithm and cleaned up with an object based analysis approach. The algorithm labels certain features based on the availability and quality of the data utilized during the mapping process. The maps are created and validated for whole reef systems across countries and not focused on a small set of reefs. For some areas we only have limited reference data available or the data is dependent on expert interpretation only. A map generated in this way may not be as accurate as a very localized map created with extensive surveys over a small area, but it does allow for mapping on a much larger scale and globally consistent basis.
If you are finding significant errors, please contact us with a description of the issue to email@example.com. Directions for submitting feedback are in the Contact Summary section below.
While many localized errors cannot be immediately corrected on the Atlas, it is always possible to download the data for your local area and alter the data layers in your own GIS platform to reflect additional local data or knowledge you have.
We welcome your feedback!
As this is an evolutionary process, and the Allen Coral Atlas is in a beta stage, the maps and monitoring data may have issues, some of which we are aware of, others we’d love to have you report to us so we can triage what we can and cannot resolve.
Please submit any identified errors with suggested corrections to firstname.lastname@example.org including: Reef name(s); coordinates and/or a georeferenced polygon (in kml, shapefile, or JSON format); screen shots from the Atlas of relevant area (annotated with details), explanation of the error and your suggestion for correcting it/them; any relevant field data; your contact details.
We triage the feedback and, if possible, especially when its returning error, determine if it can be solved by adjusting the semi automated mapping process. Some errors can not be resolved as a result of the constraints of the mapping approach and input dataset used.
With ongoing accessibility of new, more and better satellite sensors next to further developments in mapping and masking routines, theoretically any new data could be integrated in improving and updating existing versions of maps for some mapping regions. However this will depend on available resources for the Atlas project.
If you have georeferenced data for a region on the Atlas, we may be able to utilize it for our ongoing revisions to the maps. Please get in touch with us at email@example.com or contact a member of the Atlas team.
Periodically, we will publish updates to the maps you find on the Atlas based on feedback we have received or improvements to the mapping algorithm. The most recent publication dates of all of our maps can be found here.
The dates of the source imagery for all of our maps can be found here.
How to contact us…
firstname.lastname@example.org - email us here to contribute data sets or to inquire about the types of datasets we are able to utilize
email@example.com - email us here for help with using the Atlas, our API, or other questions related to the tools
firstname.lastname@example.org - write to us with any errors or issues you see on the Atlas. To submit an error or correction, please include at minimum:
The URL at the location where you see the issue
A description of the issue you see
If available, please also include:
Screenshots and/or marked-up image of the issue
Any available data or existing map to support the proposed correction