Live From Lisbon
Standards in Action in Canada:
Laying the foundation for
infrastructure
LIsbon, March 2001
Henry Kucera
Canadian Advisory Council
Holonics Data Management Group Ltd
www.holonics.ca
Any time..!
Any where..!
Any data..!
Partners/Sponsors
Centre for Topographic
Information (Sherbrooke)
GeoConnections
International Standards Organization
(Standards Council of Canada)
Partners/Participants
Holonics Data Management Group
CubeWerx
Helical Systems Ltd.
Safe Software Inc.
Caris
Intelec Geomatics
National interests in Sustainability
…. Information on many processes
Mine Operations
Pesticide Permit
Environmental
Assessment Act
Forest Tenures
Watersheds
Management
X
Water Licenses
X
Fisheries Stream class A
X
Lakes Database
Waste Permit
X
Fish Stock Releases
Hatchery Mgt
Rare & Endangered
Species
X
X
Petroleum
Exploration
Ecosystem
Integrity
X
(biophysical habitat
WETLAND)
Fisheries
Shipping of
products
Coastal Zone
Management
Adopting open standards & specifications
from the international arena is critical
Canada is building several national infrastructures:
 Canadian Geospatial Data Infrastructure;
 GeoScience Knowledge Initiative;
 National Forest Information System;
 Ocean Portal and Marine infrastructure;
 National Transportation Network
Key to success is seen in open standards and specifications and
the SCOTS products based on the standards:
 ISO TC211 and ISO JTC1 SC32
 OGC (Open GIS Consortium): WMT-1,2 and now MPP;
 W3C (World Wide Web Consortium): XML, XHTML;
 3i (Information Interoperability Institute): Industry led group working on open
source interoperbility tools based on ISO TC211 & JTC1-SC32, OGDI and OGC
WMS-WFS;
Strategic Goals for
Standards in Canada
Strategic goals are to:
achieve interoperability by establishing a common information
infrastructure for use by all stakeholders
 promote and leverage existing and evolving Canadian Technology
and expertise (e.g., CEONet, MID-C, AquaGIS, III/OGDI, and others);
 gain competitive advantage by consolidating various independent
Canadian initiatives;
 nurture the development of Canadian expertise and products to
provide entry to foreign markets
 cooperate with international activities to ensure the Canadian
solution is in tune with international community;
 ensure the compliance of Canadian products by funding standards
activities (Standards Council of Canada);
 demonstrate solutions for the global delivery of integrated geospatial
information, applications and services.

Canada is adopting Standards and profiles to
support implementations in many environments
Multi-source
Multi-resolution
Multi-temporal
Multi-schema
Marine Charts
ITD
1:50K
Input Data
Integration
PITD
1:250K
Imagery
FRAMEWORK DATA
VMAP
1&2
VITD
UVMAP
1:50K
1:10K
CADRG
1:250K
•LIDAR
•SAR
•etc
Vector
Data
Tactical
Data
Business Data
Usage
INFORMATION
GENERATION
SEARCH & RESCUE
SURVEILLANCE
EDUCATION
& TRAINING
POLICY &
PLANNING
Data
Assimilation &
Management
INTEGRATION
& CONFLATION
SERVICES
DISTRIBUTED
PRODUCTION
DATA MANAGEMENT
&
PRODUCT DISSEMINATION
Standards in Action
Demonstration Highlights
Canada has created a demonstration site to showcase the
components of a standards-based distributed spatial architecture.

Distributed navigation, data access, viewing and download as an implementation
of Simple feature Access (ISO/TC 211 19125-1 & 19125-2), Metadata (ISO/TC 211
19115), and Spatial referencing by coordinates (ISO/TC 211 19111);

GeoSpatial Standards based data products, related to ISO/TC 211 19107 (Spatial
Schema), ISO/TC 211 19110 (feature cataloging methodology), and IS0/TC 211
(spatial reference by coordinates);

Multilingual support for metacontent as per ISO/TC211 19115 (Metadata);

Open Geospatial Data Store Interface, related to ISO/TC 211 19119 (Services);

Geographic Markup Language, related to the ISO/TC 211 19118 (Encoding);

Electronic nautical charts, related to the ISO/TC 211 19117 (Portrayal);

