The District of Columbia

Address Points - MAR (AddressPt)

Address Points - MAR (AddressPt)

by Department of Consumer and Regulatory Affairs on Weekly

Keywords
About: Addresspts, Address Point, Street Address, Address, Building Number, Street Number, Address Location, Quadrant, Street Type, location
Taking place at: Washington, D.C., District of Columbia, DC, DC GIS, DCGIS

Abstract

Address Point locations. The dataset contains locations and attributes of Address points, created as part of the Master Address Repository (MAR) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies.

It contains the addresses in the District of Columbia which are typically placed on the buildings. More information on the MAR can be found at:

http://octo.dc.gov/DC/OCTO/Maps+and+Apps/Online+Mapping/All+Online+Maps/Master+Address+Repository


All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.

METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

Purpose

This data is used for the planning and management of Washington, D.C. by local government agencies.

Use constraints

Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.

Point of contact

GIS Data Coordinator
in D.C. Office of the Chief Technology Officer

4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: (202) 727-5660
hours: 8:30 am - 5:30 pm

Credits

DC Department of Consumer and Regulatory Affairs
DC Office of the Chief Technology Officer

Data accuracy

Accuracy
Data believed to be complete and accurate, subject to change. In process of validation by source and/or responsible agency.

OCTO GIS performed several first round QA/QC to check the completeness and accuracy of the address points.

1. Quad Test - Test the Quadrant field in the data against the DC quad geography to see which address points are located in the wrong quadrant.

2. Ward Test - Test the Ward field in the data against the Ward geography to see which address points are located in the wrong ward.

3. Street Name Test - Select address points on street name and, based on clustering, see which address points do not fall along the selected street corridors. This test was performed for all A to W streets, 1st to 63rd streets, all state named avenues, most major roads, and random local streets.

4. Address Number Test - Select address points by unit block and, based on clustering, to check which address points do not fall along selected address range corridors.

5. Water Test - Select which address points intersect waterbodies.

6. Building Test - Since most address points should occur in buildings, select points that do not intersect a building. This test just flags points for further review.

7. Road Test - Select where address points intersect road polygons.

Since dated planimetrics were used in the test, the results mostly flagged data for further research. OCTO GIS also performed a detailed visual inspection of the city. This identified areas missing address points. OCTO GIS provided a report detailing the findings of the tests and a map showing the coded points and areas of omission.

Upon final delivery of the data, OCTO GIS performed several QA/QC to check the completeness and accuracy of the address points.

1. Address Identifier Check - Perform a summation on the address key field (ADDRESS_ID) and review for uniqueness and null values.

2. Address Range Check - Check for address numbers outside of the acceptable DC range, 1 through 8500.

3. Address Suffix Check - Check Address suffix for discrepancies.

4. Address Test - Compare the street name to the DDOT street list.

5. Address Test - Compare the street name and type to the DDOT street list.

6. Address Test - Compare the street name, type, and quad to the DDOT street list.

7. Quad Test - Test the Quadrant field in the data against the DC quad geography to see which address points are located in the wrong quadrant.

From these tests, several records were flagged with incorrect values or locations. These errors were fixed before OCTO generated a new address point layer.

Logical consistency
Validated by source and/or responsible agency

Completeness
Currently, the addresspts layer representing MAR ( Master Address Repository) addresses has 135,480 address. The file is approximately 99% complete and contains locations with full addresses ( 900 Pennsylvania Avenue NW) and partial addresses (Washington Monument).

These are the categories of missing addresses currently:

- New Development Areas in Southeast Quadrant
- Large Apartment and Condo Complexes
- Random individual addresses across the District

Horizontal positional accuracy
Building centroids were generated using ArcGIS and used to generate the first pass of MAR points. On the second pass, it was found that the OwnerPts were not always on buildings and therefore had to be moved to the building centroids. Wherever building footprints did not exist in the building layer but the building appeared on the ortho, a visual center of the building on the ortho was used.

Vertical positional accuracy
N/A

