# Presentation: 630003

## U.S. National Spatial Data InfrastructureUpdate on FGDC-Coordinated Activities

- Douglas Nebert
- FGDC/GSDI Secretariat

## Presentation Overview

- Background on U.S. NSDI
- NSDI Coordination Activities
- Baseline activities status
- I-Team, Clearinghouse, Metadata, Framework, Standards
- Geospatial One-Stop Initiative
- Module Status and Milestones
- Participation
- Relation to other e-government activities

## Foundation of US NSDI

- NSDI established as initiative under the interagency coordinating committee, the Federal Geographic Data Committee (FGDC)
- FGDC has 17 member federal organizations, official liaison with 35 state councils, and other sectoral organizations
- Executive Order 12906 (1994) compelled federal government participation in NSDI

## Objectives of the Infrastructure

- To promote use and re-use of spatial data for multiple purposes by government and citizens
- To encourage participation of self-disciplined providers or data and services
- To establish baseline services that support community discovery and access to geo-information (directory of services, common data schemas, search gateways, gazetteer, reference software implementation)

## Organization of FGDC

**Organization of FGDC**

- Steering
- Committee

- Coordination
- Group

*Secretariat*
*Staff*

## NSDI Coordination Activities

- Coordination Group of agency leads meets monthly to discuss common issues
- Steering Group meets 2-3 times per year to address high-level guidance
- FGDC Secretariat assists in the day-to-day coordination functions of the NSDI

## FGDC Secretariat

- Secretariat is a permanent office at U.S. Geological Survey to support the FGDC
- Staff of 20 continues to support ***baseline activities*** and assisting in Geospatial One-Stop Initiative coordination and execution
- Four new staff members handle executive management, project documentation, budget, and outreach activities for One-Stop

## Baseline activities

- FGDC continues to promote:
- Interaction with consensus and formal standards activities
- Metadata standardization and education
- Clearinghouse implementation and enhancement
- Framework data standardization
- I-Team formation and coordination

## Interaction with Standards Groups

- FGDC has Standards Working Group for the development of consensus Federal standards
- FGDC is Principal Member of OpenGIS and contributes to technical specification development
- FGDC is member of the US ANSI/INCITS L1, which represents the US in ISO on geomatics
- FGDC participates through a number of national experts in ISO TC 211 Work Items creating the 19100 series of standards

## Metadata Standardization

- US Continues to use and promote the FGDC Metadata Content Standard, Version 2, 1998
- FGDC hosted informal workshop with US, Canada, and UK on interpreting and advancing ISO metadata, 22-24 January
- The U.S. and Canada are committed to co-develop a North American Profile of metadata working through Standards Canada and ANSI/INCITS

## ISO Metadata Activities

- ISO 19115 (Metadata) has recently been split into two documents:
- 19115 will hold the formal UML and definitions
- Technical Specification 19139 will publish the formalization of ISO 19115 metadata in XML through use of an XML Schema
- For education and development purposes, FGDC will focus on ISO 19139 for interoperability and clarity
- FGDC will promote development of XSL Stylesheets to render ISO 19139 metadata

## OpenGIS Involvement

- Catalog Services 2.0 Revision Working Group has been formed to integrate catalogs and registries
- FGDC is sponsoring a Geospatial One-Stop Transportation Pilot and Portal (discussed later)
- FGDC will participate in Critical Infrastructure Protection Initiative (CIPI-1)

## Catalog Services

- Foundation of Clearinghouse
- Supports the “Publish, Find, Bind” approach
- Challenge to support:
- Data discovery
- Service discovery
- Association of each

## Catalog Service Research

- Catalog Service

- Internet

- Catalog V2 Choices:
-  Z39.50
-  CORBA
-  UDDI?
-  ebXML?
-  SOAP?
-  REST (Get/Post)

## Clearinghouse Implementation

- The NSDI Clearinghouse continues to grow using the Z39.50 protocol
- 245 Metadata Collections are registered in the Clearinghouse registry

## Clearinghouse Nodes

