GeoViQua-PTB GeoViQua-PTB December 2011:December 2011:GEOPortal implementation GEOPortal implementation statusstatus

7 December 2011

AUTHOR:Nicola Trocino (Sapienza Consulting)

Nicola.trocino@sapienzaconsulting.com

Gregory Fallourd (Sapienza Consulting)Gregory.fallourd@sapienzaconsulting.com

+39 06.942.932.42

Sapienza Proprietary information 2011

REF: SAP-SD-ESA-EOP-PRE-0082REF: SAP-SD-ESA-EOP-PRE-0082

Content

1.GEOSS new requirements

2.GEOPortal 2.1 presentation

3.GeoViQua portal: testing environment

4.Portal Test options for GeoViQua

Sapienza Proprietary information 2011

GEOSS requirements for GEOPortal (GWP) Improve dataset visibility

Promote GEOSS data-CORE

Help data access Provision of visual help for resource and component quick

recognition

New GCI in GEOSS architecture: EuroGEOSS broker – EuroGEOSS Broker (EGB) makes the link between GWP

and Clearing House (CH)– Shall improve search capabilities

GCI 2011GEOPortal

www.geoportal.org

EuroGEOSS Broker

GEOSS clearinghouse

GEOSS resourcesData Access, Dissemination, Processing, Others

GEO secretariat Homepage

GEOSS registry

GEOPortal: www.geoportal.org New 3D globe: Google Earth plugin:

– Improved Performances and capability visualisation compared to previous flash plug-in – Direct load of KML files described through discovered metadata – Direct load of geoRSS feed

Enhanced data access:– Context passing from GEOPortal to Data Service Provider which allow

direct access/browsing of remote services through OpenSearch description document

– Direct access to data through GENESI and FedEO(open data and service access)

– New Map Viewer allowing direct load of WMS Implementation of GEOSS validated categories:

– Component structured for easy query and retrieval Interaction with Broker via CSW 2.0.2

GeoViQua portal: testing environment Testing Environment visible at: http://

scgeoviqua.sapienzaconsulting.com Clone of GEOPortal actually on production:

– Based on Liferay 5.1.2 platform, J2EE– Rely on Liferay database to leverage Portal functionalities– Local GeoNetwork catalogue for custom functionalities (geoRSS

aggregator, SBAs, Country list) Access point to datasets and catalogue resources:

– Through calls to EuroGEOSS Broker search services – Result display in:

• Text lists based on organised results found by the broker• In 2D(WMS resources) /3D Globe (kml, geoRSS)

Will interface with GeoViQua and catalogues through CSW 2.0.2 Integration of GeoViQua development will be performed by Sapienza Portel or remote portlet (WSRP) could be used to embed new

component in the portal

Portal functionalities in GeoViQua contextJIRA requirements relevant to portal testing environment :

1.Quality search

2.Quality visualisation

3.Peer reviewing and sharing

1. Quality Search and Result Display Portal (based on catalogue and broker functionalities and services)

could allow: – Search of Data and Dataset based on their:

• Type• Location or Bounding Box• Date range• Sensor • Usage• Quantitative quality threshold or specified values

– Display results:• Easily recognisable quality symbols when available (eg. Star based

classification)• Classify dataset results according to their quality ranking

– Portal data display depends on results provided by the catalogue through the broker

– Portal functionality depends on:• How metadata are organised in the DB• Catalogue service interfaces allowing specific queries• Results provided by catalogue and broker

Quality Parameters and Search

Quality metadata:– Quality parameters shall be standardised– The Clearing House and the Broker shall

implements the standards

NOTE: Portal is a the bottom of the chain and the visualization of quality info depends on the availability and search-ability of info from the other GCI components (EGB , Clearing House, Catalogues)

2. Quality visualisation & processing quality data Data quality could be visualised as:– Quality info availability (via icons) – 2D charts – Inter-comparison maps (overlay on map viewer)– Quality/error flags (on result list, metadata description or

3D globe)

3. Peer Reviewing and metadata commenting

Metadata results visualised by user are decoupled from where they are stored:

– GWP -> EGB -> Catalogue -> DB– Editing/adding information to metadata requires retracing

metadata source– Editing metadata requires access rights

Options:– Creating 3rd party DB linking metadata with reviews and

comments• Portal shall allow comments addition to metadata:

– Free-text comment– Data rating– User details (identity, company/agency, contacts)– Auto: Date/time– Add interactive links

– Create direct links between Portal and source DB: security and feasibility issues

Thank you