This data set contains only Weekly Activity Reports (WAR) that were submitted via eWell since April 2004.

Abstract (en): Version 3 release notes: Add data for 2016.Order rows by year (descending) and ORI.Removed data from Chattahoochee Hills (ORI = "GA06059") from 2016 data. In 2016, that agency reported about 28 times as many vehicle arsons as their population (Total mobile arsons = , population = 2754.Version 2 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The Arson data is an FBI data set that is part of the annual Uniform Crime Reporting (UCR) Program data. This data contains information about arsons reported in the United States. The data sets here combine all data from the years 2001-2015 into a single file. The year 2006 is not available. Please note that the files are quite large and may take some time to open.The raw data that I downloaded from NACJD has monthly data. The data here is yearly and was created by adding all the monthly columns together for each variable. The format is similar to the UCR's Offenses Known data where each row is an agency-year and columns are crime counts for various crimes. Instead of various crimes, here it is the type of arson such as arson of a single occupancy building, a storage building, or a motor vehicle. Like the Offenses Known data it has the number of reports found to have actually occurred ("actual"), be unfounded, cleared, and cleared with an arrestee under the age of 18. There are also columns for the total number of arsons reported to police, total number of arsons of uninhabited buildings, and estimated damage from the arson.About 30% of the rows were from agencies that did not report any months of data. I removed these rows to reduce file size. I did not make any changes to the data other than the following: Change some column names, reorder columns, and spell out the month in the months reported variable (originally some months were abbreviated). Years 2001 and 2002 had "1" and "2" as their reported years which I changed to "2001" and "2002". I deleted the agency of Oneida, New York (ORI = NY03200), since they had multiple years that reported single arsons costing over $700 million. I also added state, county, and place FIPS code from the LEAIC (crosswalk).When an arson is determined to be unfounded the estimated damage from that arson is added as negative to zero out the previously reported estimated damages. This occasionally leads to some agencies have negative values for arson damages. You should be cautious when using the estimated damage columns as some values are quite large. Negative values in other columns are also due to adjustments (zeroing out the error) from month to month. Negative values are not meant to be NA in this data set. All the data was downloaded from NACJD as ASCII+SPSS Setup files and read into R using the package asciiSetupReader. All work to clean the data and save it in various file formats was also done in R. For the R code used to clean this data, see here. https://github.com/jacobkap/crime_data. The zip file contains the data in the following formats and a codebook: .csv - Microsoft Excel.dta - Stata.sav - SPSS.rda - RIf you have any questions, comments, or suggestions please contact me at jkkaplan6@gmail.com. Smallest Geographic Unit: Police agency

Updated daily postings on Montgomery County’s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions – of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by “EJustice”, a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims’ privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation.

dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect:

-Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law.]

Update Frequency: Daily

Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been

Code Enforcement Violations that were reported to the Development Services Department prior to January 2018 and were and closed out between 2015 and 2018. For more recent data on code enforcement violations, please visit OpenDSD.

These data provide incident-level information on criminal homicides including date, location, circumstances, and method of offense, as well as demographic characteristics of victims and perpetrators and the relationship between the two. For this dataset, the original Uniform Crime Reports data were completely restructured into a nested, or hierarchical, form with repeating records. Specifically, the file contains one record for each agency per year (record type "A"), nested within which is one record per incident (record type "I"). Victim records (record type "V") are in turn nested within incident records, and offender data are repeated for all offenders on each victim record. Part 3, ORI List, contains Originating Agency Identifier (ORI) codes used by the FBI and the corresponding agency name.

Abstract (en): The UNIFORM CRIME REPORTING PROGRAM DATA: PROPERTY STOLEN AND RECOVERED, 2014 file (also known as the Supplement to Return A) is collected at the agency level and includes detailed monthly data on the nature of crime and the value and type of property stolen and recovered incident to each crime. The Return A Supplement requires that a value be established for property stolen and recovered in each Crime Index category except aggravated assault. It is designed to record the value of property stolen and recovered in the following eleven classifications: Currency/notes, Jewelry and Precious Metals, Clothing and Furs, Locally Stolen Motor Vehicles, Office Equipment, Televisions/Radios, Firearms, Household Goods, Consumable Goods, Livestock, and Miscellaneous. The determination of the value of property stolen is an obligation of the investigating officer, and such information is essential to assure the completeness of a law enforcement investigative report on stolen property. The data were originally assembled by the Federal Bureau of Investigation (FBI) from reports submitted by agencies participating in the UCR. The ICPSR file was processed from Return A Supplement files provided by the FBI. ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed consistency checks.; Checked for undocumented or out-of-range codes.. Property crimes reported by law enforcement agencies in the United States. self-enumerated questionnaireStarting with the year 1998, each of the four parts of the UCR data collection archived by ICPSR is released as a separate study under its own study number. The Property Stolen and Recovered data for the years 1975-1997 can be found in UNIFORM CRIME REPORTING PROGRAM DATA: 1975-1997 (ICPSR 9028).

