E-Government Initiative

1. E-Government Initiative Geospatial Information One-Stop FGDC Coordination Group January 10, 2002 John Moeller

2. Geospatial One-Stop • Project outline: • Develop and implement Framework Data standards • Inventory, document and publish Framework data holding in NSDI Clearinghouse • Publish metadata for planned data acquisition and update for Framework data • Prototype and deploy enhanced data access and web mapping services for Federal Framework data • Establish comprehensive Federal Portal as a logical extension to the NSDI Clearinghouse Network

3. Current Model Data User Data User Data Use r Data Use r Data User Data User Data User NSDI Gateway Portal Portal Portal Data Producer Data Producer Portal Data Producer Data Producer Data Producer Data Producer

4. Other standards- based portals Future Model Federal Users Civilian Users National Policy Tribal Users Makers Commercial Users State Users Local Users DoD Users International Users NSDI One-Stop Portal State Governments Civilian Sector Local Governments Commercial Sector Tribal Governments DoD Federal Government

5. Geospatial One-Stop • Schedule: • Oct 25 Initiatives announced • Oct 30 FGDC and DOI convened a small writing team • Nov 6 Briefing for FGDC Coordination Group • Nov 7 Draft to DOI - Scott Cameron • Nov 13 Draft to OMB • Mid Nov Draft distributed to Coordination Group and Stakeholders • Dec 10 Revised Draft to DOI and OMB • Dec 20 & Jan 10 E-Gov Program Managers Meetings with OMB • Early 2002 Anticipated Start date • Fall 2003 Anticipated Completion of Geospatial Information One Stop Tasks

6. Geospatial One-Stop • What Are Agencies Asked To Do • Support the Initiative • Provide In-Kind Support for Standards Development • Theme Managers • Outreach • Support to Standards Working Group • Documentation of Existing Data and Plans • Network of Liaisons to support Initiative • Support to Project Management Team • Funding support • Web Mapping and Interoperability • Portal • Replication Services • Modeling and Facilitation

7. Scope: Framework Layers • Elevation • Orthoimagery • Hydrographic Data • Administrative Boundaries • Transportation Networks • Cadastre • Geodetic Control

8. Module 1Standards Development and Cost Benefit Analysis • Tasks: Lead: • Requirements analysis (1a) FGDC Staff • OMB BDR (1b) OMB/FGDC • Cost Benefit FGDC Staff • Draft B/C (1c) • Final B/C (1d) • Standards Development for 7 Framework Themes ( Working Draft (1e), Committee Draft (1f), Final Draft (1g), and Endorsed Standards (1h)) • Elevation USGS • Orthoimagery USGS • Hydrographic Data USGS • Administrative Boundaries Census • Transportation Networks DOT • Cadastral BLM • Geodetic Control NOAA/NGS

9. Module 1Standards Development and Cost Benefit Analysis • Timelines Duration • Requirements analysis 30 days • OMB BDR 150 days • Cost Benefit 270 days • Draft - 210 days • Final - 60 days • Standards Development for 7 Framework Themes 525 days • Working Draft - 240 days • Committee Draft - 120 days • Final Draft - 120 days • Endorsed Standard - 45 days

10. Module 1Standards Development and Cost Benefit Analysis • Performance Goals • Requirements analysis • Goal: Common requirements and business needs for Framework Data content nationally • OMB BDR • Goal: Completion of an OMB Data Call for identification of Federal Agency expenditures and outputs for collection and use of Framework categories of data • Cost Benefit • Goal: Completion of a Cost Benefit analysis of the value of commonly shared spatial data infrastructure and standards and tools that support integrated use of this data (Should this be for NSDI in total or for Framwlework?) • Standards Development for 7 Framework Themes • Goal: Standards for Framework layers are completed and deployed using a common modeling approach

11. Module 2Inventory and Document Existing Framework Data • Tasks: • Complete an inventory and document Agency Framework Data holdings using FGDC Metadata Standard and publish the Metadata in the NSDI Clearinghouse (2) • Lead: Each Agency for its own data • Timelines • Inventory, Document and Publish 150 days • Performance Goals • Invnetory, Document and Publish • Goal: All Framework data has completed Metada which is accessible and searchable in the NSDI Clearinghouse