Self-Defining Structure (SDS) and Helical Hyperspatial Codes (HH Codes) as a type
of coverage function related to the proposed ISO/TC 211 19123 (Schema for
Coverage Geometry and Functions) and 19124 (Imagery and Gridded Data
Components).
Points of Implementation
in a three tier architecture
USI
CubeView
HH Viewer
DSSI & Spatial Direct
Clients
Spatial Fusion client
USI Service Registry
Registry
HTTP,
XML
19119
WMS/WFS(OGC)
OGDI
GML
XML
Spatial Direct HH Tile
Services
CW_Convert
SDS
Utilities
CW_Load
FME
File Server
SDS, VPF, others
OGDI
WMS
Servers
Caris CubeServ
Fusion
Server
XML
SQL
Data Base
CD 19125-1,2
CubeSTOR, Oracle 8i
TC211
FGDC
GILS
Catalogue
NTDB Feature Catalog
M3/Cat
MetaManager
CEONet
Access to Data
Distributed navigation, data access, viewing and download as
an implementation of:
 Metadata (ISO/TC 211 19115), so we can find data to access.
 Catalogs (ISO/DIS 19110) to describe the type of data we are
accessing,
 Simple feature Access (ISO/TC 211 19125-1 & 19125-2),
Need a common spatial Schema so we know what types we are asking
for so we have TC211 19107 (Vector) and TC211 19123 (Image and
Gridded Data), and
 Implementations based on queries using the harmonized simple
feature model interfaces implemented based on (ISO TC211 19125)

 The ability to fuse and tranform information for different
purposes is enabled by Spatial referencing by coordinates
(ISO/TC 211 19111);
MetaData in Canada

CTIS - National Topographic Database


Canadian Earth Observation Network (CEONet)


Various data holdings, collections and services are described using
FGDC profile and communicated via a Z39.50 interface.
CGKN and other infrastructure initiatives use various
metadata profiles such as:
GILS,
 the Canadian Metadata Standard (171.3-95)
 the Dublin Core
 or a hybrid (subsets or supersets of a given specification).
Recognizing the need for a more complete, flexible and standards
compatible approach GeoConnections funded the development of
a next generation metadata manager and interface.


Products available are described in detail using metadata stored in a
database environment. As in feature catalogue, a view complying to ISO
CD.3 19115, Geographic information - Metadata standard is available.
Multi-lingual is supported by the databases.
NTDB example of a standards based
metadata & feature catalog (ISO 19110)


NTDB Feature Catalogue and Metadata
 Feature
Catalog: CTIS at Sherbrooke, developed a database
environment to manage the feature catalogue allows us to document
semantics of geospatial features and provide it according to ISO/DIS
19110, Geographic information - Feature cataloguing methodology.
This environment is functional and can be consulted on Internet.
 Metadata Products available are described in detail using metadata
stored in a database environment. As in feature catalogue, a view
complying to ISO CD.3 19115, Geographic information - Metadata
standard is available.
NTDB Data as part of CGDI
 Migration
of the existing data (60 millions records /100 GB of data) to Oracle
8i using standardized geometries (ISO CD 19125-1, Geographic information Simple feature access - Part 1: Common architecture and ISO CD 19125-2,
Geographic information - Simple feature access - Part 2: SQL option).
 This infrastructure allows to use several commercial client applications for
consulting the data (locally or via Internet).
Multistandard, Multilingual
Metadata CATaloguing = M3CAT





Web based cataloguing tool
Tested with users
Available free
Development funded by the GeoConnections
Program
Features


Approval process
Use of various technologies
Web (standalone and Internet)
Various DBMS
Support of HTML, XML and SGML
Interface to Z39.50 servers
Import and Export





M3CAT



Multi “standards” and templates:
provided with FGDC, GILS, ISO, NBII and PGGQ
Multilingual with templates, profiles and semiautomatic user driven language translation
Cataloguing aids





Wizards and Help
Metadata according to data set type (templates)
Multiple levels of data sets with inheritance
Online validations and reference parameters in pick lists
Map interface (multi-projection, multi datum)
M3Cat - Standards based
meta tool