description: Law Enforcement Locations in Kansas Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS is deleting these locations as we become aware of them, but some probably still exist in this dataset. Personal homes, administrative offices and temporary locations are intended to be excluded from this dataset, but a few may be included. Personal homes of constables may exist due to fact that many constables work out of their home. FBI entites are intended to be excluded from this dataset, but a few may be included. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2006/06/27 and the newest record dates from 2008/03/06; abstract: Law Enforcement Locations in Kansas Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS is deleting these locations as we become aware of them, but some probably still exist in this dataset. Personal homes, administrative offices and temporary locations are intended to be excluded from this dataset, but a few may be included. Personal homes of constables may exist due to fact that many constables work out of their home. FBI entites are intended to be excluded from this dataset, but a few may be included. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2006/06/27 and the newest record dates from 2008/03/06

Since 1930, the Federal Bureau of Investigation has compiled the Uniform Crime Reports (UCR) to serve as periodic nationwide assessments of reported crimes not available elsewhere in the criminal justice system. Law enforcement agencies contribute reports either directly or through their state reporting programs. Each year, summary data are reported in four types of files: (1) Offenses Known and Clearances by Arrest, (2) Property Stolen and Recovered, (3) Supplementary Homicide Reports (SHR), and (4) Police Employee (LEOKA) Data. The Offenses Known and Clearances by Arrest data files include monthly data on the number of Crime Index offenses reported and the number of offenses cleared by arrest or other means. The counts include all reports of Index Crimes (excluding arson) received from victims, officers who discovered infractions, or other sources.

Revision Note (February 10, 2025): The data pipeline for "Law Enforcement Dispatched Calls for Service: Real-Time" has been updated. A spelling error with the column "priority_original" has been corrected. Column data types and formatting have been updated to reflect DataSF standards. Law Enforcement Dispatched Calls for Service: Closed Calls has also been updated as part of a larger effort to upgrade our Calls for Service pipelines. Email support@datasf.org with any questions or concerns.

A. SUMMARY Law Enforcement Dispatched Calls for Service: Real-Time includes all calls for service that generate a record in the Department of Emergency Management's Computer Aided Dispatch (CAD) System and result in a law enforcement unit being dispatched to a location. Calls originate either from the public (via calls to the 911 call center) or from law enforcement officers in the field upon viewing an incident (‘On-View’).

This dataset represents a rolling 48 hour window of calls for service. It contains both open and closed calls. It is both updated every 10 minutes and delayed by an additional 10 minutes. Open calls are defined as active calls that are unverified, but being worked by law enforcement. Closed calls are calls that law enforcement have indicated are resolved. Not all calls for service generate a police incident report, so data does not directly correlate to the Police Incident Reports dataset. The Real-time Calls dataset contains calls handled by law enforcement which can include Police, MTA parking enforcement, the Sheriff’s Office, and others. Some fields in the calls for service data are redacted due to the sensitive nature of the call and/or privacy concerns related to the incident.

Please refer Law Enforcement Dispatched Calls for Service Explainer for full documentation.

B. HOW THE DATASET IS CREATED
Once a received 911 call is dispatched, a record (CAD#) is generated in the Department of Emergency Management's Computer Aided Dispatch (CAD) System.

C. UPDATE PROCESS Updated every 10 minutes with the past 48hrs of open and closed calls that have been dispatched.

D. HOW TO USE THIS DATASET Please refer Law Enforcement Dispatched Calls for Service Explainer for full documentation.

Note: To find data for calls originating from the 311 Connected Worker app dispatched from the Healthy Streets Operations Center (HSOC), search for the value “HSOC” in the onview_flag column.

E. KEY RELATED DATASETS Datasets: Law Enforcement Dispatched Calls for Service: Closed Calls Police Department Incident Reports: 2018 to Present Fire Department Calls for Service

Geographic Boundaries: Current Police Districts
Analysis Neighborhoods Supervisor Districts

Filtered view of County crime data to show driving under the influence for liquor and drugs.

Updated daily postings on Montgomery County’s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions – of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by “EJustice”, a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims’ privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation.

Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect:

-Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law.]