- Argentina: 		1
- Australia: 		19
- Barbados:		2
- Bolivia:			1
- Brazil: 			3
- Canada: 		>100
- Chile 			1
- China: 			1
- Colombia: 		2
- Costa Rica: 		3
- Dominica: 		1
- Dominican Republic: 	1
- El Salvador: 		2
- Ethiopia			3
- Guatemala: 		2
- Honduras: 		2

- Italy: 			2
- India			1
- Japan: 			2
- Jamaica: 		1
- Kenya:			3
- Mexico: 			2
- Nicaragua: 		2
- Norway:			1
- Peru:			1
- South Africa: 		2
- Switzerland:		1
- Trinidad & Tobago: 	1
- United Kingdom: 		9
- United States:  		186
- Uruguay: 		2
- Venezuela: 		2

- Updated: Jan 2003

## 2003 Plans for Clearinghouse

- Develop and implement compatible Web-based OGC catalog services for data and service discovery through Version 2.0 effort
- Investigate harvester, push, and indexing technology for construction of dynamic national indexes of spatial metadata and services
- Provide baseline infrastructure for the discovery of all types of data and services integrated with the Geospatial One-Stop Portal

## Framework Data

- Federal agency leads defined for each theme
- Multi-sectoral participation in ANSI-sponsored standards development teams for Framework underway to define Core representation
- Coordination of Framework data service providers to be formalized within each community
- Activity done in support of Geospatial One-Stop

##     I-Teams

- Locally formed, interdependent
- Inclusive, voluntary, open
- State, local, federal, tribal, academic, private sector
- Expanded from existing collaborations
- Brand name to help build Executive and Legislative Branch awareness

## I-Team Implementation Strategy

**I-Teams**

**Federal**
**Partners**
**Team**

**Financing**
**Solutions**
**Team**

**I-Team Implementation Strategy**

**Technology**
**Advisory**
**Group**

**FGDC and OMB**

##     The I-Team Process

- Treat data as strategic, capital assets and public goods
- Collaborate and Coordinate
- Align roles, responsibilities and resources
- Steward Data
- Organize Effective and Efficient Production and Stewardship of Data
- Pool and Leverage Investments

**Notes:**
Steward means to oversee, take care of, foster, supervision, management

##      What Do I-Teams Do?

- Address Institutional Barriers
- Identify most effective ways to collect, maintain and distribute Data
- Determine business needs, inventory data assets, identify gaps, estimate investment cost
- Designate data stewards
- Develop Enterprise Plans (I-Plans) for Data production and publication by the most appropriate partner at accuracy and scale needed by local jurisdictions
- Provide plans to OMB, agencies, DHS

## What Do I-Teams Do?

- Aid State/local participation in Geospatial One-Stop
- Work with OGC on cutting edge of technology (Semantic Translators and exchange schemas, Web Services)
- Help OMB and agencies in budget process
- Enable role, responsibility, resource alignment
- Provide, steward, and publish America’s Data Assets

##      Reasons To Form I-Teams

**The I-Team process gives States and regions a mechanism to focus upon data as strategic long term capital assets. **
**An organized region with a strategic plan and an investment strategy is more likely to attract Federal funds for essential national missions. **
**Local and State governments are looking for a mechanism that will coordinate Federal initiatives.**
**State and local governments perceive I-Teams as having the potential to result in financial incentives from the federal government.  **
**Participation in a national network will bring credibility with State executive and legislative branches.**
**They have to do it anyway.**

##      Accomplishments

- Established “I-Team” phrase to help build political awareness as multi-jurisdictional GIS consortium
- Federal agencies have accepted the idea of I-Teams and support them
- 46 States and regions have I-Teams
- Several established by Executive Order of Governor
- 9 I-Plans published, 14 I-Plans nearing completion (30-90 days)

## 
Federal Partners may not have engaged agencies
No national funding for I-Team administration and operations (It is all voluntary!)
No Federal Financial Incentives (yet)
Perception of and actual lack of coordination continues

- Federal Partners may not have engaged agencies
- No national funding for I-Team administration and operations (It is all voluntary!)
- No Federal Financial Incentives (yet)
- Perception of and actual lack of coordination continues

**Obstacles to I-Teams**

## Slide 27

