Data Distribution

The distribution of Near Real-Time (NRT, 24 hours between data acquisition and data availability) LANDHYPERNET and WATERHYPERNET data will happen through the data portals for the LANDHYPERNET (www.landhypernet.org.uk) and WATERHYPERNET (www.waterhypernet.org). However, during the current prototype phase, where improvement of the quality checks is still ongoing, and further site-specific quality checks are still being added by the site-owners, these data portals are restricted to consortium members. In addition, for the WATERHYPERNET network the distribution may be delayed to ensure that the NCEP/GDAS forecast data for wind speed are made available for the latest sequence (should be less than 24hours). Data transfer from the system to the server may also delay the NRT processing (e.g. due to poor 4G connections on the field). In the near future, these data portals will be opened to the public and will become the reference source of data for HYPERNETS.

In the meantime, a subset of the HYPERNETS data until 2023-04-31 is publicly available and can be found on Zenodo (Brando et al., 2023; Brando and Vilas, 2023; De Vis et al., 2023; Dogliotti et al., 2023; Doxaran and Corizzi, 2023a; Doxaran and Corizzi, 2023b; Piegari et al., 2023; Goyens and Gammaru, 2023; Morris et al., 2023; Saberioon et al., 2023a; Saberioon et al., 2023b; Sinclair et al., 2023). The initial datasets provided here in June 2023 were produced using the v1.0 of the HYPERNETS PROCESSOR (see Section 2.5). A new version of the datasets on Zenodo will be released in the near future, using the v2.0 of the HYPERNETS PROCESSOR.

To follow the Findable-Accessible-Interoperable and Reusable principles (FAIR), particular attention is given to the data format and metadata, and, data accessibility. Files are in the NetCDF CF-convention version 1.8 format. Common metadata (e.g. metadata section added with each data product) follow the INSPIRE directives15 in accordance with the EN ISO 19115 for the metadata elements and the Dublin Core Metadata Initiative16. Instrument, component and system metadata are bound by a unique metadata key (i.e. system id) allowing to trace the history of the system (e.g. replacement, maintenance, system updates or instrument setup improvements).