Update Frequency: Daily

The Code Enforcement Division enforces:

• Housing and Commercial Building Codes (Chapter 13)
• Rental Housing Permits (Chapter 14.5)
• Nuisance Codes (Chapter 16)
• Abandoned Vehicles on private property (Chapter 26)
• Land Development Code (Chapter 30)
• Graffiti (Chapter 13) This report lists, code complaints, violations and permits. Data is updated monthly and dates back to February 2011. Please note that addresses that are listed under the Location field as 0 W 1ST ST are null place-holders and are not accurate addresses.

This data set contains only End of Operations Reports (EOR) that were submitted via eWell since April 2004.

Crime data assembled by census block group for the MSA from the Applied Geographic Solutions' (AGS) 1999 and 2005 'CrimeRisk' databases distributed by the Tetrad Computer Applications Inc. CrimeRisk is the result of an extensive analysis of FBI crime statistics. Based on detailed modeling of the relationships between crime and demographics, CrimeRisk provides an accurate view of the relative risk of specific crime types at the block group level. Data from 1990 - 1996,1999, and 2004-2005 were used to compute the attributes, please refer to the 'Supplemental Information' section of the metadata for more details. Attributes are available for two categories of crimes, personal crimes and property crimes, along with total and personal crime indices. Attributes for personal crimes include murder, rape, robbery, and assault. Attributes for property crimes include burglary, larceny, and mother vehicle theft. 12 block groups have no attribute information. CrimeRisk is a block group and higher level geographic database consisting of a series of standardized indexes for a range of serious crimes against both persons and property. It is derived from an extensive analysis of several years of crime reports from the vast majority of law enforcement jurisdictions nationwide. The crimes included in the database are the "Part I" crimes and include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. These categories are the primary reporting categories used by the FBI in its Uniform Crime Report (UCR), with the exception of Arson, for which data is very inconsistently reported at the jurisdictional level. Part II crimes are not reported in the detail databases and are generally available only for selected areas or at high levels of geography. In accordance with the reporting procedures using in the UCR reports, aggregate indexes have been prepared for personal and property crimes separately, as well as a total index. While this provides a useful measure of the relative "overall" crime rate in an area, it must be recognized that these are unweighted indexes, in that a murder is weighted no more heavily than a purse snatching in the computation. For this reason, caution is advised when using any of the aggregate index values. The block group boundaries used in the dataset come from TeleAtlas's (formerly GDT) Dynamap data, and are consistent with all other block group boundaries in the BES geodatabase. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Abstract (en): The National Incident-Based Reporting System (NIBRS) is a part of the Uniform Crime Reporting Program (UCR), administered by the Federal Bureau of Investigation (FBI). In the late 1970s, the law enforcement community called for a thorough evaluative study of the UCR with the objective of recommending an expanded and enhanced UCR program to meet law enforcement needs into the 21st century. The FBI fully concurred with the need for an updated program to meet contemporary needs and provided its support, formulating a comprehensive redesign effort. Following a multiyear study, a "Blueprint for the Future of the Uniform Crime Reporting Program" was developed. Using the "Blueprint," and in consultation with local and state law enforcement executives, the FBI formulated new guidelines for the Uniform Crime Reports. The National Incident-Based Reporting System (NIBRS) was implemented to meet these guidelines. NIBRS data are archived at ICPSR as 11 separate data files per year, which may be merged by using linkage variables. Prior to 2013 the data were archived and distributed as 13 separate data files, including three separate batch header record files. In 2013 the FBI combined the three batch header files into one file. Consequently, ICPSR instituted new file numbering for the 2013 data. NIBRS data focus on a variety of aspects of a crime incident. Part 2 (formerly Part 4), Administrative Segment, offers data on the incident itself (date and time). Each crime incident is delineated by one administrative segment record. Also provided are Part 3 (formerly Part 5), Offense Segment (offense type, location, weapon use, and bias motivation), Part 4 (formerly Part 6), Property Segment (type of property loss, property description, property value, drug type and quantity), Part 5 (formerly Part 7), Victim Segment (age, sex, race, ethnicity, and injuries), Part 6 (formerly Part 8), Offender Segment (age, sex, and race), and Part 7 (formerly Part 9), Arrestee Segment (arrest date, age, sex, race, and weapon use). The Batch Header Segment (Part 1, formerly Parts 1-3) separates and identifies individual police agencies by Originating Agency Identifier (ORI). Batch Header information, which is contained on three records for each ORI, includes agency name, geographic location, and population of the area. Part 8 (formerly Part 10), Group B Arrest Report Segment, includes arrestee data for Group B crimes. Window Segments files (Parts 9-11, formerly Parts 11-13) pertain to incidents for which the complete Group A Incident Report was not submitted to the FBI. In general, a Window Segment record will be generated if the incident occurred prior to January 1 of the previous year or if the incident occurred prior to when the agency started NIBRS reporting. As with the UCR, participation in NIBRS is voluntary on the part of law enforcement agencies. The data are not a representative sample of crime in the United States. ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed consistency checks.; Created variable labels and/or value labels.; Checked for undocumented or out-of-range codes.. Law enforcement agencies in the United States participating in the National Incident-Based Reporting System. Smallest Geographic Unit: city 2015-06-29 Corrected error in V5011 (Ethnicity of Offender) in the Offender Segment. Funding insitution(s): United States Department of Justice. Federal Bureau of Investigation. United States Department of Justice. Office of Justice Programs. Bureau of Justice Statistics. Starting with the 2012 data, some offense, location, bias motivation, race, and ethnicity codes have been added or modified to include recent Advisory Policy Board (APB) and Office of Management and Budget (OMB) policy mandates to the UCR Program related to Human Trafficking, Hate Crime, and Race and Ethnicity information.At the recommendation of the CJIS APB and with the approval of the FBI Director, the FBI UCR Program initiated the collection of rape data under a revised definition and removed the term "forcible" from the offense name in 2013. The changes bring uniformity to the offense in both the Summary Reportin...

