Articles | Volume 18, issue 5
https://doi.org/10.5194/essd-18-3147-2026
© Author(s) 2026. This work is distributed under the Creative Commons Attribution 4.0 License.
A comprehensive database of thawing permafrost locations across Alaska: version 2.0.0
Download
- Final revised paper (published on 12 May 2026)
- Preprint (discussion started on 11 Nov 2025)
- Supplement to the preprint
Interactive discussion
Status: closed
Comment types: AC – author | RC – referee | CC – community | EC – editor | CEC – chief editor
| : Report abuse
-
RC1: 'Comment on essd-2025-557', Anonymous Referee #1, 25 Jan 2026
- AC1: 'Reply on RC1', Hailey Webb, 30 Mar 2026
-
RC2: 'Comment on essd-2025-557', Anonymous Referee #2, 04 Mar 2026
- AC2: 'Reply on RC2', Hailey Webb, 30 Mar 2026
Peer review completion
AR – Author's response | RR – Referee report | ED – Editor decision | EF – Editorial file upload
AR by Hailey Webb on behalf of the Authors (09 Apr 2026)
Author's response
Author's tracked changes
Manuscript
ED: Referee Nomination & Report Request started (10 Apr 2026) by Achim A. Beylich
RR by Anonymous Referee #2 (24 Apr 2026)
ED: Publish as is (25 Apr 2026) by Achim A. Beylich
AR by Hailey Webb on behalf of the Authors (04 May 2026)
The authors present a comprehensive compilation of evidence for abrupt and non-abrupt permafrost thaw in Alaska, integrating 19,540 locations from 44 diverse sources spanning seven decades. In addition, the authors use the database to evaluate existing permafrost maps and to explore the spatial patterns of the two types of thaw using auxiliary data. Given the significance of abrupt permafrost thaw for both local and global effects, combined with the current lack of regional-scale datasets for land managers, the database represents a unique and valuable contribution that will be useful to a broad audience.
Prior to publication, the following issues must be addressed:
Figure quality and consistency needs to be increased (see specific comments below)
Some of the discussion material focused on abrupt thaw impacts should be moved to the introduction or removed
The available inventory of permafrost thaw features is limited not only by where abrupt thaw is taking place, but also possibly by where investigations are being made. You touch on this point in L367-L372. Can you also comment on how the violation of the assumption of 'random sampling' might affect the results of your statistical tests, and which regions, if any, you think might be overrepresented
Specific manuscript comments
L66-68 In the beginning of paragraph 2, the contrast to gradual thaw should also be stated in terms of impacts. The comparison of cm/yr (rate of change) vs (duration and impact) for abrupt thaw could be made more commensurate
L86: "events": but items listed in parentheses are landforms/features. Is the 'event' the initiation of these features?
L116: how were lines converted to points?
L124: consider rephrasing for clarity: "we have not manually verified each individual feature, but rather the features in the database reflect the accuracy of their source datasets" or something
L125: "lacking validation data of" -> "lack of validation data for"
L127: what are the ongoing opportunities for community feedback?
L127: Rather than asserting that it is an effective means, you could state that by providing accuracy, the reliability and limitations of the dataset are provided transparently. Separately, you can comment on community feedback (being specific) and opportunities for continued improvement.
L146: This section could be reworded for clarity: "We chose not to ... case for all areas"
Figure 1: This figure needs to be cleaned up:
- the resolution of this image should be increased.
- There is a problem with the "intermontane boreal" legend item in 1b
- The titles are redundant - information is in caption and legend.
- the grid lines in the viscinity of the legend are not oriented correctly
- while not essential, an outline of the Alaska state border (for consistency with other figures) and/or a map of neighbouring territories would improve the figure
Figure 2: The resolution of this image should be increased, or converted to a vector format.
Sec. 3.3: There appears to be significant spatial structure in Figure 4, suggesting that the mapping 'errors' may represent a systematic bias rather than random mapping resolution mismatch. Can you comment on where these discrepencies tend to occur and how that information could be used to better interpret the maps.
Figure 3: histogram titles are redundant. Information is in axes and caption. Change axis label from 'elevation' to 'relative elevation'
Figure 5 & caption: Rather than call the left hand colour blue/green, please use a colour with a less ambiguous name.
- clarify in figure caption that agreement is based on your aggregated high-mid class
- figure title is unnecessary
Figure 6 caption: typo "independent"
Figure 6: Text titles are redundant (e.g. "Non-ice-dependent abrupt thaw proecesses"
Figure 6: for greater visual clarity, consider reducing the marker point size in this and other maps.
L347: "three military training lands in the U.S. Army Fort Wainwright " is this correct?
L353-364: this could be tightened up. L353-358 in particular is more suitable for the introduction.
Comments on dataset and repository:
1. versioning of dataset: consider including v2.0.0 or v2 in paper title, it is easy to miss in the abstract.
2. I would strongly recommend using tagged commits in git (you could also put version number in a file) instead of separate directories for versioning. Similarly, using a generic name for your files (e.g. Alaska_Permafrost_Thaw_Database.csv) will make it easier to maintain workflows as more contributions are added and the version number changes. Your scripts could then read the version file to embed the version into the geojson, if necessary.
3. In the two csv files, be consistent with column naming (e.g. DataSourceType vs DtSrcTy) and with style (e.g. all in lowercase_with_underscores / snake_case or all with FirstLetterCapitalized / PascalCase). It will make it easier for people to use the dataset.
4. Add a unique identifier for each feature: FeatureName may not be unique as more data are added.
5. There appear to be duplicated columns between the two csv files (Thaw_Database and Topographic_Variables). Why not just merge these into a single file?
6. The topographic variables file does not seem to be mentioned in the paper. If multiple files are included in the dataset, please ensure the directory tree is well described.