Minnesota Geospatial Commons Test Implementation Geospatial Commons Workgroup

Minnesota Geospatial Commons Test Implementation Geospatial Commons Workgroup Jessica Deegan, Metropolitan Council Presentation to State Agency Geospatial Advisory Council July 13, 2010

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 geospatial resources

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 support at top and grass roots � Metro. GIS, DNR, Mn. Geo, Mn/DOT �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 MN �Geo apps and web services even less accessible �Opportunities to share more directly/effectively behind the scenes �Users & Producers want it � Survey results of geo data consumers

Why Create It? User/Producer Survey �Nearly 540 respondents; from casual map user to GIS professional General Other (please public; 5. 6% specify); 3. 7% Non profit organization; 6. 5% Education (including students); 23. 7% Public sector; 38. 7% Private sector; 21. 9% �Downloading data to use in desktop GIS still common – but increasing need for: � Finding data in alternative ways – e. g. Google Search � Demand for services, especially geocoding is prominent. � Easy linking between services and desktop or web applications

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

Key Functions Find Evaluate Share Administration

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 services �User Reviews (quality, reliability, etc. ) �Web service monitoring

Key Functions - Share �Publish � Metadata � Data for download � Services for consumption �Feeds (RSS & Twitter) �News/discussion �Shared development space �Best practices

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 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

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

What are Web Services? od Flo nt Poi I need to know… Query Environmental Mapping Commons Information EOC el Lev es at rdin o Co Point Coordinates Address Fe ed Metro. GIS Geocoding Service lot Aerial Photos Elevation Data Download Mn. Geo DNR Water Quality s Dept. Agriculture Stream ID MPCA

What are Web Services? �Designed for easy sharing �Waiting there to use on the Internet �Real Time! – no need for downloads/updates �No need to centralize all data back