Difference between revisions of "SDI-Service"
(→Use Cases) |
(→Small Deployment) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:gCube Features]] | + | [[Category:gCube Features]][[Category: SDI components]][[Category: gCube Spatial Data Infrastructure]] |
| − | == Overview == | + | == Spatial Data Infrastructure (SDI) service Overview == |
The SDI-Service is a REST gCube service that acts as main control point for the entire SDI. It handles configuration of geo-services, while providing simple APIs to interact with it. | The SDI-Service is a REST gCube service that acts as main control point for the entire SDI. It handles configuration of geo-services, while providing simple APIs to interact with it. | ||
This document outlines the design rationale, key features, and high-level architecture, the options for their deployment and as well some use cases. | This document outlines the design rationale, key features, and high-level architecture, the options for their deployment and as well some use cases. | ||
| Line 22: | Line 22: | ||
The picture below describes the overall architecture of gCube SDI and the interaction between its components. The SDI-service manages all instances across contexts, allowing for a better control of policies, and acting as gateway for SDI configuration retrieval. | The picture below describes the overall architecture of gCube SDI and the interaction between its components. The SDI-service manages all instances across contexts, allowing for a better control of policies, and acting as gateway for SDI configuration retrieval. | ||
[[Image:SDI_Service_Architecture.png|frame|center|SDI Architecture]] | [[Image:SDI_Service_Architecture.png|frame|center|SDI Architecture]] | ||
| + | |||
| + | === Interaction with subsystems === | ||
| + | |||
| + | Interaction with subsystems can be achieved by integrating the [[SDI Library]]. | ||
== Deployment == | == Deployment == | ||
| Line 28: | Line 32: | ||
=== Small Deployment === | === Small Deployment === | ||
| + | Source code can be found at [https://code-repo.d4science.org/gCubeSystem/sdi-service | code repo]. | ||
== Use Cases == | == Use Cases == | ||
| + | For additional informaion on how to interact with the service read page [[Interaction_with_SDI-Service | Interaction with SDI-Service]] | ||
=== Well suited use cases=== | === Well suited use cases=== | ||
Latest revision as of 17:22, 2 February 2023
Contents
Spatial Data Infrastructure (SDI) service Overview
The SDI-Service is a REST gCube service that acts as main control point for the entire SDI. It handles configuration of geo-services, while providing simple APIs to interact with it. This document outlines the design rationale, key features, and high-level architecture, the options for their deployment and as well some use cases.
Key features
SDI-Service is a REST service offering the following key features:
- SDI Configuration management
- APIs to easily query the IS and the SDI's geo-services configuration details
- APIs to configure geo-services through the infrastructure contexts
- GeoSpatial datasets management
- APIs to publish both data and metadata into the SDI
Design
Philosophy
SDI facilities are prominent features in data infrastructures, and they must serve heterogeneous needs. In order to keep control of the SDI over the infrastructure, the SDI-Service acts as a central point of interaction for applications. The choice of REST API has been made in order promote its interoperability across applications implementation.
Architecture
The picture below describes the overall architecture of gCube SDI and the interaction between its components. The SDI-service manages all instances across contexts, allowing for a better control of policies, and acting as gateway for SDI configuration retrieval.
Interaction with subsystems
Interaction with subsystems can be achieved by integrating the SDI Library.
Deployment
Large Deployment
Small Deployment
Source code can be found at | code repo.
Use Cases
For additional informaion on how to interact with the service read page Interaction with SDI-Service
Well suited use cases
Well suited use cases addressed by the service are :
- Retrieve endpoint and credentials to interact with geo-services
- Configure geo-services on a context base
- Publish/update common geospatial dataset formats
Less well suited use cases
Less suited use cases are :
- Editing geospatial datasets
