Indoor Environmental Quality – Residential Apartment, Bolzano, Italy (2023–2026)
Abstract
Time-series dataset of indoor environmental quality (IEQ) measurements collected at 5-minute intervals from March 2023 to May 2026 in a south-facing living room (25 m²) of a residential apartment in Bolzano, Italy. Data were acquired using a Netatmo HomeCoach sensor and cover four years of continuous monitoring across four CSV files (one per year). Variables include: timestamp, air temperature (°C), relative humidity (%), CO₂ concentration (ppm), noise level (dB), and atmospheric pressure (hPa). The apartment is equipped with radiators for heating and an air conditioning system for cooling. The dataset is suitable for occupancy pattern analysis, thermal comfort studies, indoor air quality benchmarking, and training/validation of building energy or comfort models. LICENSE: CC-BY 4.0DOI: 10.5281/zenodo.20098783 Related resources: Platform: https://www.moderate.cloud (interactive access, API) Documentation: https://moderate-project.github.io/moderate-docs Source code / tools: https://github.com/MODERATE-Project/ Project website: https://moderate-project.eu Grant Agreement: Horizon Europe GA 101069834 This dataset is released under Creative Commons Attribution 4.0 International (CC BY 4.0). You may use, share, and adapt the data for any purpose, provided you give appropriate credit. If you use this dataset, please cite: C. Pozza (2026). Indoor Environmental Quality – Residential Apartment, Bolzano, Italy (2023–2026). Zenodo. https://doi.org/10.5281/zenodo.20098783Project: MODERATE (Horizon Europe GA 101069834). https://www.moderate.cloud
FAIR Overall Score
Keywords
Digital Object Identifier (DOI)
Citation
Landing page / DOI
Legal constraints
Creative Commons Attribution 4.0 International
Contact for metadata
FAIR Overall Score: 81%
Evaluated by F-UJI - An Automated FAIR Data Assessment Tool: https://doi.org/10.5281/zenodo.6361400
Findable Moderate
-
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/0.5)
-
Persistent identifier for metadata is registered and maintained by a PID authority (0/0.5)
-
Core data citation metadata is available (0/1)
-
Core descriptive metadata is available (0/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) (0/1)
Related docs
No docs sources are available.