Dallas Police Public Data - Officer Involved Shootings City Of Dallas
List of every shooting incident that occurred in NYC going back to 2006 through the end of the previous calendar year.
This is a breakdown of every shooting incident that occurred in NYC going back to 2006 through the end of the previous calendar year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning before being posted on the NYPD website. Each record represents a shooting incident in NYC and includes information about the event, the location and time of occurrence. In addition, information related to suspect and victim demographics is also included. This data can be used by the public to explore the nature of shooting/criminal activity. Please refer to the attached data footnotes for additional information about this dataset.
List of every shooting incident that occurred in NYC during the current calendar year.
This is a breakdown of every shooting incident that occurred in NYC during the current calendar year. This data is manually extracted every quarter and reviewed by the Office of Management Analysis and Planning before being posted on the NYPD website. Each record represents a shooting incident in NYC and includes information about the event, the location and time of occurrence. In addition, information related to suspect and victim demographics is also included. This data can be used by the public to explore the nature of police enforcement activity. Please refer to the attached data footnotes for additional information about this dataset.
This Data includes all officer-involved shootings since 2009. Transparency is a priority for the Orlando Police Department and we will continue to include more information in this Dataset.
Starting in 2014 all officer-involved shooting investigations are reviewed by the State Attorney's Office. A link to the State Attorney's review letter is provided for investigations that are complete. Prior to 2014 only cases where the someone was hit as a result of the shooting were reviewed by the State Attorney's Office. All other cases were reviewed internally. A link to those findings are provided.
This dataset contains individual-level homicide and non-fatal shooting victimizations, including homicide data from 1991 to the present, and non-fatal shooting data from 2010 to the present (2010 is the earliest available year for shooting data). This dataset includes a "GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized-access dataset, but with "UNKNOWN" in the shooting column.
Each row represents a single victimization, i.e., a unique event when an individual became the victim of a homicide or non-fatal shooting. Each row does not represent a unique victim—if someone is victimized multiple times there will be multiple rows for each of those distinct events.
The dataset is refreshed daily, but excludes the most recent complete day to allow the Chicago Police Department (CPD) time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.
A version of this dataset with additional crime types is available by request. To make a request, please email dataportal@cityofchicago.org with the subject line: Violence Reduction Victims Access Request. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup.
How does this dataset classify victims?
The methodology by which this dataset classifies victims of violent crime differs by victimization type:
Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.
To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset. For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Victims dataset do not align with the homicide/non-fatal shooting categorization:
- In instances where a homicide victimization does not correspond to an IUCR code 0110 or 0130, we set the IUCR code to "01XX" to indicate that the victimization was a homicide but we do not know whether it was a fi
This dataset represents the information the Colorado Springs Police Department (CSPD) was required to report to the State of Colorado Division of Criminal Justice after an officer involved shooting. It is important to note the State of Colorado developed the options for each data field; these multiple choice items were not created by CSPD. Data provided for people categorized as "suspects" in these incidents. CSPD has chosen at this time to continue to update this information even though CSPD no longer has the requirement to report this information in this way. The data collection and reporting was required for the time period 1/1/2010 to 6/30/2020. Law enforcement agencies will have the responsibility to collect and report different use of force information effective 7/1/2023.
Due to technical issues the Active Calls dataset may experience intermittent delays in automated data refreshing. Staff is actively monitoring the situation.
The calls listed here are only those where the element assigned to the call has arrived and is currently working the call. It does not include any calls for service, whether currently being worked or not, that are not releasable due to privacy laws.
Records of Officer Involved Shootings (OIS) from 2005 to the present, including a brief narrative synopsis. Beginning in Q3 2023, the summary will be replaced with a link to the FRB findings documented, prepared for public release. A link for each OIS will be embedded in the file. Data set does not contain records from active investigations. Data is visualized in a dashboard on the SPD public site (https://www.seattle.gov/police/information-and-data/use-of-force-data/officer-involved-shootings-dashboard), please reference as a guide for use. Dashboard is available for download.
Updates are posted twice a year (January and July), as cases complete the inquest process (https://kingcounty.gov/services/inquest-program.aspx).
Use of force data also available here: https://data.seattle.gov/Public-Safety/Use-Of-Force/ppi5-g2bj and is updated daily. Data includes Type III - OIS.
2013 Non-Fatal Shootings as reported to the Maryland Coordination and Analysis Center (MCAC)
Bloomington Police Department cases where officers have fired a gun at an individual.
Key code for Race:
A- Asian/Pacific Island, Non-Hispanic B- African American, Non-Hispanic C- Hawaiian/Other Pacific Island, Hispanic H- Hawaiian/Other Pacific Island, Non-Hispanic I- Indian/Alaskan Native, Non-Hispanic K- African American, Hispanic L- Caucasian, Hispanic N- Indian/Alaskan Native, Hispanic P- Asian/Pacific Island, Hispanic S- Asian, Non-Hispanic T- Asian, Hispanic U- Unknown W- Caucasian, Non-Hispanic
Key Code for Reading Districts:
Example: LB519
L for Law call or incident B stands for Bloomington 5 is the district or beat where incident occurred All numbers following represents a grid sector.
Disclaimer: The Bloomington Police Department takes great effort in making open data as accurate as possible, but there is no avoiding the introduction of errors in this process, which relies on data provided by many people and that cannot always be verified. Information contained in this dataset may change over a period of time. The Bloomington Police Department is not responsible for any error or omission from this data, or for the use or interpretation of the results of any research conducted.
This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.
Data Description: This data represents officer involved shooting incidents by the Cincinnati Police Department. An officer involved shooting (OIS) may be defined as the discharge of a firearm, which may include accidental and intentional discharges, by a police officer, whether on or off duty.
Data Creation: This data is created through reporting by the Cincinnati Police Department.
Data Created By: The source of this data is the Cincinnati Police Department.
Refresh Frequency: This information will not be updated while the Cincinnati Police Department undergoes transfer to a new data management system.
CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/c64e-ybfz/
Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.
Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).
Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad
Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.
Information provided in an excel spreadsheet of the GPS coordinate locations of the Shooting Ranges in Nova Scotia.
DISCLAIMER: This dataset only include cases that have been officially closed with a final court disposition made on the legality of the shooting. This dataset should not be compared to other similar datasets as they often use sources such as news reports, public records, and social media posts that unofficial and unverified. SUMMARY: This dataset contains information related to officer involved shootings reported by the Vermont State Police (VSP) between 1977 and the previous year. These data are collected by the VSP investigative unit on a case-by-case basis. This particular dataset is made available in an effort to highlight and address both concerns of officer involved shootings. Should you have questions about this dataset, you may contact Scott Waterman at the Vermont State Police (802-241-5312 | scott.waterman@vermont.gov). To access a summary page of this dataset, select the “About” tab on the right side of this page and scroll down to the attachments and click on the PDF document.
Data Description: This dataset captures confirmed shooting events in the City of Cincinnati. Shootings events are captured in the Computer Aided Dispatch System (CAD), and are ultimately stored in the City's Records Management System (RMS).
No personal or identifying (or otherwise sensitive) victim or suspect information is included in this data set.
Data Creation: This data is created through the City’s computer-aided dispatch (CAD) system.
Data Created By: The source of this data is the Cincinnati Police Department.
Refresh Frequency: This data is updated daily.
CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/xw7t-5phj
Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.
Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).
Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad
Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.
This data set contains New York City Police Department provided domestic violence incident data for calendar years 2020, 2021 and 2022. In addition, ENDGBV obtained through Open Data the number of shooting incidents for calendar years 2020, 2021 and 2022. The data includes counts of the number of domestic violence incidents, shooting incidents and the number of expected domestic violence incidents and shooting incidents by: race (American Indian/Alaska Native, Asian/Pacific Islander, Black, and White) and sex (male, female) for New York City, each borough (Bronx, Brooklyn, Manhattan, Queens and Staten Island). It also provides the count and rate of domestic violence and shooting incidents by police precinct. The expected number of domestic violence incidents and shooting incidents were calculated by taking the total number of actual domestic violence and shooting incidents for a given geography (New York City, the Bronx, Brooklyn, Manhattan, Queens and Staten Island) and proportioning them by demographic breakdown of the geographic area.
Permits are generally required when asserting the exclusive use of city property, like a sidewalk, a street, or a park. See http://www1.nyc.gov/site/mome/permits/when-permit-required.page
This dataset contains aggregate data on violent index victimizations at the quarter level of each year (i.e., January – March, April – June, July – September, October – December), from 2001 to the present (1991 to present for Homicides), with a focus on those related to gun violence. Index crimes are 10 crime types selected by the FBI (codes 1-4) for special focus due to their seriousness and frequency. This dataset includes only those index crimes that involve bodily harm or the threat of bodily harm and are reported to the Chicago Police Department (CPD). Each row is aggregated up to victimization type, age group, sex, race, and whether the victimization was domestic-related. Aggregating at the quarter level provides large enough blocks of incidents to protect anonymity while allowing the end user to observe inter-year and intra-year variation. Any row where there were fewer than three incidents during a given quarter has been deleted to help prevent re-identification of victims. For example, if there were three domestic criminal sexual assaults during January to March 2020, all victims associated with those incidents have been removed from this dataset. Human trafficking victimizations have been aggregated separately due to the extremely small number of victimizations.
This dataset includes a " GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized dataset, but with "UNKNOWN" in the shooting column.
The dataset is refreshed daily, but excludes the most recent complete day to allow CPD time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.
How does this dataset classify victims?
The methodology by which this dataset classifies victims of violent crime differs by victimization type:
Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.
To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset.
For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Vi
NYPD Crime stats for the week of November 18-24, 2013.
Crime stats as compared to 12, 15, 20, and 23 years ago, Citywide
Citywide crime statistics for the week of September 16-23, 2013
Dallas Police Active Calls - Geolocation
Crime statistics published by the NYPD for the week of September 16-23, 2013.
Citywide crime statistics for the week of September 9-15, 2013
Crime statistics published by the NYPD for the week of September 2-8, 2013.
The program described below ended in 2019. This dataset is being retained for historical reference.
The information displayed represents a de-identified listing of arrest data from August 1, 2012 to July 31, 2016, that was used by the Chicago Police Department’s Strategic Subject Algorithm, created by the Illinois Institute of Technology and funded through a Department of Justice Bureau of Justice Assistance grant, to create a risk assessment score known as the Strategic Subject List or “SSL.” These scores reflect an individual’s probability of being involved in a shooting incident either as a victim or an offender. Scores are calculated and placed on a scale ranging from 0 (extremely low risk) to 500 (extremely high risk).
Based on this time frame’s version of the Strategic Subject Algorithm, individuals with criminal records are ranked using eight attributes, not including race or sex. These attributes are: number of times being the victim of a shooting incident, age during the latest arrest, number of times being the victim of aggravated battery or assault, number of prior arrests for violent offenses, gang affiliation, number of prior narcotic arrests, trend in recent criminal activity and number of prior unlawful use of weapon arrests.
Please note that this data set includes fields that are not used to calculate SSL, for example, neither race nor sex are used in the Strategic Subject Algorithm. Portions of the arrest data are de-identified on the basis of privacy concerns. The attributes used in the Strategic Subject Algorithm were revised on an ongoing basis during the lifetime of the program.
Complaints received by the Civilian Office of Police Accountability and its predecessor agency.
A case will generate multiple rows, sharing the same LOG_NO if there are multiple complainants or subjects. Each row in this dataset is a complainant or subject in a specific case.
Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.
Complaints received by the Civilian Office of Police Accountability and its predecessor agency.
A case will generate multiple rows, sharing the same LOG_NO if there are multiple officers. Each row in this dataset is an officer in a specific case.
Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.
Some location data has a data quality issue and has temporarily removed while we resolve the issue. WE will work on making it available as the highest priority.
The Seattle Police Department (SPD) replaced its Records Management System (RMS) in May 2019. To preserve data quality and continuity between systems (2008-Present), SPD relied on the National Incident-Based Reporting System (NIBRS). The standardization of crime classifications allows for comparison over time. For more information on definitions and classifications, please visit https://www.fbi.gov/services/cjis/ucr/nibrs.
Additional groupings are used to analyze crime in SPD’s Crime Dashboard. Violent and property crime categories align with best practices. For additional inquiries, we encourage the use of the underline data to align with the corresponding query.
Disclaimer: Only finalized (UCR approved) reports are released. Those in draft, awaiting approval, or completed after the update, will not appear until the subsequent day(s). Data is updated once every twenty-four hours. Records and classification changes will occur as a report makes its way through the approval and investigative process.
Rate: Firearm-related Deaths per 100,000 Persons (age adjusted)
Definition: Deaths with a firearm-related injury as the underlying cause of death. ICD-10 codes: W32-W34 (unintentional), X72-X74 (suicide), X93-X95 (homicide), Y22-Y24 (undetermined intent), Y35.0 (legal intervention)
Data Sources:
1) Centers for Disease Control and Prevention, National Center for Health Statistics. Compressed Mortality File. CDC WONDER On-line Database accessed at http://wonder.cdc.gov/cmf-icd10.html
2) Death Certificate Database, Office of Vital Statistics and Registry, New Jersey Department of Health
2) Population Estimates, State Data Center, New Jersey Department of Labor and Workforce Development
Data Description: This data represents officer involved shooting incidents by the Cincinnati Police Department. An officer involved shooting (OIS) may be defined as the discharge of a firearm, which may include accidental and intentional discharges, by a police officer, whether on or off duty.
The demographic information for the subjects and officers are available at the following links. The datasets can be linked using the UNIQUE_REPORT_ID. Please keep in mind an incident may have more than one subject and more than one officer involved. Officers: https://data.cincinnati-oh.gov/safety/Police-Firearm-Discharge-Officers/82xu-949a/ Subjects: https://data.cincinnati-oh.gov/dataset/Police-Firearm-Discharge-Subjects/dxac-g4wm/
Data Creation: This data is created through reporting by the Cincinnati Police Department.
Data Created By: The source of this data is the Cincinnati Police Department record system
CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/c64e-ybfz/
Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.
Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).
Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad
Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.
Rate: Deaths per 100,000 15-19 year old males
Definition: Deaths with a firearm-related injury as the underlying cause of death. ICD-10 codes: W32-W34 (unintentional), X72-X74 (suicide), X93-X95 (homicide), Y22-Y24 (undetermined intent), Y35.0 (legal intervention)
Data Source:
1) Centers for Disease Control and Prevention, National Center for Health Statistics. Compressed Mortality File. CDC WONDER On-line Database accessed at http://wonder.cdc.gov/cmf-icd10.html
2) Death Certificate Database, Office of Vital Statistics and Registry, New Jersey Department of Health
3) Population Estimates, State Data Center, New Jersey Department of Labor and Workforce Development
Data Description: This data represents the demographics of the officers involved in shooting incidents by the Cincinnati Police Department. This dataset is supplemental Police Firearm Discharge - Incidents which can be found at the following link: https://data.cincinnati-oh.gov/safety/Police-Firearm-Discharge-Incidents/n625-s9aa/
The datasets can be linked using the UNIQUE_REPORT_ID. Please keep in mind an incident may have more than one subject and more than one officer involved.
Fireballs and bolides are astronomical terms for exceptionally bright meteors that are spectacular enough to to be seen over a very wide area. The following table provides a chronological data summary of fireball and bolide events provided by U.S. Government sensors. Ground-based observers sometimes also witness these events at night, or much more rarely in daylight, as impressive atmospheric light displays. This website is not meant to be a complete list of all fireball events. Only the brightest fireballs are noted.
A meteoroid is generally defined as an asteroid or comet fragment that orbits the Sun and has an approximate size between ten microns and a meter or so. Meteors, or "shooting stars," are the visible paths of meteoroids that have entered the Earth's atmosphere at high velocities. A fireball is an unusually bright meteor that reaches a visual magnitude of -3 or brighter when seen at the observer's zenith. Objects causing fireball events can exceed one meter in size. Fireballs that explode in the atmosphere are technically referred to as bolides although the terms fireballs and bolides are often used interchangeably.
During the atmospheric entry phase, an impacting object is both slowed and heated by atmospheric friction. In front of it, a bow shock develops where atmospheric gases are compressed and heated. Some of this energy is radiated to the object causing it to ablate, and in most cases, to break apart. Fragmentation increases the amount of atmosphere intercepted and so enhances ablation and atmospheric braking. The object catastrophically disrupts when the force from the unequal pressures on the front and back sides exceeds its tensile strength.
Objects causing fireballs are usually not large enough to survive passage through the Earth's atmosphere intact, although fragments, or meteorites, are sometimes recovered on the ground. The approximate total radiated energy in the atmosphere is provided in unit of Joules, a unit of energy given in kilograms times velocity squared, or kg x (m/s)2. An event with an energy equivalent of one thousand tons of TNT explosives is termed a kiloton (kt) event, where 1 kt = 4.185 x 1012 Joules. In the accompanying table, the total radiated energy is given but this is always less that the total impact energy. Peter Brown and colleagues have provided an empirical expression to approximately provide the total impact energy in kt (E), given the optical radiant energy in kt (Eo) (see: Brown et al., The flux of small near-Earth objects colliding with the Earth. Nature, vol. 420, 21 Nov. 2002, pp. 294-296).
E = 8.2508 x Eo0.885
The accompanying table provides information on the date and time of each fireball event, its geographic location, its altitude and velocity at peak brightness, its approximate total optical radiated energy and its calculated total impact energy. The pre-impact velocity components are expressed in a geocentric Earth-fixed reference frame defined as follows: the z-axis is directed along the Earth's rotation axis towards the celestial north pole, the x-axis lies in the Earth's equatorial plane, directed towards the prime meridian, and the y-axis completes the right-handed coordinate system.
http://neo.jpl.nasa.gov/fireball/
Complaints received by the Civilian Office of Police Accountability and its predecessor agency.
| Each complaint is represented by a single line. When multiple people are involved, values for each of them are separated by the | character. In all such columns, the people are presented in the same order. For example, the first value in one column corresponds to the same person as the first value in another column. |
Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.
Data Description: This data represents the demographics of the subjects of officer involved shooting incidents by the Cincinnati Police Department. This dataset is supplemental to Police Firearm Discharge - Incidents which can be found at the following link: https://data.cincinnati-oh.gov/safety/Police-Firearm-Discharge-Incidents/n625-s9aa/
The datasets can be linked using the UNIQUE_REPORT_ID. Please keep in mind an incident may have more than one subject and more than one officer involved.
Ramsey County conducts special permit archery hunts each fall in partnership with the Metro Bowhunters Resource Base. This dataset shares archery harvest totals. The annual hunts have been conducted since 2000. All participating hunters attend a pre-hunt orientation, agree to special hunt rules and pass an archery safety class and shooting proficiency test. Archers may keep their deer or donate the venison to local food shelves. During the hunts, entire parks or portions of a park may be closed. Archery hunting is the county's preferred method of deer population control.
This was one single topic among a couple from the May 2019 Mixed Topic survey. To view the survey questions, click on the following link:
https://www.edmontoninsightcommunity.ca/c/a/5enTBQVbIsLKnhCBvlqKoy?t=1
Open from May 14 - 21, 2019.
At the time the survey was launched survey invitations were sent to 11,525 Insight Community Members. 2,926 members completed the survey which represents a completion rate of 25%. A total of 2,946 respondents completed the survey: 2,926 Insight Community Members and 6 from the call to action button on our web page and 14 using the anonymous link(s) on edmonton.ca/surveys which will have no demographic information.
Column definitions can be found as an attachment to this dataset (under the About option, in the Attachment section).
The Other Outcomes dataset includes information on whether the trial includes measures of depression, anxiety, substance use, sleep, anger, quality of life and functioning. Results in this dataset are provided for each treatment arm. The name of the measure is included as well as the between-group effect sizes. Use this dataset to learn how about the effects of PTSD treatments on other outcomes. Values abstracted as not applicable ("NA") or not reported ("NR") from the study are null values (empty cells). Study level variables, like military status and percent female, are included for ease of filtering. These columns are not individual arm or arm comparison level data.
The Study Interventions dataset includes information about each of the specific treatment arms that were studied in all RCTs. Each study arm was coded to indicate the type of intervention or comparison condition. This dataset includes the study-level Study Class as well as individual variables for each category of treatment, coded as Yes or No for each arm. Study arm treatment category variables are as follows: Pharmacotherapy (as well as a subclass such as antidepressant, antianxiety, etc.); Psychotherapy (as well as a subclass to identify trauma-focused or non-trauma-focused therapy); Complementary and Integrative Health (CIH; as well as a subclass such as relaxation or meditation); Nonpharmacologic Biological; Nonpharmacologic Cognitive; Collaborative Care; Other Treatments; Control The Study Intervention dataset also includes information on the format of the treatment (individual, group, couples, mixed); treatment delivery method (in person, by phone, by video, technology alone, technology assisted, written or mixed); dose or amount of treatment and, treatment completion and adherence. Use this dataset to learn about treatment studies of a particular type
Each record is an arm of the study, labeled as A, B, C, or D. Values abstracted as not applicable ("NA") or not reported ("NR") from the study are null values (empty cells).
The Harms dataset includes information on serious adverse events and participant withdrawals from the studies due to adverse events. Adverse events are reported as the percent of participants within a treatment group that experienced an adverse event or who withdrew from the study. Detail on the specific adverse event or reason for withdrawal is provided when available. This dataset also reports on the percentage of patients who attempted or completed suicide (when available). Values abstracted as "NA" or "NR" from the study are represented as null values/empty cells in this dataset. Study level variables like military status and percent female are included for filtering purposes
The Sample Characteristics dataset includes information on the participants who are included in the studies. This information is provided at the study level—meaning, data are not broken down into the specific treatment arms such as the intervention or control groups. Use this dataset if you want to learn more about the number of participants in the study; inclusion and exclusion criteria related to substance use and suicidality; baseline clinical characteristics such as PTSD severity, trauma type, military status, and comorbidities; and, basic demographic information such as age, gender or race for the sample as a whole (not individual participants). Visualizations made from this dataset will be based on the 496 RCTs included in the PTSD-Repository. Values reported as "NA" or not reported "NR" by the study are null values (empty cells). Data is at the study level.