Mazia 1150m - Canopy Height Model 24032026

Full metadata Maps repository

Abstract

The canopy height model (CHM) of the site F1, part of the long-term monitoring sites of the LTER project. The data is based on a LiDAR drone flight (sensor: Riegl MiniVUX-1UAV). The creation of the CHM is done in R with the package lidR by first normalizing the height of the point cloud and then rasterizing it.

FAIR Overall Score

96%

Keywords

South Tyrol, Canopy Height Model, Forest

Digital Object Identifier (DOI)

https://doi.org/10.48784/a100-hp91

Citation

Online link to the 'Mazia 1150m - Canopy Height Model 24032026' description on GeoNode

Supplemental information

This dataset is related to https://stac.eurac.edu/browser/#/collections/lidar_forestmapping_mazia_environtwin.

Legal constraints

Creative Common Attribution 4.0 International (CC BY 4.0): You are free to share and adapt under the following conditions: attribution and no additional restriction. (https://creativecommons.org/licenses/by/4.0/deed.en)

Download online resources

image tiff · Mazia 1150m - Canopy Height Model 24032026 image/png · Mazia 1150m - Canopy Height Model 24032026 application pdf · Mazia 1150m - Canopy Height Model 24032026 image jpeg · Mazia 1150m - Canopy Height Model 24032026 image png · Mazia 1150m - Canopy Height Model 24032026

FAIR Overall Score: 96%

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

Findable 100%
Accessible 100%
Interoperable 100%
Reusable 83%
Findable Advanced
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 · 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)
Metadata includes descriptive core elements (creator, title, data identifier, publisher, publication date, summary and keywords) to support data findability.
FsF-F2-01M · 2/2
  • Core data citation metadata is available (1/1)
  • Core descriptive metadata is available (1/1)
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 · 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)

Assessed 2026-09-07 (metrics 0.8)

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