Lineage / Sources

  • Owner Points
    database, location and attribution
    ownerpoints
    by DC Office of Tax and Revenue, 2004
  • Customer File
    database, location and attribution
    WASA customers
    by DC Water and Sewer Authority, 2004
  • MPD Addresses
    database, location and attribution
    MPD addresses
    by Metropolitan Police Department, 2004
  • Mobile Video Addresses
    database, location and attribution
    Mobile Video addresses
    by DC Office of Tax and Revenue, 2004
  • Registered Vehicles
    database, location and attribution
    Registered Vehicles
    by DC Department of Motor Vehicles, 2004
  • Drivers Licenses
    database, location and attribution
    Drivers Licenses
    by DC Department of Motor Vehicles, 2004
  • Businesses
    database, location and attribution
    Businesses
    by Dun and Bradstreet, 2004
  • Mayor's Call Center
    database, location and attribution
    Mayor's Call Center
    by Executive Office of the Mayor, 2004
  • Street File
    database, location and attribution
    MPD Street File
    by Metropolitan Police Department, 2004
  • Property Owners
    database, location and attribution
    Property Owners
    by DC Office of Tax and Revenue, 2004
  • Property Inventory
    database, location and attribution
    Property Inventory
    by DC Office of Tax and Revenue, 2004
  • Registered Voters
    database, location and attribution
    Registered Voters
    by DC Board of Elections and Ethics, 2004
  • Health Care Safety Net database
    database, location and attribution
    Health Care Safety Net database
    by DC Department of Health, 2004
  • E 911 Street File
    database, location and attribution
    E 911 Street
    by DC Fire and Emergency Medical Services, 2004
  • Street Centerline
    database, location and attribution
    Street Centerline
    by DC District Department of Transportation, 2004
  • New addresses
    database, location and attribution
    Addresses
    by DC Department of Consumer and Regulatory Affairs, 2004
Lineage / Processes
Priti Mathur
in ARCBridge Consulting and Training, Inc

203 Elden Street, Suite#3
Herndon Virginia, 20170, USA

phone: 703-834-6511
fax: 703-834-6514
hours: 8:00 AM - 6:00 PM M-F
The Address Point Creation and verification Process:

ARCBridge Consulting reviewed 15 address databases identified as source material for the MAR. Addresses of each dataset were parsed, validated, and verified against the initial Master Address Table (MAT) created using the OTR database. All unverified and invalid addresses were manually reviewed. Addresses, which were invalid due to missing address components, were further examined in the manual process.

The manual review was based on the following information: Street Name, Street Range, Building Polygons, Property Scanned Images, and the Ortho. MAR addresses were also tested against the Mobile data as Mobile addresses were verified by field verification and thus more accurate.

The manual review was based on the 1999 planimetric data provided by OCTO, predominantly on buildings and street centerlines. Therefore, accuracy of addresses depended somewhat on the accuracy and currentness of the planimetric data. As a result, manual review was limited by the planimetric data and the owner point X,Y coordinates provided by OCTO.

The address points were primarily created from the 'Ownerpoints' database from the DC Office of Tax and Revenue (OTR) given to ARCBridge by DC OCTO.


OTR: 172,470

Phase I:

The 'Premiseadd' field was parsed to separate the address components. Addresses with the above mentioned components were treated as complete address. Staff checked whether the X,Y values of the complete addresses existed. If a good address didn't have X,Y values, then it was added. Addresses were manually reviewed to check the address location. Addresses, whose street number, name, and location matched, were treated as complete and added to MAR.

Phase II:

The addresses from the 'Address 2' field were processed, as while reviewing a number of addresses in the 'Address2' field appear correct. Staff checked whether the X,Y values of the complete addresses existed. If a good address didn't have X,Y values, then it was added. Addresses were manually reviewed to check the address location. Addresses, whose street number, name, and location matched, were treated as complete and added to MAR.

Phase III:

The remaining addresses that either had missing component or didn't appear correct were manually reviewed. Addresses components were then reviewed. For example: If the street type was missing or wrong and all the other components like street name, number, and location were correct, then the street type was added or changed. Staff checked whether the X,Y values of the complete addresses exist or not. If a good address didn't have X,Y values, then it was added. These modified addresses were added to the MAR.

Phase IV:

The remaining addresses that could not be verified, didn't appear correct, or were ambiguous were moved into the comment table.


WASA: 132,868

WASA addresses didn't have X,Y values, therefore the addresses were geocoded to add X,Y coordinates.

