Version: Energy Scenario Modeling



Download 65.34 Kb.
Date conversion13.12.2016
Size65.34 Kb.

GEO Architecture Implementation Pilot, Phase 2

Version: <0.2>

Energy Scenario Modeling

Date: <24 May 2012>



1.Scenario: Generation of local atlases for decision-support in solar energy policy planning and private investment.

1.1Actors


Actors that benefit from the AIP-5 Energy Scenario have been identified at the early stage of the proposal.

  • GEOSS Resource Provider: for the energy scenario they include data providers in energy, geography (physical and administrative) and meteorology. They provide the raw or transformed Earth observation components (data, metadata, catalogue, methodology, services, tools…) in a GEOSS interoperable compliant form for the realization of the scenario as follow:

    • MINES ParisTech

      • Solar energy datasets.

    • French Ministry in charge of environment

      • Land Cover from Corine Land Cover 06 (CLC06)

      • Wind speed classification (10 meters high mean speed)

    • French Mapping Agency (IGN)

      • Natural and protected areas, administrative limits

    • Università degli Studi di Genova (UNIGE)

      • Air temperature at 2-meter height. Point-wise uncertainty in air-temperature mapping

  • SBA Integrator: The scenario aims at providing access to a combination of irradiation map and other meteorological data (e.g. temperature) with additional geospatial data (e.g. elevation, land cover, administrative units…) at a scale suitable for analysis (1/250 000) witch will benefit to local decision makers. Based on the use of the GCI and Community Resources, the SBA Integrator will developed and deployed the persistent applications required to achieve the scenario goals.

    • MINES ParisTech will develop a dedicated WebGIS Client for geodata visualization and data retrieval.

    • Other client solution capable-of providing visualization, retrieval and/or analysis and modeling have been identified in the AIP-5 response. This includes the Pyxis and TU Dresden GIS client solutions.

  • GEOSS User: This scenario address two types of GEOSS users:

    • High end-users like local policy planners that need easy accessible information that is recent, of known quality including uncertainties in order to support local policies for energy planning and attract investors.

    • Private investors and/or installers of renewable energy systems, who conduct studies for sitting, sizing and want to estimate return-on-investment on their solar plants.

2.Implementation

2.1Deployed Components

In order to provide the portfolio of maps to the GEOSS users all the granular layers and associated information need to be deployed, discoverable and accessible. This require several interoperable components including:



  • A Community Portal

  • A GeoServer hosting OGC compliant Web Services

  • A Catalogue providing standard ISO Metadata for dissemination

  • Geodata Visualization WebGIS client

