Difference between revisions of "Geo Explorer"

From Gcube Wiki
Jump to: navigation, search
(Created page with '{| align="right" ||__TOC__ |} A service for performing assessment and harmonization on occurrence points of species. The aim is to provide users with an interface and methods fo…')
 
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category: gCube Spatial Data Infrastructure]]
 +
 
{| align="right"
 
{| align="right"
 
||__TOC__
 
||__TOC__
 
|}
 
|}
  
−
A service for performing assessment and harmonization on occurrence points of species. The aim is to provide users with an interface and methods for assessing if occurrence points are repeated, anomalous or for performing processing and aggregation operations on such data.
+
 
 +
GeoExplorer is a web application that allows users to navigate, organize, search and discovery internal or external layers.
 
This document outlines the design rationale, key features, and high-level architecture, as well as the deployment context.
 
This document outlines the design rationale, key features, and high-level architecture, as well as the deployment context.
  
 
== Overview ==
 
== Overview ==
  
−
The goal of this service is to offer a single entry point, in a certain scope, for processing, assessing and harmonizing occurrence points belonging to species observations. Data can come from the Species Discovery Service or they could be uploaded from a user by means of a web interface.  
+
The main objective of this application is to offer centralized environment for access to the entire spatial data in a certain scope. By external visual components, as [[Gis_Viewer | GisViewer]] it's also possible to explore and analyze a personal set of selected resources.
  
 
The service is able to interface to other infrastructural services in order to expand the number of functionalities and applications to the data under analysis.
 
The service is able to interface to other infrastructural services in order to expand the number of functionalities and applications to the data under analysis.
 +
 +
<!-- === Key features ===
 +
 +
<font color=red>TO BE COMPLETE</font> -->
  
 
== Design ==
 
== Design ==
Line 16: Line 23:
 
=== Philosophy ===
 
=== Philosophy ===
  
