Name: Department of Youth Rehabilitation Facilities
Display Field: NAME
Type: Feature Layer
Geometry Type: esriGeometryPoint
Description: The dataset contains point locations for sites identified by the DYRS Management and Real Estate, 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. These do not contain group homes under contract with DYRS.
Copyright Text: DC Department of Youth Rehabilitation Services
Description: Transfer Points. The dataset contains locations and attributes of transfer points, 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 Street Lights
Copyright Text: District of Columbia, Department of Transportation. Operational Support and Applied Technology (OSAT) - Spatial Data Systems.
Description: FEMS Engine Local Alarm Districts locations. The dataset contains locations and attributes of Engine Local Alarm Districts, 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. Written documentation provided by FEMS identified Engine Local Alarm Districts locations. The dataset was created using the Street Center Line dataset as reference and snap base. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.Updated by FEMS May 2019.
Description: FEMS Battalion Alarm Districts locations. The dataset contains locations and attributes of Battalion Alarm Districts, 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. Written documentation provided by FEMS identified Engine Local Alarm Districts locations. The dataset was created using the Street Center Line dataset as reference and snap base. Battalion Alarm Districts were aggregated from Engine Local Alarm Districts
Copyright Text: Fire and Emergency Medical Services
Description: This dataset contains points for fire stations that were initially identified from DC Fire and EMS Department records and heads-up digitized from 2002 orthophotographs, and have been updated based on current conditions.
Copyright Text: Fire and Emergency Medical Services
Description: Regional Evacuation Routes. This dataset contains contains points representing locations of Regional Evacuation Routes, 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. Files provided by the District Department of Transportation contained DC, beltway, and regional evacuation routes. OCTO merged these layers together to form one layer. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Copyright Text: DC Homeland Security and Emergency Management Agency
Description: Metropolitan Police Department (MPD) Police Districts. The dataset contains polygons representing of MPD Districts, 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. Police jurisdictions were initially created selecting street arcs from the planimetric street centerlines and street polygons, water polygons, real property boundaries and District of Columbia boundaries.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, economic development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019.On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.
Description: The dataset contains polygons representing of MPD Police Sectors, 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. In 2017 the Metropolitan Police Department formed an additional operational geographic layer called Sector. The Sector model brings additional management accountability to districts and allows for faster dispatch, lower response times, and improved service to the community. Sectors are made up of multiple Police Service Areas (PSAs) and are headed by a Captain. Please note that PSA is still an active operational model used by MPD; Sector is an additional layer between the PSA and District levels.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, economic development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019.On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.
Description: Metropolitan Police Department (MPD) Police Service Areas (PSA). The dataset contains polygons representing of MPD PSA, 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. Police jurisdictions were initially created selecting street arcs from the planimetric street centerlines and street polygons, water polygons, real property boundaries and District of Columbia boundaries.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, economic development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019. On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.
Description: This dataset contains point locations for all publicly identified sites and office locations including headquarters, station, field office and investigative unit locations. This dataset was created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO), MPD and participating D.C. government agencies. Facilities and offices were obtained from MPD's Office of Corporate Communications, through interviews with MPD's Criminal Intelligence, and Tactical Crime Analysis Unit and through site surveys conducted by DC GIS staff.
Description: Regional Streets beyond DC. This dataset contains contains lines representing locations of Regional Streets beyond DC, 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. These locations were identified from public records and heads-up digitized from the 1995 orthophotographs. METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.
Copyright Text: DC Emergency Management Agency (EMA)
Description: The dataset contains locations for cooling centers operated during the summers in Washington, DC. They are typically activated during heat advisories and updated yearly. It is shared 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.
Description: Area boundaries for the MPD Summer Crime Initiative in 2019. The District of Columbia Metropolitan Police Department (MPD) and other partner agencies have identified these areas for improvement in social and public safety resources.
Description: 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
Copyright Text: District Department of Transportation
Description: Points in this layer represent the locations of Capital Area Food Bank (CAFB) programs and public partners in the DMV (DC, Maryland, and Virginia). Data were compiled by the CAFB through internal tracking, and the layer was shared with the DC government as a courtesy. Sensitive locations were removed from the layer, prior to CAFB sharing it with the DC government, for privacy reasons.The layer was shared with the Office of Planning's Food Policy division in May 2016 and is based on 2015 data. The Food Policy Division conducts research, engages with residents, and collaborates with other DC agencies to create a more just, healthy, and sustainable food system in the District. Check dcfoodpolicy.org for more information.
Description: This data represents all ShotSpotter incidents that were classified as “Probable Gunfire”, “Single_Gunshot”, or “Multiple_Gunshots” occurring within one of the six coverage areas defined below since January 1, 2014. The Department plans to continue to release this data with quarterly updates. Classifications are assigned by ShotSpotter and represent their assessment of what kind of impulse noise occurred. Some impulses initially dismissed as non-gunfire are manually audited and resubmitted to the dataset after ground truth analysis. MPD began implementing the ShotSpotter system in 2006 and has added sensors and upgraded components of the system at various times. ShotSpotter has also enhanced their ability to distinguish gunshots from other impulse noises. For example, the number of impulse noises coded as gunshots during Independence Day celebrations have significantly decreased over the past four years. ShotSpotter does not provide coverage for the entire District of Columbia. Official coverage areas are designed by ShotSpotter in conjunction with MPD, to target high population density areas with frequent sounds of gunshots incidents. A ShotSpotter incident may involve one gunshot or multiple gunshots depending on the time elapsed between each shot. Each incident is given a serial number ID when it occurs. The Latitude and Longitude of the incidents are rounded to three decimal places due to privacy concerns. This roughly corresponds to a 100 meter resolution.
Description: Metropolitan Police Department (MPD) Police Service Areas (PSA). The dataset contains polygons representing of MPD PSA, 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. Police jurisdictions were initially created selecting street arcs from the planimetric street centerlines and street polygons, water polygons, real property boundaries and District of Columbia boundaries.2019 Boundary Changes:Periodically, MPD conducts a comprehensive assessment of our patrol boundaries to ensure optimal operations. This effort considers current workload, anticipated population growth, economic development, and community needs. The overarching goals for the 2019 realignment effort included: optimal availability of police resources, officer safety and wellness, and efficient delivery of police services. These changes took effect on 01/10/2019. On 03/27/2019, this boundary was modified to adjust dispatching of North Capitol Street’s northwest access roads to be more operationally efficient.
Description: 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.ASC 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.
Copyright Text: District Department of Transportation
Description: It is important for the community to understand what is – and is not – a hate crime. First and foremost, the incident must be a crime. Although that may seem obvious, most speech is not a hate crime, regardless of how offensive it may be. In addition, a hate crime is not a crime, but a possible motive for a crime.It can be difficult to establish a motive for a crime. Therefore, the classification as a hate crime is subject to change as an investigation proceeds – even as prosecutors continue an investigation. If a person is found guilty of a hate crime, the court may fine the offender up to 1½ times the maximum fine and imprison him or her for up to 1½ times the maximum term authorized for the underlying crime.While the District strives to reduce crime for all residents of and visitors to the city, hate crimes can make a particular community feel vulnerable and more fearful. This is unacceptable, and is the reason everyone must work together not just to address allegations of hate crimes, but also to proactively educate the public about hate crimes.The figures in this data align with DC Official Code 22-3700. Because the DC statute differs from the FBI Uniform Crime Reporting (UCR) and National Incident-Based Reporting System (NIBRS) definitions, these figures may be higher than those reported to the FBI. Each month, an MPD team reviews crimes that have been identified as potentially motivated by hate/bias to determine whether there is sufficient information to support that designation. The data in this document is current through the end of the most recent month. The hate crimes dataset is not an official MPD database of record and may not match details in records pulled from the official Records Management System (RMS). Unknown or blank values in the Targeted Group field may be present prior to 2016 data. As of January 2022, an offense with multiple bias categories would be reflected as such. Data is updated on the 15th of every month.
Description: In July 2019, the Metropolitan Police Department (MPD) implemented new data collection methods that enabled officers to collect more comprehensive information about each police stop in an aggregated manner. More specifically, these changes have allowed for more detailed data collection on stops, protective pat down (PPDs), searches, and arrests. (For a complete list of terms, see the glossary on page 2.) These changes support data collection requirements in the Neighborhood Engagement Achieves Results Amendment Act of 2016 (NEAR Act).The accompanying data cover all MPD stops including vehicle, pedestrian, bicycle, and harbor stops for the period from July 22, 2019 to December 31, 2019. A stop may involve a ticket (actual or warning), investigatory stop, protective pat down, search, or arrest.
Description: Whenever a forcible stop or a frisk is conducted, MPD officers are required to submit an incident report which includes specific factors which supported the determination that reasonable suspicion was present to use the minimum amount of force necessary to stop or frisk a person. Although the primary purpose of the stop and frisk incident report is to collect information on forcible stops or frisks, officers frequently use this report to document non-forcible stops. Thus, the incident type “stop and frisk” may include non-forcible stops, forcible stops, and frisks. Each row of information in the attached dataset represents an individual associated with a stop and frisk incident. Not all individuals of an incident may have been stopped or frisked. For example, two individuals may have been associated with a stop or frisk incident but only one person may have been stopped. The other person may include a witness. Moreover, two individuals may have been stopped where only one person is frisked. A “stop” is a temporary detention of a person for the purpose of determining whether probable cause exists to arrest a person. A “frisk” is a limited protective search on a person to determine the presence of concealed weapons and/or dangerous instruments.
https://mpdc.dc.gov/node/1310236
Description: When a non-forcible stop is conducted, MPD officers may document it on a field contact report instead of an incident report. A field contact report is also used to record general contact with a citizen. This dataset only captures the field contact type where the officer has indicated it is a stop by classifying it as a “pedestrian stop”, “vehicle stop”, or “bicycle stop.”A “stop” is a temporary detention of a person for the purpose of determining whether probable cause exists to arrest a person. A “frisk” is a limited protective search on a person to determine the presence of concealed weapons and/or dangerous instruments.
The Metropolitan Police Department (MPD) upgraded its records management system in 2012 and 2015. During each implementation, data collection processes may have changed. For example:
- The date field for field contact reports prior to January 2, 2012 was not migrated to the current record management system. As a result, tens of thousands of records carry a date of January 1, 2012. Therefore, MPD is unable to provide field contact data prior to January 2, 2012.
- With the implementation of the most recent RMS in 2015, MPD began collecting race and ethnicity data according to the United States Census Bureau standards (https://www.census.gov/topics/population/race/about.html). As a result, Hispanic, which was previously categorized under the Race field, is currently captured under Ethnicity.
Race and ethnicity data are based on officer observation, which may or may not be accurate. Individuals are not required to provide their date of birth and/or age; therefore, there may be blank and/or unknown ages.
https://mpdc.dc.gov/node/1310236
Description: In July 2019, the Metropolitan Police Department (MPD) implemented new data collection methods that enabled officers to collect more comprehensive information about each police stop in an aggregated manner. More specifically, these changes have allowed for more detailed data collection on stops, protective pat down (PPDs), searches, and arrests. (For a complete list of terms, see the glossary on page 2.) These changes support data collection requirements in the Neighborhood Engagement Achieves Results Amendment Act of 2016 (NEAR Act).The accompanying data cover all MPD stops including vehicle, pedestrian, bicycle, and harbor stops for the period from July 22, 2019 to December 31, 2019. A stop may involve a ticket (actual or warning), investigatory stop, protective pat down, search, or arrest.
Description: This dataset contains all felony counts sentenced from 2010 onward and includes offender demographic information such as gender, race, and age, as well as sentencing information such as the offense, offense severity group, and the type and length of sentence imposed. The dataset is updated annually. Individuals interested in more extensive data sets may contact the Sentencing Commission via email at sccrc@dc.gov.
Description: In the District of Columbia, the laws related to the recreational use and possession of marijuana have changed at two milestones: the effective dates of the Marijuana Possession Decriminalization Amendment Act of 2014 on July 17, 2014, and of Initiative 71 on February 26, 2015 (https://mpdc.dc.gov/marijuana).
Description: This data includes adult arrests made by the Metropolitan Police Department (MPD). The information within this report pertains to reports entered into MPD’s Record Management System (Cobalt) whereby an arrest occurred. Totals are based on the most serious arrest charge (i.e., each row denotes one arrest, not one charge), and one person may be booked on more than one arrest charge.
Description: OVSJG Grant Recipients. Each year, OVSJG awards nonprofit organizations and government agencies grants to fund a wide variety of victim service, truancy reduction, juvenile justice, and reentry programs.