Earth Data Community

AAI

Wed, 26 Aug 2026 00:00:00 +0000

Community AAI and Infrastructure Proxy#

Ensures the AAI interoperability across the EOSC Nodes.

User authentication for access to onboarded resources will rely on the Data Terra Single Sign-On integrated with the EOSC AAI Federation which has been in production since February and connected to MyAccessId since early March. It complies with the technical requirements (AARC blueprint architecture specifications) and regulatory requirements (privacy notice, incident response, etc.) defined by the EOSC AAI WG.

Copernicus Climate Data Store (C3S)

Wed, 26 Aug 2026 00:00:00 +0000

Copernicus Climate Data Store (C3S)#

This tool allows you to retrieve Copernicus Climate Data Store (C3S).

Any user willing to use this tool needs to create a new account.
Compose your request directly on C3S and copy/paste it in the input field “Request”
Users need to add their CDS API Key to Galay (see below). Documentation on where to get the CDS API key can be found here.
Be aware that for being able to download dataset from C3S, users also need to agree to their term of use (Licence to use Copernicus Products) on the C3S website.

Set up user credentials on Galaxy#

To enable users to set their credentials and provide their CDS API Key for this tool, make sure the file config/user_preferences_extra.yml has the following section:

Mon, 01 Jan 0001 00:00:00 +0000

User Access Policies#

EOSC Node Data Terra specific policies for access and use of onboarded services

Resource catalogue

Wed, 26 Aug 2026 00:00:00 +0000

Resource catalogue#

The Node Resource Catalogue has adopted a foundational design choice based on a unified catalogue model built on DCAT. In this approach, every resource is exposed as a dcat:Resource, while its specific nature is indicated via the dcterms:type property. Datasets are additionally typed as dcat:Dataset to ensure full DCAT-AP compliance, whereas other resource types (e.g. Software, Publications, Services, etc.) are represented solely through dcterms:type, linked to a controlled SKOS vocabulary. Data harvesting is performed through a dedicated component provided by the French Gaia Data project (MTEP). In parallel, specific connectors are being developed to aggregate additional categories of research outputs, including CodeMeta for software, DataCite for publications, and GeoDCAT-AP for geospatial data and services. A key advancement is the design of an intelligent EOSC connector acting as a local quality gate. Before any metadata is exposed to the EOSC EU Node (EEN), it undergoes strict validation ensuring the presence of mandatory Persistent Identifiers (PIDs), licenses, and core metadata fields. This mechanism guarantees a “zero rejection” policy by the European Knowledge Graph. The system is designed to preserve rich, domain-specific metadata locally (e.g. spatial and temporal extent, fine-grained provenance) while projecting only a strictly compliant subset to the EEN. Finally, metadata records are enriched through a combination of rule-based processing and AI-assisted enrichment techniques.

Registry services

Mon, 01 Jan 0001 00:00:00 +0000

Registry services#

Guidance on how to register a service Catalogue in the EOSC Data Terra Node and on how to make research product profiles discoverable through the EOSC Resource Hub (complementary discovery services)

Coming soon

Helpdesk

Mon, 31 Aug 2026 00:00:00 +0000

Helpdesk#

Integrates the helpdesks of EOSC Nodes within the EOSC Federation to provide a federated support channel between users and providers from nodes..

For the Helpdesk, the service instance provided either by the EOSC EU Node (EEN) or by EGI through the EOSC Mesh project will enable the centralization of user support requests for the Data Terra Node. As the operational support teams are already in place, they will use the centralized ticketing system to manage user requests and provide effective support. Data Terra is also actively involved in the working group co-designing the EOSC Federation Helpdesk, with the following objectives: (i) Provide an overview of the Minimum Viable Product (MVP) for Federating Capability (FC-3); (ii) Define ticket management workflows; (iii) Define the escalation process; and (iv) Define the minimum information to be exchanged in cross-node tickets.

Onboarding procedure

Mon, 01 Jan 0001 00:00:00 +0000

Onboarding procedures#

How to contribute as Data Source#

How to provide Service#

Service monitoring

Mon, 01 Jan 0001 00:00:00 +0000

Service monitoring#

Information about the quality and availability of services and resources made available through EOSC Nodes into the EOSC Federation.

For Monitoring, a similar approach to Helpdesk will be adopted by relying on a dedicated instance provided through EOSC Mesh. Data Terra services, which already expose health-check endpoints, will be monitored from this centralized instance, providing a unified view of service availability and operational status across the node.

Service and Research Product Accounting

Mon, 01 Jan 0001 00:00:00 +0000

Service and Research Product Accounting#

Provide information about the usage of services offered by EOSC Nodes within the EOSC Federation.

Coming soon

Service management system

Mon, 01 Jan 0001 00:00:00 +0000

