Address Points


Identification Information:
Citation:
Citation Information:
Publication Date: 20030101
Title: Address Points
Geospatial Data Presentation Form: tabular digital data
Online Linkage: https://dcgov.box.com/v/address-points
Description:
Abstract: The dataset contains locations and attributes of address points, created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and Department of Buildings (DOB). It contains the addresses in the District of Columbia which are typically placed on the buildings. Visit opendata.dc.gov/pages/addressing-in-dc#documentation for more information on the MAR.
Purpose: Location of street addresses in the District of Columbia.
Status:
Progress: Complete
Maintenance and Update Frequency: Daily
Spatial Domain:
Bounding Coordinates:
West Bounding Coordinate: -77.13
East Bounding Coordinate: -76.90
North Bounding Coordinate: 39.01
South Bounding Coordinate: 38.78
Keywords:
Theme:
Theme Keyword Thesaurus: None
Theme Keyword: master address repository
Theme Keyword: location
Theme:
Theme Keyword Thesaurus: ISO 19115 Topic Categories
Theme Keyword: location
Place:
Place Keyword Thesaurus: None
Place Keyword: District of Columbia
Place Keyword: Washington DC
Access Constraints: Other Constraints
Use Constraints: This work is licensed under a Creative Commons Attribution 4.0 International License.
Point of Contact:
Contact Information:
Contact Organization Primary:
Contact Organization: Department of Buildings
Contact Address:
Address Type: mailing and physical
Address: 1100 4th Street SW
City: Washington
State or Province: DC
Postal Code: 20024
Contact Voice Telephone: (202) 671-3500
Point of Contact:
Contact Information:
Contact Organization Primary:
Contact Organization: Office of the Chief Technology Officer
Contact Position: GIS Data Coordinator
Contact Address:
Address Type: mailing and physical
Address: 200 I Street SE
City: Washington
State or Province: DC
Postal Code: 20003
Country: US
Contact Voice Telephone: (202) 727-2277
Contact Electronic Mail Address: dcgis@dc.gov
Hours: 8:30 am - 5 pm
Point of Contact:
Contact Information:
Contact Organization Primary:
Contact Organization: Office of the Chief Technology Officer
Contact Position: GIS Data Coordinator
Contact Address:
Address Type: mailing and physical
Address: 200 I Street SE, 5th Floor
City: Washington
State or Province: DC
Postal Code: 20003
Country: US
Contact Voice Telephone: (202) 727-2277
Contact Facsimile Telephone: (202) 727-5660
Contact Electronic Mail Address: dcgis@dc.gov
Hours: 8:30 am - 5 pm
Data Set Credit: Office of the Chief Technology Officer
Native Data Set Environment: Esri ArcGIS 13.0.3.36057
Data Quality Information:
Lineage:
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: E 911 Street File
Type of Source Media: None
Source Citation Abbreviation: E 911 Street File
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Property Inventory
Type of Source Media: None
Source Citation Abbreviation: Property Inventory
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Owner Points
Type of Source Media: None
Source Citation Abbreviation: Owner Points
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Property Owners
Type of Source Media: None
Source Citation Abbreviation: Property Owners
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: New addresses
Type of Source Media: None
Source Citation Abbreviation: New addresses
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Street Centerline
Type of Source Media: None
Source Citation Abbreviation: Street Centerline
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Health Care Safety Net database
Type of Source Media: None
Source Citation Abbreviation: Health Care Safety Net database
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Registered Voters
Type of Source Media: None
Source Citation Abbreviation: Registered Voters
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Street File
Type of Source Media: None
Source Citation Abbreviation: Street File
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Mayor's Call Center
Type of Source Media: None
Source Citation Abbreviation: Mayor's Call Center
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Businesses
Type of Source Media: None
Source Citation Abbreviation: Businesses
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Drivers Licenses
Type of Source Media: None
Source Citation Abbreviation: Drivers Licenses
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Registered Vehicles
Type of Source Media: None
Source Citation Abbreviation: Registered Vehicles
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Mobile Video Addresses
Type of Source Media: None
Source Citation Abbreviation: Mobile Video Addresses
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: Customer File
Type of Source Media: None
Source Citation Abbreviation: Customer File
Source Contribution: location and attribution
Source Information:
Source Citation:
Citation Information:
Publication Date: 20040101
Title: MPD Addresses
Type of Source Media: None
Source Citation Abbreviation: MPD Addresses
Source Contribution: location and attribution
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 Contact:
Contact Information:
Contact Organization Primary:
Contact Organization: Office of the Chief Technology Officer
Contact Position: GIS Data Coordinator
Contact Address:
Address Type: mailing and physical
Address: 200 I Street SE, 5th Floor
City: Washington
State or Province: DC
Postal Code: 20003
Country: US
Contact Voice Telephone: (202) 727-2277
Contact Facsimile Telephone: (202) 727-5660
Contact Electronic Mail Address: dcgis@dc.gov
Hours: 8:30 am - 5 pm
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 Organization Primary:
Contact Organization: ARCBridge Consulting and Training, Inc
Contact Person: Priti Mathur
Contact Position: President
Contact Address:
Address Type: mailing and physical
Address: 203 Elden Street, Suite#3
City: Herndon
State or Province: Virginia
Postal Code: 20170
Country: US
Contact Voice Telephone: 703-834-6511
Contact Facsimile Telephone: 703-834-6514
Contact Electronic Mail Address: support@arcbridge.com
Hours: 8:00 AM - 6:00 PM M-F
Process Step:
Process Description:
On Friday August 18, 2023, the Office of the Chief Technology Officer updated  the Master Address Repository (MAR) datasets, including address points, points of interest, intersections, blocks, and a new data layer named retired address points.

