the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
British Antarctic Survey's aerogeophysical data: releasing 25 years of airborne gravity, magnetic, and radar datasets over Antarctica
Tom A. Jordan
Fausto Ferraccioli
Carl Robinson
Hugh F. J. Corr
Helen J. Peat
Robert G. Bingham
David G. Vaughan
Download
- Final revised paper (published on 25 Jul 2022)
- Supplement to the final revised paper
- Preprint (discussion started on 18 Feb 2022)
- Supplement to the preprint
Interactive discussion
Status: closed
-
RC1: 'Comment on essd-2022-49', Anonymous Referee #1, 08 Apr 2022
General comments
This article summarises the main findings of 28 years of aerogeophysical data surveys over Antarctica. It also describes the data acquisition and instrumentation for each of the 24 airborne geophysical surveys, and the data processing applied to the 64 datasets accompanying this article. The authors of the paper also outline the format of the data and the publishing strategy they adopted following the FAIR data principles. They also present a new data portal to download the aerogeophysical data and interactive open access tutorials for displaying and checking the quality of the data. In addition, the authors also discuss the potential for extracting englacial stratigraphy from radar data, and the potential re-use of the BAS aerogeophysical data.
The dataset provided in this compilation is a valuable contribution to the Antarctic scientific community and should prove an extremely useful resource for further exploring the Antarctic Ice Sheet and the underlying geology, for example mapping the internal stratigraphy of the Antarctic Ice sheet (e.g., AntArchitecture). The dataset provided is freely available in a friendly, and easy to use interface aiming to reach a wider community of specialists and non-specialists.
Thanks to the authors for their hard work and all the great job they have done in compiling and publishing the aerogeophysical data from BAS surveys. These data are very valuable to any ice sheet/shelf modeller, and therefore should be published.
There are a few minor comments and suggestions that might help improve the manuscript and the accompanying user guide, such as: citing references in chronological order, shortening long sentences, and being consistent with the proper use of “reflectors” and “reflections”.
In addition, I suggest double check the tutorial provided in Matlab and Python as some minor errors were found in Matlab.
Specific comments
- Introduction
L73: I think it should be “subglacial geology” or “geology underlying the ice”, not both
L75-76: References in chronological order. Please cite references in chronological order throughout the manuscript as well
L84-88: Personally, I think 47 words is a bit too long. Please consider shortening the length of this sentence and other sentences throughout the manuscript (more than 50 words in some sentences). Longer sentences make it harder to follow the main idea
L95: I think it should read “… (hereafter abbreviated to WAIS and EAIS, respectively) …” include a comma after EAIS
L116-117: maybe it would read better “(…) data have been relatively inaccessible to the wider scientific communities (…)” - Background
L142: I’m not sure if the “Figures 2-3 demonstrate (…)” the data have been used progressively; I think the figures show products derived from the aerogephysical surveys instead
L268: Weddell Sea Rift “System” (include System)
L270: I think the sentence “(…) a new digital elevation model of the bed underlying the ice streams of the (…)” would read better as “(…) a new digital elevation model of the subglacial topography around the (…)”
L277: Delete “(…), the product of (…)”
L284-289: It is a bit hard to follow this sentence. Please consider shortening or improving punctuation
L293: please consider enumerating the examples after “…such as”, I think it would help the reader to follow the examples
L326: it reads “(…) and ed picks respectively.” I think a comma is missing “(…) and ed picks, respectively.” - Data acquisition and processing
L347: In this case, maybe the word “Usually” is more suitable than the word “Generally”
L377-378: “When in standard swath mode, all 378 antennae are configured in H orientation with the starboard and belly antennae also in H orientation” is there any reference you could cite maybe?
L381-383: reference?
L436: I think adding commas to the sentence “…ADC cards rather than a digitising scope allowed phase…” so it would read as “…ADC cards, rather than a digitising scope, allowed phase…”
L440-447: It would be useful if you could provide a reference for PASIN1 and PASIN2
L457: in the sentence “…mixed antenna gain path for areas where ice is heavily disrupted where the starboard signal can be…” is the second “where” the word you wanted to use? Maybe the word “and” is more suitable (?)
L459: please consider enumerating the “minor modifications”, so the sentence would read “…reduce noise and improve system operations, including: (1) low-pass filters in the RF switches, (2)…”
L467-471: are there any references you could cite?
L523: is there any key reference for the definition?
L532: I think it reads better as “Additional processing may include the use of masks…”
L568-569: Maybe change “see Table 3” to “see hyperlinks provided in Table 3”
L579: the PASIN system was(?) designed to retain...
L584: I think it reads better “The second step included...” instead of “Following on from this first step,…”
L589: Maybe including a semicolon and a comma, make the sentence easier to follow (?) “…a moving-average window filter used; however, no Synthetic…”
L596: include a comma after “however”
L603: I think is easy to follow as “over West Antarctica. Figure 6a shows…”
L607-608: Maybe use “. In contrast” instead of “however” (?)
L622: delete “Note that”
L625: is there a missing word after “…such as…”?
L626: maybe “Additional techniques, to prevent misinterpretation of the ice thickness, have also…” reads better (?)
L627: delete “and thus may affect ice thickness estimates”. Also, consider adding “it has been” after “…, as…” so it reads “, as it has been previously…”
L631-632: Is “reflector” the word you want to use, or maybe “reflection”? Also, please consider deleting “…on from the processing the…” and “the last step was to “pick” the”, so it reads “Following radar data processing, bed and ice surface reflections were picked”
L632: delete “It is worth stating that”
L638: delete “. This was”
L639: “reflector” or “reflection”?
L641: “reflector” or “reflection”?
L643-650: please consider rephrasing this paragraph
L661-664: Please consider rephrasing this paragraph, it’s hard to follow
L666: “reflector” or “reflection”?
FAIR data publishing
L788: the link does not work when clicking from the document
L799: maybe “aim” is more suitable than “end goal” -
FAIR data publishing
L788: the link does not work when clicking from the document
L799: maybe “aim” is more suitable than “end goal” -
Discussion
L852-853: add “lateral” to “…(laterally) continuous…”. How a well-preserved and lateral continuous englacial layer suggests changes in past ice-flow conditions?
L857: include “lateral” to “…quantifying the (lateral) continuity of englacial…”
L858: include “it” to “…conditions, and (it) can also be used…”
L860: include “new” to “…(new) acquisition strategies.”
L861: include “lateral” to “…for mapping the (lateral) continuity…”
L867: include “lateral” to “…in assessing layer (lateral) continuity.”
L870: include “lateral” to “…indicate high (lateral) continuity.”
L887-888: maybe you could be a little more specific about “surface noise”
L889: Consider including some references about the echo-free zone (?). For example: Drews et al., 2009 (doi: 10.5194/tc-3-195-2009) or Drewry and Meldrum, 1978 (doi: 10.1017/S0032247400018271).
L895: Which version of BedMachine (Antarctica?) did you use?
L907: Add “lateral” before “continuity”
L925: I think the region is called Ellsworth Subglacial Highlands (not “Mountains”)
L942: Please cite references in chronological order
L943-946: Please consider rephrasing this sentence, it is hard to follow as it is.
L953: “…these data…” instead of “…this data”
L957: Change “…this data…” to “…these data…”
L958: Delete “such”
L1010: Delete “Lastly, and”
L1016: Consider change from “Combined, these will likely…” to “These data combined…” -
Conclusion
L1035: Change the word “can” to “could”
L1039: Add the word “and” before “thus” -
Figures and tables
Figure 1: I think it would be better to use the International System of Units and derived units for the scale bar, i.e. m or km. It would also keep consistency with other figures on the manuscript (e.g., distance axis). I would also suggest removing the blue background of the figure (and keeping consistency with other figures in the manuscript), and to consider including a graphic legend next to the figure.
Figure 3: to keep consistency with other figures of Antarctica in the text, I would suggest removing the blue background to the Antarctic image. Perhaps, it would be useful to include a vertical scale in the echograms.
Figure 4: It is hard to read what is written inside each box. Could you please increase the font size?
Figure 6: Please consider labelling all the panels (outside the echogram) and refer to the labels instead of "the top panels. Also, consider including the time in one of the y-axis to keep consistency (i.e., Figure 7).
Figure 8. Please label the polygons. Also, consider having two separate figures showing the ice surface velocity and the ILCI. I think it would also be useful to include an ice thickness map in this figure.
Figure 9: there are no labels for the rectangles in Figure 8. I can’t really distinguish the ice surface velocity below the ILCI.
Table 2: great table, very useful. Are there any key references for each radar system you could cite maybe?
Table 3: The hyperlinks (http://data.bas.ac.uk…) as they are written at the moment are broken.
Technical comments
Please check the Matlab code for reading the radar netcdf file
It reads
xlabel('Fast Time Sample Number', fontSize = 10) % set axis title
ylabel('Amplitude (dB)', fontSize = 10) % set axis title
it should read
xlabel('Fast Time Sample Number', 'FontSize', 10) % set axis title
ylabel('Amplitude (dB)', 'FontSize', 10) % set axis title
Please check the Python codes are ok.
Regarding the new platform for downloading data. The only potential complication I can think about at this point is the interface to select and download the data. Is not super easy to download a segment of interest. I had to navigate through several segments before I could actually select the segment I was intending to download. Some additional difficulties happened when more than one dataset was activated in the visualisation of the data. For example, there is a pop-up window that does not show what is selected with the cursor, it shows random segments of the dataset. Additionally, I think it would be useful if you could include an option to download a complete line by selecting the segments manually and then clicking a “download” button maybe (?)– if there is already an option like this I missed it, in which case it would be great to make it a bit more evident. It would save some time for the users.
Citation: https://doi.org/10.5194/essd-2022-49-RC1 -
AC1: 'Reply on RC1', Julien Bodart, 14 Jun 2022
We would like to thank both reviewers for very insightful and constructive reviews of our manuscript, as well as the editorial team for handling the review process. We are very pleased to see that both reviewers recognised the importance and usefulness of our dataset and manuscript, as well as the time invested in standardising and publishing the data following the FAIR principles. Both reviewers have provided us with some excellent comments, which have undoubtedly improved the quality of our manuscript.
In the attached supplement, we begin by addressing the comments from Reviewers #1, followed by those made by Reviewer #2. We have formatted the comments of each reviewer in italics, and have indented our responses in red below each comment. Attached to this response letter are also two versions of the manuscript, one with changes highlighted in red (‘ESSD_dataPaper_BAS_resubmit_highlighted’) and the final updated version with all changes incorporated but not highlighted (‘ESSD_dataPaper_BAS_resubmit’).
- Introduction
-
RC2: 'Comment on essd-2022-49', Neil Ross, 09 May 2022
This is a very welcome paper/manual/documentation of the BAS aerogeophysical system & the open release of an astonishing amount of aerogeophysical data acquired over multiple decades. On behalf of the scientific community I would like to say thank you, and pay testimony to the considerable work and effort that is represented by, and outlined in, this paper. This important paper and data release are vitally important for understanding ice sheet dynamics and change, and the scientific community can now use these data. I found it particularly useful to see all the different surveys reviewed, and key references provided for those surveys, in one single document. It is also very useful to see the technical aspects and set up of the PASIN radar system so comprehensively documented formally for the first time (aside from the slightly difficult to access ‘Terra Antarctica’ report from 2006). Documentation of the evolution of the BAS aerogeophysical system since 1994 is also useful.
Major comments
- This ‘data paper’ is all encompassing and highly informative, and thereby provides a very useful ‘one-stop-shop’ for those working with and analysing BAS aerogeophysical datasets. At times, this all-encompassing nature has its disadvantages however, resulting in a very long and at times slightly unwieldly manuscript. I therefore wonder whether there were ways to streamline it a little. Perhaps sections 4 & 5 could be reduced in length? Section 5 presents an interesting case study/exemplar of the use of the data facilitated by the open data release, but it does tend to imbalance the closing stages of the paper towards the radar dataset, particularly since magnetic and gravity examples are not given.
- There is a need to be consistent with recognition/acknowledgement of external partners when reviewing all the surveys. There is somewhat strange non-UK bias when detailing external collaborations (e.g. contrast the description of the IMAFI survey in lines 261-276 with ICEGRAV and PolarGAP surveys in 277-282 & 284-289). I think it would be good to acknowledge the involvement of UK non-BAS institutions a little more. Even if individual collaborators/PIs are not referred to by name, then there should be parity of acknowledgement (e.g. why UTIG, Technical University of Denmark, but not the University of Edinburgh, Bristol etc.?). This suggestion is about consistency of approach really. It may also be appropriate and fitting to recognise Richard Hindmarsh’s scientific contribution to the IMAGE-GRADES survey.
- Picking uncertainty: the section on radar bed picking might need to be a bit more open about potential errors associated with different pickers. Different people, often not radar experts, picked radar data using standard protocols and systems. Individual calls need to be made however, and these can be difficult to make (as I picked the IMAFI dataset whilst a postdoc I should know!). My understanding is that some pickers were not experienced radar users or researchers so different surveys may have different errors.
- Are small-scale opportunistic/targeted surveys missing from the data release? I’m thinking of surveys like that of Flask Glacier (https://doi.org/10.3189/2013AoG63A603) and surveys over the ice rises of the Weddell Sea (I’m aware of ice rise survey flights undertaken in the 2010/11 season on behalf of Richard Hindmarsh). It might be worth a ‘mopping up’ paragraph in section 2.2 to capture opportunistic/targeted surveys.
- Section 5: I think it is important to re-frame section 5 to make it clear that it is an exemplar case study to avoid radar-dataset bias. I also think that section 5 could be considerably condensed. The whole point of section 5 is to demonstrate the validity/usefulness of releasing the data openly. What is the ‘added-value’ provided by the release? This is the priority of this section, rather than the admittedly interesting findings etc. of the ILCI analysis. I therefore suggest that section 5 be reworked to make this demonstration clearer (see minor comments relating to section 5 below for more details). It may also be worthwhile flagging the potential application of AI on this ‘big data’ dataset in section 5.
Minor Comments
Line 36 – “not openly available” rather than “unpublished in full”?
Line 37 – how about more generic language? i.e. rather than “gravity inversions, bed-reflectivity….”, what about “geological and glaciological applications”?
Line 52 – rather than “fully processed”, “online radar dataset”?
Line 67 – it is not just bedrock beneath the ice. Could be sediment or water.
Line 68 – ice sheet ‘bed’ is not necessarily an accessible term to non-glaciologists. Define this term?
Line 72 – Napoleoni et al 2020 would be an appropriate recent reference here as it used BBAS data. I note it is referenced elsewhere in the manuscript, so is not an additional reference.
Line 87 – “modern digital aerogeophysical surveying”?
Line 89 – typo “aerogeophysics”
Line 91 – “…have played a vital role….”
Lines 97-103 – a very long sentence. Split in two?
Line 115 – “…for understanding…”?
Line 117 – no need for “As a result,….”. Start sentence with “This lack…”?
Section 2.1 – it might be useful to make it clear at the start of this section that the data release for 1994-2004 does not include processed RES data.
Line 163 – is there a reference for TORUS? I understand that it is not a survey that was really worked up, but there is an AGU abstract that could potentially be referenced (https://ui.adsabs.harvard.edu/abs/2003AGUFM.C31B0402J/abstract). Possibly also https://doi.org/10.3189/002214308784409125 ? Might also be worth inserting a line about the scientific aims of the TORUS survey to be consistent with the descriptions of the other surveys in this paragraph?
Line 178 – Is “coverage” the correct term here? How about “areal extent” instead?
Line 185 – I don’t think “techonomic” is the correct term here? “Tectonic”?
Lines 190-192 – is it worth inserting PASIN 1 and PASIN 2 in this sentence to explain the separation of 2004-2015 and 2015-2020?
Table 1 – is Evans Ice Stream ‘WAIS’? Some might argue it is APIS. Same applies to Dufek, is it really WAIS or is it EAIS?
Table 1 & section 2.2.1 – made me wonder whether some ‘opportunistically-acquired’ PASIN datasets might be missing from table 1 and the data release. I’m thinking specifically about Crane/Flask Glacier (https://doi.org/10.3189/2013AoG63A603) and Weddell Sea ice rise surveys undertaken in 2010-11. There may be others. If these are not included in the data release then it might be useful to make it clear in this manuscript that the data release does not include occasional small-scale opportunistically-acquired datasets like these.
Table 1 – could table rows be colour filled to visually distinguish PASIN1 and PASIN2 surveys?
Lines 228-238 – it would be worth explaining here that the data released here is approximately one half of the overall AGAP project RES data. The US data AGAP data are archived and available elsewhere already (e.g. CReSIS data website).
Line 258 – “collaborative projects” – collaborative with who? Information is provided for the ICEGRAV survey, but not IMAFI.
Line 261 – “test” rather than “assess”? This project was definitely hypothesis-driven.
Line 284-289 – a rather long unwieldy sentence. I recommend splitting in two.
Lines 305-308 – Some detail on outlet glaciers/ice streams surveyed is missing here. Academy Glacier, Bailey and Slessor ice streams, and Support Force Glacier were surveyed. The survey lines over Bungenstock Ice Rise (whilst welcome) were opportunistic and a low priority target compared to the surveys of these outlet glaciers/ice streams.
Line 360 – “All BAS aerogeophysical…” (i.e. delete ‘of’).
Figure 5 – requires annotation of antennas and magnetometers on Figure 5a.
Figure 5 caption (and elsewhere in text body) – “antennae” or “antennas”? I’ll leave that up to the authors and copy editors to decide on. I note lines 444-448 have a mixture of usage.
Line 425-428 – I’m not sure “…acquire logarithmic detected waveforms to complex coherent acquisition.” quite makes sense. Is there a missing word (e.g. “…to facilitate complex…”)?
Line 432 – Typo “aiborne”
Line 435 – “”…modern methods of digitisation…”?
Line 448 – “configured” not “configure”
Lines 439-452 – Quite a bit of this paragraph seems to be repetition of figure caption 5?
Line 458 and elsewhere in this section – Make it clear that the radar system is PASIN-2.
Line 462 – “Data” from PASIN-1 or PASIN-2 or both?
Line 466 – Missing MHz (x2) “10-MHz” and 13-MHz”
Line 469 – “The radar…” PASIN2?
Line 487 – “….of the PASIN 1 & 2 systems is…”
Line 487-492 – why are these parameters important enough to warrant text body description? Is this not simply repetition of the information provided in the table?
Line 497 – Trimble not Timble (x2)
Line 508-513 – I appreciate that these LiDAR data are ‘released’ as part of the along-track measurements, but in at least 1 survey (IMAFI) & probably more, swath data were acquired. Are there plans to process and release these data in future?
Line 532-535 – This sentence is a bit complex. Perhaps split after “been applied” to read “…been applied. This includes the use of….”
Line 556 – “…important geophysical signatures…”?
Line 559 – “Magnetic data were then….”
Line 560 – “noises” or “noise”?
Line 566 – “shows” rather than “provides an insight of”?
Line 573 – “referred to as” rather than “just referred as”?
Line 588-590 – not strictly true as written as SAR techniques were later applied to a subset of the data (Heliere et al. 2007). Perhaps re-word to avoid confusion, explaining that the released data & Vaughan et al. 2006 not SAR processed? It would be useful to revisit the BBAS data and re-process with SAR techniques, followed by re-picking & release. The importance of the survey area (i.e. Pine Island Glacier/Thwaites) may warrant this, though admittedly it is a big job which is well outside the scope of this data release & manuscript.
Line 592-593 – Is this statement 100% correct? I didn’t think that the 2006/7 IMAGE-Grades survey data were SAR processed (Maybe also the Wilkes Basin survey?). Perhaps I have this wrong however.
Line 600-601- this sentence would benefit from a reference. Would Castelletti et al. 2019 be appropriate here? https://doi.org/10.1017/jog.2019.72
Line 625 – Castelletti reference may be appropriate here too?
Line 628-630 – Which survey was the Flask Glacier from? This is perhaps an example of the targeted/opportunistic surveys that I discuss in major comments above. Would be good to explain if this was part of one of the released survey datasets (Table 1) or is something else, even possibly not released here.
Line 632-635 – A sentence that is probably worth splitting in two. Also needs a little clarification by what is meant by “institutes”.
Line 636 – Opens with “we”, but I suspect that this is not appropriate here. “The BAS approach is to pick….” might be better. I’m aware that many people worked as ‘pickers’ (including myself) to pick the bed for these surveys, and at least some of these were not necessarily people with significant radioglaciology experience beforehand. It might be worth reflecting this in the text.
Line 638 – “…manual re-picking….”?
Line 659 – provide an example/reference for an ‘older survey’ like this.
Line 674-678 – provide a range of typical crossover errors from the surveys here? I’m aware that Ross et al. 2012 https://www.nature.com/articles/ngeo1468 includes separate RMS errors for smooth and rough topography, so could be useful in this regard. Aside from crossover errors have BAS ever undertaken any other error assessment on picking of the bed from the radar datasets (e.g. comparison of picks by different pickers etc.)?
Table 3 caption – should the data held at CReSIS be linked to a DOI?
Line 739 – “…exported and made available…”?
Lines 765-776 – lots of repetition of figure caption information here (e.g. “highlighted in blue”). I recommend careful editing to remove unnecessary repetition.
Line 811-812 – “The portal interactively showcases….”?
Line 845-846 – I suggest swopping “geophysical data” in here, rather than “radar data”. The radar data are simply being used here as an exemplar on behalf of the entire dataset released and described. It would be good to reduce the potential view of section 5 being radar-biased, and instead be inclusive of all the data types (but without a case study exemplar for each).
Lines 850-878 – Can this section be considerably shortened?
Line 852 – move “limited” to earlier in the sentence? E.g. “…suggest limited changes….”? 852-854 took me a while to fully comprehend so some form of rewording probably necessary.
Lines 879-883 – A lot of the text here can be reduced by simply inserting “between 2004-2020” in the first sentence, and referring to table 1. Then the second sentence listing all the surveys can be deleted?
Lines 904-907 – be specific about the differences between AGAP and BBAS surveys? i.e. one was SAR processed, the other was not.
Line 908 – The end of this paragraph presents an opportunity to reinforce the important message of section 5, i.e. to demonstrate the validity and usefulness of releasing the whole dataset openly (i.e. that this sort of metadata level analysis can be undertaken on a continent-scale, and that new and developing techniques and approaches (e.g. AI etc.) can be applied). That then mitigates the potential radar data bias that comes across with section 5 at present.
Lines 916-923 – lots of geographic locations referred to in this paragraph. These need annotated on a figure.
Line 939 – where it says “further exploited in the future” make the case that this is only possible because these data have now been so comprehensively and openly released. There’s an important argument and case to be made here as there is still work to be done across the scientific community (and funders) about the importance of undertaking and funding the work necessary to facilitate data release. The authors have an important and high-profile opportunity here and my recommendation is to reinforce this case here strongly.
Line 942 – at the risk of recommending citing my own work, an appropriate reference to cite here could be Ross et al. TC 2020 https://tc.copernicus.org/articles/14/2103/2020/tc-14-2103-2020.html
Lines 943-952 - I suggest these lines be removed. They are very radar data-/glaciology-specific, and I think it dilutes the broader geophysical importance of the entire dataset a little. The ILCI analysis of the radar data should be a representative of the entire dataset demonstrating why open data is so important. It’s an excellent example, it probably just needs to be presented in a slightly different way.
Line 956 – Napoleoni et al 2020 https://tc.copernicus.org/articles/14/4507/2020/tc-14-4507-2020.html would be appropriate here. It is referenced elsewhere in the manuscript so is not an additional reference.
Lines 991-995 – this sentence is unnecessary. Just insert appropriate references in line 989-991.
Line 1000-1005 – it wasn’t totally clear that there is a current plan to release the 1994-2004 RES data from the text here. Is there one?
Line 1009 – reference Castelletti et al. again here?
Line 1008-1009 – it might be worth inserting a comment here that were data to be re-processed with new approaches then the aerogeophysical data platform could be used or adapted to release those data openly.
Line 1011 – Is there a plan to release these raw radar data files to the community?
Line 1025 – 2D radar data released 2004 onwards only.
Line 1044 – RINGS and AntArchitecture action groups: are there DOIs or references that can be linked to here? 10-20 years from now readers may wonder what these action groups were without this.
Dr Neil Ross (Newcastle University)
Citation: https://doi.org/10.5194/essd-2022-49-RC2 -
AC2: 'Reply on RC2', Julien Bodart, 14 Jun 2022
We would like to thank both reviewers for very insightful and constructive reviews of our manuscript, as well as the editorial team for handling the review process. We are very pleased to see that both reviewers recognised the importance and usefulness of our dataset and manuscript, as well as the time invested in standardising and publishing the data following the FAIR principles. Both reviewers have provided us with some excellent comments, which have undoubtedly improved the quality of our manuscript.
In the attached supplement, we begin by addressing the comments from Reviewers #1, followed by those made by Reviewer #2. We have formatted the comments of each reviewer in italics, and have indented our responses in red below each comment. Attached to this response letter are also two versions of the manuscript, one with changes highlighted in red (‘ESSD_dataPaper_BAS_resubmit_highlighted’) and the final updated version with all changes incorporated but not highlighted (‘ESSD_dataPaper_BAS_resubmit’).