Phase I:

The 'Address' field was parsed to separate the address components. Addresses with the above mentioned components were treated as complete addresses. Staff checked whether X,Y values of the complete addresses existed. If any good address didn't have XY values then it was added. Addresses were manually reviewed to check the address location. Addresses, whose street number, name & location matched, were treated as good and complete and added to MAR.

Phase II.

The remaining addresses that either had a missing component or didn't appear correct were manually reviewed. Addresses components were then reviewed. For example: If the street type was missing or wrong and all the other components like street name, number, and location were correct, then the street type was added or changed. Staff checked whether X,Y values of the complete addresses existed. If a good address didn't have X,Y values, then it was added. These modified addresses were then added to the MAR.

Phase III.

Addresses that could not be verified, didn't appear correct, or were ambiguous were moved to the comment table.


MPD: 269,350

Phase I:

The 'Address' field was parsed to separate the address components. Addresses with the above mentioned components were treated as complete addresses. Staff checked whether the X,Y values of the complete addresses existed. If a good address didn't have XY values, then it was added. Addresses were manually reviewed to check their location. Addresses, whose street number, name, and location matched, were treated as complete and added to MAR.

Phase II:

The remaining Addresses that either contained a missing component or didn't appear correct were manually reviewed. Addresses components were then reviewed. For example: If the street type was missing or wrong and all the other components like street name, number, and location were correct, then the street type was added or changed. Staff checked whether the X,Y values of the complete addresses existed. If a good address didn't have X,Y values, then it was added. These modified addresses were added to the MAR.

Phase III:

Addresses that couldn't be verified, didn't appear correct, or were ambiguous were moved to the comment table. Numerous MPD addresses were moved to the comments table as most of them appeared theoretical, such as a full address with no associated building.


OTR- Mobile Video data: 156,527

Mobile addresses were created and verified at the physical location of the address, thus strengthening the validity of the attribution. Most other source information was generated and verified using manual in-house procedures.

Mobile Video addresses were manually reviewed to check the address locations. Addresses, whose street number, name, and location matched, were treated as valid. The remaining addresses were moved to the comments table.

Addresses with comments were manually reviewed. Addresses components were reviewed, for example: If type was missing or wrong and all the other components like street name, number & location were correct then type was added/changed. These modified correct addresses were moved out of the Comment table and added to the valid Mobile Video address table.

Many of the same procedures were run on the remaining source datasets:

DMV - Registered Vehicles - 53,507
DMV - Drivers License: - 140,595
D&B - Business: - 38,625
MCC - EMA - 195,857
MPD - Street File - 128,699
OTR- Property Owners - 129,800
OTR- Property Inventory - 161,408
BOEE- Registered Voters - 318,318
DOH - 201,796
FEMS - E 911 - 142,407
DDOT- Street Centerline - 33,291
DCRA - New Addresses - 151

Total Address Records Reviewed - 2,275,669


Working with Unverified Addresses:

Phase I:

The full address field of each dataset was parsed to separate the address components using the MDS Tool. Addresses with the all the required components were treated as complete addresses. All addresses validated and verified. All unverified addresses were manually reviewed to create address points. Unverified addresses were geocoded if the dataset did not have X, Y coordinates. Addresses, whose street number, name, and location matched, were treated as complete and added to MAR. Good addresses that the analyst was unable to verify were placed in the comments table.

Phase II:

Addresses that either had missing components or didn't appear correct were manually reviewed. Addresses components were then reviewed. For example, if the streey type was missing or incorrect and all other components, like street name, number, and location, were correct, then the streey type of the address location type was added or changed.

If the street number was missing or incorrect, then the street number range and adjacent building numbers were used to correct or add the street number. If street name was missing or incorrect, then the street name at the address point location was identified and added or modified. If the quad was missing or incorrect, then the quad at the address point location was identified and added or modified.

If any address was complete but the address point was at the wrong location, then staff identified the related street name and range from the street centerlines and moved theaddress point to the correct location manually. Then, the moved address points' X,Y values were updated.

These modified correct addresses were added to the MAR.

Phase III.

Staff then completed the comments table. Addresses that couldn't be verified, didn't appear correct, or were ambiguous were moved to the comment table. It contains all of the reject addresses from the 15 source datasets.