Updated daily postings on Montgomery County’s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions – of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by “EJustice”, a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims’ privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation.

dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect:

-Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law.]

Update Frequency: Daily

Revision Note (February 10, 2025): The data pipeline for "Law Enforcement Dispatched Calls for Service: Closed" has been updated. The largest updates are: Consistent geo-masked intersections have been applied to all historical data We have resolved a bug that was incorrectly mapping calls with no recorded _location See our Release Notes here for all changes. Email support@datasf.org with any questions or concerns. A. SUMMARY Law Enforcement Dispatched Calls for Service: Closed includes all calls for service that generate a record in the Department of Emergency Management's Computer Aided Dispatch (CAD) System and result in a law enforcement unit being dispatched to a _location. Calls originate either from the public (via calls to the 911 call center) or from law enforcement officers in the field upon viewing an incident (‘On-View’). The Closed Calls dataset only includes calls for service that have been closed, and is updated every 24 hours. Not all calls for service generate a police incident report, so data does not directly correlate to the Police Incident Reports dataset. The Closed Calls dataset contains all calls handled by law enforcement which can include Police, MTA parking enforcement, the Sheriff’s Office, and others. Some fields in the calls for service data are redacted due to the sensitive nature of the call and/or privacy concerns related to the incident. Please refer to the Dispatched Calls for Service Explainer for full documentation B. HOW THE DATASET IS CREATED Once a received 911 call is dispatched, a record (CAD#) is generated in the Department of Emergency Management's Computer Aided Dispatch (CAD) System. C. UPDATE PROCESS Updated daily at 5:00am with the previous day's data. D. HOW TO USE THIS DATASET Please refer to the Dispatched Calls for Service Explainer for full documentation. Note: To find data for calls originating from the 311 Connected Worker app dispatched from the Healthy Streets Operations Center (HSOC), search for the value “HSOC” in the onview_flag column. E. KEY RELATED DATASETS Datasets: Law Enforcement Dispatched Calls for Service: Real-time Police Department Incident Reports: 2018 to Present Fire Department Calls for Service Geographic Boundaries: Current Police Districts Analysis Neighborhoods Supervisor Districts

Law Enforcement Locations Any location where sworn officers of a law enforcement agency are regularly based or stationed. Law Enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies. Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police). In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS deleted these locations as we became aware of them, but some may still exist in this dataset. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes are included due to the fact that the New Mexico Mounted Police work out of their homes. TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; Bureau of Alcohol, Tobacco, Firearms, and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. FBI entities are intended to be excluded from this dataset, but a few may be included. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, the NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 08/14/2006 and the newest record dates from 10/23/2009

An investigation into the arrest and strip search of a 53 year old male in inner Sydney in March 2015 and subsequent unsuccessful prosecution of him for hindering police in the execution of their duty.