Peer Review History

Original SubmissionNovember 2, 2021
Decision Letter - RunGuo Zang, Editor

PONE-D-21-34995The use of spatial data and satellite information in legal compliance and planning in forest managementPLOS ONE

Dear Dr. Lindenmayer,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

==============================

ACADEMIC EDITOR: please make the framing of the work more clearer and clarify the data used.Please ensure that your decision is justified on PLOS ONE’s publication criteria and not, for example, on novelty or perceived impact.

For Lab, Study and Registered Report Protocols: These article types are not expected to include results but may include pilot data. 

==============================

Please submit your revised manuscript by Mar 26 2022 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.
  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.
  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols. Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols.

We look forward to receiving your revised manuscript.

Kind regards,

RunGuo Zang

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at 

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and 

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. We note that Figures 1, 6, 7 and 8 in your submission contain map images which may be copyrighted. All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For these reasons, we cannot publish previously copyrighted maps or satellite images created using proprietary data, such as Google software (Google Maps, Street View, and Earth). For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright.

We require you to either (1) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (2) remove the figures from your submission:

1. You may seek permission from the original copyright holder of Figure 1, 6, 7 and 8 to publish the content specifically under the CC BY 4.0 license.  

We recommend that you contact the original copyright holder with the Content Permission Form (http://journals.plos.org/plosone/s/file?id=7c09/content-permission-form.pdf) and the following text:

“I request permission for the open-access journal PLOS ONE to publish XXX under the Creative Commons Attribution License (CCAL) CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). Please be aware that this license allows unrestricted use and distribution, even commercially, by third parties. Please reply and provide explicit written permission to publish XXX under a CC BY license and complete the attached form.”

Please upload the completed Content Permission Form or other proof of granted permissions as an "Other" file with your submission.

In the figure caption of the copyrighted figure, please include the following text: “Reprinted from [ref] under a CC BY license, with permission from [name of publisher], original copyright [original copyright year].”

2. If you are unable to obtain permission from the original copyright holder to publish these figures under the CC BY 4.0 license or if the copyright holder’s requirements are incompatible with the CC BY 4.0 license, please either i) remove the figure or ii) supply a replacement figure that complies with the CC BY 4.0 license. Please check copyright information on all replacement figures and update the figure caption with source information. If applicable, please specify in the figure caption text when a figure is similar but not identical to the original image and is therefore for illustrative purposes only.

The following resources for replacing copyrighted map figures may be helpful:

USGS National Map Viewer (public domain): http://viewer.nationalmap.gov/viewer/

The Gateway to Astronaut Photography of Earth (public domain): http://eol.jsc.nasa.gov/sseop/clickmap/

Maps at the CIA (public domain): https://www.cia.gov/library/publications/the-world-factbook/index.html and https://www.cia.gov/library/publications/cia-maps-publications/index.html

NASA Earth Observatory (public domain): http://earthobservatory.nasa.gov/

Landsat: http://landsat.visibleearth.nasa.gov/

USGS EROS (Earth Resources Observatory and Science (EROS) Center) (public domain): http://eros.usgs.gov/#

Natural Earth (public domain): http://www.naturalearthdata.com/

3. We note that you have stated that you will provide repository information for your data at acceptance. Should your manuscript be accepted for publication, we will hold it until you provide the relevant accession numbers or DOIs necessary to access your data. If you wish to make changes to your Data Availability statement, please describe these changes in your cover letter and we will update your Data Availability statement to reflect the information you provide.

Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice.

Additional Editor Comments (if provided):

please revise the ms according to the concerns of the reviewers.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

Reviewer #2: Yes

**********

3. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

**********

4. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

**********

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: This is an interesting paper which presents a very detailed applied study concerning the application of digital terrain analysis, specifically topographic slope angle, to forest management prescriptions. The results are novel in terms of the context, namely, the efficacy of differently grained DEMs and the slope derivative to inform the monitoring and evaluation of forest management prescriptions designed to protect water catchments. The paper presents an extremely thorough empirical analysis as well as providing an in-depth discussion of the practical relevance of the results. The paper warrants publishing in PLOS ONE subject to a minor revision to take account of the following points.

L60 - “isn’t” should be “is not”

L62 – remove brackets as this is a key point, not an aside

L72 does “best” = “most cost effective”? What are criteria for assessing what is “best” here?

L74 – strictly speaking a DEM is not remote sensing data. It is a spatial data layer modelled from a satellite-based or otherwise air-borne active sensor.

