NSDI National Spatial Data Infrastructure National Geospatial Enterprise

NSDI National Spatial Data Infrastructure National Geospatial Enterprise Architecture An Architectural Process Overview Presented by Eliot Christian USGS/FGDC 28 Jan 2004 1

NSDI Presentation Outline National Spatial Data Infrastructures (SDIs) Requirements of Law and Policy ² E-Government Act (FGDC) ² Federal Policy (Circular A-16) Process for Achieving Interoperability ² Services Oriented Architecture ² Technical Standards ² Framework Data 15 March 2005 National Geospatial Enterprise Architecture 2

NSDI Presentation Outline National Spatial Data Infrastructures (SDIs) Requirements of Law and Policy ² E-Government Act (FGDC) ² Federal Policy (Circular A-16) Process for Achieving Interoperability ² Services Oriented Architecture ² Technical Standards ² Framework Data 15 March 2005 National Geospatial Enterprise Architecture 3

NSDI What is a Spatial Data Infrastructure? National Spatial Data Infrastructure Ø SDI’s are composed of organizations or cross-cutting communities who adopt common standards for geospatial data Ø Global Spatial Data Infrastructure (GSDI) members represent National SDI’s (about 50 at present) Ø GSDI Clearinghouse currently has 381 "nodes" (searchable metadata collections) 15 March 2005 National Geospatial Enterprise Architecture 4

NSDI Objectives for Spatial Data Infrastructures source: Open Geospatial Consortium (OGC) National Spatial Data Infrastructure • Easier access to multiple online info sources and services • Use and reuse different vendor solutions. Integrated View • Reduce deployment costs by reusing information from other communities • Tools to provide custom information to users • Foundation for interoperable service networks 15 March 2005 Queries extract info from diverse sources Whoville Buildings Roads Images Targets Boundaries. . . Cedar Lake Whoville Cedar Lake Catalog View Internet Common interfaces enable interoperability Gazetteer Geoparser Coordinate Transform Other Services Web Mapping Server, Web Feature Server, Web Coverage Server Vendor Data Geocoder Metadata Local Government National Government Other Collections Data Metadata National Geospatial Enterprise Architecture Catalog Services Clearinghouse 5

NSDI Presentation Outline National Spatial Data Infrastructures (SDIs) Requirements of Law and Policy ² E-Government Act (FGDC) ² Federal Policy (Circular A-16) Process for Achieving Interoperability ² Services Oriented Architecture ² Technical Standards ² Framework Data 15 March 2005 National Geospatial Enterprise Architecture 6

Requirements of Law and Policy NSDI E-Government Act (FGDC) National Spatial Data Infrastructure Section 216 of the E-Government Act, "Common Protocols for Geographic Information Systems", establishes in law the authorities and responsibilities of the Federal Geographic Data Committee (FGDC) The law defines "geographic information" as: "information systems that involve locational data, such as maps or other geospatial information resources" 15 March 2005 National Geospatial Enterprise Architecture 7

NSDI Requirements of Law and Policy E-Government Act (FGDC) National Spatial Data Infrastructure E-Government Act of 2002 requires: Ø the development of common protocols for the development, acquisition, maintenance, distribution, and application of geographic information [. . . ] Ø The common protocols shall be designed to (1) maximize the degree to which unclassified geographic information from various sources can be made electronically compatible and accessible; and (2) promote the development of interoperable geographic information systems technologies 15 March 2005 National Geospatial Enterprise Architecture 8

NSDI Requirements of Law and Policy Federal Policy (Circular A-16) National Spatial Data Infrastructure OMB Circular A-16: "establishes a coordinated approach to electronically develop the National Spatial Data Infrastructure" Purpose of the NSDI: To encourage the collection, processing, archiving, integration, and sharing of geospatial data and information using common standards and interoperable systems and techniques 15 March 2005 National Geospatial Enterprise Architecture 9

NSDI Requirements of Law and Policy Federal Policy (Circular A-16) National Spatial Data Infrastructure "provides direction for federal agencies that produce, maintain or use spatial data either directly or indirectly" directs such agencies, "both internally and through their activities involving partners, grants, and contracts" to: (1) Prepare, maintain, publish, and implement a strategy for advancing geographic information and related spatial data activities appropriate to their mission, in support of the NSDI Strategy. [. . . ] (2) Collect, maintain, disseminate, and preserve spatial information such that the resulting data, information, or products can be readily shared with other federal agencies and non-federal users, and promote data integration between all sources. [. . . ] 15 March 2005 National Geospatial Enterprise Architecture 10