12. Module 3Inventory and Document Planned Data Collection Activities • Tasks: • Complete an inventory and document all planned Agency Framework Data collection activities using FGDC Metadata Standard and publish the Metadata in the NSDI Clearinghouse (3) • Lead: Each Agency for its own data • Timelines • Inventory, Document and Publish 210 days • Performance Goals • Inventory, Document and Publish • Goal: All planned data collection activities for Framework data are documented and the completed Metada is accessible and searchable in the NSDI Clearinghouse

13. Module 4Interoperable WebMapping and Clearinghouse Services • Tasks: Lead: • Develop Interoperability Tools (4a) GAI WG, FGDC, OGC • Web Mapping and Data Access specs (4b) GAI WG, FGDC, OGC • Prototype Services Integration (4c) GAI WG, FGDC, OGC • Timelines: 690 days • Develop Interoperability Tools 390 days • Web Mapping and Data Access specifications 240 days • Prototype Services Integration 60 days • Performance Goals • Requirements analysis • Goal: Prototype and deploy standards-based data access and web mapping services for Federal Framework data

14. Module 5Agency Deployment of Commercial-grade Portal services • Tasks: Install and deploy reusable, commercial grade data access and service capability for the Geospatial One Stop Portal (5) • Lead: Each agency and FGDC Staff for its own distributed node of the Portal • Timelines: 120 days • Performance Goals • Goal: Establish comprehensive Federal Portal as a logical extension to the NSDI Clearinghouse Network

15. Geospatial One-Stop • Anticipated Next Steps • FGDC Steering Committee Meeting Discussion • Agency Commitments for Task Accomplishment and Resources • Establish Project Team • Begin Kick-off Meetings

16. Geospatial One-Stop • Support and Commitments • Provide Agency, Contractor or In-Kind Support • Standards Development Theme Managers • Standards development participation • Outreach • Support to Standards Working Group • Documentation of Existing Data and Plans • Network of Liaisons to support Initiative • Support to Project Management Team • Funding support (combination of within Agency, For Specifications and Prototyping, and for common pool of support) • Web Mapping and Interoperability • Portal • Replication Services • Modeling and Facilitation

17. Template for Identification of Agency Resource Commitments • Agency Contact for Geospatial One Stop: (List Name and contact information) • Modules/Task Listing • Module 1: • Task and Funding Level: (List Task and level of commitment) • What: (Type of work of skill such as Standards Development Leader, Data Modeling support, Outreach etc.): • How: (Within Agency, Contractor, Detail, $ contributed to a common pool) • Who: (Name of person(s) or contractor) • Same format for Modules 2, 3, 4, 5:

18. Geospatial One-Stop • Project Management Team • Will consist of personnel who are working full time or substantially on Geospatial One-Stop Initiative • Will be virtual team with the possibility of a core set of people who work at a common location • Will be responsible for leading various modules and work tasks of Geospatial One-Stop and for overall project support • Project Management Team Composition • FGDC Staff Personnel - Staff Director, Clearinghouse, Framework, Standards, BDR, OMB Initiatives Coordination • Framework Standards Team Leaders • Other personnel who either lead components of the Initiative or who provide Management or support for the Initiative

19. Generalized Modeling Approach Universe of Discourse (each of 7 communities) Conceptual Model Feature Model in UML expert intervention Conceptual Model using ISO 19118/19103 objects in UML Application Schema UML-XML encoding transform Common Community Data Transfer Schema in XML Data Transfer Schema XML validation Encoded Feature Data

20. Possible Interactions With OGC • Participation in development of FGDC Data Content Standards documents? • How should abstract UML models be developed for each theme in conformance with 19109 Rules for Application Schema? • Exactly how can feature-based UML data content models be cast into standard XML documents based on a single theme Schema for exchange? Use of 19118 and GML ?.?

21. Possible Interactions With OGC • How can legacy data stores be exported into a different Core data content model and defined XML encoding? • Are schema transformations from ‘private’ to ‘public’ schemas feasible, and where/when should such transformations take place? • Can commercial-grade, high-throughput Web Feature Services be demonstrated and deployed for all seven Framework data themes within 12-18 months?