Why Joint Workgroup? DNR, MnGeo, Mn/DOT very interested Major opportunity to collaboratively develop one web place Technical Leadership Workgroup Web Services Trust Issues Broker/Portal Implementation MnGeo Standards Geospatial Commons Workgroup
Why Create It? No single web location to find or share geo data in MN Geo apps and web services even less accessible
Why Commons Portal = where you find. Belongs to some one else. Commons = where you share. Belongs to all.
Key Functions - Evaluate Metadata viewer Map viewer Link to content provider Connect user to web service Download data and other resources User Reviews (quality, reliability, etc.)
Key Functions - Administration Catalog maintenance Harvesting Security & User management User profiles (producers) Registry of web service users Governance
Key Functions – Other? News/discussion Shared development space Best practices Web service monitoring
Project Plan – Key Points Test implementation with ESRI GeoPortal Extension MnGeo 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, MnGeo Jessica Deegan, Met. Council Jim Dickerson, MnGeo Jessica Fendos, DEED Josh Gumm, Scott County John Harrison, Mn/DOT Mark Kotz, Met. Council (Chair) Susanne Maeder, MnGeo Chris Pouliot, DNR Nancy Rader, MnGeo Hal Watson, DNR Paul Weinberger, Mn/DOT