For more information regarding the construction of the MAR, refer to the "DC Addressing Final Report."
GIS Data Coordinator
in Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: 202-727-5660
hours: 8:30am - 5:30pm
To generate the address point feature class, OCTO GIS staff exported the address view from the DC MAR database as a oracle dump file. The address view pulls data from: 1.) DC MAR for address key; 2.) DDOT Street Spatial Database for street information; and 3.) OCTO GIS enterprise geodatabase for square, suffix, and lot (SSL).

Staff imported this file into the GIS enterprise geodatabase and created an event theme using the x,y coordinates. The event theme was converted to a feature class.

Staff then overlayed the feature class with the following layers:

- 2002 ANC
- 2002 Ward
- Police Service Area
- Police District
- Police Regional Operations Command
- Zip Code
- Neighborhood
- Neighborhood Cluster
- 2002 SMD
- Voting Precinct
- Census Tract

Staff then regenerated the address view to capture SSL values. This information was added to the address point layer.

Distribution

Most DC GIS datasets can be downloaded from "http://dcgis.dc.gov" on the data center page. Orders can also be made by contacting OCTO GIS at "dcgis@dc.gov", especially for datasets not available for download.

Distribution liability
Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.

Distributed by
GIS Data Coordinator
in D.C. Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: (202) 727-5660
hours: 8:30 am - 5 pm

Entity

AddressPt

Attributes

  • FID / ESRI
    Internal feature number.
  • OBJECTID / ESRI
    Internal feature number.
  • XCOORD
    X Coordinate of Address Point
  • SITE_ADDRE
  • YCOORD
    Y Coordinate of Address Point
  • ROADWAYSEG
  • STATUS_ID
    Status Identifier
  • SQUARE
    Address location property square
  • SUFFIX
    Address location property suffix
  • ENTRANCETY
  • LOT
    Address location property lot
  • ADDRNUMSUF
  • ADDRESS_ID
    Address identifier
  • STREET_TYP
  • STATUS
    Status Value
    • ACTIVE /
    • RECOMMENDED /
    • ASSIGNED /
    • RETIRE /
    • TEMPORARY /
    •  
  • SSL
    Address location Square, Suffix, and Lot
  • ADDRNUM
    Address location house number
  • FULLADDRES
  • STNAME
    Address location street name
  • QUADRANT
    Address location quadrant name
  • ZIPCODE4
    Address location Zip +4 Code
  • NATIONALGR
  • CITY
    Address location city
  • HOTSPOT
    Address location hot spot
  • STATE
    Address location state name
  • ANC
    Address location Advisory Neighborhood Commission
  • METADATA_I
  • OBJECTID_2
  • ASSESSMENT
  • ASSESSME_1
  • TYPE_
    Address Type
    • Address / Location has a full address
    • Place / Location does not have a full address
    •  
  • PSA
    Address location Police Service Area
  • WARD
    Address location Ward name
  • CLUSTER_
    Address location neighborhood cluster name
  • POLDIST
    Address location police district
  • ROC
    Address location regional operations command area
  • ZIPCODE
    Address location Zip code
  • CENSUS_TRA
  • VOTE_PRCNC
  • SMD
    Address location Single Member District
  • SHAPE / ESRI
    Shape geometry
  • CFSA_NAME
    Address CFSA area name
  • NEWCOMMSEL
  • NEWCOMMCAN
  • CENSUS_BLO
  • CENSUS_B_1
  • FOCUS_IMPR
  • LATITUDE
    Latitude of address
  • LONGITUDE
    Longitude of Address
  • ACTIVE_RES
  • RES_TYPE
    Residential Type
    • Residential /
    • Non Residential /
    • Mixed - Use /
    •  
  • ACTIVE_R_1
  • WARD_2002
  • WARD_2012
  • ANC_2002
  • ANC_2012
  • SMD_2002
  • SMD_2012

Metadata

FGDC Content Standards for Digital Geospatial Metadata / FGDC-STD-001-1998 as of 20121011

Provided by
GIS Data Coordinator
in D.C. Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

phone: REQUIRED: The telephone number by which individuals can speak to the organization or individual.
fax: (202) 727-5660
hours: 8:30 am - 5:30 pm