1. Background
   1. OpenStreetMap Capability Prototype
      1. Create our own version of the OSM software stack not available to the public
      2. We are looking at limited partnerships to test collaboration using the OSM software stack
      3. Use USGS Best Practices Model for Transportation
      4. Apply standards so that edits will be consistent between agencies
      5. Collaboratively edit roads using the OSM software stack.
   2. OpenStreetMap
      1. OpenStreetMap is a free editable map of the whole world. It is made by volunteers.
      2. OpenStreetMap allows you to view, edit and use geographical data in a collaborative way from anywhere on Earth.
   3. We are leveraging the OSM idea and technology, not duplicating it
   4. USGS OSMCP work group
      1. Kevin McNinch
      2. Eric Wolf
      3. Chuck Matthys
      4. Greg Matthews
2. Standards
   1. Mapability
      1. Standards_Level1_Mapping Document
      2. Standards_Level1_Mapping Spreadsheet
   2. Geocoding
   3. Routing
   4. HPMS
3. Agencies and Responsibilities
   1. USGS - Editing of US Routes, Interstates, Ramps and Service Roads.
   2. Kansas (tenative) - Data Access & Support Center (DASC) - Editing of State Routes.
   3. Team Members Link
4. Data
   1. Roads from State of Kansas
      1. Crosswalked to USGS transportation schema
      2. Loaded into the OSM software stack that the USGS sets up
   2. Area of Interest
   3. Roads from state contributors
   4. Roads from Federal Agency Contributors
   5. Roads from County and City Contributors
   6. Roads from individuals
5. Timeline
   1. 1 to 3 months after OSM technology stack set up
      1. Start collaboration outline and have agreement
      2. Create Project Portal web site for collaboration
      3. Get the standards in place for mapability
      4. Get OSMCP up and running
      5. Start capability prototype with collaborator and edit roads
      6. Create lessons learned document
   2. Rapid prototyping
      1. Add more standards
      2. Work on dif detection and exchange with FME
      3. Add additional agencies if OSMCP works
      4. Add additional themes if OSMCP works
6. Licensing Issues
   1. OSM - Creative Commons License
      1. Attribution - ShareAlike 2.0
   2. USGS - Public Domain
   3. Summary - The USGS is unable to download OSM data and use it without adopting their license structure
   4. Summary - The USGS can share our data with OSM as a one way upload to OSM
7. Technology
   1. Open Street Map Technology Stack
      1. Open Source Software
      2. Web-based Feature Editing
   2. Hardware
      1. USGS Hosted Server
      2. External access via web
      3. Investigating Using "Cloud" Based Computing Resources
8. Next Steps
   1. Formal Requirements Gathering
   2. More Partners
   3. Additonal Themes
   4. Expanded Geographic Area
   5. Public Volunteer Component
   6. Additional Standards
   7. Exchange Diff Files Over Geographic Areas