A presentation to Alberta government officials

1
A technical overview to adopting and supporting
the CGDI

• A presentation to Alberta government officials
• Edmonton, Alberta
• April 19, 2006

2
Agenda

• Overview of CGDI adoption
• Step by step adoption
• Step 1 Sharing data
• Step 2.1 Sharing map layers
• Step 2.2 Using map layers
• .

3
Implementing CGDI

• CGDI is designed for incremental adoption
• Start small
• CGDI allows you to
• Provide services
• Use services
• do both!

4
Implementing CGDI

• Four distinct yet related steps
• Adopt CGDI policies
• Adopt CGDI framework data
• Adopt CGDI standards
• Use CGDI services

5
CGDI policies

• CGDI policies promote data sharing
• Reduce / eliminate duplication of effort
• Geomatics accord
• Not strictly necessary for CGDI, but very useful

6
CGDI Framework Data

• Commit to supplying best-available data to the
  CGDI
• Use CGDI framework data in geomatics products

7
CGDI standards

• Standards for
• Publishing
• Metadata for Geodata
• Registries
• Mapping and analysis
• Web Map Services
• Web Feature Services
• many others

8
CGDI services

• Portals
• CGDI Discovery Portal (Generic)
• Other portals (NLWIS, INAC, Marine, etc.)
• Services
• Distributed
• WMS, WFS, etc.
• Centralized
• Gazetteer, etc.

9
Step 1 - Sharing Data

• Describe your public data holdings and publish
  the metadata
• FGDC GEO profile / z39.50
• Soon to come ISO 19115 / CAT 2.0
• Publish this metadata
• Use the CGDI Discovery Portal.

10
Step 2.1 Sharing Map Layers

• Publish your data using WMS
• Identify and install WMS software
• Identify key layers of information and create WMS
  layers
• Publish those services to a web site
• Use the CGDI Discovery Portal
• A new registry is under development
• A prototype registry is at http//ngistc1.agr.gc.c
  a/registry/main.html

11
Step 2.2 - Using Map Layers

• Build some client applications that use WMS
  services
• Identify and install WMS client software
• Should support Web Map Context, Filter Encoding,
  and Styled Layer Descriptor technologies.
• Identify key layers of information and create
  applications
• Embed simple maps in web pages
• e.g. using MapBuilder
• Create sophisticated Web Maps
• e.g. using Chameleon

12
Step 2.3 Customize Map Layers

• Add some Styled Layer Descriptors (SLDs)
• Identify customized views of existing WMS layers
• for a road layer, create topographic map and road
  map views
• Create the SLDs
• Publish the SLDs using a web site

13
Step 2.4 Store Map Views

• Add the ability to save Web Map Context documents
• Identify useful web map client views
• Store them using Context documents
• Publish them using a web site
• A registry is under development

14
Step 3.1 Allow Edits / Queries

• Publish your data using WFS
• Identify and install WFS software
• Identify key layers of information and create WFS
  layers
• Suitable layers are those where clients may want
  to be able to analyze and manipulate features
  (e.g. buffer)
• Publish those services to a web site
• Use the CGDI Discovery Portal
• A new registry is under development
• A prototype registry is at http//ngistc1.agr.gc.c
  a/registry/main.html

15
Step 3.2 Provide richer queries

• Add Filter Encoding capabilities
• Identify and install FE software
• Create Filters to restrict the return of
  information
• Highways instead of all Roads
• Publish those Filters to a web site

16
Step 4.1 Deliver attribute data

• Make your geolinkable data accessible for mapping
  and analysis
• Identify geolinkable data
• Identify and install GDAS software
• Create GDAS metadata
• Publish key datasets for mapping and analysis
• A prototype registry is at http//ngistc1.agr.gc.c
  a/registry/main.html

17
Step 4.2 Map attribute data

• Map GDAS data using a Geolinking Service
• Install a Geolinking Service
• Create a Geolinking WMS
• Incorporate static or dynamic WMS layers into
  your WMS client applications

18
Step 5.1 Add web processing

• Web-enable calculations and models with a WPS
• Identify and install WPS software
• Create WPS processes
• Publish calculations to a registry
• A prototype registry is at http//ngistc1.agr.gc.c
  a/registry/main.html

19
Step 6.1 Add Sensors

• Deliver data in real time using Sensor
  Observation Services
• Sensor Web at OGC is developing rapidly

20
Step 7.1 Restrict Access

• Address requirements for restricted and secure
  access
• GeoDRM at OGC is developing rapidly
• CGDI standards for Access Control and DRM are not
  yet identified
• CGDI best practice
• Implement DACS

21
Step 8.1 Increase reliability

• Standardize planned service outages
• Uptime during weekday working hours
• Use redundant services
• replicate services with a partner
• Use dynamic service binding (a.k.a. Enterprise
  Service Bus)

22
Step 9.1 Improve performance

• Use performance-enhancing technologies
• Use load balancing. E.g.
• server farms
• load-balancing routers
• Use performance-enhancing technologies. E.g.
• AJAX (Asynchronous JavaScript And XML)
• kaMap