## 
Producers, users steward America’s data assets
NSDI - the infrastructure
Geospatial One-Stop - a Presidential initiative to accelerate completion of the infrastructure
I-Teams - a process to help produce and steward data 
The National Map, Census Modernization, FEMA NFIP, HSIP - Programs that can use I-Teams to produce products to fulfill essential national missions and foster coordination

- Producers, users steward America’s data assets
- NSDI - the infrastructure
- Geospatial One-Stop - a Presidential initiative to accelerate completion of the infrastructure
- I-Teams - a process to help produce and steward data
- The National Map, Census Modernization, FEMA NFIP, HSIP - Programs that can use I-Teams to produce products to fulfill essential national missions and foster coordination

**How I-Teams participate**

## E-government: Geospatial One-Stop

- OMB has established 24 e-government initiatives across the U.S. Government to seek savings of scale by formalizing re-usable G2G services
- Geospatial One-Stop Initiative intends to make it easier, faster, cheaper for all levels of government and the public to get access to geospatial information.

## It improves our ability to:
Support the business of government
 planning, regulation, detecting change
Support Decision making
 response, mitigation, prediction, intergovernmental coordination

**Support the business of government**
-  planning, regulation, detecting change
**Support Decision making**
-  response, mitigation, prediction, intergovernmental coordination

**Purpose of Geospatial One-Stop**

## Geospatial One-Stop Workplan

**Requirements Gathering and Analysis**: defining business and transactional drivers with data
**Data Standards Development Process**: Create abstract and implementation specifications for common data themes (Framework)
**Documentation**: Catalogs for existing and planned data collection
**Portal and Service Deployment**: Support discovery of and access to distributed data and services by web client users and other applications (E-gov)

## Geospatial One-Stop Modules

- Develop rigorous data content standards for Framework data themes using a common structured modeling language
- Document Framework holdings in Clearinghouse
- Document planned Framework data collection in Clearinghouse
- Implement Framework data services
- Implement a common access portal

## Raises the visibility of the strategic value of geographic information.
Increases federal agency accountability for the stewardship and sharing of geospatial resources.
Establishes a collaborative model for directing an intergovernmental initiative.

**Increases federal agency accountability for the stewardship and sharing of geospatial resources.**
**Establishes a collaborative model for directing an intergovernmental initiative.**

**Geospatial One-Stop Effects**

**Notes:**
GOS is a Presidential management initiative – it raises the visibility of the NSDI to a new level of importance.
OMB directing this initiative defines a new reality for federal agency cooperation.
The establishment of a multi-sector Board of Directors to help guide this initiative is a new model for collaboration and insures the buy-in and participation of state and local organizations.

## Geo-Partnerships

**Expectations**
**Standards**
**Metadata**
**Stewardship**

**Incentives**
**Tools**
**Training**
**Software**
**Grants**

**Better data will result in improved public services**

**Geo-Partnerships**

## Geo-partnerships will lead to:

**. . . A National, Distributed GIS**

**Geo-partnerships will lead to:**

- Common Services

- Catalog/Registry

## Intergovernmental Board of Directors

**Intergovernmental Board of Directors**

- National Association of State CIOs
- National States Geographic Information Council
- National Association of Counties
- National League of Cities
- International City/County Managers Association
- Intertribal GIS Council
- Western Governors Association
- Department of Interior
- Department of Commerce
- Department of Transportation
- NASA

**Notes:**
State, Local and Tribal Government:
	State, local and Tribal governments will be equal partners in all of the activities of Geospatial One Stop.  Organizations that will help manage Geospatial One Stop activities include:
	State:
National States Geographic Information Council
National Association of State CIOs 

	Local:  
National Association of Counties
National League of Cities
International City/County Managers Association

	Tribal: 
Intertribal GIS Council

	Other:
	Private sector, academic and other organizations also have significant roles to play in the Geospatial One-Stop and NSDI activities.  The organizations include:
Open GIS Consortium
         University Consortium for Geographic Information                        Sciences
GeoData Alliance
Geospatial Information  & Technology Association 
Spatial Technologies Industry Association, and 
Professional Associations

## Draft process diagram

- Review
- State and
- E-Gov User
- Requirements

