Minnesota Geospatial Commons Test Implementation Geospatial Commons Workgroup

  • Slides: 14
Download presentation
Minnesota Geospatial Commons Test Implementation Geospatial Commons Workgroup Chair: Mark Kotz, Metropolitan Council Presentation

Minnesota Geospatial Commons Test Implementation Geospatial Commons Workgroup Chair: Mark Kotz, Metropolitan Council Presentation to State Wide Geospatial Advisory Council June 30, 2010

Overview �Test implementation of the “Minnesota Geospatial Commons” �What is it? �Who is involved?

Overview �Test implementation of the “Minnesota Geospatial Commons” �What is it? �Who is involved? �Why do this? �When – timeline?

What is the “Commons”? �A single place we all go to find and share

What is the “Commons”? �A single place we all go to find and share geospatial resources

Metro. GIS Policy Board Organization Coordinating Committee Technical Leadership Workgroup Geospatial Commons Workgroup Mn.

Metro. GIS Policy Board Organization Coordinating Committee Technical Leadership Workgroup Geospatial Commons Workgroup Mn. Geo & Advisory Councils Mn. Geo Standards Web Services Trust Issues Broker/Portal Implementation Identify Issues Define Requirements Identify Solutions Implement

Why Joint Workgroup? � Strong Metro. GIS support at top and grass roots �

Why Joint Workgroup? � Strong Metro. GIS support at top and grass roots � DNR, Mn. Geo, Mn/DOT very interested � Previous work by Standards Committee � Opportunity to collaboratively develop one web place Technical Leadership Workgroup Geospatial Commons Workgroup Web Services Trust Issues Mn. Geo Standards Broker/Portal Implementation

Why Create It? �No single web location to find or share geo data in

Why Create It? �No single web location to find or share geo data in MN �Geo apps and web services even less accessible �Opportunities to share more directly/effectively behind the scenes

Why “Commons” �“Portal” = where you find. Belongs to some one else. �“Commons” =

Why “Commons” �“Portal” = where you find. Belongs to some one else. �“Commons” = where you share. Belongs to all.

Key Functions - Find �Search � Structured interface � Spatial (e. g. bounding box)

Key Functions - Find �Search � Structured interface � Spatial (e. g. bounding box) � Metadata � Google accessible �Catalog (viewable page) �Registry (back end database)

Key Functions - Evaluate �Metadata viewer �Map viewer �Download data or connect to web

Key Functions - Evaluate �Metadata viewer �Map viewer �Download data or connect to web services �User Reviews (quality, reliability, etc. ) �Web service monitoring

Key Functions - Share �Publish � Metadata � Data for download � Services for

Key Functions - Share �Publish � Metadata � Data for download � Services for consumption �News/discussion �Shared development space �Best practices

Key Functions - Administration �Catalog maintenance �Harvesting �Security & User management �Registry of web

Key Functions - Administration �Catalog maintenance �Harvesting �Security & User management �Registry of web service users �Governance

Project Plan – Key Points �Test implementation with ESRI Geo. Portal Extension �Mn. Geo

Project Plan – Key Points �Test implementation with ESRI Geo. Portal Extension �Mn. Geo is hosting �Roughly 300 person hours �Sign off on resource commitment by 4 agencies (project sponsors) �Demo at GIS/LIS Conference in Oct. ?

Final Points �Driven by producers �Solid business needs �Strong executive commitment �Highly talented workgroup

Final Points �Driven by producers �Solid business needs �Strong executive commitment �Highly talented workgroup

Active Workgroup Members � Chris Cialek, Mn. Geo � Jessica Deegan, Met. Council �

Active Workgroup Members � Chris Cialek, Mn. Geo � Jessica Deegan, Met. Council � Jim Dickerson, Mn. Geo � Jessica Fendos, DEED � Josh Gumm, Scott County � John Harrison, Mn/DOT � Mark Kotz, Met. Council (Chair) � Susanne Maeder, Mn. Geo � Chris Pouliot, DNR � Nancy Rader, Mn. Geo � Hal Watson, DNR � Paul Weinberger, Mn/DOT