Difference between revisions of "GCube-SDI-Suite"

Revision as of 15:59, 23 February 2021

gCube-SDI-Suite is a set of gCube java components that allows for the management of GIS resources (i.e. GeoSpatial DataSets, Metadata, Services..) in D4Science Spatial Data e-Infrastructure. It provides Java implementations of both client-side and service-side features, and it is built on top of OGC standards implementations. It is powered by gCube Features, fully integrating with the infrastructure.

Design

gCube-SDI-Suite is designed as a modular set of components, each of which can be used as dependency by another application. It fully relies on gCube for infrastructure integration.

The suite code can be found at [[1]], and it is distributed as the following maven artifact in gCube repositories :

<dependency>
  <groupId>org.gcube.spatial.data</groupId>
  <artifactId>gcube-sdi-suite</artifactId>
  <type>pom</type>
</dependency>

Philosophy

gCube-SDI-Suite aim is to to simplify developpers' life in managing GIS resources by

• Offering easy ways to perform common tasks
• Encouraging reuse of code by modularization of feature and reduction of dependency tree
• Isolating complexity of GIS resources management and infrastructure integration
• Allowing for easy extension of behaviour

Components

gCube-SDI-Suite main components are :

• SDI-Service the main service managing the SDI resources;
• SDI_Library the main library for clients;

Following components are also part of the suite :

• SDI-Interface java library with common classes definition;
• SDI-Test-Commons common library for test purposes;
• SDI-Generic-Client common library for Dynamic Clients;
• gCube-GeoServer-Client Dynamic Clients towards GeoServer REST API;
• gCube-GeoNetwork-Client Dynamic Clients towards GeoNetwork REST API;
• gcube-GeoServer-Connector internal library used to authenticate gCube calls towards Geoserver;

Use cases

Common use cases can be achieved as described in this section.

Using java clients

The best way to interact with the SDI is by using a provided java client described here.

Managing configurations

REST Interfaces