L77-78 – this sentence needs to be rewritten to make clearer the meaning given it is the basis for the relevance of the paper’s analyses.

L 105-108, 109-112 – these read more like conclusions, rather than introductory statements, as they are anticipating the results.

L 192 – how was slope calculated in Arc GIS? I.e. different functions can be used to calculate gradients in the X and Y direction.

L221 – can the authors clarify that there were Lidar shots for every grid cell? If not, then some interpolation would have been required.

L224 – was there a rationale behind the class intervals?

L268 – it is not clear why you would need to test for spatial autocorrelations given all the data being analysed are DEMs on a regular grid, it is not clear why autocorrelation would be an issue?? What was the autocorrelation of concern?

L346 – I think the differences between the values of the differently scaled slope grides are better described as differences and not errors. I say this because slope can be accurately calculated at a range of scales for the same location and differ in their values.

L360 - clarify that this result was found from all three scaled slope grids, or if not, which scale was used.

General comments:

1. It would be helpful if the authors could clarify if all three scales are relevant to the scale at which the forest management guidelines are intended to be applied. For example, I don’t think that forest management prescriptions are meant to be applied at a 1m resolution. Wouldn’t the appropriate scale of analysis be the slope calculated at a scale that captures the variation within a logged coup; which I assume is equivalent to what the authors call a cut block? In any case, some discussion is warranted of the scale at which slope is calculated compared with the scale at which forest management prescriptions are applied. It is not clear from the methods what the scale of the neighbourhood analysis used to calculate slope (e.g. 3x3 moving window?), so perhaps this point could be dealt with by providing further details in that section? This also applies for the field measurements form the transects. It is not clear how slope was calculated along the 12-32.5m long transects (was the entire length of the transect used?) nor how this scale related to the scale at which forest management prescriptions are intended to be applied in a forest block.

2. If length is an issue for the editor, the section titled "Comparisons with analysis of steep slopes by VicForests" could be edited back as it provides a lot of detail about the authors communications with the agency which is not essential to the paper's important findings.

Reviewer #2: This study addresses an important aspect of environmental management that is open to misuse, clarifying critical details with sound data. It’s important that it is published, but I think it could be improved with some minor changes.

The main issue is that the framing of the study needs to be clearer. Given that DEMs have been use for decades for similar purposes, it’s unclear why this is an important question until the reader reaches the Discussion. The core of it is in line 564, where the OCR claimed that these DEMs overstated the slope. I think that needs to be up-front in the Intro – concerns have been expressed that DEMs overstate the slope.

A second although not essential issue is that the paper would be stronger if it investigated a mechanism, so that the findings are more widely applicable. I can see two possible options from the findings:

1. Lower resolution DEMs (larger cells) smooth the landscape by averaging the contents of the cell. Where there is greater change in slope within a cell (eg gullies), you could expect the DEM to underestimate the slope (eg the 30m DEM).

2. The accuracy of point heights used in a DEM can cause errors in slope calculations, but unless such errors have a systematic trend, this should just create noise rather than bias (eg the 10m DEM)

You could either test these as hypotheses or summarise them as key findings.

Other minor issues:

60: Delete ‘locating’

82: Saying that DEMs are already considered essential seems to conflict with the idea that you’re presenting something novel. That needs to be said in context – “The use of DEMs is essential for forest management planning to identify steep slopes and exclude logging from these areas, however, some have contended that…”

88: Add comma between ‘LiDAR and’

109: Unless this is the primary aim of the paper, maybe state it after the other aim(s). The first of these should be to investigate whether DEMs distort slopes as claimed.

152: Practice, not practices

202-205: Seems to be repeating earlier parts of the paragraph a bit, maybe simplify the paragraph as a whole.

212-214: A minimum patch size should be clearly specified that breaches the code. If there is no published value, make this clear and say that you’re using 5m because there isn’t a standard. That could also feed into the Discussion, highlighting that systems are open to abuse if no patch size has been specified.

272: Drop the final ‘the’

367: ‘Consisted of’ implies that it was all 1m patches. Perhaps change to ‘included’.

468: Lose the period after the first ‘the’

568-570: This is the core finding and is important. I’d open the results with this.

630ff: It’s unclear how this section fits the paper overall. While they seem like questionable actions, I’d only include them if you can show clearly how they breach your findings.

683: Such ‘data’

701: “compliance with laws preventing logging on steep slopes is require[d]”

**********

6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step.

Revision 1

Professor David Lindenmayer

Dr Chris Taylor

Fenner School of Environment and Society

The Australian National University