Meta model to allow users to insert and
use standards, profiles of standards and
templates
Multilingual and cultural templates
Semantic Analysis Tools for mapping
between languages and templates
Datastore
Z39.50 Service
Database
CubeView
Service
Interface
Spatial Direct
Java API
O G C c o m p lia n t
C lie n ts & M a p S e rv e rs
OGDI
Interface
Spatial Load Facility (FME & OGDI)
Data Cleansing , Topology Validation
& Quality Assurance
OGDI
Server
Tomcat JSP Apache Web
Server
Server
CubeSERV
Server
CubeSTOR Server
S Q L C lie n ts
(e .g ., H H V ie w e r)
CARIS Server
SQL Engine
DLG
EOO
..Many
CubeSTOR
Spatial Cartridge
Oracle 8i
Spatial
Server in
Fredericton
Data in
Sherbrooke
Oracle Network Computing
Architecture
Multiple datasets
Data in
Ottawa,
Victoria,
NASA etc.
Text
Cartridge
•Spatial data
•Attribute data
•Meta data
•Spatial data
•Attribute data
•Meta data
OGDI - Feature Server:
OGDI
A P I C a lls
u s in g
(C ln _ )
OG
DI
D riv
er
F la t
F ile
D a ta s to
re
The OGDI is a very
useful tool in the
absence of a
completed web
feature server
specification
OGDI
A P I C a lls
w ith R P C (c ln _ )
G ra s s la n d
S o ftw a re
C lie n t
In fo rm a tio n C o m m u n ity
F la t
F ile
D a ta s to re
OGDI
D riv e r
GLTPD
OGDI
A P I C a lls u s in g
(C ln _ )
D a ta S e rv e r
OGDI
DB
D riv e r
DBMS
C L IE N T / S E R V E R
A rch ite ctu re
U sin g O G D I
S e rv e r
In fo rm a tio n C o m m u n ity
It has been
implemented by
several vendors
including Intergraph,
CubeWerx and
Global Geomatics
Access using an Integrated Web Client or
CubeVIEW
Java Server
pages
Java Integration Server
Spatial data
CubeWerx Java API
Metadata and
non-spatial data
CubeSERV
(Cascading)
Integrated
Capabilities
Html pages
Integrated
Maps
CubeSTOR / Oracle
Other ISO 19125
compliant data
stores
A Core Underlying Metadata model
CLASS IF I CATI ON S CHEM E
r efe r en c ed in
th e d efin itio n o f
SUB JECT_CLASS_ USAG E
# ID
o L O CAL N AM E
fo r
r efe r en c ed in
fo r
p ar tition of
provide ac cess path
P ARAME TE R
a re fer e nc e to
#
*
*
*
*
o
o
o
o
a re fer e nc e to
L INEAGE
#
*
o
o
o
o
o
CI TATI ON
ID
EF FEC TIVE_ DAT E
C ART O_ NU MBER
PR OJ EC T_ N UM BER
F IELD _YEAR S
D ESC RIPTIO N
EXPIR Y_ DAT E
ID
IS F IL T ER ED
IS OPT ION AL
MU LT IVAL UED
NAME
D EFAUL T
D ESC RIPTIO N_ EN
D ESC RIPTIO N_ FR
SEPARAT OR
c on tstr a ins
c ha r ac ter iz es
p ar tition ed into
is c h ar a cte r iz e d b y
GE OM ET RY E LE ME NT
CAT AL OGUE E NT RY
a re fer e nc e fo r
#
*
o
o
*
*
o
*
m ain tain ed by
fo r
th e c us tod ia n o f
ID
NAME
D ESC RIPTIO N_ EN
D ESC RIPTIO N_ FR
UR L
CR EATIO N D AT E
R EVISION D ATE
AU TH OR ITY
CAT AL OGUE
DAT A SE RV I CE
P OLY GO N
L INE
P OI NT
b ou n d
r ep r es e nta tion of
d es c rib ed b y
CONT ACT
#
*
o
o
o
o
o
o
o
o
ID
NAME
D ELIVER Y_ POIN T
AD MINIST RATIVE_ AREA
PO ST AL _ CO DE
C OU NT R Y
VO IC E_T EL EPH ON E
F ACSIMIL E_ T EL EPH ON E
E- MAIL_ ADD RESS
C ON T AC T IN ST RU CT ION S
a ty p e o f
r ep r es e nte d b y
DAT A SE T
d es c rib ed b
y
QUAL I TY
#
*
o
*
o
o
ID
EF FEC TIVE_ DAT E
R EVISION _D AT E
REPO RT _ TEXT
Q UAL ITY_T YPE
EXPIR Y_ DAT E
fo r
d es c rib ed b y
fo r
in
o
o
o
o
o
o
o
o
o
D ATASET _T ITL E
O RIG INATO R
PU BL ISH ER
PU BL ICATIO N_ DAT E
PU BL ICATIO N_ EDIT IO N
PU BL ICATIO N_ ISSU E
PU BL ICATIO N_ SER IES
SC AL E
IM AG E
c ov e re d b y
S PATI AL EX TE NT
S UBJE CT
o C W_ F ID
p ar tial e xte n to f
a co llec tion of
fou nd in
#
o
*
o
o
o
C W_ F ID
N AME
GSC_ SO UR CE_ CO VER
M ISC
D B_L INK
L EGEND _C OD E
Ac cess by
in sta nc e o f
a n in sta nc e of
fo r
S CHEME AS SO CI AT I ON
in sta nc e o f
c olle ctio n o f
link to
q ua lifie d by
link to
CONT ACT ROL E
#
*
o
o
ID
RO LE_N AME
D ESC RIPTIO N_ EN
D ESC RIPTIO N_ FR
*
o
o
o
o
EF FEC TIVE_ DAT E
PR OG RESS
U PDATE_ FR EQ UENC Y
U PDATE_ LEVEL
C OM MEN T_ TEXT
b as e d o n
d es c rib ed b y
la ye rcolas
f s of
s ub s et o f
c las sifie s
DAT A CO LL ECTI ON
fo r
fo r
F EATURE CLASS US AGE
fo r
S TATUS
c olle ctio n o f
F EATURE CLASS
c olle ctio n o f
# ID
o N AME
* SU BJ ECT
o C UST OD IAN
la ye r o f
fo r
CONT ENT
m an ag e d b y
c on c ep tis
fo rc o ntr a in e d b y
o fin vo lve d in
p ar e nt o f
q ua lifie d by
fo r
USAGE
* USE
o U SE_ DAT E
o U SE_ LIM ITAT IO N
d es c rib ed b y
SUB JECT CO NCEPT
T C SP AT I AL REF ERENCE INFO RM AT IO N
d es c rib ed b y
d efin e c oo r din a te s fo r
# ID
* EF FEC TIVE_ DAT E
o R EVISION _D AT E
#
*
o
o
o
o
*
o
ID
NAME
C L ASS T YPE
AU TH OR ITY
D ESC RIPTIO N_ EN
D ESC RIPTIO N_ FR
CR EATIO N D AT E
R EVISION D ATE
th e e qu iva le nt o f
e qu iva le nt to
S UBJE CT S YNONYM Y
a me mb er o f
r efe r en c e in
d efin ed in
h as me mb e rs in
a ss ign e d to
d efin ed by
S UBJE CT RANK
SUBJEC T M EM BERSH IP
th e r an k of
c hild of
OGC based Web Map and Feature
Server Architecture
OGC Web Map Server
Specifications (V1.0.0)
Presentation
• Web Browser
Rendering
• Map server
OGC Web Feature Server
Specifications (Draft V0.0.10)
Feature Delivery
• Feature Server
• Presentation
• Map
service
Server service
• Feature
Server service
Providing for Symbology Using
OGC Web Map Server Specification V.1.0.0
OPERATIONS:
Presentation
Web Browser
OGC Web Map Server
Specifications (V1.0.0)
• Describe Capabilities
• Select Features
• Generate Map
REQUEST:
• GetCapabilities (HTTP Get)
• GetMap (HTTP Get)
• GetFeatureInfo (HTTP Get))
Rendering
Map server
RETURN :
• Capabilities (XML)
• Map (Many Formats)
• FeatureInfo (MIME Type)
Introducing concept of “Style Layer Descriptor” inside GetMap request
Feature denifinition and Styled Layer Descriptor in
XML as a type of encoding as defined by
ISO/TC 211 19118
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE GetMap SYSTEM "GetMap.dtd" >
<StyledLayerDescriptor>
<NamedLayer name="INWATERA_1M:Foundation">
<NamedStyle name="0x0000FF/0x2E4AAB"/>
</NamedLayer>
<NamedLayer name="BUILTUPA_1M:Foundation">
<UserStyle>
<PolygonSymbol>
<Geometry>
<FetchFeatureProperty name="wkb_geom"/>
</Geometry>
<StrokeColor>#507070</StrokeColor>
<StrokeWidth>1.0</StrokeWidth>
<StrokeOpacity>1.0</StrokeOpacity>
<FillColor>pink</FillColor>
<FillOpacity>1.0</FillOpacity>
</PolygonSymbol>
</UserStyle>
</NamedLayer>
Encoding a reference to a SLD
stored centrally
<NamedLayer name="COASTL_1M:Foundation">
<NamedStyle name="0x101040"/>
</NamedLayer>
<NamedLayer name="ROADL_1M:Foundation">
<UserStyle>
<LineStringSymbol>
<Geometry>
<FetchFeatureProperty name="wkb_geom"/>
</Geometry>
<StrokeColor>#ff0000</StrokeColor>
<StrokeWidth>1.0</StrokeWidth>
</LineStringSymbol>
</UserStyle>
</NamedLayer>
<NamedLayer name="AEROFACP_1M:Foundation">
<NamedStyle name="http://www.magi.com/~wtl/images/gif16/2269_16.gif"/>
</NamedLayer>
</StyledLayerDescriptor>
An example of rendering with Styled
Layer Descriptor (SLD)
Generating S57 Electronic
Chart Portrayal

