Implementation of Geoportal Solutions eCommerce and Security

1
Implementation of Geoportal SolutionseCommerce
and Security

• Christian Elfers, con terra GmbH

2
Aim of a Geoportal

• Central point of access for user to distributed
  geospatial resources of a Spatial Data
  Infrastructure
• Pattern Publish-Find-Bind

Geoportal
Discovery
Management
Access
Information consumer, User
Content-Provider, Data owner
Geospatial resource
Geospatial resource
Geospatial resource
Geospatial resource
SDI
3
Role of metadata for Geoportals

• Content Provider and Data Owner use metadata to
  describe their resources (publish)
• Users utilize metadata to search, find and
  evaluate these resources (find)
• Metadata should also be used to describe
  binding facilities

Geospatial resources
Metadata
Services
Applications
Data Access
4
Current Binding-Support in ISO-Metadata

• ISO19115 Describing geospatial data resources
• Distribution Elements to access data aim is a
  manual contact or ftp-access
• Data access online via download or offine via
  postal means
• ISO19119 Describing geospatial service
  resources
• Service-Endpoint and describtion of access
  useable!
• Access via OGC Web Services

5
Binding facilities are limited

• What if more sophisticated functionalities are
  necessary?
• resources are access controlled
• license is needed for usage
• terms-of-use have to be agreed to
• payment for resource usage
• These require additional infrastructure
  facilities horizontal services
• Access control and Identity management
• Licence management
• Pricing and Ordering
• Those services are typically part of a Geoportal,
  but not yet standardized

6
Example I

• Geoportal with shop for commcercial data access

7
Architecture Geoshop (commercial data access)
Configure, buy and access data products
Find data products
Geoportal
Geoshop
Call
Catalogue
Orders
Web Pricing Ordering Service
Price configurations
Metadata
Deliver
Describe access
Produce
FME Server
Describe contents
Spatial data
8
Web Pricing and Ordering Service (WPOS)

• Web Pricing Ordering Service that is able to
  provide Geo-eBusiness functionality
• Based on WPOS Specification (OGC Discussion
  Paper 02-039r1)
• The WPOS defines four steps for each transaction
  between customer, portal and data supplier
• Capabilities list of all products available
• Price model configuration, cost optimization,
  transactions and documentation for each product
• Price calculation Returns the price based on the
  configuration
• Ordering and delivery
• Price- and Configuration model is based on XML
  complex Configuration Pricing Format (XCPF)
• Topic of OGC GeoDRM WG and the new WG Ordering
• con terra contributes to both working groups

9
Geoportal Query-Results, Open Order-Wizard
10
Configure your product
11
Place configured product in the basket
12
Finalize order
13
Example II

• Geoportal with
• Access Control/secured OGC Services

14
Access Control for Geospatial resources
15
securityManager

• Set of horizontal services to secure OGC services
• Identity- and Policy-Management using
  IT-standards
• Security-Service to control service access
• Security-Client to offer client applications a
  standardized interface
• Integrateable into existing Geoportals and their
  environements
• Aim is to keep interoperability and to do
  transparent access control
• Topic of OWS-4/GeoDRM-Testbed and the new WG
  Security
• con terra contributes to both initiatives

16
Securing OGC Services
User
Portal
Users application
6 do access control
Service provider
17
Finding a Service through metadata
18
Open a Gate as authorized user (log in)
19
Use opened Gate in any OGC Application
20
Use WMS service as authorized user
21
Public users have to agree to terms of use to
open gate
22
Use WMS service as public user
23
Conclusions

• Extended binding facilities are needed by both,
  legal and commercial aspects for Geoportals
• Horizontal services are needed
• Interoperability is a must-have
• Tend to be non-geospecific, standardization has
  to acknowledge IT specifications that are
  avaiable
• Standardization comitees should
• define how they should be used in the
  geospatial domain
• how they need to integrated in common patterns
  (P-F-B,
• Metadata, )
• Extending Specifications to SOAP may help!

24
Thanks for your attention!

• Questions?

Christian Elfers con terra GmbH christian.elfers_at_c
onterra.de