2012 Wards. The dataset contains polygons representing boundaries of District of Columbia 2012 election wards, 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. The DC Office of Planning provided the boundaries to the DC GIS program.

These data represent Wards 2012 in Washington, DC. Urban tree canopy (UTC) and possible planting area (PPA) metrics have been calculated for Wards within the study area. UTC results provided in vector format with attribute fields (area/percent metrics/percent change metrics) for each land cover class and UTC type (UTC, PPA, Unsuitable UTC, UTC Change).

2012 Wards. The dataset contains polygons representing boundaries of District of Columbia 2012 election wards, 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. The DC Office of Planning provided the boundaries to the DC GIS program.

Generalized Policy from the Comprehensive Plan Amendment Act of 2010, effective April 8, 2011.This data set is part of the Comprehensive Plan of the District of Columbia. It categorizes how different parts of the District may change by 2025. It highlights areas where more detailed Comprehensive Plan policies have been provided to manage this change. These policies may generally be found in the ten Area Elements. This dataset should be used to guide land use decision-making in conjunction with the Comprehensive Plan text, the Future Land Use Map, and other Comprehensive Plan maps. Boundaries within the dataset are to be interpreted in conjunction with these other resources in addition to the information shown here.

Household type, Education, Disability, Language, Computer/Internet Use, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: Ward 2012. Current Vintage: 2015-2019. ACS Table(s): DP02. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: December 18, 2019. National Figures: data.census.gov. The United States Census Bureau's American Community Survey (ACS): About the Survey, Geography & ACS, Technical Documentation, News & Updates. This ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2010 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

Voting Precincts 2012. The dataset contains polygons representing District of Columbia voting precinct boundaries. Precincts were changed based on the ward redistricting following the 2010 census. Precincts were established by the DC Board of Elections and Ethics (DC BOEE) and 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. All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.

Household type, Education, Disability, Language, Computer/Internet Use, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: 2012 Wards (State Legislative Districts [Upper Chamber]). Current Vintage: 2017-2021. ACS Table(s): DP02. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: December 12, 2022. National Figures: data.census.gov. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables. Data Processing Notes: This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

Data provided here are from the DC's 311 service request center. They represent all service requests such as abandoned automobiles, parking meter repair and bulk trash pickup. Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at https://311.dc.gov, electronic and US mail service or via other methods of communication. The Office of Unified Communications (OUC) oversees the designated call center for all 311 calls and for all District 911 calls. Please also visit the DC 311 Service Request Map which allows the public to see service requests in the last 30 days. Users can view requests by Ward within charts. Just set the area filter to select service requests. Click on a service request to view details.

The National Transportation Atlas Databases 2014 (NTAD2014) is a set of nationwide geographic datasets of transportation facilities, transportation networks, associated infrastructure and other political and administrative entities. These datasets include spatial information for transportation modal networks and intermodal terminals, as well as the re¬lated attribute information for these features. This data supports research, analysis, and decision-making across all transportation modes. It is most useful at the national level, but has major applications at regional, state and local scales throughout the transportation community. The data used to compile NTAD2014 was provided by our partners within the United States Department of Transportation (USDOT) and by other agencies throughout the United States Federal Government. These contributors are the actual data stewards and are ultimately responsible for the maintenance and accuracy of their data. This data was sourced from the information contained in the Census Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The content of the MAF/TIGER database is undergoing continuous census data updates and is made available to the public through a variety of TIGER/Line® shapefiles.

Occupancy status, Units, Rooms, Year built, Owner/Renter (Tenure), Mortgage/Rent costs, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: 2012 Wards (State Legislative Districts [Upper Chamber]). Current Vintage: 2017-2021 ACS Table(s): DP04. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: December 12, 2022. National Figures: data.census.gov. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables. Data Processing Notes: This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

The dataset contains locations and attributes of building construction and alteration permits applied for and approved by the District of Columbia Department of Buildings. These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC.

Traffic volume of Roadway Blocks. The dataset contains traffic volume data, created as part of the District of Columbia, Department of Transportation (DDOT) Roads and Highways database. A database provided by the District of Columbia, Department of Transportation identified traffic volume. Count data is collected (both direction) at pre-selected locations on Highway Performance Monitoring System (HPMS) Sections on a three-year cycle. These counts are converted to Annual Average Daily Traffic (AADT).

