the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
A long-term multiscale Critical Zone dataset integrating environmental monitoring and an open-air laboratory: The Alento River Catchment Observatory
Abstract. This paper presents an open-access dataset from the Alento River Catchment (ARC) in southern Italy, a strategic Mediterranean Critical Zone observatory integrating long-term environmental monitoring with an open-air laboratory. Long-term observations of weather variables, streamflow, reservoir water level, groundwater depth, soil water content, and soil matric potential are complemented by targeted field campaigns involving hydrogeophysical surveys, stable water isotope analyses, soil physical and hydraulic measurements, spectral measurements, and high-resolution UAV-based mapping. The principal value of the ARC dataset lies in the coordinated integration of continuous and campaign-based observations across multiple spatial and temporal scales and Critical Zone compartments, providing a basis for linking localized soil and subsurface processes with field- and catchment-scale hydrological responses. Since 2016, the ARC has been a component of the European TERrestrial Environmental Observatories (TERENO) network. The dataset includes both directly measured and derived products, with documented processing procedures, quality-control information, calibration results, and missing-data records. The principal value of the ARC dataset lies in the coordinated integration of continuous and campaign-based observations across multiple spatial and temporal scales and Critical Zone compartments. The combined observations can support the development, calibration, evaluation, and intercomparison of process-based hydrological and Critical Zone models, the evaluation of Earth Observation products, and the investigation of scale-dependent relationships among point-, field-, hillslope-, and catchment-scale observations. The complete dataset is openly accessible through Figshare under a CC BY 4.0 license. (Romano et al., 2026; https://doi.org/10.6084/m9.figshare.31229608).
- Preprint
(4003 KB) - Metadata XML
- BibTeX
- EndNote
Status: open (until 20 Nov 2026)
- RC1: 'Comment on essd-2026-725', Anonymous Referee #1, 20 Oct 2026 reply
-
RC2: 'Comment on essd-2026-725', Anonymous Referee #2, 04 Nov 2026
reply
The manuscript presents a rich, openly accessible dataset combining long-term hydrological observations with soil, geophysical, isotopic and topographic measurements from the Alento River Catchment (ARC). Its potential value lies in bringing together observations collected at different spatial and temporal scales, from individual soil profiles and experimental sites to catchment-scale monitoring. The dataset has clear potential value, and its range of complementary observations is a notable strength. However, I recommend strengthening the manuscript’s conceptual framing by explaining how the data components relate to one another, identify the intended scale of inference, state the limits of catchment representativeness and improving the shared data files.
The manuscript appears to overlap with Romano et al. (2018), which previously described the Alento River Catchment Observatory and its monitoring infrastructure. Please clarify which datasets, variables, sites and observation periods were already reported or made available in that publication, and identify explicitly the new, extended, reprocessed or newly released data included here. A dataset-by-dataset comparison, including links and persistent identifiers for previously published data, would help establish the added value of the present data paper and distinguish genuine data reuse from redundant presentation (figure 7 of this manuscript as an example).
General assessment
The dataset may be useful to researchers studying soil–water dynamics, hydrological processes and water-flow pathways within the critical zone. However, its contribution to a deeper understanding of Critical Zone evolution is unclear and should be clarified.
The manuscript provides extensive descriptions of the instruments, field campaigns, processing steps and data files. This level of detail can support data inspection and reuse, which are central to an ESSD data description. However, the manuscript would benefit from distinguishing more clearly between information essential for evaluating and reusing the data and highly granular technical details that could be moved to the supplementary materials or repository documentation. More importantly, it should explain how the different components form a coherent dataset, what kinds of Critical Zone research the dataset can support, and what conclusions can—and cannot—be drawn about the catchment as a whole.
Major comments
The detailed descriptions of acquisition methods, processing and variables are generally valuable, particularly where they enable users to understand the data and assess their quality. The manuscript also describes a wide range of measurements, including continuous hydrometeorological observations, soil measurements, hydrogeophysical surveys, stable isotopes and LiDAR-derived terrain data. Nevertheless, some of the technical detail appears disproportionate to its contribution to understanding the dataset or assessing its quality. The authors should review the manuscript for repetition and distinguish between information needed to assess data quality, limitations and reproducibility; information needed to locate, interpret and reuse the files. For example, operational or instrument-specific detail could be summarized in tables or provided in the repository documentation. The aim should not be to reduce documentation at the expense of reuse, but to make the main text more focused and easier to navigate. A concise overview table linking each dataset to its location, spatial and temporal coverage, measurement purpose, processing level and principal limitations could help achieve this. The shared data file structure can be improved in the repository. Each file should be usable on its own and, for example, include at minimum clear column headers.
The manuscript combines observations from sites and datasets with different spatial extents, sampling designs and temporal coverage. The ARC framework includes catchment-scale hydrological records alongside more detailed observations at selected experimental sites, including MFC1, MFC2 and GOR1. This nested approach can be scientifically valuable because intensively monitored sites may help explain processes that influence broader-scale hydrological responses. At the same time, the manuscript should clarify that the more intensively studied sites may not be representative of the full catchment Critical Zone structure (land cover, land cover evolution, regolith structure, soil type…). The paper notes that the observations are geographically concentrated within the ARC and frames their broader value in terms of transferable scientific questions rather than statistical representativeness. This important qualification should be carried consistently through the manuscript, particularly where the dataset is discussed as an integrated catchment observatory. The questions that should be clarified relate to: How the intensively monitored sites were selected and which soil, land-cover, topographic or hydrological conditions they represent? How their characteristics compare with those of the wider catchment? Which inferences are supported at the experimental-site scale, and which—if any—are intended to apply at the catchment scale? How important are the spatial coverage and limitations of the observations, including areas or conditions that are underrepresented? If the sites are not designed to represent the catchment statistically, this should be stated explicitly. Their functional relevance at the catchment scale can still be compelling, but it should be explained in terms of the processes they illuminate and the ways in which the observations can be related to catchment-scale measurements—not by implying that the sites represent the catchment as a whole.
The dataset brings together observations from several fields, including hydrology, soil science, hydrogeophysics, stable-isotope science and terrain analysis. However, combining measurements from different disciplines does not, by itself, establish their interdisciplinary integration. The manuscript could explain more clearly how the datasets can be used together. For example: which observations are co-located, and at what spatial and temporal scales? Are there common identifiers, coordinate systems, temporal conventions or metadata that support data linkage? Which variables or processes can be jointly investigated using the different components? Are there demonstrated or proposed workflows for integrating continuous monitoring, field surveys and geophysical observations? The authors should also distinguish between data that are directly integrated or linked and data that are simply presented within the same repository. This would help readers assess the dataset’s interdisciplinary value and understand the practical effort required to combine its components.
All appendices should be removed from the manuscript and provided as supplementary metadata in the dataset repository. Information from the tables could be incorporated into the CSV files as column headers. The end dates across all CSV files could also be harmonized. Is there a reason to retain samples for which no data are available?
More detailed comments
Line 32: what type of CZ models?
Keywords: what type of isotopes
Line 110: specify stable isotopes of the water molecules
Table 1: UARC and LARC not listed
Lines 282-292: size of MFC1
Line 354 “… installed at 2.0m…”
Lines 364-397: measurement error?
Lines 484-487: This approach is not straightforward and remains the subject of debate and ongoing refinement. The manuscript would benefit from discussing the limitations reported in the literature when using it to identify the water sources used by trees. Relevant examples include Barbeta et al. (2022; https://doi.org/10.1111/nph.17857) and Montemagno et al. (2023; https://doi.org/10.1002/eco.2582).
Figure 4: All isotope data should be revised with a quality check. d-excess of -20 permill for the soil solution in 19/10/2020 or >>25 permil for the GW in 19/05/2021 seems to be off – especially when compared to all other values in the time series that do not come close to that.
Lines 558-559: blank values and detection limit of the SOC analysis
Line 614: give more specific examples of CZ functioning that could be directly related to the shared dataset
Line 650: explain “deep-soil water”
Line 692: 23% and 49% seems to be more appropriate
Line 891: 19 instead of 13?
Table A232a: harmonized the column label as for MCF1
Table A25c: no column for Z in the .csv file
Citation: https://doi.org/10.5194/essd-2026-725-RC2 -
RC3: 'Comment on essd-2026-725', Anonymous Referee #3, 16 Nov 2026
reply
General Comments:
This paper describes an openly available critical zone dataset for the Alento River Catchment (ARC) in Italy. The dataset includes a combination of long-term observations and field surveys and experiments. Overall, this is a valuable introduction to a CZ dataset in the Mediterranean region, and should enable studies that span surface water, groundwater, land use, meteorology, and soil processes. However I have several suggestions to improve this narrative and the dataset.
The dataset could be made easier to use with a more comprehensive readme file with additional information about the data. I would suggest adding some of the specific information that is currently in the appendix of the paper. Without some additional information, like coordinates associated with each file, the dataset would be hard to use. It would also be useful to provide higher resolution data than daily where it is available, for example I assume some of the weather stations provide sub-daily precipitation, and possibly stage was recorded continuously, which would help identify effects of events in this relatively small catchment. This is optional, but a notebook or tool would also help users start analyzing the data, for example a Jupyter notebook or something similar in addition to the csv files, which replicates some of the figures in the paper and/or provides an introduction to the dataset.
It is not clear to me the difference between the “Critical Zone Observatory” and the “Open Air Laboratory” and why these are distinguished. It seems like either format could include all of these types of datasets. Possibly the OAL concept came prior to the CZO and both where funding mechanisms throughout the monitoring history, but the value of these two similar concepts to separate the dataset is not clear to me. Specifically it seems like the CZO is used to refer to continuous monitoring and the OAL to the detailed soil characterization, but I’m not sure why this is the case.
The temporal and spatial overlap of sites and studies is discussed as an advantage, but it is hard to digest how things overlap. A table or timeline figure would be useful, in addition to the provided maps, to summarize beginning and end dates for the long term continuous monitoring, and how specific sampling or field experiments match with the availability of those data.
Specific comments:
In the dataset downloaded from Figshare, I noticed there are two readme files that seem to be the same.
The Figure 1 map lists sites, which are not named except for what variables they measure, and I think they match with sites listed in Table 1. It might be useful to highlight site names on the map, especially the few sites that are discussed later in the paper with field campaigns (I think MFC2 and GOR1).
Figure 2A could better highlight the areas that b-d show as insets (with a bold square around the areas or arrows between panels).
Figure 13: the top two panels are not very useful (the precipitation and water yield time-series). The main analysis uses the cumulative WY and P over all years, so it seems like it would be better to plot those instead on the same panel (two lines showing cumulative time-series) and show the same vertical dashed line as in column d.
The Data Availability Section is Section 6, followed by Section 7 which is a conclusion. This may be correct as per journal guidelines but seems out of order to me.
Citation: https://doi.org/10.5194/essd-2026-725-RC3
Data sets
Complete dataset reflecting the spatial and thematic components of the Alento critical zone (CZ) observatory. N. Romano et al. https://doi.org/10.6084/m9.figshare.31229608
Viewed
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 554 | 188 | 72 | 814 | 74 | 78 |
- HTML: 554
- PDF: 188
- XML: 72
- Total: 814
- BibTeX: 74
- EndNote: 78
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
General comments
The paper presents a dataset collected in the Alento catchment, a 411 km² catchment in southern Italy, that is relevant for critical zone studies in a Mediterranean context. The basis of the dataset is hydrometeorological and hydrological data dating back to 1994 for the oldest station. This basis has been complemented in recent years with sub-catchments (~10 ha) field campaigns to document other variables such as soil moisture, isotope concentrations in various compartments, geophysical data on more limited durations. This additional data provides information that transforms the Alento catchment into a critical zone observatory (CZO). Unfortunately, in the provided data set, discharge measurements on the two MFG2 and GOR1 catchments are not provided, although streamflow gauges are mentioned in Figure 3. This considerably lowers the value of the dataset, as it does not allow to relate discharge with soil moisture dynamics (as an example).
Data from critical zone observatories such as the Alento catchment are always worth being shared, as they represent a very long-term investment to collect valuable data. This is particularly true for Mediterranean regions where such datasets are scarce. The data can be used to perform comparative studies between catchments or to calibrate and assess models of various complexities. Soil moisture data are also relevant for the calibration of satellite products.
I fully support the effort of the authors to publish this dataset. However, several points, detailed below, must be addressed before possible publication of the paper.
A general point concerns the time step at which the data are provided. The authors have chosen to provide daily aggregated time series, even if the data are acquired at shorter time scales. One of the interests of the dataset is to be located in a Mediterranean catchment, where rainfall events are often of short duration. Potential users of the data include researchers interested in flash floods and the daily time step does not allow capturing the rapid dynamics of the hydrological response. Daily time step data remain useful to study water resources and droughts, but if the authors were providing sub-daily data, this would enhance the value of the data set.
The authors also mention a full weather station, including the four components of the radiative budget, recorded at a hourly time step, but they only provide daily reference evapotranspiration ET0. Once again, the full hourly dataset would be interesting for future users. So why do they only provide daily ET0?
Another limit of the current presentation of the dataset is the description of the quality assessment/quality control which is often not very detailed. Accuracy of the measurements should be provided is possible.
Specific comments
Line 139: Part of the dataset is already described in Romano et al. (2018), but the dataset presented in the present paper is longer. Could you precise in the manuscript which variables continue to be acquired and provide a contact if readers are interested in updated time series.
Line 170: is it possible to get the discharge corresponding to the water level times series?
Line 191: water level is interesting but discharge is much more interesting for computing water balance.
Line 222: define water-yield the first time it is used (instead of line 229).
Line 257: Nasta et al. (2017)? (Nasta et al. (2018) not cited in the reference)
Line 286: not consistent to provide daily data for a Mediterranean catchment with intense rainfall events and quick dynamics.
Lines 303-304: “Quality assurance procedures included routine inspection of the time series to identify physically unrealistic values and periods affected by instrument malfunction, data logger interruptions, power supply failures, or communication problems.”. This sentence is not very precise and more information about data quality check could be provided, together with estimates of uncertainties. This sentence is found several times in the paper and the remark is valid for all the occurrence of the sentence (e.g lines 329-330,
Line 309: was Eq. (3) verified using in situ sampling?
Line 342: provide the manufacturers here.
Line 345: precision about the sampled compartments (rainfall, discharge??)
Line 356: why do you only provide daily aggregated data if hourly values are available. The short time scale variability is interesting in Mediterranean catchments.
Line 385: same remark as above for soil moisture: quick variation of soil moisture would be interesting to follow soil infiltration during intense events.
Line 400: in general soil moisture is also sampled closer to the surface (for instance for the calibration of remote sensing products). Why only 15 and 30 cm depth?
Line 416: Is the range of matrix potential for the MPS-6 sensor exact?
Line 431: is it necessary to have specific softwares to visualize/analyze such data?
Line 437: the interest of geophysical methods is to explore deep layers, and in particular the weathered soil. So why did you only explore the first 3m depths?
Line 480: provide the accuracy of the isotope analyses.
Figure 5C: the catchment on the right bottom side is not legible
Line 530: you provide the density of the emitted points. The relevant information to characterize the accuracy of the DTM is the density of points at the soil surface.
Line 6607: why did the authors not include the retention and hydraulic conductivity curves?
Line 610: long-term environmental observatory and not repository?
Line 629: I agree that high-intensity events are relevant for the study site, so why did the authors not provide sub-daily data?
Figure 7: discharge is provided, but, in the paper, there is no information on how discharge is obtained from water level measurements.
Figure 7: the elevation of the groundwater depth sensor should be provided in the metadata, not in a figure caption.
Figure 8: there are differences between CNRS data and the GS3 sensors for the years 2020-2022. This is not commented in the paper.
Figure 9: same remark as for Figure 8
Line 735: the break mentioned here is not so obvious in Figure 13c
Line 1244: the reference that appears in FigShare (Nasta, Paolo (2026). The Alento Observatory for Agro-Environmental Research in the Mediterranean: Integrating Critical Zone Monitoring and Open-Air Laboratory Data (Dataset). figshare. Dataset. https://doi.org/10.6084/m9.figshare.31229608.v8) is different from what is provided in the paper (titles and authors are different). Furthermore, good practice when publishing a data set is to cite all the persons who contributed to data acquisition, not only the person that formatted them.
References
Romano N., Nasta, P., Bogena, H.R., De Vita, P., Stellato, L., and Vereecken, H.: Monitoring hydrological processes for land and water resources management in a Mediterranean ecosystem: The Alento River catchment observatory, Vadose Zone J., 17, 80042. doi:10.2136/vzj2018.03.0042, 2018.
Analysis of the data set
The data set is provided on FigShare as a .zip file organized in several sub-directories with the DEM, and the data from the various sub-catchments.
The data set in the .zip file is not documented enough to be usable by other persons and it must be revised substantially. Ideally, the information provided in the .zip file should be sufficient so that a person that does not know the data set is able to understand the content of each file (location, measured variables and units). If the reader is interested in more detailed information about the data processing, it can refer to the data paper. But the .zip file should be as auto-sufficient as possible. So most of the information provided in the tables provided in Appendix should appear in the ReadMe files.
Formats: First of all, the dataset contains some files in formats that are not open: the readme is a .docx file and should be a .txt file. There are also excel files that should be converted to .csv files to fulfill with the criteria of open formats. For the geophysical files, dates in the name of the files should be in SI format: YYYY-MM-DD.
ReadMe files: The authors have provided a file named readme that includes information about the whole data set content, but some information is missing (see below) and when the future users open the individual files, it is not always possible to understand what is its content (see below). I recommend adding ReadMe files in all the sub-directories, and to add metadata in each individual file (information presently included in the paper tables provided in appendix). Indeed, some files do not include any metadata and it is not possible to know what is the content of the columns content and the units. To overcome this problem, I would recommend the addition of metadata at the beginning of each .csv files with # at the beginning of each line, including
Additional comments
In all files, provide the coordinate system and a description of the columns and units.
DEM sub-directory: the coordinate system should be provided.
EMI and ERT sub-directories: the content of the columns and the units must be specified. The content of the columns seems to be specific of the data type and should be explained for non-specialists. If processed data are also included, they software used to obtain them should be specified.
Isotopes’ measurements: provide the locations where the data were measured and provide the data in .csv not in .xlsx
Water potential (pot) and water content (theta): provide the location of the measurement points and provide information of the content and units of the columns
MFC1/ MFC1_Q_DtGW: in the .docx readme file, only two columns are described but the file contains 4 columns. Water table depth appears as negative values. Are they depth relative to the soil surface? If yes, could you provide the absolute altitude of the surface? This information is necessary if the various levels are used to map the groundwater level.
MCF2/Coordinates_weather_stations: what is the coordinate system and the reference for altitudes? In addition, provide the data in .csv not in .xlsx
MCF2/soil properties: impossible to understand the content of this file as there is no information about the content of the columns
MCF2/Spectra: impossible to understand the content of this file as there is no information about the content of the columns
MCF2/TDR: provide information on the coordinate system
For discharge data, add in the metadata the catchment size.