FGDC Address Data Standard Scope, Status, and Structure  United States Street, Landmark, and Postal Address Data Standard"  Scope: Street, landmark, and postal addresses in the United States  Status: FGDC-endorsed standard  Structure: One data standard in four parts:  Data Content  Data Classification  Data Quality  Data Exchange

Purpose of the Standard  Provide a systematic basis for recording all addresses in the United States  Provide one standard that meets the address data management needs of:  Local address administrators  Emergency response and navigation  Postal and package delivery  Administrative recordkeeping  Address data aggregation  Support best practices in address data management

Organization of the FGDC Standard  Data Content  Data Classification  Data Quality  Data Exchange o Two profiles: USPS and NENA (still in draft)

Number, Subaddress and Street Name Elements  Address Number Elements  Address Number Prefix  Address Number  Address Number Suffix  Complete Address Number  Street Name Elements  Street Name Pre-Modifier  Street Name Pre-Directional  Street Name Prefix Type  Separator Element  Street Name  Street Name Suffix Type  Street Name Suffix Directional  Street Name Post Modifier  Subaddress Elements  Subaddress Type  Subaddress Identifier  Subaddress Element  Complete Subaddress  Intersection Corner Elements  Corner Of

Landmark, Place Name and Postal Elements  Landmark Elements  Landmark Name  Complete Landmark Name  Place Name Element  Place Name  Attribute: Place Name Type  Postal Elements  USPS Box Type  USPS Box ID  USPS Box Group Type  USPS Box Group ID  USPS Route  USPS Box  USPS Address  USPS General Delivery Point

Address Attributes  Identify records  Support geometry  Describe status  Provide base information for quality assurance  Connect addresses to other features and other addresses

Address Data Quality  Identifies elements of Address Data Quality  Supports testing of tabular and spatial data  Describes testing procedures (38 tests)  Provides base information for quality assurance  Each test provides information about methodology, reports, and how used.  Example code is also provided.

Address Data Exchange  Provides an XML protocol for seamless exchange of data  Federal Standard requires use of XML  Protects data producers and data consumers  Flexible exchange –missing fields on either side do not affect transfer  Useful in on-going exchange and aggregation efforts

Federal, State and Local Adoption and Use  Census and other federal agencies are using the Standard  Several states, counties and cities have adopted the standard, and are implementing data models that use it  Planning to work with other Federal agencies to develop profiles for their use  Planning to propose Addresses as the eighth data theme in the NSDI Framework

Benefits of the Standard  Quality is an integral part of the data  Model for exchanging data in a standard way  Definitive syntactical logic for address data

NENA NG9-1-1 CLDXF Standard Civic Location Data Exchange Format NENA Next Generation Data Development Working Group NENA Next Generation (NG9-1-1) United States Civic Location Data Exchange Format (CLDXF) Standard

What Is CLDXF?  Standardized way to exchange call civic location (address) information  Created by NENA NGDD WG as part of NG9-1-1 suite of standards  Status: Not yet adopted.  Profile of IETF Geo-priv PIDF-LO  Related by profile to the new FGDC address data standard  A profile restricts or extends a base standard (without contradicting it) for a particular application.

CLDXF Contents Elements needed to compose addresses in call records: Country, state, and place names and codes Street name elements Address number elements Landmark name Subaddress elements

What CLDXF Excludes Addresses that are unacceptable in call records: Intersection addresses Address ranges PO Box, RR and similar addresses Information not needed in the address portion of a call record: Address IDs and attributes Address classes Address quality tests

Creating the CLDXF – FGDC Profile Compared the business purposes of the standards Determined which address classes and elements were needed for NENA purposes Mapped FGDC elements and NENA elements to each other Compared the element definitions, examples, notes, etc. in complete detail. Noted all discrepancies. Reviewed FGDC address classes and determined which were useful in CLDXF. Within the profile, restricted or extended the FGDC standard as needed to accommodate discrepancies and exclusions. Listed the steps needed to convert between NENA and FGDC address records.

What's in the Profile? Detailed, element by element comparison of FGDC and NENA elements Which NENA element corresponds to which FGDC elements Discrepancies, comparisons, reconciliation Other restrictions and extensions: parts, classes, domains of values Step-by-step task list for converting address records between NENA and FGDC standards. Conformance requirements

Result Address data exchange will be included in the NG9-1-1 suite of standards CLDXF will be a NENA standard and statement of best practice for voluntary adoption by PSAPs nationwide. CLDXF conforms to the IETF PIDF-LO but makes it US-specific. CLDXF and FGDC standards are tightly related. Address data managers can exchange data across the standards. The three standards reinforce each other.

Questions and Discussion