- Target 22+
- e-gov initiatives
- and other e-gov

- Face-to-face
- Town Hall
- Discussions

- Call for business
- requirements of
- portal

- Develop
- consolidated
- use cases

- Compose/
- convene
- 7 MATs

- Extract data
- requirements

- Initial Portal
- Functional
- Design

- Calls for requirements
- and participation

- Extract common
- data
- requirements

- Construct
- Draft Model

- Write draft
- std docs

- Construct
- Draft
- Standard

- Public
- Review

*Under ANSI *
*INCITS L1*

- Vote at
- ANSI INCITS
- L1

- Vote at
- ANSI

- Public
- Review

- FGDC
- Endorsement

*revise*

*revise*

*e.g. transportation*

- Prototype
- specific
- G2G functions

- Establish
- portal  interface
- to services

- Prototype
- map/data
- services

- Finalize
- map/data
- services

*refine*

- Document
- existing and
- planned data

- Service and
- Data
- Clearinghouse

- Augment
- portal
- functionality

*refine*

**Draft process diagram**
**of Geospatial OneStop**
** ****revised 01Mar02**

*register*

*time (not to scale)*

- Prepare
- Questions,
- Organize

**Portal Team**

**Requirements Team**

**Standards Teams**

## 1. Data Standards Development for One-Stop

- Develop business cases in a participatory process to define the intersection of functional requirements that lead to data
- Identify primary stakeholders, federal and otherwise
- Define a data content model adequate to support the intersection of needs
- Model using a common modeling language (UML)
- Develop full standard document to include model
- Publish as Framework Core Data Content Standard by ANSI, endorsed by FGDC
- Define a specific implementation schema in OGC Geography Markup Language (GML) that can be used for data access and validation
- Implement conformant services for Framework data

## Module 1: Data Standardization

- Define a well-known package of GIS data that can be exchanged without negotiation for immediate use
- More robust packages can be defined and exchanged by the same approach, but one must support Core at a minimum
- Do not replace more comprehensive FGDC standards, but are a subset of their content
- Do not define the internal data models used in mission critical systems, only a package for import and export

## Data Standards approach

- UML

- XMI

- XSD

- + Narrative = Standard

- UGAS

- Implementation
- Annex to Standard

## Available Now:
Elevation	
Hydrography		
Government Units	
Geodetic Control		
DOQ			
Transportation (Roads)	

- Available Now:
- Elevation
- Hydrography
- Government Units
- Geodetic Control
- DOQ
- Transportation (Roads)

- Available February:
- Cadastral
- Air
- Rail
- Transit

**Notes:**
Waterways has not been included - more information is needed before we can discuss in detail. Need to check on referencing other sub-parts to ensure consistency with past presentations or info provided to board.

## Framework Data Themes

**Base Standard**

**Transportation**

**Elevation**

**Cadastral**

**Hydrography**

**Governmental Units**

**Orthoimagery**

**Geodetic Control**

**Air**

**Rail**

**Roads**

**Waterways**

**Transit**

## Standards documentation in support of ANSI
Identification of unique features and assignment of IDs
Source authority of data and modifications
Theme maintenance and documentation
Standardization of modeling methods
Common referencing of linear features such as roads, streams, rail
Management of similar or same features across themes.
Co-management of data within a theme

- Identification of unique features and assignment of IDs
- Source authority of data and modifications
- Theme maintenance and documentation
- Standardization of modeling methods
- Common referencing of linear features such as roads, streams, rail
- Management of similar or same features across themes.
- Co-management of data within a theme

**Common Issues in Base Standard**

**Notes:**
Need to clarify some of the language etc.. To convey. Goal is to provide examples of the interconnectivity of process. 

## Module 2. Document Framework Holdings in Clearinghouse

- Identify agency holdings (only original or value-added) of Framework data themes
- When standards are approved and organization has Web services online to serve the data, must ‘flag’ data and register the services
- Use existing or new Clearinghouse nodes to host and serve the metadata

## Module 2 Approach

- Streamlined search interface for Framework Data
- On-line metadata tool for undocumented framework datasets
- Temporary document
- Replaced by detailed metadata