Moving citation locations in the District of Columbia. The data contained in this layer pertain to moving violations issued by the District of Columbia's Metropolitan Police Department (MPD) and partner agencies with the authority. For example, DC's enforcement camera program cites speeders, blocking the box, and other moving offenses. Moving violation locations are summarized ticket counts based on time of day, week of year, year, and category of violation. Questions about the contents of the data should be directed to the Metropolitan Police Department (MPD). Process note: data was originally downloaded from the District Department of Motor Vehicle's eTIMS meter work order management system. Data was exported where the Office of the Chief Technology Officer (OCTO) geocoded citation data to the street segment level. Data was then visualized using the street segment centroid coordinates.

Advisory Neighborhood Commissions (ANCs) are collections of Single Member Districts (SMDs). ANCs allow input from an advisory board made up of the residents of the neighborhoods directly affected by government action. The ANCs are the body of government with the closest official ties to the people in a neighborhood. ANCs present their positions and recommendations on issues to various District government agencies, the Executive Branch, and the Council. They also present testimony to independent agencies, boards and commissions, usually under rules of procedure specific to those entities. By law, the ANCs may also present their positions to Federal agencies. This data set reflects the boundaries approved by the DC Council in May, 2012, for official 2013 ANCs. ANC's consider a wide range of policies and programs affecting their neighborhoods. These include traffic, parking, recreation, street improvements, liquor licenses, zoning, economic development, police protection, sanitation and trash collection, and the District's annual budget. No public policy area is excluded from the purview of the Advisory Neighborhood Commissions. The intent of the ANC legislation is to ensure input from an advisory board made up of the residents of the neighborhoods directly affected by government action. The ANCs are the body of government with the closest official ties to the people in a neighborhood. ANCs present their positions and recommendations on issues to various District government agencies, the Executive Branch, and the Council. They also present testimony to independent agencies, boards and commissions, usually under rules of procedure specific to those entities. By law, the ANCs may also present their positions to Federal agencies.

The Vision Zero data contained in this layer pertain to moving violations issued by the District of Columbia's Metropolitan Police Department (MPD) and partner agencies with the authority to do so. For example, the District Department of Transportation's (DDOT) traffic control officers who prevent congestion through enforcement and control at intersections throughout the District. Locations of moving violations are identified from a database provided by the District Department of Motor Vehicles (DMV).The data is summarized by ticket counts based on time of day, week of year, year, and category of violation. The summary form was created as a series of aggregated street segment data, in order to view spatial patterns on a weekly basis. This is a temporal crosstab of violation types (defined below) by week and time of day (ranges defined below).Users are able to query by week to get a DC-wide yearly and weekly perspective on over 40 different combinations of violations. Create interesting street segment heat maps which can get quite specific to identify patterns and answer questions. For example, where are the majority of Unsafe Operator moving violations in the AM Rush of 2012? These data will give up to 52 distinct street segments of information – one for each week of the year.Field Definitions:Identification Weeknumber – Week of Year, based on a Sunday start of the week StreetSeg – Street Segment ID, corresponds to the DDOT street centerline ‘StreetSegID’ field Registered Name – Street nameStreetType – Type of Street (Road, Ave, etc)Quad – DC Quadrant FromAddLeft – Unit number start (for approximating this segment’s block) ToAddLeft – Unit number end (for approximating this segment’s blockMovingLow Speeding (Under 20mph) - speed violations under 20mphHigh Speeding (above 20mph) - speed violations over 20 mph including reckless drivingUnsafe Driving -violations for driving maneuvers unsafe to traffic Unsafe Vehicle - violations for vehicle characteristics unsafe to traffic Unsafe Operator- violations for operator (driver) characteristics unsafe to trafficOther- miscellaneous violationsImportant Notes: Records which could not be associated to a street centerline segment (StreetSeg) were excluded from these summariesRecords which do not have a time of day associated with the violation were excluded from these summaries.

The dataset contains a subset of locations and attributes of incidents reported in the ASAP (Analytical Services Application) crime report database by the District of Columbia Metropolitan Police Department (MPD). Visit crimecards.dc.gov for more information. This data is shared via an automated process where addresses are geocoded to the District's Master Address Repository and assigned to the appropriate street block. Block locations for some crime points could not be automatically assigned resulting in 0,0 for x,y coordinates. These can be interactively assigned using the MAR Geocoder.On February 1 2020, the methodology of geography assignments of crime data was modified to increase accuracy. From January 1 2020 going forward, all crime data will have Ward, ANC, SMD, BID, Neighborhood Cluster, Voting Precinct, Block Group and Census Tract values calculated prior to, rather than after, anonymization to the block level. This change impacts approximately one percent of Ward assignments.