Spatial Data Infrastructures: Architecture

1
Spatial Data InfrastructuresArchitecture
Approach

• X-BorderSpatial and urbanization planning
• Aachen

Some slides are based on Ioannis Kanellopoulos
Improving Access to Environmental Information in
Europe the INSPIRE Initiative
2
Overview

• Design Metaphor
• SDI Basis (Integration mechanism)
• SDI Functions and Components
• Relevant SDI Player

3
1.1. Spatial Data Infrastructure Bridge Building
eBusiness Service WPOS
Environment B
Environment A
Security Service WA/SS
Data Access Service WMS,WFS,..
Encoding jpg,GML,...
4
1.2. Example of data mismatch at borderline (1)
Discrepancies in Transport Network Data between
Northern Ireland and Ireland, Source MOLAND-NI
5
1.3. Example of data mismatch at borderline (2)
6
2.1. Architecture Distributed Environment

• Setting up and connecting of initially unknown
  resources
• Publish data sets (name, ID, abstract, layer) and
  services (Type, URL) as meta data (ISO
  19115/19119/OGC Capabilities)
• Find data sets and services with catalog search
  engine (CS-W)
• Bind Application(-clients) to data and services
  (URL, ID, names), versioning

publish
find
bind
7
2.2. Getcapabilities Request

• A mechanism for service self-describing
• Service interface (type, version, operations,
  content)
• Version negotiation
• Fundamental OGC Operation (BSM/OWS common)
• Requires only a valid URL
• Request example http//mywms.org/servlets?REQUEST
  GetCapabilitiesVERSION1.1.0SERVICEWMS
• WMS response example
• Service (getmap, HTTP Get URL, HTTP POST URL)
• Layer (name, abstract, styles, boundingbox,)

8
2.3. Used HTTP request methods

• HTTP GET
• Key-value-Pair
• Supported by regular browsers
• Limited length (4096?)
• HTTP POST
• XML (Object) encoding for more complex
  information models
• Not limited
• No encoding required (space, ä, )
• HTTP SOAP
• Transport more defined
• Use of powerful tools and components
• Transport of binary ascii possible

WMS
WFS
Geo-DRM?
9
2.3. Architecture Integration by Cascading

• Integration of distributed resources
• with the same service type interface
• simple and powerful

WM-Client
OGC defined interface
WMS-Service
WMS-Client
WMS-Serv.
WMS Serv.
10
2.4. Cascading Security eBusiness
WSC-Client
WMS-Client

• Enhanced functionalities need to support basic
  cascading mechanism
• Examples
• Web Security Service
• Web Pricing Ordering S.
• Web Terms of Use Service
• geoDRM
• and corresponding clients

WSS-Service
WMS-Serv.
WSC
WMClient
WSS-Service
WSS-Service
WMS-Service
WMS-Service
11
3.1. SDI core Components
12
3.2. Architecture with Components
13
3.3. Hands-on Approach Skunk works

• Staff some IT knowledge required (Network, web
  server, IT Administrator)
• Web Mapping Service, version 1.0.0, 1.1.0
• Free Software, e.g. deegree, httpwww.deegree.org
  
• Many services are running on tomcat web server
  (apache.org) and using Java (java.sun.com)
• Internal test Use own Web Mapping Client
• Set-up De-Militarized Zone (DMZ)
• External test external WMC, e.g.
• http//tim-online.nrw.de
• Input yours WMS URL into the WMC

14
3.4. Cluster-wide services

• Some network services support content services,
  e.g
• Catalog (CS-W)
• WAS Web Authentication Service
• Monitoring Service
• Question Who is operates them?
• Maintenance of meta data crucial for acceptance
• Monitoring Service helpful in a larger
  environment
• Federation of catalogs
• CS-W 2.0.1/ ISO Application Profile
• Federation with harvesting and distributed search
  possible
• URLs of current core of 5-8 catalogs managed by
  CeGI

15
4.1. Relevant Player

• INSPIRE
• More http//inspire.jrc.it
• OpenGeoSpatial Consortium
• More http//www.opengeospatial.org
• XML Schema Schemas.opengeospatial.net
• ISO
• http//www.isotc211.org

16
4.2. INSPIRE Characteristics

• ESDI build on top of National and Regional SDIs

• More than just data
• it includes documentation, means to discover,
  access, evaluate, ..
• it includes organizational agreements needed to
  coordinate/ administer at various scales
• it influences both data collection and
  application development through minimal
  appropriate standards and policies

17
4.3. INSPIRE principles

• The following principles govern INSPIRE
• a) that spatial data should be collected once and
  maintained at the level where this can be done
  most effectively
• b) that it must be possible to combine seamlessly
  spatial data from different sources across the EU
  and share it between many users and applications
• c) that it must be possible for spatial data
  collected at one level of government to be shared
  between all the different levels of government
• d) that spatial data needed for good governance
  should be available on conditions that are not
  restricting its extensive use
• e) that it should be easy to discover which
  spatial data is available, to evaluate its
  fitness for purpose and to know which conditions
  apply for its use.

18
4.4. Open Geospatial Consortium

• The OGC
• Not-for-profit, international consortium
• 250 industry, government, and university members
  (about 1/3 from Europe)
• Specification Development Program (since 1994)
• similar to other Industry consortia like W3C,
  OMG, etc.
• Class A liaison with ISO/TC211
• Interoperability Program (since 1999)
• a global, innovative, hands-on engineering and
  testing program designed to accelerate interface
  development and bring interoperability to the
  market
• OGC Web Service Testbeds (OWS)
• Interoperability Experiments
• Outreach and Community Adoption Program (since
  2002)
• awareness raising, education and training,
  encourage take up of OpenGIS interfaces,
  business development
• Subsidiaries OGC Europe, OGC Australia,

OGC Vision A world in which everyone benefits
fromgeographic information and services made
available across any network, application or
platform. OGC Mission Our core mission is to
deliverspatial interface specificationsthat are
openly available for global use.
19
4.5. Service Standards Hierarchy
Global
ISO, W3C, IETF
Cross - Industry (Horizontal)
OASIS, WS-1, ANSI, CEN, ISO, UN/CEFACT,
RosettaNet / UCC...
10 more
Scope
Industry Based (Vertical)
XX-XML, RosettaNet, OASIS, OGC, SEDRIS, OMA,
eMSA, SIF....
hundreds more
Organisation Specific
Microsoft, IBM, Network Providers ,
hundreds to thousands more
Shared Business Process Specificity
20
Summery

• Understanding
• SDI Architecture
• Basic SDI Mechanisms
• SDI Functions
• WS abbreviations
• First Hands-on experiences
• Use WMS HTTP GET first
• Share URLs with lists
• Get to know relevant players
• Find more resources
• Start to understand tendencies

21
Contact

• Universität Münster
• Institut für Geoinformatik
• Dr. Roland M. Wagner
• eMail roland.wagner_at_uni-muenster.de