NSDI Requirements of Law and Policy Federal Policy (Circular A-16) National Spatial Data Infrastructure (4) Use FGDC data standards, FGDC Content Standards for Digital Geospatial Metadata, and other appropriate standards, documenting spatial data with the relevant metadata, and making metadata available online through a registered NSDI-compatible Clearinghouse node. [. . . ] Before the obligation of funds, ensure that all expenditures for spatial data and related systems activities financed directly or indirectly, in whole or in part, by federal funds are compliant with the standards and provisions of the FGDC. All Information Technology systems which process spatial data should identify planned investments for spatial data and compliance with FGDC standards within the Exhibit 300 capital asset and business plan submission (see OMB Circular A-11, sec. 300). 15 March 2005 National Geospatial Enterprise Architecture 11

U. S. National Spatial Data Infrastructure (NSDI) NSDI National Spatial Data Infrastructure Ø Extensive partnerships established Ø Law and policy for federal spatial data Ø President’s management agenda initiative Ø E-Government portal developed Ø Clearinghouse network thriving Ø Standards – international, community 15 March 2005 National Geospatial Enterprise Architecture 12

NSDI U. S. National Spatial Data Infrastructure (NSDI) National Spatial Data Infrastructure Partnerships Clearinghouse (catalog) Metadata Framework Data Standards 15 March 2005 National Geospatial Enterprise Architecture 13

Toward a National Geospatial Enterprise Architecture NSDI National Spatial Data Infrastructure Given SDI requirements under U. S. law and policy, How can the U. S. NSDI leverage aspects of Enterprise Architecture? 15 March 2005 National Geospatial Enterprise Architecture 14

NSDI Presentation Outline National Spatial Data Infrastructures (SDIs) Requirements of Law and Policy ² E-Government Act (FGDC) ² Federal Policy (Circular A-16) Process for Achieving Interoperability ² Services Oriented Architecture ² Technical Standards ² Framework Data 15 March 2005 National Geospatial Enterprise Architecture 15

NSDI Process for Achieving Interoperability Services Oriented Architecture National Spatial Data Infrastructure Ø Software components of systems are now built to interoperate primarily through the passing of structured messages at interfaces designed for networking Ø Each set of operations exposed at such a network interface is defined as a “service” Ø NSDI requires this interoperability approach, known as a Services Oriented Architecture 15 March 2005 National Geospatial Enterprise Architecture 16

Example: Web Map Service (“get. Map”) http: //gisdata. usgs. net/servlet/com. esri. wms. Esrimap? servicenam e=133 urban& request=get. Map&version=1. 1. 1&srs=EPSG: 4326&width=1000&hei ght=500& format=image/jpeg&b. Box=-77. 02, 38. 885, -77. 01, 38. 895& layers=UA_ORTHO_Washington 01& 15 March 2005 17

Process for Achieving Interoperability NSDI Services Oriented Architecture National Spatial Data Infrastructure Ø A small number of well-defined and commonly supported services provide broad NSDI interoperability Ø Registries of services (e. g, UDDI, eb. XML, GSA Core. Gov, . . . ) can be helpful if there are many service specifications in use NSDI Services could be delineated in an FEA Services Reference Model (SRM) 15 March 2005 National Geospatial Enterprise Architecture 18

Process for Achieving Interoperability NSDI Technical Standards National Spatial Data Infrastructure U. S. NSDI employs various standards, e. g. , ² OGC Web Map Service, Web Coverage Service, Web Feature Service ² ISO 23950 (information search and retrieval service) ² ISO/IEC 11179 (metadata registries) ² ISO 19115 (documentation and representation) ² ISO 3166 (place codes) ². . . among others NSDI Technical Standards could be listed in an FEA Technical Reference Model (TRM) 15 March 2005 National Geospatial Enterprise Architecture 19

NSDI Process for Achieving Interoperability Framework Data National Spatial Data Infrastructure "Framework" refers to a collaborative effort on seven themes of commonly used digital geographic data: ² ² ² ² 15 March 2005 geodetic control orthoimagery elevation transportation hydrography governmental units cadastral (land ownership) National Geospatial Enterprise Architecture 20

Process for Achieving Interoperability NSDI Framework Data National Spatial Data Infrastructure Key aspects of Framework Data: ² institutional relationships and business practices that encourage the maintenance and use of data ² procedures, technology, and guidelines that provide for integration, sharing, and use of these data NSDI Framework Data could align to the FEA Data Reference Model (DRM) 15 March 2005 National Geospatial Enterprise Architecture 21

An Architectural Process Overview NSDI Summary National Spatial Data Infrastructure Law and policy for NSDI, other SDI's, already require Services Oriented Architecture, and emphasize open standards for data, metadata, and services Ø NSDI services could be delineated in an FEA Services Reference Model (SRM) Ø NSDI technical standards could be listed in an FEA Technical Reference Model (TRM) Ø NSDI Framework Data could align to the FEA Data Reference Model (DRM) 15 March 2005 National Geospatial Enterprise Architecture 22