MECHANICALLY VENTILATED buildings in SUMMER
Abstract
In this layer, the user can find a prediction of the occupants' thermal feeling (TF) according to specific scenarios recommended in the Standard EN 16798-1, and values of Operative Temperature referring to the four Indoor Environmental Quality categories.
FAIR Overall Score
Keywords
Supplemental information
No information provided
Legal constraints
Not Specified: The original author did not specify a license.
Contact for resource
Eurac Research - Center for Sensing Solutions
andrea.vianello@eurac.edu
Bolzano, ITA
Contact for metadata
University of Ca' Foscari
lorenza.pistore@unive.it
Download online resources
SHAPE-ZIP · MECHANICALLY VENTILATED buildings in SUMMER charset UTF-8 · MECHANICALLY VENTILATED buildings in SUMMER format_options=charset UTF-8 · MECHANICALLY VENTILATED buildings in SUMMER csv · MECHANICALLY VENTILATED buildings in SUMMER excel · MECHANICALLY VENTILATED buildings in SUMMER gml2 · MECHANICALLY VENTILATED buildings in SUMMER json · MECHANICALLY VENTILATED buildings in SUMMER text xml +subtype gml 3.1.1 · MECHANICALLY VENTILATED buildings in SUMMER image/png · MECHANICALLY VENTILATED buildings in SUMMER application pdf · MECHANICALLY VENTILATED buildings in SUMMER image jpeg · MECHANICALLY VENTILATED buildings in SUMMER image png · MECHANICALLY VENTILATED buildings in SUMMER image/png8 · MECHANICALLY VENTILATED buildings in SUMMER
FAIR Overall Score: 77%
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)
- 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)
- Found PID pointing to data which is NOT registered (does not resolve properly) -: https://doi.org/10.48784/223508fa-58e8-4514-a303-404fb396b99d
-
Core data citation metadata is available (0/1)
- Failed to parse RDF, trying to fix RDF string and retry parsing everything before line -: 1
- Not all required core descriptive metadata elements exist, missing -: ['creator', 'object_identifier']
-
Core descriptive metadata is available (0/1)
- Failed to extract Datacite JSON -: 'bytes' object has no attribute 'get'
-
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 Moderate
-
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 (0/2)
- Could not identify qualified related resources in metadata
-
Related resources are referenced by machine readable links or identifiers within appropriate metadata properties indicating the relation type (0/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)
Related docs
| # | Name | Description | Link | Date published | Category |
|---|---|---|---|---|---|
| 1 | Maps web services URLs | Here you can find all the available web service URLs provided by Maps, to consume datasets through an interoperable client (QGIS, Python, etc.) or to develop codes for analysis. The most relevant services to access datasets are: WMS (Web Map Service) to visualize layers in a map and to query them); WFS (Web Feature Service) or WCS (Web Coverage Service) to download raw datsets and use them for deep analysis or transformation. | Link | Dec. 13, 2021 | Maps |
| 2 | maps.eurac.edu documentation | maps.eurac.edu is based on Geonode, here the link to the official documentation | Link | April 28, 2021 | Maps |