−
This represents an endpoint for users who want to process species observation in order to explore their coherence and to extract some hidden properties from collected data coming from difference sources. This is meant as a complement to other services for species and occurrence points analysis.
+
GeoExplorer is based on [http://www.infovis-wiki.net/index.php/Visual_Information-Seeking_Mantra Visual Information-Seeking Mantra], which is an approach to summarize the best user-interations order to get some information from a visual application: Overview first, Zoom and filter, Details on demand.
 +
 
 +
The application use a cloud network of geospatial resources called [http://geonetwork-opensource.org/ Geonetwork], these resources are tipically [http://geoserver.org Geoserver] Layers. It's still possible to get external layers by their [http://en.wikipedia.org/wiki/Web_Map_Service WMS] representation.
 +
 
  
 
=== Architecture ===
 
=== Architecture ===
 
The subsystem comprises the following components:
 
The subsystem comprises the following components:
  
−
* '''Inputs Managers''': a set of internal processors which manage the variety of inputs that could come from users or from other services;
+
* '''GeoExplorer Central Controller''': manage all the internal components and their interactions;
  
−
* '''Occurrence Point Processors''': a set of internal objects which can invoke external systems in order to process data or extract hidden properties from them. These include Clustering, Anomaly Points Detection etc.;
+
* '''Layers Grid Manager''': a set of objects and widgets that allows layers discovering by a grid;
  
−
* '''Occurrence Points Enrichment''': a connector to another d4Science service (the [https://gcube.wiki.gcube-system.org/gcube/index.php/Occurrence_Data_Enrichment_Service Occurrence Enrichment Service]) dealing with the enrichment of occurrence points associated information, which is able to add indications about the chemical and physical characteristics of the oceans and earth;  
+
* '''Layer Info Panel''': widget that show all layer info (details on demand);
  
−
* '''Occurrence Points Operations''': a connector to another d4Science interface which is able to operate on tabular data, by performing visualization, aggregation and transformations.
+
* '''External WMS Layer Importer''': a set of objects for import an external WMS layer;
  
−
* '''Processing Orchestrator''': an internal process which manages the interaction and the usage of the other components. It accepts and dispatches requests coming from outside the service.
+
* '''Layer Preview Generator''': an utility for obtain a preview image of a layer;
  
−
A diagram of the relationships between these components is reported in the following figure:
+
* '''Data Retrieving Logic ''': a set of object that manage data filter, paging and ordering, exploiting the Geonetwork OGC Catalog Service for the Web ([http://en.wikipedia.org/wiki/Catalog_Service_for_the_Web CSW]);
  
−
[[Image:occpointsreco.png|frame|center|Occurrence Points Reconciliation Service, internal architecture]]
+
* '''GCube GeoExplorer ''': an external wrapper which interact with some GCube components (such ASL, Workspace Light Tree, and so on).
  
−
== Deployment ==
 
−
All the components of the service must be deployed together in a single node. This subsystem can be replicated on multiple hosts and scopes, this does not guarantee a performance improvement because it is a management system for a single input dataset.
 
  
−
=== Small deployment ===
+
A diagram of the relationships between these components is reported in the following figure:
  
−
The deployment follows the following schema as it needs the presence of other complementary services.
+
[[Image:geoExplorerDiagram.png|frame|center|GeoExplorer, internal and external architecture]]
  
−
[[Image:occpointsarchitecture.png|frame|center|Occurrence Points Reconciliation Service, deployment schema]]
+
== Deployment ==
 +
All the components of the service must be deployed together in a single node. This subsystem can be replicated on multiple hosts and scopes, this does not guarantee a performance improvement because it is a management system for a single input dataset.
  
 
== Use Cases ==
 
== Use Cases ==

Latest revision as of 13:23, 6 July 2016



GeoExplorer is a web application that allows users to navigate, organize, search and discovery internal or external layers. This document outlines the design rationale, key features, and high-level architecture, as well as the deployment context.

Overview

The main objective of this application is to offer centralized environment for access to the entire spatial data in a certain scope. By external visual components, as GisViewer it's also possible to explore and analyze a personal set of selected resources.

The service is able to interface to other infrastructural services in order to expand the number of functionalities and applications to the data under analysis.


Design

Philosophy

GeoExplorer is based on Visual Information-Seeking Mantra, which is an approach to summarize the best user-interations order to get some information from a visual application: Overview first, Zoom and filter, Details on demand.

The application use a cloud network of geospatial resources called Geonetwork, these resources are tipically Geoserver Layers. It's still possible to get external layers by their WMS representation.


Architecture

The subsystem comprises the following components:

  • GeoExplorer Central Controller: manage all the internal components and their interactions;
  • Layers Grid Manager: a set of objects and widgets that allows layers discovering by a grid;
  • Layer Info Panel: widget that show all layer info (details on demand);
  • External WMS Layer Importer: a set of objects for import an external WMS layer;
  • Layer Preview Generator: an utility for obtain a preview image of a layer;
  • Data Retrieving Logic : a set of object that manage data filter, paging and ordering, exploiting the Geonetwork OGC Catalog Service for the Web (CSW);
  • GCube GeoExplorer : an external wrapper which interact with some GCube components (such ASL, Workspace Light Tree, and so on).


A diagram of the relationships between these components is reported in the following figure:

GeoExplorer, internal and external architecture

Deployment

All the components of the service must be deployed together in a single node. This subsystem can be replicated on multiple hosts and scopes, this does not guarantee a performance improvement because it is a management system for a single input dataset.

Use Cases

Well suited Use Cases

The subsystem is particularly suited when experiment have to be performed on occurrence points referring to a certain species or family. The set of operations which can be applied, even lying on state-of-the-art and general purpose algorithms, have been studied and developed for managing such kind of information.

Retrieved from "https://gcube.wiki.gcube-system.org/index.php?title=Geo_Explorer&oldid=25107"