Difference between revisions of "GeoPortal"
(Undo revision 33811 by Fabio.sinibaldi (talk)) |
(→Design) |
||
Line 26: | Line 26: | ||
Aim of the framework is to maximize adaptability by supporting custom model and behaviour definition. | Aim of the framework is to maximize adaptability by supporting custom model and behaviour definition. | ||
− | === Architecture=== | + | === Architecture === |
[[Image:Geo Portale(1).png|frame|center|GeoPortal Architecture]] | [[Image:Geo Portale(1).png|frame|center|GeoPortal Architecture]] | ||
Line 36: | Line 36: | ||
'''Dynamic GUIs''' rely on java client libraries to communicate to the [[GeoPortal Service]], managing validation and management of GIS projects. | '''Dynamic GUIs''' rely on java client libraries to communicate to the [[GeoPortal Service]], managing validation and management of GIS projects. | ||
The service relies on the [[StorageHub | D4Science Workspace]] to store and access attached documents and on the [[Spatial Data Infrastructure | D4Science SDI]] to offer '''OGC''' Compliant Services (e.g. WMS, WFS, WCS, etc.). It also uses an internal archive of Profiled Document to manage publication lifecycle and for querying purposes. | The service relies on the [[StorageHub | D4Science Workspace]] to store and access attached documents and on the [[Spatial Data Infrastructure | D4Science SDI]] to offer '''OGC''' Compliant Services (e.g. WMS, WFS, WCS, etc.). It also uses an internal archive of Profiled Document to manage publication lifecycle and for querying purposes. | ||
+ | |||
+ | === Extensible Model === | ||
+ | Dataset schemata are defined as '''Profile''', and every managed collection of documents refer to a specific Profile. A complex geo-temporal dataset linked to a Profile is called '''Profiled Document'''. | ||
+ | This approach allows for the definition of tailored Profiles allowing the management of a heterogeneous collection of documents. Moreover, it supports evolution by intrinsically enabling the extensions of any Profile. | ||
+ | |||
+ | [[Image:DataCube model.png|frame|center|'''Profile''' and '''Profiled Document''']] | ||
== Deployment == | == Deployment == |
Revision as of 18:08, 2 February 2021
Contents
Overview
GeoPortal is a feature-complete framework enabling the publication, access and management of GIS projects consisting of multiple documents, images, and datasets. It can be configured with the XML specification of the GIS project data model.
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
GeoPortal key features are :
- Support for publication lifecycle
- By supporting complex Data (Meta + Payloads) archives;
- By enableing versioning, workflows, access policies;
- By supporting several materialisations (GIS, Databases, ...)
- By managing indexes (Meta catalogues, Index GIS layers)
- Maximise reusability
- By exploiting space-time GeoPortal Service
- By allowing for configurable behaviour;
- By supporting a generic meta-model;
- By offering configurable GUIs (Management grid, Insert/Edit Form, Data Viewers);
- External Data Integration
- By exploiting OGC standards.
Design
Philosophy
Aim of the framework is to maximize adaptability by supporting custom model and behaviour definition.
Architecture
The framework provides the following Dynamic GUIs, which use the Profile metadata definition to enable tailored:
- Data Collection : Form assisting users to publish GIS projects;
- GIS Viewer : allowing any user to visualise projects on a map;
- Project Viewer : assisting users in accessing information, documents, images and datasets associated with the GIS project.
Dynamic GUIs rely on java client libraries to communicate to the GeoPortal Service, managing validation and management of GIS projects. The service relies on the D4Science Workspace to store and access attached documents and on the D4Science SDI to offer OGC Compliant Services (e.g. WMS, WFS, WCS, etc.). It also uses an internal archive of Profiled Document to manage publication lifecycle and for querying purposes.
Extensible Model
Dataset schemata are defined as Profile, and every managed collection of documents refer to a specific Profile. A complex geo-temporal dataset linked to a Profile is called Profiled Document. This approach allows for the definition of tailored Profiles allowing the management of a heterogeneous collection of documents. Moreover, it supports evolution by intrinsically enabling the extensions of any Profile.