**Notes:**
Blending of FGDC Content Standard for Digital Geospatial Metadata and ISO 19115
Compliant with FGDC and ISO 19115
Guidance Document
Review by FGDC Coordination Group and GOS Contacts

## Selecting Framework Theme

## Selecting Geographic Area

## Selecting Clearinghouses

- Querying

## Reviewing Results

## Module 3. Document planned Framework data collection in Clearinghouse

- Revitalizing the former annual A-16 call for data requirements, establish a new common system within Clearinghouse to advertise data collection plans and data requirements
- System valid for all levels of government and commercial interests can participate

## Module 3 Approach

- Modify existing FGDC on-line metadata collection tool
- Add budget information fields
- Upload XML or comma delimited files
- Data Access via simplified query page
- Plans visualization through geographic interface

## Investment Elements

- Type of funding
- Incremental
- Recurring
- Other
- Costs
- Projected
- Budgeted
- Other

- Partnered Funds
- Partnering Agency
- Timing
- Estimated start
- Estimated completion

## Planned Data Explorer

## 4. Implement Framework data services at all participating organizations

- Project will include a Web Service prototyping phase to demonstrate service capabilities and interactions
- Participant organizations will be expected to develop and operate high reliability OGC Web Services for their Framework data prior to Portal construction

## Geospatial One-Stop Transportation Pilot (GOS-TP)

- OpenGIS Consortium (OGC) will assist in modeling process to define proper UML that conforms to ISO rules and can be implemented as GML
- Engage OGC members in implementing Web Feature Services to extend multiple available data systems (U.S. and Canada)
- Demonstrate a Web client application that can display and query multiple Framework data sources based on a common data model
- Approach to be followed for other themes

## GOS-TP Goal & Objectives

- Implement a vertical slice of GOS, testing the assumptions made in the broader GOS objectives using the Road Transportation theme.
- Primary Objectives:
- Test assumption that Unified Modeling Language (UML) model can be successfully translated to an encoding schema
- Test assumption that Federal, State, Local, and/or Tribal data can be translated to a schema different from their local, native schema
- Pilot a portal-based system implementing metadata, data access (including translation), and web mapping

## GOS-TP Technical Architecture

**DOT Portal**
**Node**

**GOS-TP Technical Architecture**

**Oregon**
**Node**

**WFS-X**

**WMS****SLD**

**Jackson**
**County**
**Node**

**WFS-X**

**WMS****SLD**

**Siskiyou**
**County**
**Node**

**WFS**

**WMS****SLD**

**WOS**

**California**
**Node**

**WFS**

**WMS****SLD**

**WRS**

**WRS CG**

**WMS CG**

**WFS CG**

**WOS CG**

**User**
**Browser**

**WFS****	****Web Feature Service**
**WFS-X****	****Web Feature Service, ****Translating**
**WMS****	****Web Map Service**
**SLD****	****Styled Layer Descriptor**
**WRS****	****Web Registry Service**
**WOS****	****Web Object Service**
**CG****	****Client Generator**

_**Acronyms**_

## GOS Transportation Pilot Status

- The UML-to-GML Application Schema (UGAS) software will be on-line in its initial version early February.
- The node development work is underway and on schedule
- Anticipate IOC in late March FOC in late April.

## Task 5 Objectives

- Provide one point of access to Geospatial OneStop community data
- Support public and G2G transactions on common geospatial data resources
- Support basic user and application user access to online Framework data

## One-Stop Portal Concept

- Portal is an online access point for geospatial data,maps of data, and metadata about data
- Information is stored at data provider sites, not in Portal
- Portal utilizes open standards for interoperability
- Geospatial web service specifications
- Metadata and content standards
- Portal builds upon NSDI by providing direct access to data that is specific to task & location
- Web-based user interface for human access
- Application interface for GIS/DSS access

## Portal Implementation Plan

- Plan approved by GOS Board of Directors Oct 9
- Form Portal Team
- Define requirements for version 1 of Portal
- Launch OGC Interoperability Initiative to develop Portal
- Multi-vendor solution
- Integrate COTS components into standards-based framework
- GOS agencies provide cost-sharing resources
- Demonstrate "alpha version" to GOS
- Install "beta version" at government facility

