Address_Points_from_National_Address_Database eng; USA 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 information applies to the dataset Mara Kaminowitz US Department of Transportation Deputy Geospatial Information Officer 855-368-4200 1200 New Jersey Ave. SE Washington DC 20590 United States nad@dot.gov point of contact 2026-03-31 ISO 19139 Geographic Information - Metadata ISO/TS 19139:2007 point 96893147 EPSG:3857 EPSG 6.18.3(9.3.1.2) National Address Database (NAD) 2017-08-10 creation 2026-03-31 revision US Department of Transportation originator mapDigital The Address Points from National Address Database dataset was compiled on March 31, 2026 by the US Department of Transportation. The National Address Database (NAD) is a spatial database containing address data, point location coordinates, jurisdictions, record-level metadata and other supporting data for addressable locations including structures, some sub-units within those structures, and landmarks as included in the aggregated datasets from providers included therein. To provide address information to enhance transportation safety and a broad range of other government services. Acknowledgment of the Department of Transportation (DOT), the U.S. Census Bureau, Geography Division, and the following partners: Seminole Tribe of Florida, Rosebud Sioux Tribe South Dakota, Alabama 911 Board, Baldwin County Alabama, State of Alaska, Coastal Villages Region Fund Alaska, Denali Borough Alaska, Dillingham Alaska, Fairbanks North Star Alaska, Haines Alaska, Matanuska-Susitna Alaska, Municipality of Anchorage Alaska, Yakutat Alaska, State of Arizona, Arkansas Geographic Information Office, Costa Mesa City California, Merced County California, Sacramento County CA, San Bernardino County ITD California, Santa Barbara County Fire GIS California, Santa Cruz County GIS California, Shasta County California, Solano County California, Ventura County California, Colorado OIT GIS, State of Connecticut, Kent County Delaware, New Castle County Delaware, Sussex County Delaware, OCTO DATA TEAM District of Columbia, Holmes County Florida, Jackson County Florida, ATLANTA.GA.US, State of Idaho, State of Illinois, Indiana Geographic Information Council, State of Iowa, State of Kansas, State of Kentucky, City of Baton Rouge-Parish of East Baton Rouge Government, Terrebonne Parish Consolidated Government Louisiana, ngesi.maine.gov Maine, Maryland Department of Information Technology, BOSTON and MASSGIS Massachusetts, Geospatial Information Office Minnesota, Swift County Minnesota, Northeast Emergency Communications Center 911 Missouri, Missouri GIS Advisory Council, Montana State Library, State of Nebraska, State of New Jersey, University of New Mexico EDAC, New York State Geospatial Services, State of North Carolina, State of North Dakota, State of Ohio, State of Oklahoma, Mayes County 911 Oklahoma, Oregon Department of Administrative Services, Blair County Pennsylvania, Centre County Pennsylvania, Cumberland County Pennsylvania, Fayette County Pennsylvania, Indiana County Pennsylvania, Lawrence County Pennsylvania, Montgomery County Pennsylvania, Tioga County Pennsylvania, Washington County Pennsylvania, Westmoreland County Pennsylvania, State of Rhode Island, Oconee County GIS South Carolina, York County South Carolina, City of Sioux Falls South Dakota, TN STS GIS Services, State of Texas, Utah Geospatial Resource Center (UGRC), U.S. Virgin Islands, Vermont Enhanced 911 Board, Virginia Geographic Information Network, State of Washington, State of Wisconsin, Sauk County Wisconsin, West Virginia GIS, Albany County Wyoming, Big Horn County Wyoming, Campbell County Public Works Wyoming, Crook County Assessors Office Wyoming, Fremont County Wyoming, Greenwood Mapping Inc Teton Wyoming, Laramie County Wyoming, Lincoln County GISIT Wyoming, Natrona County Wyoming, Sublette County Wyoming, Sweetwater County Wyoming, Uinta County Wyoming data is continually being updated Mara Kaminowitz US Department of Transportation Deputy Geospatial Information Officer 855-368-4200 1200 New Jersey Ave. SE Washington DC 20590 United States nad@dot.gov point of contact data is updated every three months 2026-07-01 ========================= NGDA National Geospatial Data Asset Address Theme Transportation Theme NGDAID196 theme NGDA Portfolio Themes 2010-11-01 publication 2013-08-24 revision https://www.geoplatform.gov/ngda-themes https NGDA Portfolio Themes Home Page Webpage containing information and standard definitions for National Geospatial Data Asset (NGDA) Portfolio Themes. information U.S. United States USA United States of America Seminole Tribe Rosebud Sioux Virgin Islands of the U.S. place Geographic Names Information System (GNIS) 2008-10-28 publication https://www.usgs.gov/tools/geographic-names-information-system-gnis https USGS GNIS Home Page The official federal repository for domestic geographic names and the national standard for geographic nomenclature. information Published data made available as a part of the NAD is provided as a public service to enhance open government, transparency, and accountability. The NAD is a compilation of data provided by state, local, and tribal governments and is made available "as is." Although the NAD is open data, it is not intended for use as a mailing list and is subject to individual state statutes that prohibit its use as a mailing list. The NAD is a work of the federal government and as such is not subject to copyright protection in accordance with 17 U.S.C. § 105. It is available for re-use without limitation or restriction. limitation not listed Access Constraints: The National Address Database (NAD) is, with few exceptions, aggregated from state data, which is in turn aggregated from local data. While it is considered to be authoritative and every reasonable effort is made to ensure the accuracy and completeness of the data, the United States Department of Transportation (USDOT) makes no warranties, expressed or implied, concerning the accuracy, completeness or suitability of the data, and it should not be construed or used as a legal description. In no event shall USDOT become liable to users of this data, or any other party, for any loss or damages, consequential or otherwise, including but not limited to time, money, or goodwill, arising from the use, operation or modification of the data. In using this data, users further agree to indemnify, defend, and hold harmless USDOT for any and all liability of any nature arising out of or resulting from the lack of accuracy or correctness of the data, or the use of the data. The states that partner with USDOT to provide data for the NAD do so willingly, with no obligation. Not every state that provides data to the NAD has complete coverage. As state address programs expand and mature, USDOT expects the coverage to expand as well. vector data is used to represent geographic data eng; USA location Native Dataset Environment: Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 -171.5 -67 18.5 71.5 2026-03-31 false National Address Database (NAD) Schema Definition 2023-04-17 publication 2026-03-31 revision https://www.transportation.gov/gis/nad/nad-schema https NAD Schema Documentation Official schema documentation and data dictionary for the National Address Database (NAD), detailing attribute names, types, and domains. information ESRI File Geodatabase 1.0 GeoServices REST API 1.0 US Department of Transportation NAD Program Manager 1200 New Jersey Ave. SE Washington DC 20590 United States nad@dot.gov distributor None. No fees are applicable for obtaining the dataset. https://www.transportation.gov/mission/open/gis/national-address-database/national-address-database-nad-disclaimer ESRI File Geodatabase ESRI File Geodatabase download https://services.arcgis.com/xOi1kZaI0eWDREZv/ArcGIS/rest/services/Address_Points_from_National_Address_Database_view/FeatureServer GeoServices http://www.geoplatform.gov/spec/esri-map-rest GeoServices REST API Web service using open specification of the Open Web Foundation http://geoservices.github.io/ download information applies to the dataset Attribute Correctness directExternal Attributes (State, County, CDP, AIA, Tribal Subdivision) validated via point-in-polygon spatial join against Census TIGERweb. Coordinates recalculated in GCS WGS 1984 using FME. Domain values standardized via lookup tables. National Address Database (NAD) Schema Definition 2023-04-17 publication All published records meet mandatory attribute domains and coordinate precision requirements defined in the NAD schema. true Logical Integrity directInternal Validation of GUID formats, jurisdictional spatial integrity, and duplicate detection based on coordinate and sub-address uniqueness. National Address Database (NAD) Schema Definition 2023-04-17 publication Data follows the logical rules for 1-to-1 relationship between GUIDs and features, and spatial containment within specified jurisdictions. true Feature Completeness directInternal Assessment of record presence across contributing jurisdictions. Measurement of mandatory vs. optional attribute population. National Address Database (NAD) Schema Definition 2023-04-17 publication 100% of published records contain mandatory spatial and jurisdictional attributes. Overall completeness varies by voluntary provider submission. true Horizontal Positional Accuracy directInternal Point coordinates (x, y, z) validated to ensure placement within the geographic extent of the attributed state boundary. National Address Database (NAD) Schema Definition 2023-04-17 publication Positional accuracy is consistent with source data methodologies (GNSS, geocoding, or parcel centroids). Features conform to jurisdictional boundary constraints. true This lineage summarizes NAD source referencing, processing workflow, transformations, filters, and provenance pointers; publication date and maintenance frequency are recorded in the metadata's dateStamp and resourceMaintenance elements. Source datasets are provided by the organizations listed in the metadata record's credit element; consult the credits for provider-specific coverage, capture dates, and contacts. Feature-level provenance fields (e.g., NAD_Source, DateUpdate) identify the origin and update timing of individual records. National Address Database (NAD) Contributor List (see metadata credits) 2026-03-31 publication Processing workflow (chronological): ingest → schema map → reproject → screen special characters → dedupe → attribute standardize → jurisdiction validate → stage for publish. Tools: SAFE FME Workbench (Schema Mapper, Point On Area Overlayer, CoordinateExtractor, LatLongToMGRSConverter), Esri ArcGIS Pro (QA), Python 3.x (automation and reporting). Ingestion/QA/standardization/staging occurred approximately 3 month period leading up to publication; publication (quarterly cadence). Coordinate transforms: input CRSs accepted include NAD83 (EPSG:4269 and various State Plane EPSG:269xx), WGS84 (EPSG:4326), Web Mercator (EPSG:3857), and local State Plane CRSs. Transformations performed with SAFE FME Workbench EsriReprojector using specified Esri transformation parameters; ArcGIS Project used as independent QA. Published geometry is provided in Web Mercator (EPSG:3857). Latitude/Longitude attributes are recalculated from SHAPE geometry in GCS WGS 1984 (EPSG:4326) and rounded to six decimal places. USNG/MGRS values derived at precision=5 using FME LatLongToMGRSConverter. Records with missing or ambiguous CRS definitions are flagged/rejected. Deduplication and exclusions: duplicate detection performed per NAD_Source provider group. Identical attribute+coordinate duplicates: keep first occurrence. Duplicate attributes at unique coordinates: retain up to 100 occurrences; occurrences beyond 100 are rejected. Records with null/invalid geometry, negative or missing primary address numbers, or missing street names are rejected unless explicitly attributed as Landmark Address Classification. Domain attributes that cannot be standardized via lookup tables are rejected. Rejected and exception records are returned to providers for remediation. Attribute standardization: domain-restricted attributes normalized using FME Schema Mapper and lookup tables. Jurisdiction validation performed via point-in-polygon spatial join against Census TIGERweb place polygons; missing jurisdiction values are populated from TIGER where possible; conflicting jurisdiction values are rejected. Records that pass all checks are staged for publication. Publication is carried out on a quarterly cadence (see metadata resourceMaintenance); NAD does not maintain an archive of prior releases nor a public changelog for releases. Exception reports are provided to contributors after each processing cycle. Feature-level provenance attributes (NAD_Source, DateUpdate) are retained to identify origin. Detailed provider metadata and contacts are available via the metadata credits list; providers are the authoritative source for provenance and positional accuracy of their submitted features. Mara Kaminowitz US Department of Transportation Deputy Geospatial Information Officer 855-368-4200 1200 New Jersey Ave. SE Washington DC 20590 United States nad@dot.gov custodian data is updated every three months Mara Kaminowitz US Department of Transportation Deputy Geospatial Information Officer 855-368-4200 1200 New Jersey Ave. SE Washington DC 20590 United States nad@dot.gov custodian