METER ATMOS 41 all-in-one weather station (A2 Roof Building NOI Techpark, Bolzano - Italy)
Abstract
This dataset contains meteorological observations recorded by a METER ATMOS 41 all-in-one weather station installed on the roof of Building A2 at NOI Techpark. The main monitoring period began around 2022, and the station remains installed at the site. The recorded variables include solar radiation, precipitation and maximum precipitation rate, lightning activity and distance, wind direction, wind speed and gust speed, air temperature, vapour pressure, vapour pressure deficit, and atmospheric pressure. Additional measurements include the station’s tilt along the X and Y axes, RH sensor temperature, and diagnostic information related to the battery, barometer, and data logger. Observations are generally recorded at 20-minute intervals.
FAIR Overall Score
Keywords
Digital Object Identifier (DOI)
https://doi.org/10.48784/a0128ce8-db80-4a62-9ec7-b1684d8f5afd
Citation
Roberto Mendicino, & Simone Tritini. (2026). ATMOS METER 41 Weather Station A2 Roof Building NOI Techpark (Bolzano) (Version 2026) [Dataset]. Center for Sensing Solutions. https://doi.org/10.48784/A0128CE8-DB80-4A62-9EC7-B1684D8F5AFD
Legal constraints
This dataset is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). You are free to share and adapt the material, provided that appropriate credit is given, a link to the license is included, and any changes are indicated. No additional legal or technological restrictions may be applied. (https://creativecommons.org/licenses/by/4.0/)
Contact for metadata
Eurac Research - Center for Sensing Solutions
supportcss@eurac.edu
Viale Druso, 1 / Drususallee 1, eurac research, Bolzano, Autonomous Province of Bolzano, 39100, Italy
FAIR Overall Score: 96%
Evaluated by F-UJI - An Automated FAIR Data Assessment Tool: https://doi.org/10.5281/zenodo.6361400
Findable Advanced
-
Metadata identifier follows a defined unique identifier syntax or scheme (IRI, URL, UUID, HASH or PID) (1/1)
-
Metadata identifier follows a defined persistent identifier syntax (0.5/0.5)
-
Persistent identifier for metadata is registered and maintained by a PID authority (0.5/0.5)
-
Core data citation metadata is available (1/1)
-
Core descriptive metadata is available (1/1)
-
Metadata contains a PID or URL which indicates the location of the downloadable data content (1/1)
-
Metadata is given in a way major search engines can ingest it for their catalogues (Dublin Core or schema.org or DCAT encoded in microdata, RDFa, embedded JSON-LD or meta tags see e.g. Google Dataset Search webmaster guidelines) (2/2)
Accessible Advanced
-
Information about access restrictions or rights can be identified in metadata (1/1)
-
Metadata are retrievable via their specified identifier (1/1)
-
Data are retrievable via the identifiers given in metadata (1/1)
-
Identifier leading to metadata matches a scheme indicating a standardized web communication protocol. (1/1)
-
Identifier leading to data are matching a schema indicating a standardized web communication protocol. (1/1)
-
The communication protocol found in identifiers (IRIs) leading to metadata supports authentication. (1/1)
-
The communication protocol identified in data links (IRIs) supports authentication. (1/1)
Interoperable Advanced
-
Parsable, structured metadata (JSON-LD, RDFa) is embedded in the landing page XHTML/HTML code (2/2)
-
Parsable, structured metadata (RDF, JSON-LD) is accessible through content negotiation, typed links or sparql endpoint (2/2)
-
Metadata uses terms from registered vocabularies that are identified by their namespaces (2/2)
-
Related resources are referenced in plain text within appropriate metadata properties indicating the relation type (2/2)
-
Related resources are referenced by machine readable links or identifiers within appropriate metadata properties indicating the relation type (2/2)
Reusable Moderate
-
Minimum information (resource type) about the available data content is specified in the metadata (1/1)
-
Information on the manner and form (file size and type or service (API) endpoint and protocol) in which data is delivered is provided (0/1)
-
Licence information is given in an appropriate metadata element (1/1)
-
Metadata contains elements which hold provenance information which can be mapped to PROV based on PROV-DC. (1/1)
-
Metadata contains elements which hold provenance information using formal provenance ontologies (PROV, PAV). (0/1)
-
Community specific metadata standard is detected using namespaces or schemas found in provided metadata (1/1)
-
Multidisciplinary but community endorsed metadata (RDA Metadata Standards Catalog, fairsharing) standard is detected by namespace (1/1)
-
Data is available in a file format recommended by the research community (long term file formats, open file formats or scientific file format) (1/1)
Snippet code
#To set up the connection, the following two packages are required.
library(DBI)
library(RPostgres)
#Using the tidyverse in R, we can circumvent the direct usage of SQL language, and can use the more user-friendly dplyr syntax. For this we need these packages.
library(dplyr)
library(dbplyr)
#For data wrangling and visualization we will use these packages.
library(sf)
library(lubridate)
library(ggplot2)
library(mapview)
#Set up the connection
#The following sets up the connection to the SQL database. This is currently only possible within the ScientificNet. The parameters are copied from the documentation.
conn <- dbConnect(Postgres(),
dbname = "climate_data",
host = "10.7.18.68",
port = 5432,
user = "climate_user",
password = "meteo_data")
##################################
#List the available tables.
dbListTables(conn)
#The daily values are stored in the table stations_data.
tbl(conn, "stations_data")
#The climatologies (averages for the period 1981-2010) values are stored in the table climatologies.
tbl(conn, "climatologies")
#And finally the metadata with the station locations and more info on the processing in metadata.
tbl(conn, "metadata")
##########################
#Additional examples for create map and plots are available at: http://edp-doc.eurac.edu/cdb_doc/notebooks/Access-CDB-R-ubuntu.html
##########################Related docs
| # | Name | Description | Link | Date published | Category |
|---|---|---|---|---|---|
| 1 | Connection to PostgreSQL database | Necessary steps to connect to the PostgreSQL DB. Example with the Cimate Database. Available only inside ScientificNet | Link | June 10, 2021 | PostgreSQL |
| 2 | Climatic and Hydrological timeseries | This page contains description and documentastion of Climate DB, ADO and 4DMED projects | Link | April 14, 2023 | PostgreSQL |