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).

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).

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).

The dataset contains location and attributes of traffic controls located at each intersection in the District of Columbia. All traffic poles, pavement markings, traffic cabinets and cameras located within 10 meters of curb face intersections are collected. Poles must support traffic control devices in order to be collected. This includes traffic control signs, traffic signals, traffic arms and cameras. The data set does not include poles supporting only name plate signs and parking enforcement signs.

Traffic Stations. The dataset contains locations and attributes of Permanent Count stations and Weigh In Motion stations, created as part of the District of Columbia, Department of Transportation (DDOT) Street Spatial Database (SSD). A database provided by the District of Columbia, Department of Transportation identified Permanent Count stations.

This special topic poll, fielded January 27-31, 2005, was undertaken to assess public opinion on traffic congestion in the Washington, DC, area. Respondents who commuted in the greater Washington, DC, area were asked about traffic conditions in the region, their primary means of transportation to and from work, the length of their commute, what they liked and disliked most about their commute, and whether they had ever relocated or adjusted their work schedule to improve their commute. Those polled rated the different types of public transportation available in the area, how often they used the Metrorail subway system, and why they did not ride it more often. Views were sought on proposals to expand the Metrorail system and build new highways in the area, sources of funding for transportation projects, and whether measures such as high occupancy vehicle lanes, adjustable tolls, and building new roads were effective in easing traffic congestion. Respondents were also asked about the type of vehicle they drove, how often they traveled by car, how much time they spent driving, and how often driving invoked feelings such as independence, relaxation, and anger. A series of questions asked respondents how often they and others were guilty of behaviors such as speeding or road rage, and whether they engaged in activities such as eating or reading while driving. Additional topics addressed the use of automatic cameras at traffic lights and stop signs and whether existing traffic laws were too tough on teenage drivers. Demographic variables included sex, age, race, household income, education level, and political party affiliation.

The Automated Safety Cameras (ASC) is a division of the District Department of Transportation (DDOT) that uses photo enforcement cameras as a traffic calming measure to enforce traffic laws, and to reduce violations on DC’s streets and most intersections. ATE is currently enforcing Posted Speed Limit (Speed), Stop Sign (Failure to come to a complete STOP), Red-Light (Running Red-Light), Bus Lane, Bus Zone, School Bus Stop-Arm, and Truck Restriction routes.This version of ASC data includes devices with no coordinates and because of that, the data is in table format. Data can be mapped using Lat/Lon or X/Y MD State Plane (Meters) but there will be records with null coordinate values.

The dataset contains location and attributes of traffic controls features located at each intersection in the District of Columbia. All traffic poles, pavement markings, traffic cabinets and cameras located within 10 meters of curb face intersections are collected. Poles must support traffic control devices in order to be collected. This includes traffic control signs, traffic signals, traffic arms and cameras. These traffic contorl devices are part the data sets tables and are related to there particular pole. The data set does not include poles supporting only name plate signs and parking enforcement signs.

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).

The dataset contains location and attributes of traffic controls located at each intersection in the District of Columbia. All traffic poles, pavement markings, traffic cabinets and cameras located within 10 meters of curb face intersections are collected. Poles must support traffic control devices in order to be collected. This includes traffic control signs, traffic signals, traffic arms and cameras. The data set does not include poles supporting only name plate signs and parking enforcement signs.

The accompanying data cover all MPD stops including vehicle, pedestrian, bicycle, and harbor stops for the period from January 1, 2023 – December 31, 2024. A stop may involve a ticket (actual or warning), investigatory stop, protective pat down, search, or arrest. If the final outcome of a stop results in an actual or warning ticket, the ticket serves as the official documentation for the stop. The information provided in the ticket include the subject’s name, race, gender, reason for the stop, and duration. All stops resulting in additional law enforcement actions (e.g., pat down, search, or arrest) are documented in MPD’s Record Management System (RMS). This dataset includes records pulled from both the ticket (District of Columbia Department of Motor Vehicles [DMV]) and RMS sources. Data variables not applicable to a particular stop are indicated as “NULL.” For example, if the stop type (“stop_type” field) is a “ticket stop,” then the fields: “stop_reason_nonticket” and “stop_reason_harbor” will be “NULL.” Each row in the data represents an individual stop of a single person, and that row reveals any and all recorded outcomes of that stop (including information about any actual or warning tickets issued, searches conducted, arrests made, etc.). A single traffic stop may generate multiple tickets, including actual, warning, and/or voided tickets. Additionally, an individual who is stopped and receives a traffic ticket may also be stopped for investigatory purposes, patted down, searched, and/or arrested. If any of these situations occur, the “stop_type” field would be labeled “Ticket and Non-Ticket Stop.” If an individual is searched, MPD differentiates between person and property searches. Please note that the term property in this context refers to a person’s belongings and not a physical building. The “stop_location_block” field represents the block-level location of the stop and/or a street name. The age of the person being stopped is calculated based on the time between the person’s date of birth and the date of the stop. There are certain locations that have a high prevalence of non-ticket stops. These can be attributed to some centralized processing locations. Additionally, there is a time lag for data on some ticket stops as roughly 20 percent of tickets are handwritten. In these instances, the handwritten traffic tickets are delivered by MPD to the DMV, and then entered into data systems by DMV contractors. On August 1, 2021, MPD transitioned to a new version of its current records management system, Mark43 RMS. Beginning January 1, 2023, fields pertaining to the bureau, division, unit, and PSA (if applicable) of the officers involved in events where a stop was conducted were added to the dataset. MPD’s Records Management System (RMS) captures all members associated with the event but cannot isolate which officer (if multiple) conducted the stop itself. Assignments are captured by cross-referencing officers’ CAD ID with MPD’s Timesheet Manager Application. These fields reflect the assignment of the officer issuing the Notice of Infraction (NOIs) and/or the responding officer(s), assisting officer(s), and/or arresting officer(s) (if an investigative stop) as of the end of the two-week pay period for January 1 – June 30, 2023 and as of the date of the stop for July 1, 2023 and forward. The values are comma-separated if multiple officers were listed in the report. For Stop Type = Harbor and Stop Type = Ticket Only, the officer assignment information will be in the NOI_Officer fields. For Stop Type = Ticket and Non-Ticket the officer assignments will be in both NOI Officer (for the officer that issued the NOI) and RMS_Officer fields (for any other officer involved in the event, which may also be the officer who issued the NOI). For Stop Type = Non-Ticket, the officer assignment information will be in the RMS_Officer fields. Null values in officer assignment fields reflect either Reserve Corps members, who’s assignments are not captured in the Timesheet Manager Application, or members who separated from MPD between the time of the stop and the time of the data extraction. Finally, MPD is conducting on-going data audits on all data for thorough and complete information. Figures are subject to change due to delayed reporting, on-going data quality audits, and data improvement processes.

