16-00_Habitats Networking Architecture Istanbul

Social Validation of INSPIRE
Annex III Data Structures in
EU Habitats


Premysl Vohnout

Jachym Cepicky

Michal Sredl

Karel Charvat

Help Service

Remote Sensing

Habitats Networking
Architecture and Invoking
Services


HABITATS NETWORKING
ARCHITECTURE

The HABITATS Networking Architecture has the goal
of defining a system able to ensure the
interoperability and security of provided data and
services. In particular, since integration with the
INSPIRE initiatives is needed, it is based on:

•

A methodological approach able to define a
system architecture that is scalable and adaptable to
the specifications and standards currently being
defined;

•

The adoption of a Service Oriented Architecture
based on Web Services and SOAP technology.

INSPIRE Networking
architecture

HABITATS NETWORKING
ARCHITECTURE

HABITATS NETWORKING
ARCHITECTURE

•

Data layers
–

management data and files
on storage, eventually guarantee access to
external sensors

•

Server (engine layer)
–

defines tools, which
guarantee basic services on the server side
–

supplying service

•

Client layer
–

is client side of Web services,
which guarantee access of users to
services

•


HABITATS NETWORKING
ARCHITECTURE

•

Application layer is some form of wrapping
elementary client services into application
or into such form, which could be used by
other Web tools

•

Presentation layer contain such web tools,
which allow to combine and publish single
objects from the application level as part of
Web presentation


HABITATS NETWORKING
ARCHITECTURE

The reference laboratory has the following
roles:

•

To offer a possibility for testing new
services

•

To offer access to global data for pilots

•

To support implementation of cross
-
pilot
scenarios

•

To make the Habitats services discoverable
for external platforms


HABITATS NETWORKING
ARCHITECTURE

INSPIRE

INVOKING SERVICES

The INSPIRE Spatial Data Service and
Invoke Service
–

Draft, implements rules
defining that Invoke service has to be
accessible via Internet and offers a mean to
invoke the linked spatial data services.



INSPIRE

INVOKING SERVICES

Invoke shall support in order to allow clients
invoking spatial data services. Taking into
account the potentially wide diversity of
interfaces and protocols, invoke services
are services that allow access to sufficient
service metadata to enable the activation or
execution of the spatial data service.


HABITATS INVOKING
SERVICES

In Habitats we are dealing with the broader
understanding of Invoking Services. We will
consider this as a possibility to invoke any
type of geospatial services according to
ISO19119 classification with platform. This
means running services without the
necessity to have any application on the
client side. In this first version of the
deliverable we are dealing with invoking
service using Reference Laboratory

INVOKING OF DISCOVERY
SERVICES

The reference laboratory uses its own
catalogue, but there are also possibilities to
invoke another catalogue from a remote
platform into the system. There are two
possibilities:

•
To harvest metadata into the reference
laboratory

•
To provide direct search of remote
catalogues


INVOKING OF DISCOVERY
SERVICES

INVOKING OF VISUALISATION
SERVICES

•
From catalogue

•
Adding URL

INVOKING OF VISUALISATION
SERVICES

INVOKING OF VISUALISATION
SERVICES

WMS

coordinate transformation

Invoking WFS, WCS

See proxy4ows http://proxy4ows.org/about/

Proxy4OWS enables to visualize and work
with large vector data and raster data in the
web environment. It basically transforms
OGC Web Feature Service and OGC Web
Coverage service to OGC Web Mapping
service calls.

Invoking WFS, WCS

WPS

INVOKING

In HSLayers, a new class WPSClient was
introduced. The class implements generic
OGC WPS client with graphical user
interface. HSLayers WPSClient performes
GetCapabilities request on the server and
creates a list of available processes.
Processes are rendered into a drop
-
down
menu.

WPS

INVOKING

When a user chooses the process he wants
to run, DescribeProcess is called. Based on
ProcessDescription response, a generic
input form is generated. After all input data
is specified, and when users click the
button, an Execute request is called, and
when it is finished, an execute response is
parsed and outputs of the form are filled.


WPS

INVOKING

SOS
INVOKING

The actual version of component supports
only operations from OGC SOS Core
Profile which must be implemented in every
OGC SOS compliant services.



SOS
INVOKING

Operations supported in the actual version
are:

•
GetCapabilities

•
DescribeSensor

•
GetObservation


SOS
INVOKING

Tady chybi obrazek

Embed component

Pure HTML

–

this type is based on pure
HTML and does not contain any other UI
components

Simple ExtJS
–

this type uses ExtJS library
for generating UI container

Advanced ExtJS
–

this type uses ExtJS
library also as Simple ExtJS type and also
contains another UI components (tree with
list of all layers in map)


Embed component

Embed component

Tady chybi obrazek

Learn

more

http://www.slideshare.net/kcharvat/habitats
-
deliverable
-
441

http://inspiredhabitats.ning.com/group/habitat
s
-
service
-
toolkit

http://www.habitats.cz/