## Portal Connectivity

**Portal Connectivity**

## Portal Milestones

- Portal Management Team convened: 2002 Oct 11
- Call for Additional Requirements sent out: Nov 5
- CFAR responses due: Nov 22
- GOS-PI RFQ released by OGC: Dec 18
- RFQ responses received: 2003 Jan 22
- Participants selected: Jan 30
- Kickoff during OGC meeting: Feb 3-7
- Working alpha version demonstrated: May 9
**Working beta version on Agency server: June 6**

## 3 Classes of Information(as seen by GOS Portal)

- _Primary_: Created for, or of direct interest to, GOS.
- Applicable standards:
- Framework *(usually)*
- Metadata
- Web Services (WMS, WFS, WCS)
- _Secondary_: Accessible through the GOS Portal.
- Applicable standards:
- Metadata
- Web Services (WMS)
- _Tertiary_: Discoverable through the GOS Portal.
- Applicable standards:
- Metadata

## Web Service Standards

- OGC Web Services
- Web Map Service (WMS) - pictures of geospatial data
- Web Feature Service (WFS) - vector data
- Web Coverage Service (WCS) - gridded/continuous data
- Cost factors:
**OGC-compliant server software**
- Server hardware & networking
- Operational reliability & performance
**Integration of state/local/tribal data**

## Web Map Service (WMS)

- Mature, well-established specification
- Version 1.0 issued 2000-04
- Version 1.1.1 issued 2001-12
- ISO CD 19128 corresponds to v1.1.1
- Server & client support in many vendor products & freeware
- Scope: geographic data rendered as images ("maps"),not actual data values
- Operations:
- GetCapabilities - send XML description of server holdings
- GetMap - produce map of desired area
- GetFeatureInfo (opt.) - describe feature at point

## Interoperable Web Mapping

**Interoperable Web Mapping**

**Server 1**

**Server 2**

**Server 3**

**Server 1: Topography**

**Server 2: Hydrography**

**Server 3: Govt Unit Boundaries**

## Web Feature Service (WFS)

**Web Feature Service (WFS)**

- WFS 1.0 approved 2002-09
- Scope: storage & retrieval of geographicvector feature data (point/line/polygon)
- Hydrography, Transportation, Government Units, Cadastral, Geodetic Control
- XML data encoding format:_Geography Markup Language_ (GML)
- _Filter Specification_: Restrict WFSoutput based on user criteria
- Operations:
- GetCapabilities
- DescribeFeatureType
- GetFeature

- Transaction *(optional)*
- LockFeature *(optional)*

## OGC Web Feature Service

**OGC Web Feature Service**

- Mission
- System A

- Web Feature
- Browser/
- Client Application

- Mission
- System B

- Native Format

- GML
- (XML)

- WFS

- WFS

*translation*
*utilities*

- B

- private
- schema

- P

- public
- schema

- transformation
- rules

## Web Coverage Service (WCS)

- Draft v0.7 released 2002-04; vote for adoption 2003-02
- Scope: Retrieval of gridded, swath, TIN or other "coverage" data in binary or other formats(HDF, GeoTIFF, NITF, NetCDF, etc.)
- Elevation, Orthoimagery
- Operations:
- GetCapabilities
- GetCoverage

## Proposed Strategy/Sequencing

| Publish FGDC metadata for existing theme data | Feb 2003(OMB deadline) |
| --- | --- |
| Prototype WMS/WFS with draft (pre-standard) Framework data corresponding to assigned theme(s) | March 2003 |
| Prototype Web Feature/Coverage Service with draft (pre-standard) Framework data | Sept 2003 |
| Framework standard approved | Oct 2003 |
| Operational WMS with Framework Data | Dec 2003 |
| Operational WFS/WCS with Framework Data | June 2004 |

## Douglas Nebert

- <date/time>

**Douglas Nebert**

- U.S. Federal Geographic Data Committee
- _[http://www.fgdc.gov](http://www.fgdc.gov/)_
- GSDI Secretariat
- http://www.gsdi.org
- ddnebert@fgdc.gov