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.

The dataset contains locations and attributes of retired 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). There are over 40,000 retired addresses. These once existed, but no longer do. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the AddressPt is called ADDRESSES_PT and its features additional useful information such as placement location, created date, last edited date, begin date and more.

This Address Standards document has been developed to describe the addressing standards used for the Master Address Repository (MAR). The MAR is DC Government’s official address database and is widely used across the City of Washington, DC. The OCTO Data Team which is part of the Office of the Chief Technology Officer (OCTO), is responsible for maintaining the MAR.

The relationship between a property and an address is many-to-many. In DC a SSL (Square, Suffix, Lot) is used to identify a property. One SSL can have multiple addresses located on it. This often includes garden-style apartment complexes as well as corner buildings with separate addresses facing each adjacent street. One address can also sit upon multiple SSLs. One single family residence can sit upon multiple lots. The cross reference table contains the many-to-many relationship between address IDs and SSLs. [A small percentage of addresses do not have an associated SSL (such as metro entrances or many addresses on Federal property.] Use this cross reference table to relate the District's address points in the Master Address Repository (MAR) with the SSLs and vice versa.

The Master Address Repository (MAR) Viewer is part of the District's location services documented in Addressing in DC. It makes locating addresses or place name as easy as possible by employing spell check and lists of street names or property aliases. Find the Ward a property falls in, or its police district, and more details.

Address Residential Units. This dataset contains residential units and attributes of Address points, created as part of the Master Address Repository (MAR) for the D.C. Residential units can be condominiums or also apartments. Office of the Chief Technology Officer (OCTO) and DC Department of Consumer and Regulatory Affairs . 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 https://opendata.dc.gov/pages/addressing-in-dc.

An address anomaly is an address whose location is illogical. In other words, the address does not follow the normal rules of the District of Columbia’s (DC) addressing grid system. There are different types of anomalies.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Range Features shapefile contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. This shapefile contains a record for each address range to street name combination. Address ranges associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that this shapefile includes all unsuppressed address ranges compared to the All Lines shapefile (edges.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefiles contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line shapefiles are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

The District of Columbia government uses the Master Address Repository (MAR) to implement intelligent search functionality for finding and verifying addresses, place names, blocks and intersections.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Range/Feature Name Relationship File contains a record for each address range/linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Range Relationship File (addr.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute which can be used to link to the Feature Names Relationship File (featnames.dbf).

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Ranges Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

Context

OpenAddresses's goal is to connect the digital and physical worlds by sharing geographic coordinates, street names, house numbers and postal codes.

Content

This dataset contains one datafile for each state in the U.S. South region (although some are arguably not in the South).

States included in this dataset:

• Alabama - al.csv
• Arkansas - ar.csv
• Washington D.C. - dc.csv
• Delaware - de.csv
• Florida - fl.csv
• Georgia - ga.csv
• Kentucky - ky.csv
• Louisiana - la.csv
• Maryland - md.csv
• Mississippi - ms.csv
• North Carolina - nc.csv
• Oklahoma - ok.csv
• South carolina - sc.csv
• Tennessee - tn.csv
• Texas - tx.csv
• Virginia - va.csv
• West Virginia - wv.csv

Field descriptions:

• LON - Longitude
• LAT - Latitude
• NUMBER - Street number
• STREET - Street name
• UNIT - Unit or apartment number
• CITY - City name
• DISTRICT - ?
• REGION - ?
• POSTCODE - Postcode or zipcode
• ID - ?
• HASH - ?

Acknowledgements

Data collected around 2017-07-25 by OpenAddresses (http://openaddresses.io).

Address data is essential infrastructure. Street names, house numbers and postal codes, when combined with geographic coordinates, are the hub that connects digital to physical places.

Data licenses can be found in LICENSE.txt.

Data source information can be found at https://github.com/openaddresses/openaddresses/tree/9ea72b079aaff7d322349e4b812eb43eb94d6d93/sources

Inspiration

Use this dataset to create maps in conjunction with other datasets for crime or weather

Also known as place names. The dataset contains locations and attributes of address alias points, created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and participating DC government agencies. It contains address alias names in the District of Columbia which are typically placed on buildings. These alias names represent named features such as: - Schools - Federal Buildings - Military Installations - Hospitals - Museums - Monuments - University Structures - Fire and Police Stations - Libraries - Metro Facilities - Historical Landmarks - Recreation Centers - Mile Markers - Marinas and more. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the AddressAliasPt is called PLACE_NAMES_PT and features additional useful information such as created date, last edited date, begin date, and more.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

DC Atlas Pro is a mapping tool that contains hundreds of different data layers, organized by category. DC Atlas Pro is the updated version of DC Atlas Plus, both of which were created by OCTO GIS, as an easy way to view geographic information about the District of Columbia. This new and improved version of DC Atlas allows you to search for addresses, intersections, or place names; analyze and identify data; and create maps that you can share. For detailed instructions on how to use DC Atlas Pro, please visit the Get Help / How to Use This Map section of the application.

The dataset contains locations and attributes of blocks, created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and participating DC government agencies. The blocks used street centerlines information from DDOT. Blocks include named alleys in DC (such as 'WALTER ALLEY NE'). A block represents a street segment which usually has two bordering streets. The coordinates for the blocks are located at the midpoint of the street segment. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the BlocksPt is called BLOCKS_PT and is primarily based off of street data from DC Department of Transportation's Roads & Highways database, it also features additional useful information such as created date, last edited date, begin date, and more.

The MAR Web Geocoder is a web browser-based tool for geocoding locations, typically addresses, in Washington, DC. It is developed by the Office of Chief Technology Officer (OCTO) and can input Excel or CSV files to output an Excel file. Geocoding is the process of assigning a location in the form of geographic coordinates (often expressed as latitude and longitude) to spreadsheet data. This is done by comparing the descriptive geographic data to known geographic locations such as addresses, blocks, intersections, or place names.

District addresses for the District Land. The dataset contains of addresses for the District land (Owned, Operated, and Maintained), created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Databases researched by the DC Office of the Chief Technology Officer (OCTO) identified DC Agency locations and DC GIS staff geo-processed the data.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Range Relationship File contains the attributes of each address range. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. The address ranges in the TIGER/Line files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines shapefile (edges.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (edges.shp). The TIGER/Line files contain potential address ranges, not individual addresses.