Geospatial Task Force meeting

1

• Geospatial Task Force meeting
• March 26, 2008

2
Draft agenda

• Review/Discuss Phase 1 Objectives
• Use Case Development
• Integration with EN infrastructure and tools
• Integration with EN Schema
• ID and implement GeoRSS GML demonstration
  projects
• Wiki intro
• Updates
• Proposal for next call

3

• Use Case Development
• Diagrams and More

4
Use Case Types

• Basic business scenarios
• Tech level activity diagrams
• Basic tech strategy questions what are we trying
  to do?
• -what can we NOT do now that we know we
  need/want to?

5
The two worlds Geo and Tabular
3
6
Use Case informing Schema1) Services 2) Kind of
data
7
Defining broad business strategy options
8
Use Case Narratives and EN partners

• Use Case 1 An agency person has tabular data on
  EN XML node from their own database, uses a
  converter tool to code it for mapping, and
  exports to a mapping service on the fly. (HERE
  application)
• Use Case 2 Leveraging EN security infrastructure
  for geospatial exchanges (WA Location Finder)
• Use Case 3 Exchange of geo-coded point data on
  the EN which can be mapped using a Web Map
  Service
• Use Case 4 User has complex geo and complex
  tabular data use case which requires full GML
  (MnRAD) want to automate business process

9
Use Case A Multi - Interoperability
Multi client, EN, GEOOS Reg, WFS
WFS
EN Node
WMS
GEOSS Registry(CSW)
Show EN data resource in GEOSS
Search for data, human or REST
Select resources
Choose
files
drill down
Choose
points
EN Keys returned
Convert from/to GML
Execute EN Query
This could be poly NPL site
Return EN Data
Map Resulting Data
convert
Where is WFS going?
Return map
Map plus rich attribute
ENDS Connectivity
10
Use Case B Client subscribes to RSS Feed for new
construction permits
Could include data flow/key/identifier Emergency
response example USGS edit workflow via rss feed
11
Integration with EN infrastructure and tools

• Use of EN security on Geo Services
• Use of Geo Services with EN Services

12
Use Case C WA Geo Processing GeoFinder for
integration with EN infrastructure
13
GeoFinder Facilitated Access to Open GIS
Consortium (OGC) Data Services and to Non-Public
Geospatial Data Downloads (Innovate)
Figure 1 Architecture Diagram for GeoFinder
Facilitated Access to OGC Data Services at EPA
14
Integration with EN Schema

• Its clear we can do a lot without any
  modification to existing EN schema
• e.g., stylesheets or other translations
• Where is it useful for FUTURE schema development
  to incorporate GeoRSS/GML directly?
• Lets use the use case to figure that out

15
Identify and implement GeoRSS GML demonstration
projects

• EN / GEOSS Interoperability Demonstration Project
  (Open for discussion)
• Project Objectives
• Demonstrate discovery of GEOSS data and service
  assets made available through EPA and partners.
• Provide examples and lessons learned to help
  identify gaps in current EPA registration in
  GEOSS data and service catalogs
• Demo use of flow of EN data outside the Network
• Show how EN security model can be used by clients
  using non-EN client technology
• Utilize OpenGIS standards
• Use commercial mapping APIs and consumer grade
  client GIS technology to illustrate flexibility
  of WSOA for building operational environmental
  analysis capabilities

16
EN / GEOSS Interoperability Demo Project (cont.)

• Milestones / Deliverables
• Help finalize guidance for adoption of standards
  compliant geo encoding for EN data flows
• Develop sample schema fragments for existing
  flows
• Geo enable one or more EN flows in PNW / PS
  region using GML
• Develop 1 or 2 comprehensive use cases that
  define pilot scenario
• Select an existing client application as the
  basis for client development
• Customize client application to
• Facilitate discovery of EN, GEOSS, and other data
  / services
• Facilitate access and integration of these data /
  services
• Include 1 or more specialized geoanalytical
  processing capabilities
• Create and deliver presentation and demo for EN
  National Meeting
• Using feedback from meeting, incorporate changes.

17
Attributes of a solid pilot

• Ideas expressed by the Task Force during the
  call
• Discovery across domains, ability to add context,
  federation on steroids.
• Flood/high water stuff---
• USGS NHD event data from MnRADmodel for other
  states?
• Showing data flow as package, e.g., field data
  flow in and out
• Real simple interface that could consume data
  from multiple sources
• So folk would not have to develop it
• Shared mapping resource that could be distributed
• Operational prototype
• Transformation service expose and demonstrate as
  service
• Demonstrate activity within EN data, e.g.,
  ASIWPCA DW shared tools watershed analysis
• Filtering, scrounging data
• WQX rich data source
• Expand EN data into new areas of coverage
• Demonstrating interoperability
• Security
• Data exchange
• Discovery
• Show ability to add new resources, e.g., ability
  to plug and play

18
For demonstration

• Audience ---show that something works in
  automated
• Actually register and find and use
• GIS folks know this stuff, Node folk may not
• There is also OGC Sensor Web Enablement
• Needed feature
• Business relevant polygon or line on EN and other

19
Wikispace Introduction

• The Geospatial Task Force now has a wiki at
  http//geotf.wikispaces.com/ for members to
  provide comments, discuss issues, and share ideas
  during the time between calls
• Shawna will post all materials created for this
  task force on the GeoTF wikispace and will
  monitor the space regularly to keep it productive

20
Updates

• MnRAD / National Hydrography Dataset (NHD)
• Others?

21
Proposal for next call

• Date
• Complex geo example
• Example GeoRSS as Shared Schema Components (SSC)