1 / 14

Minnesota Geospatial Commons Test Implementation

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?

vanig
Download Presentation

Minnesota Geospatial Commons Test Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Minnesota Geospatial CommonsTest Implementation Geospatial Commons WorkgroupChair: Mark Kotz, Metropolitan Council Presentation to State Wide Geospatial Advisory Council June 30, 2010

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

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

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

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

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

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

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

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

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

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

  12. 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.?

  13. Final Points • Driven by producers • Solid business needs • Strong executive commitment • Highly talented workgroup

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

More Related