INTERFACE project UAV meteorological Database


Abstract

Project: INTERFACE (Euregio Science Fund) Dataset: UAV meteorological data collection Partners: UniTrento, University of Innsbruck Sites: Mezzolombardo Sensors: anemometer (wind), temperature; humidity, pressure, solar radiation Date of data collection: 2025.08.01, 2025.09.18, ongoing

FAIR Overall Score

92%

Keywords

INTERFACE, UAV, Drone, wind measurement, anemometer, surface energy balance, eddy covariance tower, temperature, humidity, solar radiation, database, Atmospheric conditions, Meteorological geographical features

Digital Object Identifier (DOI)

https://doi.org/10.48784/bb0b7fab-fc1a-4104-a100-8d8ab80e2202

Creators

  • Stefano Tondini

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: 92%

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

Findable 100%
Accessible 100%
Interoperable 100%
Reusable 67%
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 · 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-11-13 (metrics 0.8)

Snippet code

Copy to clipboard
#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
##########################

# 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