Difference between revisions of "GIS Viewer"

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…')
 
m (Leonardo.candela moved page Gis Viewer to GIS Viewer)
 
(8 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
|}
 
|}
  
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.
+
 
This document outlines the design rationale, key features, and high-level architecture, as well as the deployment context.
+
GisViewer is a web application system that allows you to interactive explore, manipulate and analyze geographic data.
  
 
== 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 goal is to provide a standalone interactive analysis tools for information that has one or more spatial characteristics, such as environment maps, geospatial areas, points of occurrence, and so on, all in a web app that must have a simple and intuitive interface that is also the most general possible.
  
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 18:
 
=== 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.
+
GisViewer is based on Exploratory Data Analysis (EDA) approach, using synergistically computer capabilities to do complex calculations and the man's ability  to identify cognitive patterns.
 +
 
 +
The web-app uses the layer concept: a layer is a minimal visual form of spatial data, it can be a region map, a vector (such as a points set), a variables distribution, and so on. The GisViewer can show one or more layers in an interactive map, allowing users to dissect both information of a layer, and the relationships between more layers. It's possible to examinate more overlapped layers, by setting their transparencies, formats and filters.
 +
Tabular geospatial data can be extract by interactive selectiion of geographical area. Finally, geospatial data can be exported using several output formats.
 +
 
 +
 
  
 
=== 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;
+
* '''GisViewer 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 Managers''': a set of internal objects and widgets that represent a layer info;
  
* '''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;  
+
* '''Openlayers Map''': a set of internal objects and widgets that manage the map, taking advantage of [http://openlayers.org Openlayers Framework];
  
* '''Occurrence Points Operations''': a connector to another d4Science interface which is able to operate on tabular data, by performing visualization, aggregation and transformations.
+
* '''Data Features''': a set of internal object and widgets that show and represent tabular geospatial data;
  
* '''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.
+
* '''Utils''': a set of utilities, it include a [http://en.wikipedia.org/wiki/Contextual_Query_Language cql filter] manager and a [http://en.wikipedia.org/wiki/Web_Map_Service WMS]/[http://en.wikipedia.org/wiki/Web_Feature_Service WFS] request url maker;
  
A diagram of the relationships between these components is reported in the following figure:
+
* '''Geonetwork''': an external network of spatial objects, used for highly scalable storing of geospatial resources;
  
[[Image:occpointsreco.png|frame|center|Occurrence Points Reconciliation Service, internal architecture]]
+
* '''GCubeGisViewer''': 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:gisViewerDiagram.png|frame|center|GisViewer, internal and external architecture]]
  
[[Image:occpointsarchitecture.png|frame|center|Occurrence Points Reconciliation Service, deployment schema]]
+
== Deployment ==
 +
All the components of the widget 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 ===
+
<!-- == 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.
+
=== Well suited Use Cases === -->

Latest revision as of 14:27, 6 July 2016


GisViewer is a web application system that allows you to interactive explore, manipulate and analyze geographic data.

Overview

The goal is to provide a standalone interactive analysis tools for information that has one or more spatial characteristics, such as environment maps, geospatial areas, points of occurrence, and so on, all in a web app that must have a simple and intuitive interface that is also the most general possible.


Design

Philosophy

GisViewer is based on Exploratory Data Analysis (EDA) approach, using synergistically computer capabilities to do complex calculations and the man's ability to identify cognitive patterns.

The web-app uses the layer concept: a layer is a minimal visual form of spatial data, it can be a region map, a vector (such as a points set), a variables distribution, and so on. The GisViewer can show one or more layers in an interactive map, allowing users to dissect both information of a layer, and the relationships between more layers. It's possible to examinate more overlapped layers, by setting their transparencies, formats and filters. Tabular geospatial data can be extract by interactive selectiion of geographical area. Finally, geospatial data can be exported using several output formats.


Architecture

The subsystem comprises the following components:

  • GisViewer Central Controller: manage all the internal components and their interactions;
  • Layers Managers: a set of internal objects and widgets that represent a layer info;
  • Openlayers Map: a set of internal objects and widgets that manage the map, taking advantage of Openlayers Framework;
  • Data Features: a set of internal object and widgets that show and represent tabular geospatial data;
  • Utils: a set of utilities, it include a cql filter manager and a WMS/WFS request url maker;
  • Geonetwork: an external network of spatial objects, used for highly scalable storing of geospatial resources;
  • GCubeGisViewer: 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:

GisViewer, internal and external architecture

Deployment

All the components of the widget 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.