The dataset contains the location and attributes of traffic signals in the District of Columbia. Attributes are aggregated to the controller level (ACISA), where a single controller directs one or more traffic signals at one intersection or clustered intersections. The following attributes of signalized intersections are tracked: leading pedestrian intervals (LPIs), No Turn on Red (NTOR) signage, all-pedestrian phases, bike phases, queue jumps, transit signal priority (TSP), pedestrian recall mode, HAWK/PHB signals, and accessible pedestrian signals (APS).This data is updated periodically and may not be current at the time of viewing. More information on safety features implemented at traffic signals can be found here: https://visionzero.dc.gov/pages/engineering.

DDOT is committed to making District streets safer for all roadway users while providing multimodal mobility and access for residents, visitors, and commercial users. A combination of traffic control devices and traffic calming measures can help meet both goals. DDOT has a full portfolio of proactive, data-based safety efforts, which can be reviewed at https://visionzero.dc.gov/pages/engineering. In addition, our Traffic Safety Input (TSI) program provides a mechanism for DDOT to hear from residents on roadway segments and intersections where users have safety concerns.

Crashes on the roadway blocks network of Washington, DC maintained by the District Department of Transportation (DDOT). In addition to locations, a related table consisting of crash details is available for each crash. This table provides some anonymized information about each of the persons involved in the crash (linked by CRASHID). These crash data are derived from the Metropolitan Police Department's (MPD) crash data management system (COBALT) and represent DDOT's attempt to summarize some of the most requested elements of the crash data. Further, DDOT has attempted to enhance this summary by locating each crash location along the DDOT roadway block line, providing a number of location references for each crash. In the event that location data is missing or incomplete for a crash, it is unable to be published within this dataset. Location points with some basic summary statistics,The DC ward the crash occurredSummary totals for: injuries (minor, major, fatal) by type (pedestrian, bicycle, car), mode of travel involved (pedestrian, bicycle, car), impaired participants (pedestrian, bicyclist, car passengers)If speeding was involvedNearest intersecting street nameDistance from nearest intersectionCardinal direction from the intersectionRead more at https://ddotwiki.atlassian.net/wiki/spaces/GIS0225/pages/2053603429/Crash+Data. Questions on the contents of these layers should be emailed to Metropolitan Police Department or the DDOT Traffic Safety Division. Questions regarding the Open Data DC can be sent to @OpenDataDC

Traffic Barrier. The dataset contains polylines representing planimetric barriers, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO). These features were originally captured in 2015 and updated in 2017. The following planimetric layers were updated: - Barrier Lines- Building Polygons- Bridge and Tunnel Polygons- Curb Lines- Grate Points- Horizontal and Vertical Control Points- Hydrography Lines- Obscured Area Polygons- Railroad Lines- Recreational Areas- Road, Parking, and Driveway Polygons- Sidewalk and Stair Polygons- Swimming Pools- Water Polygons

The Fatal and Injury Crashes Dashboard can be used by the public to locate crashes that result in an injury or fatality. Adjust the Mode, Severity and Date filters to refine the results in the map. All charts will update to reflect the collisions in current map extent. Data are available from 2017-present. Data are updated every Friday.

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).

Automated Safety Cameras (ASC) is a division of the District Department of Transportation (DDOT) that uses photo enforcement cameras as a traffic calming measure to enforce traffic laws, and to reduce violations at DC's streets and intersections. This dataset contains a summary of the warnings and violations issued by month and year by different ASC enforcement types, including Red Light, Speed, Truck Restriction, and Stop Sign violations.