The Dynamic data Portrayal is done using
IHO/IMO - S57 rules from Object Based Standards
Architecture SQL 19125

The ENC-S57, DNC Products are generated from
VLDB Multibeam Data sets using the Proposed
Matrix/ Raster Imagery and Gridded Data
Components ISO19124 in conjunction with S57
Hydrographic extended Catalogs.
But we can do more.

A proposed approach for an
image and gridded data: HHCode




HH Codes are based on the Rieman Hypercube
Structure: a coverage function where data elements
may be of different sizes, and the coverage may be in
a number of dimensions.
A coverage is defined as an object that uses a
coverage function to return one or more attribute
values for any direct position within its spatiotemporal domain.
(Schema for Coverage Geometry and Functions,
ISO/TC 211 19123).
SDS Self Defining Structure is an implementation of
of the Riemann Hypercube Structure for image and
gridded components (ISO TC 211 19124)
Scalable architecture for files, applications
and RDBMS Architectures
Data Administration and Management

Encapsulation of Metadata and Information associated
with data elements .

Encapsulation of methods related to data elements.

Handle VLDB large Volumes of data

Improve and maintain Data Quality (metadata imbedded
in the structure)

Facilitate existing Data Management Infrastructure
(connects to existing filed based on relational systems)

Facilitate Interoperability between applications.

