Multi-Family Residential Building – Hourly Energy and IEQ Monitoring Time Series - Bolzano area, Italy (2006–2009)


Abstract

This dataset contains three years of hourly monitored data from a multi-family residential building located in the Bolzano area, South Tyrol, Italy (46°N, Alpine climate). It covers the period from 1 July 2006 to 21 July 2009 and provides continuous time series combining energy consumption measurements with indoor environmental quality (IEQ) indicators and meteorological context variables. The dataset is released as original monitored data: no outlier removal, smoothing, or gap-filling has been applied. A number of anomalous values and atypical operational trends have been intentionally preserved. This makes the dataset well-suited for benchmarking and stress-testing anomaly detection algorithms, fault detection and diagnostics (FDD) tools, and data quality assessment pipelines in the building energy domain. Note: Temperature profiles are obtained after averaging on similar profiles from 8 selected apartments. The energy consumption is the aggregated value at building level (same apartments). Variable Description Unit Min Max Mean Electricity Hourly electrical energy consumption kWh 0.00 78.00 1.62 CO₂ concentration Indoor CO₂ concentration (occupancy/ventilation proxy) ppm 452 1908 832.71 Internal temperature Indoor air temperature °C 12.60 31.20 24.27 Thermal energy consumption Hourly thermal energy (heating/DHW) kWh 0.00 27.00 5.98 External global radiation Horizontal global solar irradiance W/m² 0.00 1035.00 151.95 Outside temperature Outdoor ambient air temperature °C −8.10 38.30 13.33 Note: min, max, and mean are computed over all 25,699 records. No missing values are present. Extreme values (e.g., electricity max 78 kWh/h; CO₂ max 1,908 ppm) reflect both real operational peaks and intentionally retained anomalous readings. Users should not treat these values as errors before understanding the anomaly detection context of this release. 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: M. Castagna, C. Pozza (2026). Multi-Family Residential Building – Hourly Energy and IEQ Monitoring Time Series - Bolzano area, Italy (2006–2009). Zenodo. https://doi.org/10.5281/zenodo.20096697Project: MODERATE (Horizon Europe GA 101069834). https://www.moderate.cloud

FAIR Overall Score

81%

Keywords

Energy consumption, Indoor air quality, Residential building

Digital Object Identifier (DOI)

https://doi.org/10.5281/zenodo.20096697

Citation

Castagna, Marco. (2026). Multi-Family Residential Building – Hourly Energy and IEQ Monitoring Time Series - Bolzano area, Italy (2006–2009) [Dataset]. https://doi.org/10.5281/zenodo.20096697

Creative Commons Attribution 4.0 International

Contact for metadata

EURAC research


FAIR Overall Score: 81%

Evaluated by F-UJI - An Automated FAIR Data Assessment Tool: https://doi.org/10.5281/zenodo.6361400

Findable 57%
Accessible 100%
Interoperable 100%
Reusable 67%
Findable Moderate
Metadata and data are assigned a globally unique identifier.
FsF-F1-01MD · 1/1
  • Metadata identifier follows a defined unique identifier syntax or scheme (IRI, URL, UUID, HASH or PID) (1/1)
Metadata and data are assigned a persistent identifier.
FsF-F1-02MD · 0/1
  • Metadata identifier follows a defined persistent identifier syntax (0/0.5)
    • PID syntax is OK but the PID seems to resolve to a different entity, will not use this PID for content negotiation
    • Could not find any persistent identifier for metadata which is registered
  • Persistent identifier for metadata is registered and maintained by a PID authority (0/0.5)
    • Landing page domain resolved from PID found in metadata does not match with input URL domain -:eurac.edu <> zenodo.org
Metadata includes descriptive core elements (creator, title, data identifier, publisher, publication date, summary and keywords) to support data findability.
FsF-F2-01M · 0/2
  • Core data citation metadata is available (0/1)
    • Landing page domain resolved from PID found in metadata does not match with input URL domain -:eurac.edu <> zenodo.org
    • Failed to extract Datacite JSON -: 'bytes' object has no attribute 'get'
    • No response received from -: https://doi.org/10.5281/zenodo.20096697?format=metadata_datacite4, application/vnd.datacite.datacite+xml,application/xml, text/xml;q=0.5
  • Core descriptive metadata is available (0/1)
    • Failed to parse RDF, trying to fix RDF string and retry parsing everything before line -: 1
    • Request failed, status code -: https://doi.org/10.5281/zenodo.20096697?format=metadata_datacite4, application/vnd.datacite.datacite+xml,application/xml, text/xml;q=0.5 - 406
    • Not all required core descriptive metadata elements exist, missing -: ['publisher', 'creator']
Metadata includes the identifier of the data it describes.
FsF-F3-01M · 1/1
  • Metadata contains a PID or URL which indicates the location of the downloadable data content (1/1)
Metadata is offered in such a way that it can be registered or indexed by search engines.
FsF-F4-01M · 2/2
  • 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
Metadata contains access level and access conditions of the data.
FsF-A1-01M · 1/1
  • Information about access restrictions or rights can be identified in metadata (1/1)
Metadata and data are retrievable by their identifier
FsF-A1-02MD · 2/2
  • Metadata are retrievable via their specified identifier (1/1)
  • Data are retrievable via the identifiers given in metadata (1/1)
A standardized communication protocol is used to access metadata and data.
FsF-A1.1-01MD · 2/2
  • 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)
Metadata and data are accessible through a standardized communication protocol which supports authentication.
FsF-A1.2-01MD · 2/2
  • 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
Metadata is represented using a formal knowledge representation language.
FsF-I1-01M · 2/2
  • 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 registered semantic resources
FsF-I2-01M · 2/2
  • Metadata uses terms from registered vocabularies that are identified by their namespaces (2/2)
Metadata includes qualified references between the data and its related entities.
FsF-I3-01M · 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
Metadata specifies the content of the data.
FsF-R1-01M · 1/2
  • 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)
Metadata includes license information under which data can be reused.
FsF-R1.1-01M · 1/1
  • Licence information is given in an appropriate metadata element (1/1)
Metadata includes provenance information about data creation or generation.
FsF-R1.2-01M · 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)
Metadata follows a standard recommended by the target research community of the data.
FsF-R1.3-01M · 1/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 target research community.
FsF-R1.3-02D · 0/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)

Assessed 2026-10-25 (metrics 0.8)


No docs sources are available.