As a whole this architecture follows and enables the GEOSS “Search, Find, Bind” recommendations.


  • GEOSS Energy Community Portal – www.webservice-energy.org

    • Several OGC, Web Map Services (WMS) and Web Processing Services (WPS) giving access to Solar Energy, Wind Energy, Elevation, Shadow and Environmental Impact Assessment maps, datasets and Algorithms. This Energy Community Portal is registered in the GEOSS Registry since 2009.




  • A Geographical Server

    • http://geoserver.webservice-energy.org/geoserver/ows?service=wcs&version=1.1.1&request=GetCapabilities

    • Hosted under the Energy Community Portal domain, this GeoServer host several tens of resources as WMS and WFS.




  • OGC Catalogue Service for the Web (CSW) based on Geonetwork (http://geonetwork-opensource.org/)

During the AIP-5 framework MINES ParisTech will deploy an OGC CSW Catalogue. This catalogue will offer a single Internet access point for users seeking data, maps, imageries, algorithms related to energy and environment relevant to all parts of the globe.

This catalogue will enable users to register and publish data and services to a directory (such as a registry or catalogue). It will allow publishing service metadata describing the capabilities of the services and the network address.

During the AIP-5 framework this catalogue will either registered on the GEOSS Registry or directly harvested via the GEOSS Data Broker such as the EuroGEOSS Data Broker. This will enable the harvesting process of the catalogue content and consequently the dissemination of the corresponding resources through the Geo Web Portal (GWP).

It is expected that the GEOSS Data Broker as well as the GWP will take into account the complete set of metadata that will be made available through the catalogue. Special attention will be paid to certain fields that enable the “GEOSS Data CORE” and the “Helper Application” flags to be properly displayed to the GEOSS user if available in the original metadata.




  • Geodata Visualisation Clients

MINES ParisTech will provide a customized geographic WebGIS client to allow GEOSS users to select and display geographically layers for a particular area of interest. It will based on the OpenLayers framework and will be available under the Energy Community Portal.

Other generic GIS clients such as the one from Pyxis and possibly the one from the TU Dresden (GLUES) will be tested towards the local atlas maps portfolio.


3.Scenario event.



Legend: Services in blue Products in red Actors in orange

Steps

Description

Number (#) and Use Case Description

00

 Local policy planners, private investors and/or installers of renewable energy systems (GEOSS User) are searching for resources regarding solar energy for decision making on a local area. These resources as a form of Web Services are discovered through the GEO Portal. The GEO Portal provides minimum information about available services and how to access them. This includes GEOSS Data CORE and Helper Application information.

D1. Search for resources in Registry, Clearinghouse, Community Catalogs and Portals.

 


01

Based on resources found at Step 00 and thanks to the Helper Application link, the GEOSS User accesses a WebGIS client on the Energy Community Portal displaying available energy related resources. Those resources are available on the Energy Community Portal Geoserver as OGC Web Services. The GEOSS User can triggers on demand OGC Web Services (WMS, WFS) to perform site siting and/or site sizing analysis in order to come-up with decision making. The GEOSS User can download the corresponding map layers allowing him to run legacy desktop client applications.

A1. Access web maps services and display a composite map to the user.

A3. Access data from using a service that allows for user selection of data returned based on content.

A6. Exploit - visually and analytically- in Client Applications.


02

The WebGIS client as well as all Solar Radiation and related geographical meteorological Web Services have been previously registered in the GEOSS Catalog and Service Registry (CSR) by the GEOSS Resource Provider. In order to allow Search & Discovery mechanism the GEOSS Resource Providers have previously registered all OGC Web Services within the OGC/CSW Energy Catalog. The GEOSS Resource Provider has created the appropriate Metadata and ingested this into the Catalog to allow harvesting by the GEOSS Clearinghouse. 

P1. Register resources in GEOSS Components and Services Registry (CSR) or Community Catalog.

P2. Deploy services for use in GEOSS

P3. Service Provider tests its deployed service using a proper Test tool discovered in the GEOSS CSR.


03


Reference to the GEOSS Resource Provider datasets as well as IPR (Intellectual Properties Rights) and data quality, will be provided if appropriate within the WebGIS Client.

P1. Register resources in GEOSS Components and Services Registry (CSR) or Community Catalog.

A6. Exploit - visually and analytically- in Client Applications.



Legend: Services in blue Products in red Actors in orange
Table – Steps in the Energy Scenario

4.AIP Engineering Use Cases

4.1AIP Transverse Use Cases


The GEOSS AIP Architecture approach supports the several SBA communities with a reusable process of SBA Scenarios and Engineering Use Cases.1 Scenarios are implemented by use cases. Use cases describe reusable functionality of the GEOSS service oriented architecture implemented through Interoperability Arrangements.
A summary of GEOSS AIP Use Cases is shown in Figure with details provided in the following tables. In addition to the actors shown in Figure the GEOSS Actors involved in GEOSS use cases are listed in Table 2.
20120127_usecasediagram

Figure – GEOSS AIP Use Case Summary Diagram


Table – Publish Resources Use Cases

Name

Description

Actors (may be optional)

P1. Register Resources

(AIP-3 ER: 1)



Register resources in GEOSS Components and Services Registry (CSR) or Community Catalog

P2. Deploy a Service

(AIP-3 ER: 2)



Deploy services for use in GEOSS.

  • GEOSS Resource Provider

  • SBA Integrator – optional

P3. Test a Service

(AIP-3 ER: 09)



Service Provider tests its deployed service using a proper Test tool discovered in the GEOSS CSR.

  • GEOSS Resource Provider

  • SBA Integrator – optional

P4. Develop SBA network

(AIP-3 ER: 14)



Identify resources in particular services relevant to an SBA. Promote concerted use on a larger-scale

  • SBA Integrator

  • GEOSS Resource Provider


Table – Discover Resources Use Cases

Name

Description

Actors (may be optional)

D1. Search for Resources

(AIP-3 ER: 4)



Search for resources of interest. Variations: user initiated (e.g. GWP), process initiated, searching data sharing conditions.

  • GEOSS User

D2. Aggregate Metadata2

(AIP-3 ER: 3)



Harvesting and/or query metadata from community catalogs or services via GEOSS Clearinghouse

  • GEOSS Resource Provider

  • SBA Integrator

  • GCI Operator

D3. Conduct semantic search

(AIP-3 ER: 13)



Utilize mediated vocabularies to extend GEOSS search queries across disparate domains or communities.

  • GEOSS User

D4. Semantic mapping

(AIP-3 ER: 12)



Register, mediate, and map between disparate vocabularies used to describe GEOS resources.

  • SBA Integrator

  • GEOSS Resource Provider

  • GCI Operator

D5. Launch Enabler App

(AIP-4)


Associated with resources discovered in GCI are enabler applications, e.g., clients. User launches help application including context from previous search.

  • GEOSS User

Table –Visualize and Access Use Cases

Name

Description

Actors (may be optional)

A1. Web Mapping

(new)


Access web maps services and display a composite map to the user. Allow user to modify map layers. Variation: include use of portrayal service

  • GEOSS User

A2. Access files

(new)


Retrieve a file from an access server using FTP. Variations include: user-initiated, process-initiated.

  • GEOSS User if user initiated.

A3. Access data via services

(AIP-3 ER: 5&6)



Access data from using a service that allows for user selection of data returned based on content. Variation: use of Access Broker

  • GEOSS User if user initiated

A4. User Authentication

(new)


User login with single sign-on (SSO). May used with Use Cases: A2, A3, W1. Variations: user-initiated, process-initiated.

  • GEOSS User

A5. Access with Acknowledgement

(new)


May used with Use Cases: A2, A3, W1. Variations: user-initiated, process-initiated.

  • GEOSS User

A6. Exploit Data

(AIP-3 ER: 7)



Exploit - visually and analytically- in Client Applications using information retrieved through access use cases.

  • GEOSS User


Table – Process and Automate Use Cases

Use Case

Description

Actors

W1. Execute Processing Service

(AIP-3 ER: 11)



Invoke a processing service, to produce new derivative data resources. Variations: user-initiated, process-initiated

  • GEOSS User

W2. Construct and Deploy Workflow

(AIP-3 ER: 8)



Design, deploy and execute a workflow. Described in Business Execution Language (BPEL) or any other script language.

  • SBA Integrator

  • GEOSS User

W3. Process with Waiver or License

(new)


Use metadata containing information about the waiver or license to handle aggregation of data, derived data, re-use of data, and layered data.

  • GEOSS User if user initiated


Table – Maintain and Support Use Cases

Use Case

Title

Actors

M1. Register Interoperability Arrangements

(AIP-3 ER: 10)



Register Interoperability Arrangements in the GEOSS SIR

  • GEOSS Resource Provider

  • SBA Integrator

  • GCI Operator

M2. Share Best Practices

(AIP-3 ER: 15)



Create a Best Practice relevant to GEOSS in the GEOSS BP Wiki

  • GEOSS User

  • GEOSS Resource Provider

  • SBA Integrator

  • GCI Operator

M3. Monitor Services

(AIP-3 ER: 10)



Services registered with GEOSS are routinely monitored for network connectivity and application response.

  • GCI Operator

M4. User Registration

(new)


User information is provided to a centralized authentication server to support single sign-on (SSO) with GEOSS providers.

  • GEOSS User

  • GCI Operator

M5. Metrics Management

(new)


GEOSS data provider, or GCI, gathers access and use metrics and stores information for reporting to the GCI. Variations: reports pushed, reports available for query

  • GEOSS User

  • GEOSS Resource Provider

  • GCI Operator



4.2Specialized Use Cases


N/A

5.Implementation

5.1Deployed Components


In order to provide the portfolio of maps to the GEOSS users all the granular layers of information need to be deployed, discoverable and accessible. This follows the GEOSS search, find, bind recommendations.

Firstly, we will make available all granular map layers and relevant associated information as OGC WMS (Web Map Service) and/or OGC WFS (Web Feature Service. This information will be available on a dedicated geographical server (GeoServer: http://geoserver.org) at the Energy Community Portal (www.webservice-energy.org) operated by MINES ParisTech.


In this scenario various components have been provided or re-used. This includes, a Community Portal, a Catalogue, OGC compliant Web Services, Geodata Visualization Portlets and a Generic Portal.

The Error: Reference source not found below shows how they are linked together and a detailed description of each of those components with screenshots is presented hereafter.




  • GEOSS Energy Community Portal – www.webservice-energy.org

    • Several W3C Web Services (WSDL) giving access to Solar Energy, Forecast, Hydro, Shadow, Elevation, datasets and maps

    • Several OGC, Web Map (WMS) and Web Processing Services (WPS) giving access to Solar Energy, Elevation, Shadow and Environmental Impact Assessment datasets, maps and Algorithms

This Energy Community Portal is registered in the GEOSS Registry since 2009 (see Error: Reference source not found and Error: Reference source not found).


  • EnerGEO OGC Catalogue Service for the Web (CSW)

The EnerGEO Catalogue serves as a prototype demonstrator to generally communicate architecture, logic and value of SDI and as a platform for the integration of discovery potential of different user groups in industry, science and management. It is also an example for collaboration of various partners (see Error: Reference source not found). It offers a single Internet access point for users seeking data, imagery and analytical software packages relevant to all parts of the globe. It connects users to existing databases and portals and provides reliable, up-to-date and user-friendly information – vital for the work of decision makers, planners and emergency managers.

The community portal with search facilities is currently designed and implemented based on international standards for catalogue discovery (OGC Catalogue Services CSW 2.0.2). The current state of a community-adopted metadata editor for ENERGEO is shown in Error: Reference source not found.

One first and obvious mission of such a portal is the ‘find’ task which is ideally planned to be intrinsically linked to the ‘bind’ task referring to the OGC “publish-find-bind” logic (see OGC reference model ORM: www.opengeospatial.org/standards/orm and Error: Reference source not found). The first logic step for the user is referred to as discovery services and is intrinsically linked to the definition of metadata. “How-To” documents are developed to assist users with specific tasks (e.g. how to document metadata information, how to convert ASCII to raster files,…). All these approaches are integrated in the portal (see Error: Reference source not found)

ENERGEO enables users to register and publish data and services to a directory (such as a registry or catalogue). Initially, ENERGEO allows publishing service metadata describing the capabilities of the services and the network address.



  • The GENESIS Legacy interconnection Toolbox (Error: Reference source not found) is a software component to easily transform legacy applications into Web Services with Standard compliant interfaces to facilitate the integration of existing applications into Service Oriented Architectures. It supports OGCs Web Processing Service Specification to launch processing jobs on remote servers. In addition it facilitates the deployment of catalogue services implementing the EO and CIM extension Package of the OGC CS-W ebRIM application profile.




  • The GENESIS Portal is a Portlets (JSR-286) based Portal (Error: Reference source not found) that allows to easily generate the user interface (client applications) to interact with remote web services via standard interoperable interfaces such as OGC Cataloguing using ebRIM profile of CS-W (CIM, EOP, Sensor) and the OGC WPS. The client applications on the GENESIS Portal are grouped according to their thematic domain. A specific category has been created for the Energy Scenario: “Energy Environmental Impact”. Two services can be discovered within this category: the Environmental Impact Assessment Map Service and the Environmental Impact Assessment Point Service. These two services are based on the GENESIS generic WPS client that includes portlets for the WPS service invocation and service results display. The GENESIS Portal also provides a generic workflow for the remote WPS interactions.




  • The GENESIS Geodata Visualisation Portlet system (Error: Reference source not found, Error: Reference source not found, Error: Reference source not found, Error: Reference source not found, Error: Reference source not found) provides a powerful and flexible WebGIS Client that can be instantiated in various forms and with varying functionality inside any JSR286 compliant portal or used standalone.  Each GENESIS Service Client (e.g. WPS client) can be shown with a customized geographic Web interface to capture geographic input into services and to display geographically referenced results.  GENESIS service providers can make use of a configuration portlet to entirely configure their cartographic interface to their liking.  The map configurations are fully managed through an internal geographically enabled Content Management System with versioning, access right control and gathering of usage statistics.

The Geodata Visualisation Portlets allow:



    • Connecting to OGC Web Map, Feature, Coverage and Sensor Observation Services

    • Import and visualize vector and raster data in various formats with on the fly-reprojection

    • Export maps and data in various formats

    • Configurable layer management: functionality with grouping, legends, transparency control, …

    • Range of typical map navigation tools including zooming and panning tools, overview map and zoom to gazetteer

    • Advanced querying functionality for feature data with customizable query forms and dynamic result tables for each specific feature data set.

    • Possible to display graphs on the basis of feature datasets (Bar, Pie, Column, X-Y charts) and Observations (time series plots)

    • Play animations of time-varying geographic data (WMS & features)



1



2 See also the Catalogue Use Case in “OGC Engineering Report: Water Information Services Concept Development Study,” OGC Document 11-013r6, 2011-07-012.

Page


The database is protected by copyright ©dentisty.org 2016
send message

    Main page