Address Points - MAR (AddressPt)

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: Department of Consumer and Regulatory Affairs
Originator: Office of the Chief Technology Officer
Publication_Date: Weekly
Title: Address Points - MAR (AddressPt)
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publisher: DC GIS
Online_Linkage:
<http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=AddressPt&downloadTYPE=ESRI>
Online_Linkage:
<http://dcatlas.dcgis.dc.gov/catalog/download.asp?downloadName=AddressPt&downloadTYPE=KMZ>
Description:
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.
Supplemental_Information:
MAR FAQ is located at:
<http://octo.dc.gov/DC/OCTO/Agency+Support/IT+Standards/Geography+Standards/Frequently+Asked+Questions+(FAQ>)+of+the+MAR
One important item is the status of the address. The MAR contains more addresses than are active so the following informaiton will help users determine the current addresses for the District.
What do the different statuses in the address table mean?
- ACTIVE - addresses for buildings which are standing. The overwhelming majority of addresses have the 'ACTIVE' status.
- RECOMMENDED - addresses which have been recommended (suggested) by a DC GIS employee for approval by DCRA.
- ASSIGNED - addresses which have been assigned (approved) by DCRA, but whose buildings have not yet been constructed.
- RETIRE - addresses for buildings that have been demolished or for addresses which represented space which has since been occupied by a different address (example: a retail store closing and being taken over by a neighboring store which knocks the wall down)
- TEMPORARY - addresses which will exist for a relatively short period of time. Construction trailers, special event tents may be given this TEMPORARY designation.
- MISTAKE - addresses which are incorrect. These MISTAKE addresses are automatically deleted each and every evening. These MISTAKE addresses are due to incorrect data being entered using the MAR Maintenance Tool.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: weekly
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Weekly
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.114311
East_Bounding_Coordinate: -76.909628
North_Bounding_Coordinate: 38.995547
South_Bounding_Coordinate: 38.812209
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: Addresspts
Theme_Keyword: Address Point
Theme_Keyword: Street Address
Theme_Keyword: Address
Theme_Keyword: Building Number
Theme_Keyword: Street Number
Theme_Keyword: Address Location
Theme_Keyword: Quadrant
Theme_Keyword: Street Type
Theme_Keyword: location
Place:
Place_Keyword: Washington, D.C.
Place_Keyword: District of Columbia
Place_Keyword: DC
Place_Keyword: DC GIS
Place_Keyword: DCGIS
Use_Constraints:
For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 4th St NW, Suite 930 South
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5:30 pm
Data_Set_Credit:
DC Department of Consumer and Regulatory Affairs DC Office of the Chief Technology Officer
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.4000
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
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_Report: Validated by source and/or responsible agency
Completeness_Report:
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
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
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:
Vertical_Positional_Accuracy_Report: N/A
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Office of Tax and Revenue
Publication_Date: 2004
Title: Owner Points
Online_Linkage: <http://cfo.dc.gov>
Type_of_Source_Media: database
Source_Time_Period_of_Content:
Time_Period_Information:
Source_Citation_Abbreviation: ownerpoints
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Water and Sewer Authority
Publication_Date: 2004
Title: Customer File
Online_Linkage: <http://www.dcwasa.com>
Type_of_Source_Media: database
Source_Citation_Abbreviation: WASA customers
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: Metropolitan Police Department
Publication_Date: 2004
Title: MPD Addresses
Online_Linkage: <http://mpdc.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: MPD addresses
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Office of Tax and Revenue
Publication_Date: 2004
Title: Mobile Video Addresses
Online_Linkage: <http://cfo.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Mobile Video addresses
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Department of Motor Vehicles
Publication_Date: 2004
Title: Registered Vehicles
Online_Linkage: <http://dmv.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Registered Vehicles
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Department of Motor Vehicles
Publication_Date: 2004
Title: Drivers Licenses
Online_Linkage: <http://dmv.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Drivers Licenses
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: Dun and Bradstreet
Publication_Date: 2004
Title: Businesses
Online_Linkage: <http://www.dandb.com>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Businesses
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: Executive Office of the Mayor
Publication_Date: 2004
Title: Mayor's Call Center
Online_Linkage: <http://mayor.dc.gov/DC/Mayor>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Mayor's Call Center
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: Metropolitan Police Department
Publication_Date: 2004
Title: Street File
Online_Linkage: <http://mpdc.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: MPD Street File
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Office of Tax and Revenue
Publication_Date: 2004
Title: Property Owners
Online_Linkage: <http://cfo.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Property Owners
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Office of Tax and Revenue
Publication_Date: 2004
Title: Property Inventory
Online_Linkage: <http://cfo.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Property Inventory
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Board of Elections and Ethics
Publication_Date: 2004
Title: Registered Voters
Online_Linkage: <http://www.dcboee.org>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Registered Voters
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Department of Health
Publication_Date: 2004
Title: Health Care Safety Net database
Online_Linkage: <http://doh.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Health Care Safety Net database
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Fire and Emergency Medical Services
Publication_Date: 2004
Title: E 911 Street File
Online_Linkage: <http://fems.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: E 911 Street
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC District Department of Transportation
Publication_Date: 2004
Title: Street Centerline
Online_Linkage: <http://ddot.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Street Centerline
Source_Contribution: location and attribution
Source_Information:
Source_Citation:
Citation_Information:
Originator: DC Department of Consumer and Regulatory Affairs
Publication_Date: 2004
Title: New addresses
Online_Linkage: <http://dcra.dc.gov>
Type_of_Source_Media: database
Source_Citation_Abbreviation: Addresses
Source_Contribution: location and attribution
Process_Step:
Process_Description:
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."
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Priti Mathur
Contact_Organization: ARCBridge Consulting and Training, Inc
Contact_Position: President
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Herndon
State_or_Province: Virginia
Postal_Code: 20170
Country: USA
Contact_Voice_Telephone: 703-834-6511
Contact_Facsimile_Telephone: 703-834-6514
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:00 AM - 6:00 PM M-F
Process_Step:
Process_Description:
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.
Process_Date: 8/31/2005
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Office of the Chief Technology Officer
Contact_Person: GIS Data Coordinator
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: 202-727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30am - 5:30pm
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: F:\DCGISDATA_FINAL\Maintenance\AddressPt.shp.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DCGISDATA_WORKSPACE\DCRA\MAR\addresspt.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DCGISDATA_WORKSPACE\DCRA\MAR\addresspt.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DCGISDATA_WORKSPACE\DCRA\MAR\address.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DCGISDATA_WORKSPACE\DCRA\MAR\address40606.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: E:\DCGISDATA_WORKSPACE\DCRA\MAR\addresspt_060106.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: W:\DCGISDATA_WORKSPACE\DCRA\MAR\addresspt_0081806.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\AddressPt_old.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\AddressPt_old.xml
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\temp\addrpt.xml
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity point
Point_and_Vector_Object_Count: 142452
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: State Plane Coordinate System
State_Plane_Coordinate_System:
SPCS_Zone_Identifier: 1900
Lambert_Conformal_Conic:
Standard_Parallel: 38.300000
Standard_Parallel: 39.450000
Longitude_of_Central_Meridian: -77.000000
Latitude_of_Projection_Origin: 37.666667
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000125
Ordinate_Resolution: 0.000125
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: DCGIS.AddressPt
Attribute:
Attribute_Label: OBJECTID_1
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: OBJECTID_12
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: SITE_ADDRESS_PK
Attribute_Definition: Address Identifier
Attribute:
Attribute_Label: XCOORD
Attribute_Definition: X Coordinate of Address Point
Attribute:
Attribute_Label: YCOORD
Attribute_Definition: Y Coordinate of Address Point
Attribute:
Attribute_Label: NATIONALGRID
Attribute_Definition: Address location national grid coordinate
Attribute:
Attribute_Label: STATUS_ID
Attribute_Definition: Status Identifier
Attribute:
Attribute_Label: METADATA_ID
Attribute_Definition: Metadata Identifier
Attribute:
Attribute_Label: ROADWAYSEGID
Attribute_Definition: Roadway Segment Identifier
Attribute_Domain_Values:
Attribute:
Attribute_Label: SQUARE
Attribute_Definition: Address location property square
Attribute:
Attribute_Label: SUFFIX
Attribute_Definition: Address location property suffix
Attribute:
Attribute_Label: LOT
Attribute_Definition: Address location property lot
Attribute:
Attribute_Label: ADDRESS_ID
Attribute_Definition: Address identifier
Attribute:
Attribute_Label: STATUS
Attribute_Definition: Status Value
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ACTIVE
Enumerated_Domain_Value_Definition_Source:
addresses for buildings which are standing. The overwhelming majority of addresses have the 'ACTIVE' status.
Enumerated_Domain:
Enumerated_Domain_Value: RECOMMENDED
Enumerated_Domain_Value_Definition_Source:
addresses which have been recommended (suggested) by a DC GIS employee for approval by DCRA.
Enumerated_Domain:
Enumerated_Domain_Value: ASSIGNED
Enumerated_Domain_Value_Definition_Source:
addresses which have been assigned (approved) by DCRA, but whose buildings have not yet been constructed.
Enumerated_Domain:
Enumerated_Domain_Value: RETIRE
Enumerated_Domain_Value_Definition_Source:
addresses for buildings that have been demolished or for addresses which represented space which has since been occupied by a different address (example: a retail store closing and being taken over by a neighboring store which knocks the wall down)
Enumerated_Domain:
Enumerated_Domain_Value: TEMPORARY
Enumerated_Domain_Value_Definition_Source:
addresses which will exist for a relatively short period of time. Construction trailers, special event tents may be given this TEMPORARY designation.
Attribute:
Attribute_Label: SSL
Attribute_Definition: Address location Square, Suffix, and Lot
Attribute:
Attribute_Label: ENTRANCETYPE
Attribute_Definition: Address entrance type
Attribute:
Attribute_Label: ADDRNUM
Attribute_Definition: Address location house number
Attribute:
Attribute_Label: ADDRNUMSUFFIX
Attribute_Definition: Address location house number suffix
Attribute:
Attribute_Label: STNAME
Attribute_Definition: Address location street name
Attribute:
Attribute_Label: STREET_TYPE
Attribute_Definition: Address location street type
Attribute:
Attribute_Label: QUADRANT
Attribute_Definition: Address location quadrant name
Attribute:
Attribute_Label: ZIPCODE4
Attribute_Definition: Address location Zip +4 Code
Attribute:
Attribute_Label: CITY
Attribute_Definition: Address location city
Attribute:
Attribute_Label: HOTSPOT
Attribute_Definition: Address location hot spot
Attribute:
Attribute_Label: FULLADDRESS
Attribute_Definition: House number, street name, street type, and quadrant
Attribute:
Attribute_Label: NEWCOMMSELECT06
Attribute_Definition: Address location New Community Selected 2006
Attribute:
Attribute_Label: STATE
Attribute_Definition: Address location state name
Attribute:
Attribute_Label: ANC
Attribute_Definition: Address location Advisory Neighborhood Commission
Attribute:
Attribute_Label: TYPE_
Attribute_Definition: Address Type
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Address
Enumerated_Domain_Value_Definition: Location has a full address
Enumerated_Domain:
Enumerated_Domain_Value: Place
Enumerated_Domain_Value_Definition: Location does not have a full address
Attribute:
Attribute_Label: PSA
Attribute_Definition: Address location Police Service Area
Attribute:
Attribute_Label: WARD
Attribute_Definition: Address location Ward name
Attribute:
Attribute_Label: CLUSTER_
Attribute_Definition: Address location neighborhood cluster name
Attribute:
Attribute_Label: POLDIST
Attribute_Definition: Address location police district
Attribute:
Attribute_Label: ROC
Attribute_Definition: Address location regional operations command area
Attribute:
Attribute_Label: CENSUS_TRACT
Attribute_Definition: Address location census tract
Attribute:
Attribute_Label: VOTE_PRCNCT
Attribute_Definition: Address location voting precinct
Attribute:
Attribute_Label: ZIPCODE
Attribute_Definition: Address location Zip code
Attribute:
Attribute_Label: SMD
Attribute_Definition: Address location Single Member District
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Shape geometry
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: NEWCOMMCANDIDATE
Attribute_Definition: Address location New Community Candidate
Attribute:
Attribute_Label: ASSESSMENT_NBHD
Attribute_Definition: Address Assessment Neighborhood Name
Attribute:
Attribute_Label: ASSESSMENT_SUBNBHD
Attribute_Definition: Address Assessment SubNeighborhood Name
Attribute:
Attribute_Label: CFSA_NAME
Attribute_Definition: Address CFSA area name
Attribute:
Attribute_Label: CENSUS_BLOCK
Attribute_Definition: Census Block Value Address is in
Attribute:
Attribute_Label: CENSUS_BLOCKGROUP
Attribute_Definition: Census Block Group value
Attribute:
Attribute_Label: FOCUS_IMPROVEMENT_AREA
Attribute_Definition: Focus improvement area name
Attribute:
Attribute_Label: SE_ANNO_CAD_DATA
Attribute_Definition: SDO data type
Attribute:
Attribute_Label: LATITUDE
Attribute_Definition: Latitude of address
Attribute:
Attribute_Label: LONGITUDE
Attribute_Definition: Longitude of Address
Attribute:
Attribute_Label: ACTIVE_RES_UNIT_COUNT
Attribute_Definition: Active Residential Use Count
Attribute:
Attribute_Label: RES_TYPE
Attribute_Definition: Residential Type
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Residential
Enumerated_Domain:
Enumerated_Domain_Value: Non Residential
Enumerated_Domain:
Enumerated_Domain_Value: Mixed - Use
Attribute:
Attribute_Label: ACTIVE_RES_OCCUPANCY_COUNT
Attribute_Definition: Number of Housing Units at the primary address
Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: GIS Data Coordinator
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5 pm
Resource_Description: Downloadable Data
Distribution_Liability:
For data terms and conditions, go to <http://dc.gov/page/terms-and-conditions-use-district-data>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 3.428
Ordering_Instructions: All data is available at <http://opendata.dc.gov>
Metadata_Reference_Information:
Metadata_Date: 20110909
Metadata_Review_Date: 8/31/2005
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: GIS Data Coordinator
Contact_Organization: D.C. Office of the Chief Technology Officer
Contact_Address:
Address_Type: mailing and physical address
Address: 200 I Street SE, 5th Floor
City: Washington
State_or_Province: DC
Postal_Code: 20001
Country: USA
Contact_Voice_Telephone:
REQUIRED: The telephone number by which individuals can speak to the organization or individual.
Contact_Facsimile_Telephone: (202) 727-5660
Contact_Electronic_Mail_Address: [email protected]
Hours_of_Service: 8:30 am - 5:30 pm
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.12 on Thu Jun 25 15:31:21 2015