Reduce Data Duplication and Data Loss
A Hierarchical view of
metadata deployment
Finding
Time, Place,
Theme, Focus
Assessing
Relevance, Quality, Cost,
Timeliness, Concepts, Methods, Sources,
Using
Classifications, Questionnaires, Codebooks,
Dictionaries, Database Schemas, Record Layouts
Managing
Harmonization, Integration, Creation, Preservation, Retention, Disposal
Benefits of SDS architecture for
distribution, replication and archive

Ease Storage and Retrieval of VLDB data

Fast Distributed Data Access over high speed, extranets
and wireless networks.

Ease Data Maintenance (using metadata to manage
update).

Facilitate Stability and Extendability of Long Term
Archives

Reduce impact of re-organization of data schemas
Extract old data
for re-evaluation
Acquisition
Update mechanism
supported by
synchronization of
metadata in the sds
coverage
Convert to SDS
(Candidate
Coverage Type
19123/19124)
Acquisition
&
Preprocessing
Validate Data
Helical Tools
Store in RDBMS
and dense
Data
Archives
Diff Analysis
Data
Supersede
SDS
Utilities
2D/3D
Editing
2D/3D
Multi attribute
Interpolation
Access
Mechanisms
Web Mapping
Services
FME- SDS
CARIS
Internet
Web
Applications
Products
2D/3D
cleaning
Data Fusion
2D/3D
2D/3D
Data Adjustment
visualization
Datums
Tiling
Data Analysis
and
Objectifying
Wireless
PCI
GIS/
Visualization
Managing the data and
metadata Database
•Session Layer
•HH Viewer
•HH Utilities
•CHS DIR
•Other tools
Source documents
metadata
Session info and
parameters
CHS DIR
Source data
Source Database
Server Environment
•CubeSTOR
•HH Utilities
•Task Manager
Source Database
Process control
Session Data
Standards (and SCOTS) will enable
the enterprise architecture
DISTRIBUTED
SOURCE DATA
(profiles, schema, quality)
Maps, imagery:
NTDB, AVHRR
digital elevations,
DTED etc.
Classified
imagery
Non-traditional
resources
3D models
Catalog
Service
Q
u
a
l
I
t
y
a
s
s
u
r
a
n
c
e
L
o
a
d
I
n
g
T
o
o
l
s
Common
Environment
for data
Management
Registry
Service
Transformation
Service
Feature
Service
SCOTS Tools to
support schema
mapping and
structure integration
Portrayal
Service
S
e
r
v
I
c
e
s
I
n
t
e
r
f
a
c
e
Clients
Publisher
Editor
Discovery
Viewer
Map
Service
observations,
descriptions
Heterogeneous
sources
Service Architecture
OGC, ISO TC211
Pluralistic distributed
database environment
Distribution
Multi-tool
support
Technology standards - coupled with best
business practices pave the way to open systems
Formulation
Evaluation
Development
Prototype & Testing
Methods &
Standards
Practices
Tools
Muito Abrigado!
Questions, Comments and Discussion
Come and visit the demonstration site
Descargar

Title