Canberra, ACT, 2601

4 March 2022

Re: Revisions to PONE-D-21-34995 - The use of spatial data and satellite information in legal compliance and planning in forest management

Dear Professor RunGuo Zang,

We enclose our substantially revised paper PONE-D-21-34995 - The use of spatial data and satellite information in legal compliance and planning in forest management for re-consideration for publication in PLOS ONE.

We have used the comments of the two referees to help guide our revisions – and these changes have helped further strengthen the paper. In the remainder of this letter we provide a point-by-point response to each of the comments of both reviewers.

We trust that this letter and our revised manuscript will be received favourably and look forward to hearing from you in the near future.

Yours sincerely,

David Lindenmayer

(on behalf of both authors)

COMMENTS FROM REVIEWERS

Comments from Reviewer #1:

This is an interesting paper which presents a very detailed applied study concerning the application of digital terrain analysis, specifically topographic slope angle, to forest management prescriptions. The results are novel in terms of the context, namely, the efficacy of differently grained DEMs and the slope derivative to inform the monitoring and evaluation of forest management prescriptions designed to protect water catchments. The paper presents an extremely thorough empirical analysis as well as providing an in-depth discussion of the practical relevance of the results. The paper warrants publishing in PLOS ONE subject to a minor revision to take account of the following points.

Response from authors

We thank Reviewer #1 for their very supportive comments. We do recognize that Reviewer #1 has made some insightful comments and we have worked hard to address their suggestions to help improve the manuscript.

********************************

Comments from Reviewer #1:

L60 - “isn’t” should be “is not”

Response from authors

We have corrected this typographical error.

********************************

Comments from Reviewer #1:

L62 – remove brackets as this is a key point, not an aside

Response from authors

We have removed the brackets as suggested.

********************************

Comments from Reviewer #1:

L72 does “best” = “most cost effective”? What are criteria for assessing what is “best” here? Response from authors

We have replaced the term “best” with most cost-effective as suggested by Referee #1.

********************************

Comments from Reviewer #1:

L74 – strictly speaking a DEM is not remote sensing data. It is a spatial data layer modelled from a satellite-based or otherwise air-borne active sensor.

Response from authors

This was a fair point made by Reviewer #1 and we amended the text to reflector this fact.

********************************

Comments from Reviewer #1:

L77-78 – this sentence needs to be rewritten to make clearer the meaning given it is the basis for the relevance of the paper’s analyses.

Response from authors

We have reworked the sentence as requested by Reviewer #1.

********************************

Comments from Reviewer #1:

L 105-108, 109-112 – these read more like conclusions, rather than introductory statements, as they are anticipating the results.

Response from authors

As suggested by Reviewer #1, we have now removed the text on Lines 109-113 as they did indeed anticipate the results.

********************************

Comments from Reviewer #1:

L 192 – how was slope calculated in Arc GIS? I.e. different functions can be used to calculate gradients in the X and Y direction.

Response from authors

The ArcGIS Slope tool accounts for slope gradients in both the x and y directions. We have now made this clear in our text.

********************************

Comments from Reviewer #1:

L221 – can the authors clarify that there were Lidar shots for every grid cell? If not, then some interpolation would have been required.

Response from authors

We generated LiDAR DEM from the LAS files to a 1 metre grid raster in ArcGIS. The point separation ranged between 10 cm to 25 cm. Where cells did not have points, we triangulated across void areas and used linear interpolation on the triangulated value to determine the cell value (ESRI 2021). We have now added this to our text.

Reference

ESRI (2021), LAS Dataset To Raster, https://desktop.arcgis.com/en/arcmap/latest/tools/conversion-toolbox/las-dataset-to-raster.htm, accessed 24 February 2022

********************************

Comments from Reviewer #1:

L224 – was there a rationale behind the class intervals?

Response from authors

The class intervals used in our analysis were based on the Absolute Risk Rating Methodology previously used in the Forest Audit Program for the Victorian Government (URS Australia 2011). We have now added this this to our text.

Reference

URS Australia (2011), Report Environmental Audit - Forest Audit Program Module 6 - Harvesting Performance, URS Australia Pty Limited.

********************************

Comments from Reviewer #1:

L268 – it is not clear why you would need to test for spatial autocorrelations given all the data being analysed are DEMs on a regular grid, it is not clear why autocorrelation would be an issue?? What was the autocorrelation of concern?

Response from authors

We have removed this section of the paper. Upon review, there were some issues with the spatial autocorrelation because we are analysing individual cutblocks and these are already clustered around access (i.e. roads) and specific forest types.

