Update on the Geospatial Profile

Update on the Geospatial Profile of the U.S. Federal Enterprise

Architecture (FEA)

Presented 28 October

2005by

Eliot ChristianFGDC, USGS

28 October 2005 2

FederalEnterprise

Architecture

Update on the FEA Geospatial Profile

Presentation Outline

What is the national Geospatial Profile and Why is it necessary?

What is the National Spatial Data Infrastructure?

Requirements of Law and Policy E-Government Act (FGDC) Federal Policy (Circular A-16)

Outline of the draft FEA Geospatial Profile document

28 October 2005 3

FederalEnterprise

Architecture


What is the national Geospatial Profile?

The national Geospatial Profile for enterprise architecture (EA) provides cross-cutting guidance for developing consistent EA Reference Models useful at all levels of government, but especially the U.S. Federal Enterprise Architecture (FEA).

28 October 2005 4

FederalEnterprise

Architecture


Why have a national Geospatial Profile?

The national Geospatial Profile supports: Various regional, state, and local initiatives

focused on geospatial infrastructure Office of Management and Budget (OMB)

in realizing the U.S. Federal Enterprise Architecture (FEA)

Federal Geographic Data Committee (FGDC) in advancing the U.S. National Spatial Data Infrastructure (NSDI)

28 October 2005 5

FederalEnterprise

Architecture


Objectives of the national Geospatial Profile

1. Guidance for addressing Geospatial within EA Reference Models2. Show geospatial capabilities related across EA Reference Models3. Describe how geospatial capabilities cross Lines of Business4. Give examples of Geospatial Profile in mission-oriented Use Case 5. Discuss how Geospatial may interact with other FEA Profiles 6. Provide guidance to help architects identify and exploit Geospatial7. Initiate a knowledge base for applying the Geospatial Profile

28 October 2005 6

FederalEnterprise

Architecture






Outline of the draft FEA Geospatial Profile document (version 0.2)

28 October 2005 7

FederalEnterprise

Architecture


What is the U.S. National Spatial Data Infrastructure?

Spatial Data Infrastructures are supported by organizations or 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)

28 October 2005 8

FederalEnterprise

Architecture


SDI's Implement a Services Oriented Architecture

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”

SDI's requires this interoperability approach, known as a Services Oriented Architecture

28 October 2005 9

FederalEnterprise

Architecture


Common Services in Spatial Data Infrastructures

ClearinghouseClearinghouse

GeoparserGeoparser

VendorData

Local Government

Data

NationalGovernment

Data

OtherCollections

of Data

Clearinghouse

WhovilleCedar Lake

WhovilleCedar Lake

BuildingsRoadsImagesTargetsBoundaries ...

CatalogView

Queries extract info from diverse sources

Integrated View

Gazetteer CoordinateTransform

Web Map Service, Web Feature Service, Web Coverage ServiceCatalog Services

OtherServices

Metadata Metadata Metadata Metadata

Internet

Geoparser

Geocoder

Common interfaces enable interoperability

28 October 2005 10

FederalEnterprise

Architecture


Key NSDI Service Standards

ISO 19128 Geographic information -- Web Map Service (WMS)

ISO 19123 Geographic Information -- Schema for coverage geometry and functions [ aka Web Coverage Service (WCS) ]

ISO 19142 Geographic information -- Web Feature Service (WFS)

ISO 19136 Geographic information -- Geography Markup Language (GML)

ISO 19115 Geographic Information - Metadata [successor to FGDC Content Standard for Digital Geospatial Metadata ]

ISO 23950 Information Search and Retrieval [ aka ANSI Z39.50 ]

28 October 2005 11

FederalEnterprise

Architecture







28 October 2005 12

FederalEnterprise

Architecture


Public Law(E-Government Act)

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"

NOTE: In U.S. Federal law and policy, the terms "spatial", "geospatial", "geographic", "mapping", and "locational"

when linked with the terms "data" or "information", and/or the terms "system" or "resource",

are usually equivalent.

28 October 2005 13

FederalEnterprise

Architecture



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 geographicinformation from various sources can be madeelectronically compatible and accessible; and

(2) promote the development of interoperable geographic information systems technologies

28 October 2005 14

FederalEnterprise

Architecture



"Although a wealth of geospatial information exists, it is often difficult to locate, access, share, and integrate in a timely and

efficient manner. Many Federal, state, and local agencies collect and use geospatial data in different formats and standards based on their requirements. This results in wasteful spending, redundant data collection, and can

hinder the ability of federal, state, and local governments to effectively and efficiently provide information and services

to each other, citizens, and business."

OMB Report to Congress on Implementation of the E-Government Act (March 8, 2004)

28 October 2005 15

FederalEnterprise

Architecture


Federal Policy (OMB Circular A-16)

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

28 October 2005 16

FederalEnterprise

Architecture



"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. [...]

28 October 2005 17

FederalEnterprise

Architecture



(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).

28 October 2005 18

FederalEnterprise

Architecture







28 October 2005 19

FederalEnterprise

Architecture



1. Introduction 1.1 Objectives

1.2 Audience

1.3 Geospatial Information Is Everywhere

1.4 Challenges To Be Addressed

1.5 The National Spatial Data Infrastructure

1.6 Overview of Geospatial Capabilities

1.7 Use Case Overview

1.8 Federal Policies and Drivers

1.9 Authority

http://colab.cim3.net/cgi-bin/wiki.pl?CurrentGeospatialProfileDraft(Comment on Version 0.3 after October 28, 2005 )

28 October 2005 20

FederalEnterprise

Architecture



2. Geospatial Capabilities and the FEA Reference Models

2.1 FEA Overview

2.2 How Geospatial Interacts with the FEA Reference Models

2.3 Geospatial View of the Business Reference Model

2.4 Geospatial View of the Data Reference Model

2.5 Geospatial View of the Service Component Reference Model

2.6 Geospatial View of the Technical Reference Model

2.7 Geospatial View of the Performance Reference Model


28 October 2005 21

FederalEnterprise

Architecture



AppendicesA. ReferencesB. Terminology (Glossary)C. Use CaseD. Geospatial Activity Examples

for FEA BRM Lines of BusinessE. Geospatial Business LanguageF. Geospatial Service ComponentsG. Geospatial Standards ProfileH. Excerpts form U.S. Federal Law and PolicyI. Acronym List


28 October 2005 22

FederalEnterprise

Architecture


Summary

Law and policy requires Federal agencies to apply enterprise architecture principles, and to use open standards for data, metadata, and services

The national Geospatial Profile for enterprise architecture provides more precise guidance for data and information systems that use, maintain, or reference "locational data"

Update on the Geospatial Profile

Technology

geospatial profileof

geospatial initiate

examples of geospatial

terms data

locational data

information search

federal law

national sdisabout