Service management system#

EOSC Federation FitSM-based Service Management System. defining the essential processes between EOSC Nodes to enable efficient IT service management within the EOSC Federation. It also includes Security Coordination between Nodes.

Coming soon

Tue, 25 Aug 2026 00:00:00 +0000

Hello Earth Data Community#

Mon, 01 Jan 0001 00:00:00 +0000

How to add a new tool?#

On which platform should you develop your new tool?#

Create a Virtual Machine (IaaS)#

If you are working in Norway and at the University of Oslo, Tromso or Bergen, see documentation at IaaS.

Then install planemo.

Use Planemo OVA image#

See Planemo Virtual Appliance documentation.

Develop a tool#

Best practices for developing new tools are https://galaxy-iuc-standards.readthedocs.io/en/latest/best_practices/tool_xml.html.

Always use quotes for tool directory (python3 ‘$tool_directory/psymap_simple.py’) and tool parameters (–cmap ‘$adv.colormap’)
When wrapping an existing underlying tool, use the same version than the underlying tool
from_work_dir will tell Galaxy to pick this file, this saves you the cp/mv command in the command section:

<data name="ofilename" format="png" from_work_dir="image.png"/>

If the output format depends on the type of output file, try to avoid auto_format and use change_format instead:

<data name="ofilename" format="json">
 <change_format>
 <when input="format" value="csv" format="csv" />

Add EDAM ontology in your tool, for both topics and operations. Most climate tools will have:

<edam_topics>
 <edam_topic>topic_3855</edam_topic>
 <edam_topic>topic_3318</edam_topic>
</edam_topics>

Environmental science (topic 3855)

Mon, 01 Jan 0001 00:00:00 +0000

Copernicus Atmosphere Data Store (ADS)#

This tool allows you to retrieve Copernicus Atmosphere Data Store (ADS).

Any user willing to use this tool needs to create a new account.
Compose your request directly on ADS and copy/paste it in the input field “Request”
Users need to add their ADS API Key to Galaxy (see below). Documentation on where to get the ADS API key can be found here.
Be aware that for being able to download dataset from ADS, users also need to agree to their term of use (Licence to use Copernicus Products) on the ADS website.

Set up user credentials on Galaxy#

To enable users to set their credentials and provide their ADS API Key for this tool, make sure the file config/user_preferences_extra.yml has the following section:

Mon, 01 Jan 0001 00:00:00 +0000

Zonal statistics#

This tool allows to compute zonal statistics from geospatial raster data based on vector geometries (shapefile). The raster input file must be in netCDF format with geographical coordinates (latitudes, longitudes) with the same coordinate reference system as the shapefile.

Mon, 01 Jan 0001 00:00:00 +0000

psy-map#

This tools creates an image (png format) corresponding to the visualization on a geographical map of a variable extracted from a netCDF file (input file). By default, the projection is PlateCarree and colormap is jet. These settings can be changed in Advanced settings.

It uses psy-maps, a python package to generate plots. More information about psyplot and psy-maps can be found at https://psyplot.readthedocs.io/projects/psy-maps/en/latest/

Mon, 01 Jan 0001 00:00:00 +0000

shift longitudes from netCDF file#

The wrapper aims at providing a simple utility to shift longitudes ranging from 0. and 360 degrees to -180. and 180. degrees. The input file must be in netCDF format with geographical coordinates (latitudes, longitudes) given in degrees.

Mon, 01 Jan 0001 00:00:00 +0000

Retrieve data from smithsonian volcanoes database#

This tools creates an output file (csv,json or gml format) with data retrieved from VOTW database using the selected typename. By default, the output format is csv (Comma-Separated Values). This setting can be changed by selecting another output format.

Mon, 01 Jan 0001 00:00:00 +0000

Running WRF from Galaxy portal#

Current status#

These scripts were originally written to ease the usage of WRF
The documentation on how to use these scripts is still at https://wiki.uio.no/mn/geo/geoit/index.php/WRFand_WRF-CHEM. However, the plan is to migrate all our documentation to github.

About

Mon, 01 Jan 0001 00:00:00 +0000

The Earth Data Community brings together researchers, research infrastructures, and software developers working across Earth System Science.

This initiative aims to:

Federate Earth System tools and catalogs.
Improve interoperability of research software across Virtual Research Environments (VREs), platforms and research infrastructures.
Create a governance for tool repositories, reviews, and merges.
Develop european collaborations to foster cross-domain work across scientific environmental related disciplines and research infractures.
Share practices for Research Software development, sustainability, citation, and reuse.
And more along the way — shaped by the community as this initiative grows.

If you are a researcher, student, developer, data engineer, or scientist working with data, tools, and other resources to advance scientific knowledge about the Earth, then you can be part of the Earth Data Community!