********************************

Comments from Reviewer #1:

L346 – I think the differences between the values of the differently scaled slope grides are better described as differences and not errors. I say this because slope can be accurately calculated at a range of scales for the same location and differ in their values.

Response from authors

We have removed the term “errors” from our revised manuscript. We have replaced the term with ‘difference’ where relevant. The term ‘error’ is now retained only for our descriptions of guidance provided by the data providers for the datasets themselves, i.e. “For Australia, the horizontal positional error for the SRTM DEM is within 7.2 m and the elevation error is within 9.8 m”. These positional errors were based on in field measurements used in the DEM guidance documents that were used for comparison with the DEMs themselves.

********************************

Comments from Reviewer #1:

L360 - clarify that this result was found from all three scaled slope grids, or if not, which scale was used.

Response from authors

We have now added the following amended text: “The slope raster we generated from LiDAR DEM showing all slopes >30° (including small areas at 1.0m2) indicated that all cut blocks in the Thomson water supply protection area contained slopes >30° and all but one cut block supported slopes >30° in the Upper Goulburn water supply protection area (Table 1).”

********************************

Comments from Reviewer #1:

General comments:

1. It would be helpful if the authors could clarify if all three scales are relevant to the scale at which the forest management guidelines are intended to be applied. For example, I don’t think that forest management prescriptions are meant to be applied at a 1m resolution. Wouldn’t the appropriate scale of analysis be the slope calculated at a scale that captures the variation within a logged coup; which I assume is equivalent to what the authors call a cut block? In any case, some discussion is warranted of the scale at which slope is calculated compared with the scale at which forest management prescriptions are applied. It is not clear from the methods what the scale of the neighbourhood analysis used to calculate slope (e.g. 3x3 moving window?), so perhaps this point could be dealt with by providing further details in that section? This also applies for the field measurements form the transects. It is not clear how slope was calculated along the 12-32.5m long transects (was the entire length of the transect used?) nor how this scale related to the scale at which forest management prescriptions are intended to be applied in a forest block.

Response from authors

This is an important point raised by Reviewer #1. The 2014 Management Standards and Procedures did not specify a minimum area under Clause 3.5 addressing the logging of steep slopes that would constitute a breach. The Office of the Conservation Regulator later provided a description of an average slope as the average slope of the topographic feature of interest that is subject to assessment (Zanini 2020). Again, this did not specify a minimum distance. In the absence of such specification, we used an average moving circle of a 5m radius to calculate an average slope. This used the local neighbourhood tool in ArcGIS called focal statistics. This provided for an average distance of at least 10m in distance on where a steep slope >30° could be identified. This was applied only to the slope raster generated from the LiDAR DEM, because it consisted of a cell size of 1m. This was not applied to the slope raster generated from the VicMap Elevation DTM and the SRTM DEM, because these had a respective cell size of 10m and ~30m, respectively. We contended that these datasets and associated respective cell sizes provide a good indication of where a slope exceeded the limits specified under the Management Standards and Procedures.

********************************

Comments from Reviewer #1:

2. If length is an issue for the editor, the section titled "Comparisons with analysis of steep slopes by VicForests" could be edited back as it provides a lot of detail about the authors communications with the agency which is not essential to the paper's important findings.

Response from authors

This was a fair suggestion from Reviewer #1 and we have reduced the length of this section as suggested.

********************************

COMMENTS FROM REVIEWER #2

Comments from Reviewer #2:

Reviewer #2: This study addresses an important aspect of environmental management that is open to misuse, clarifying critical details with sound data. It’s important that it is published, but I think it could be improved with some minor changes.

Response from authors

We thank Reviewer #2 for their support for our paper. We have used the suggestions of Reviewer #2 to help further strengthen the paper; we are grateful for the insights they have provided.

********************************

Comments from Reviewer #2:

The main issue is that the framing of the study needs to be clearer. Given that DEMs have been use for decades for similar purposes, it’s unclear why this is an important question until the reader reaches the Discussion. The core of it is in line 564, where the OCR claimed that these DEMs overstated the slope. I think that needs to be up-front in the Intro – concerns have been expressed that DEMs overstate the slope.

Response from authors

This was an astute point made by Reviewer #2 and we have now revised part of the Introduction to make it clearer that testing slopes with DEMs is important given claims by the regulator that slopes are overstated.

********************************

Comments from Reviewer #2:

A second although not essential issue is that the paper would be stronger if it investigated a mechanism, so that the findings are more widely applicable. I can see two possible options from the findings:

1. Lower resolution DEMs (larger cells) smooth the landscape by averaging the contents of the cell. Where there is greater change in slope within a cell (eg gullies), you could expect the DEM to underestimate the slope (eg the 30m DEM).

2. The accuracy of point heights used in a DEM can cause errors in slope calculations, but unless such errors have a systematic trend, this should just create noise rather than bias (eg the 10m DEM).

You could either test these as hypotheses or summarise them as key findings.

Response from authors

These are important points. We have added these comments to our discussions.

********************************

Comments from Reviewer #2:

Other minor issues:

60: Delete ‘locating’

Response from authors

We have delete the word “locating” as suggested by Reviewer #2.

********************************

Comments from Reviewer #2:

82: Saying that DEMs are already considered essential seems to conflict with the idea that you’re presenting something novel. That needs to be said in context – “The use of DEMs is essential for forest management planning to identify steep slopes and exclude logging from these areas, however, some have contended that…”

Response from authors

This recommended rewording from Reviewer #2 was very helpful and we have now revised the text to better frame the Introduction.

********************************

Comments from Reviewer #2:

88: Add comma between ‘LiDAR and’

Response from authors

We have corrected this typographical error as identified by Reviewer #2.

********************************

Comments from Reviewer #2:

109: Unless this is the primary aim of the paper, maybe state it after the other aim(s). The first of these should be to investigate whether DEMs distort slopes as claimed.

Response from authors

We agree with Reviewer #2 and removed the final paragraph from the reframed Introduction section.

********************************

Comments from Reviewer #2:

152: Practice, not practices

Response from authors

We have corrected this typographical error.

********************************

Comments from Reviewer #2:

202-205: Seems to be repeating earlier parts of the paragraph a bit, maybe simplify the paragraph as a whole.

Response from authors

We carefully examined the length of this paragraph as recommended by Reviewer #2. However, shortening it would have deleted key details on the spatial data approach that we employed and would have become confusing to readers.

********************************

Comments from Reviewer #2:

212-214: A minimum patch size should be clearly specified that breaches the code. If there is no published value, make this clear and say that you’re using 5m because there isn’t a standard. That could also feed into the Discussion, highlighting that systems are open to abuse if no patch size has been specified.

Response from authors

This issue was also identified by Reviewer #1. We have added additional text in our Methods section clarifying that the 2014 Management Standards and Procedures did not specify a minimum area threshold for steep slope measurements and the subsequent guidance provided by the OCR, while providing further clarification, also did not specify a minimum threshold. We used a 5m radius for a moving average across our analysis area would identify areas upon where an average slope was >30°. This is based on our own contentions.

********************************

Comments from Reviewer #2:

272: Drop the final ‘the’

Response from authors

We have amended the text as suggested by Reviewer #2.

********************************

Comments from Reviewer #2:

367: ‘Consisted of’ implies that it was all 1m patches. Perhaps change to ‘included’.

Response from authors

We have changed the text to use the word “included” as suggested by Reviewer #2.

********************************

Comments from Reviewer #2:

468: Lose the period after the first ‘the’

Response from authors

We have corrected the text.

********************************

Comments from Reviewer #2:

568-570: This is the core finding and is important. I’d open the results with this.

Response from authors

This was a good suggestion from Reviewer #2 and we have now re-ordered the sequence of key findings in the Results section to include this core finding.

********************************

Comments from Reviewer #2:

630ff: It’s unclear how this section fits the paper overall. While they seem like questionable actions, I’d only include them if you can show clearly how they breach your findings.

Response from authors

This section is important because it highlights that statements by Victorian Government agencies that only limited areas above 30 degrees in slope have been logged are inconsistent with the spatial data that we have presented. However, we recognize that both referees considered this section was too long and we have now reduced the length of the text in this section considerably.

********************************

Comments from Reviewer #2:

683: Such ‘data’

Response from authors

We have corrected the text.

********************************

Comments from Reviewer #2:

701: “compliance with laws preventing logging on steep slopes is require[d]”

Response from authors

We have corrected this typographical error.

********************************

Attachments
Attachment
Submitted filename: Submission_Response to reviewers.docx
Decision Letter - RunGuo Zang, Editor

The use of spatial data and satellite information in legal compliance and planning in forest management

PONE-D-21-34995R1

Dear Dr. Lindenmayer,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

RunGuo Zang

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

accept

Reviewers' comments:

Open letter on the publication of peer review reports

PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.

We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.

Learn more at ASAPbio .