All datasets have been updated to use the MAR 2.0 schema. The most significant change comes with the ADDRESS_ID unique identifier column which will now be named MAR_ID across all five datasets.
Process Date: 20230818
Process Contact:
Contact Information:
Contact Organization Primary:
Contact Organization: Office of the Chief Technology Officer
Contact Position: GIS Data Coordinator
Contact Address:
Address Type: mailing and physical
Address: 200 I Street SE, 5th Floor
City: Washington
State or Province: DC
Postal Code: 20003
Country: US
Contact Voice Telephone: (202) 727-2277
Contact Facsimile Telephone: (202) 727-5660
Contact Electronic Mail Address: dcgis@dc.gov
Hours: 8:30 am - 5 pm
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: 143545
Entity and Attribute Information:
Detailed Description:
Entity Type:
Entity Type Label: DCGIS.ADDRESSES_PT
Entity Type Definition: Master Address Repository address points.
Entity Type Definition Source: OCTO
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: MAR_ID
Attribute Definition: Unique MAR Identifier. Primary Key.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: ADDRESS
Attribute Definition: Concatenation of ADDRESS_NUMBER & ADDRESS_NUMBER_SUFFIX & STREET_NAME & STREET_TYPE & QUADRANT
Attribute Definition Source: OCTO
Attribute:
Attribute Label: ADDRESS_NUMBER
Attribute Definition: Street number.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: ADDRESS_NUMBER_SUFFIX
Attribute Definition: Street number suffix.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: STREET_NAME
Attribute Definition: Street type.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: METADATA_ID
Attribute Definition: Metadata identifier.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: SQUARE
Attribute Definition: Address location property square.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: SUFFIX
Attribute Definition: Address location property square suffix.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: LOT
Attribute Definition: Address location property lot.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: STATUS
Attribute Definition: Lifecycle status of an address.
Attribute Definition Source: OCTO
Attribute Domain Values:
Enumerated Domain:
Enumerated Domain Value: ACTIVE
Enumerated Domain Value Definition: Addresses for buildings which are standing. The overwhelming majority of addresses have the 'ACTIVE' status.
Enumerated Domain Value Definition Source: OCTO
Attribute Domain Values:
Enumerated Domain:
Enumerated Domain Value: RECOMMENDED
Enumerated Domain Value Definition: Addresses which have been recommended (suggested) by a DC GIS employee for approval by DOB.
Enumerated Domain Value Definition Source: OCTO
Attribute Domain Values:
Enumerated Domain:
Enumerated Domain Value: ASSIGNED
Enumerated Domain Value Definition: Addresses which have been assigned (approved) by DOB, but whose buildings have not yet been constructed.
Enumerated Domain Value Definition Source: OCTO
Attribute Domain Values:
Enumerated Domain:
Enumerated Domain Value: RETIRE
Enumerated Domain Value Definition: 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 Value Definition Source: OCTO
Attribute Domain Values:
Enumerated Domain:
Enumerated Domain Value: TEMPORARY
Enumerated Domain Value Definition: Addresses which will exist for a relatively short period of time. Construction trailers, special event tents may be given this TEMPORARY designation.
Enumerated Domain Value Definition Source: OCTO
Attribute:
Attribute Label: COUNTRY
Attribute Definition: Always will be UNITED STATES.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: X_COORDINATE
Attribute Definition: Using Maryland State Plane NAD 1983 meters coordinate system.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: Y_COORDINATE
Attribute Definition: Using Maryland State Plane NAD 1983 meters coordinate system.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: SSL
Attribute Definition: Address location Square, Suffix, and Lot.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: STREET_TYPE
Attribute Definition: Address location street type.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: ADDRESS_TYPE
Attribute Definition: For locations without an address number the value will be 'PLACE' and for locations with an address number the value will be 'ADDRESS'
Attribute Definition Source: OCTO
Attribute:
Attribute Label: QUADRANT
Attribute Definition: Address location quadrant name.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: ROUTEID
Attribute Definition: From DDOT roads & highways.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: BLOCKKEY
Attribute Definition: From DDOT roads & highways, GUID.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: SUBBLOCKKEY
Attribute Definition: From DDOT roads & highways, GUID.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: CITY
Attribute Definition: Address location city, always will be WASHINGTON.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: STATE
Attribute Definition: Address location state name, always will be DC.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: NATIONAL_GRID
Attribute Definition: National grid coordinates.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: HAS_SSL
Attribute Definition: Has property information.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: HAS_PLACE_NAME
Attribute Definition: Has place name.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: HAS_CONDO
Attribute Definition: Has residential condo unit associated with it.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: HAS_RESIDENTIAL_UNIT
Attribute Definition: Has residential units associated with it.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: STREET_VIEW_URL
Attribute Definition: Web URL to Google Maps Street View.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: RESIDENTIAL_TYPE
Attribute Definition: Residential status.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: PLACEMENT
Attribute Definition: Location of address.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: SSL_ALIGNMENT
Attribute Definition: How well addresses aligns with associated SSL (property).
Attribute Definition Source: OCTO
Attribute:
Attribute Label: BUILDING
Attribute Definition: Is associated with a building?
Attribute Definition Source: OCTO
Attribute:
Attribute Label: WARD
Attribute Definition: Address location current election ward. This is the only geography that is being stored in the database as it is so widely used. Other geographies are available using the MAR 2.0 web service.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: ZIPCODE
Attribute Definition: Address location Zip code.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: SHAPE
Attribute Definition: Shape geometry.
Attribute Definition Source: ESRI
Attribute Domain Values:
Unrepresentable Domain: Coordinates defining the features.
Attribute:
Attribute Label: MULTIPLE_LAND_SSL
Attribute Definition: Multiple Land Square, Suffix, Lot.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: GRID_DIRECTION
Attribute Definition: The grid direction of the address.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: HOUSING_UNIT_COUNT
Attribute Definition: Number of housing units today.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: RESIDENTIAL_UNIT_COUNT
Attribute Definition: Number of secondary unit designations today.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: BEFORE_DATE
Attribute Definition: The address definitely did not exist at this date.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: BEFORE_DATE_SOURCE
Attribute Definition: The source for before date.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: BEGIN_DATE
Attribute Definition: The date the address began.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: BEGIN_DATE_SOURCE
Attribute Definition: The source for the begin date.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: FIRST_KNOWN_DATE
Attribute Definition: If there is not a known begin date, then there could be the earliest known date.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: FIRST_KNOWN_DATE_SOURCE
Attribute Definition: The source for the first known date.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: CREATED_DATE
Attribute Definition: The date the address record was created in the MAR database.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: CREATED_USER
Attribute Definition: Which agency created the record.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: LAST_EDITED_DATE
Attribute Definition: When this address records was last edited by someone.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: LAST_EDITED_USER
Attribute Definition: Which agency last edited the record.
Attribute Definition Source: OCTO
Attribute:
Attribute Label: LATITUDE
Attribute Definition: Latitude of address (in decimal degrees).
Attribute Definition Source: OCTO
Attribute:
Attribute Label: LONGITUDE
Attribute Definition: Longitude of address (in decimal degrees).
Attribute Definition Source: OCTO
Distribution Information:
Distributor:
Contact Information:
Contact Organization Primary:
Contact Organization: Office of the Chief Technology Officer
Contact Position: GIS Data Coordinator
Contact Address:
Address Type: mailing and physical
Address: 200 I Street SE, 5th Floor
City: Washington
State or Province: DC
Postal Code: 20003
Country: US
Contact Voice Telephone: (202) 727-2277
Contact Facsimile Telephone: (202) 727-5660
Contact Electronic Mail Address: dcgis@dc.gov
Hours: 8:30 am - 5 pm
Distribution Liability: See access and use constraints information.
Custom Order Process: DC datasets can be downloaded from "https://opendata.dc.gov".
Metadata Reference Information:
Metadata Date: 20230816
Metadata Contact:
Contact Information:
Contact Organization Primary:
Contact Organization: Office of the Chief Technology Officer
Contact Position: GIS Data Coordinator
Contact Address:
Address Type: mailing and physical
Address: 200 I Street SE, 5th Floor
City: Washington
State or Province: DC
Postal Code: 20003
Country: US
Contact Voice Telephone: (202) 727-2277
Contact Facsimile Telephone: (202) 727-5660
Contact Electronic Mail Address: dcgis@dc.gov
Hours: 8:30 am - 5 pm
Metadata Standard Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata Standard Version: FGDC-STD-001-1998
Metadata Time Convention: local time