Dataset: Meteorological observations (Vaisala WXT536) at Malga Crocetta Valfredda (Monte Baldo, Italy) during the DECIPHER campaign and the TEAMx programme in summer 2025, raw data, University of Basel

1. Short description of dataset and instrument The provided data file contains raw measurements from a compact weather transmitter (Vaisala WXT536) installed at Malga Crocetta Valfredda (Monte Baldo, Italy) during the DECIPHER campaign (https://sites.google.com/unitn.it/decipherproject/home-page) and the TEAMx programme (https://www.teamx-programme.org/) in summer 2025. 1.2. Specifications as detailed in the instrument manual The instrument manual can be found at https://docs.vaisala.com/r/M211607EN-AA/en-US/GUID-5016B5AD-5086-442C-B943-FBCFDB7DB860/GUID-AD3DAFAA-7537-453B-969B-B3229E311DD7. Vaisala WXT536 specifications listed therein are (incomplete excerpt): Parameter Property Description/Value Barometric pressure Observation range 500 hPa to 1100 hPa Air temperature Observation range -52 °C to +60 °C Relative air humidity Observation range 0%RH to 100%RH Wind speed Observation range 0 m s-1 to 60 m s-1 Barometric pressure Accuracy for sensor element ± 0.5 hPa at 0 °C to +30 °C at 600 hPa to 1100 hPa ± 1 hPa at -52 °C to +60 °C at 600 hPa to 1100 hPa Air temperature Accuracy for sensor element ± 0.3 °C at +20 °C Relative air humidity Accuracy for sensor element ± 3%RH at 0%RH to 90%RH ± 5%RH at 90%RH to 100%RH Wind speed Accuracy for sensor element ± 3% at 10 m s-1 Barometric pressure Output resolution 0.1 hPa Air temperature Output resolution 0.1 °C Relative air humidity Output resolution 0.1%RH Wind speed Output resolution 0.1 m s-1 Wind speed Response time 0.25 s Operating conditions of the instrument are equal to the observation ranges of the measurement parameters reported above. 2. Measurement strategy during the campaign 2.1. Description of data collection The instrument was operated continuously. 2.2. Time period covered by the data 2025-06-24 to 2025-07-19 2.3. Physical location Malga Crocetta Valfredda; latitude 45°40'00.7"N; longitude 10°49'27.6"E; altitude 1320 m a. s. l.; height 3 m a. g. l. 3. Data processing 3.1. Description of the derived parameters and processing techniques used Unprocessed, raw data is presented. 3.2. Description of quality assurance and control procedures Precipitation data was removed since measurements might have periodically been influenced by vibrations of the sensor. Data on wind direction is not shown because the orientation of sensor was changed during the campaign. No quality assurance and control procedures were performed on the provided dataset. 4. Data Format 4.1. Data file structure .csv file with metadata 4.2. List of relevant parameters and units All data refers to measurements averaged over 5-min intervals. Timestamp TS is the end of a 5-min interval indicated in local time (LT). Measured meteorological parameters are scalar wind speed (m s-1) [Wind_Speed_Avg], air temperature (°C) [Air_Temp_Avg], relative air humidity (%) [Rel_Humidity_Avg] and barometric air pressure (mbar) [Barom_Press_Avg]. 5. Data remarks 5.1. Known missing data points Data is missing during two charging periods of the instrument from 2025-07-01 07:10 LT to 2025-07-01 15:35 LT and 2025-07-04 08:30 LT to 2025-07-05 14:35 LT. 5.2. Software compatibility All software that can read and process .csv files. 6. Data Sharing Policy within DECIPHER 6.1 Data Types Two data types are envisioned, namely Raw Data and Processed Data. The submission of both data types is not mandatory. "Raw Data" consists of the dataset as measured by the sensor. Data manipulation by the curators must be kept to a minimum, i.e., converting the file format and including metadata. Curators must include the tag "Raw Data" in the title of the dataset to refer to this data type. "Processed Data" consists of the dataset after manipulation through a documented, literature-compliant procedure of data processing, including data cleaning, quality control, and averaging. The procedure must be documented in the dataset description page. Curators must include the tag "Processed Data" in the title of the dataset to refer to this data type. 6.2 Internal Use Datasets will be initially accessible only to the partners who contributed measurements on Monte Baldo. The agreement between partners for the usage of other’s datasets is to propose coauthorship to the respective owners. The requirements for public data use depend on the level of data processing, whether raw or processed: The use of "Raw Data" by the project consortium is bound to a proper crediting of the dataset, using the reference reported on the dataset page. For the first 6 months after the dataset's publication, co-authorship proposals must be made to the data owners. Beyond this initial period, co-authorship is no longer mandatory, but users are encouraged to offer it to the curators. The use of "Processed Data" by the project consortium is bound to a proper crediting of the dataset, using the reference reported on the dataset page. Users of the processed data must offer co-authorship to the data curators. 7. Data Sharing and Public Data Use within TEAMx Complying with the TEAMx data management plan: “Any use of TEAMx data products, during or after the embargo period, must include an acknowledgement (i.e., citation) of the source and the data provider. Data users must inform the respective data providers if a data product is to be shared with other parties via journal articles, presentations, and research proposals. If the data product constitutes a substantial part of the work, the data provider should be offered co-authorship and the opportunity to collaborate (both during and after the embargo period). In the case of co-authorship, an additional acknowledgement of the data provider is not required.” To comply with the TEAMx data management plan and the DECIPHER data sharing policy, the use of raw data by the project consortium is bound to a proper crediting of the dataset, using the reference reported on the dataset page. The following formula is recommended by TEAMx: The [description of the data product] was collected as part of the TEAMx programme and provided by [name of the data provider, institution of data provider]. [name of the data provider]’s contribution to TEAMx was funded by [name of the funding agency, information about grant]. The data are archived at [zenodo.org] and are accessible at [URL/DOI of data product].