4 datasets found
  1. Data from: Quantifying the Size and Geographic Extent of CCTV's Impact on...

    • catalog.data.gov
    • datasets.ai
    • +1more
    Updated Mar 12, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Institute of Justice (2025). Quantifying the Size and Geographic Extent of CCTV's Impact on Reducing Crime in Philadelphia, Pennsylvania, 2003-2013 [Dataset]. https://catalog.data.gov/dataset/quantifying-the-size-and-geographic-extent-of-cctvs-impact-on-reducing-crime-in-phila-2003-d9f6e
    Explore at:
    Dataset updated
    Mar 12, 2025
    Dataset provided by
    National Institute of Justicehttp://nij.ojp.gov/
    Area covered
    Philadelphia, Pennsylvania
    Description

    These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. This study was designed to investigate whether the presence of CCTV cameras can reduce crime by studying the cameras and crime statistics of a controlled area. The viewsheds of over 100 CCTV cameras within the city of Philadelphia, Pennsylvania were defined and grouped into 13 clusters, and camera locations were digitally mapped. Crime data from 2003-2013 was collected from areas that were visible to the selected cameras, as well as data from control and displacement areas using an incident reporting database that records the location of crime events. Demographic information was also collected from the mapped areas, such as population density, household information, and data on the specific camera(s) in the area. This study also investigated the perception of CCTV cameras, and interviewed members of the public regarding topics such as what they thought the camera could see, who was watching the camera feed, and if they were concerned about being filmed.

  2. d

    Data from: Forecasting Municipality Crime Counts in the Philadelphia...

    • catalog.data.gov
    • icpsr.umich.edu
    Updated Mar 12, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Institute of Justice (2025). Forecasting Municipality Crime Counts in the Philadelphia [Pennsylvania] Metropolitan Area, 2000-2008 [Dataset]. https://catalog.data.gov/dataset/forecasting-municipality-crime-counts-in-the-philadelphia-pennsylvania-metropolitan-a-2000-fca6d
    Explore at:
    Dataset updated
    Mar 12, 2025
    Dataset provided by
    National Institute of Justice
    Area covered
    Philadelphia, Pennsylvania
    Description

    These data are part of NACJD's Fast Track Release and are distributed as they there received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except of the removal of direct identifiers. Users should refer to the accompany readme file for a brief description of the files available with this collections and consult the investigator(s) if further information is needed. This study examines municipal crime levels and changes over a nine year time frame, from 2000-2008, in the fifth largest primary Metropolitan Statistical Area (MSA) in the United States, the Philadelphia metropolitan region. Crime levels and crime changes are linked to demographic features of jurisdictions, policing arrangements and coverage levels, and street and public transit network features.

  3. Communities and Crime Dataset (Unnormalized Data)

    • kaggle.com
    Updated Feb 9, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    John (2023). Communities and Crime Dataset (Unnormalized Data) [Dataset]. https://www.kaggle.com/datasets/johnp47/communities-and-crime-dataset/discussion
    Explore at:
    CroissantCroissant is a format for machine-learning datasets. Learn more about this at mlcommons.org/croissant.
    Dataset updated
    Feb 9, 2023
    Dataset provided by
    Kagglehttp://kaggle.com/
    Authors
    John
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Source:

    Creator: Michael Redmond (redmond '@' lasalle.edu); Computer Science; La Salle University; Philadelphia, PA, 19141, USA -- culled from 1990 US Census, 1995 US FBI Uniform Crime Report, 1990 US Law Enforcement Management and Administrative Statistics Survey, available from ICPSR at U of Michigan. -- Donor: Michael Redmond (redmond '@' lasalle.edu); Computer Science; La Salle University; Philadelphia, PA, 19141, USA -- Date: July 2009

    Data Set Information:

    Many variables are included so that algorithms that select or learn weights for attributes could be tested. However, clearly unrelated attributes were not included; attributes were picked if there was any plausible connection to crime (N=122), plus the attribute to be predicted (Per Capita Violent Crimes). The variables included in the dataset involve the community, such as the percent of the population considered urban, and the median family income, and involving law enforcement, such as per capita number of police officers, and percent of officers assigned to drug units.

    The per capita violent crimes variable was calculated using population and the sum of crime variables considered violent crimes in the United States: murder, rape, robbery, and assault. There was apparently some controversy in some states concerning the counting of rapes. These resulted in missing values for rape, which resulted in incorrect values for per capita violent crime. These cities are not included in the dataset. Many of these omitted communities were from the midwestern USA.

    Data is described below based on original values. All numeric data was normalized into the decimal range 0.00-1.00 using an Unsupervised, equal-interval binning method. Attributes retain their distribution and skew (hence for example the population attribute has a mean value of 0.06 because most communities are small). E.g. An attribute described as 'mean people per household' is actually the normalized (0-1) version of that value.

    The normalization preserves rough ratios of values WITHIN an attribute (e.g. double the value for double the population within the available precision - except for extreme values (all values more than 3 SD above the mean are normalized to 1.00; all values more than 3 SD below the mean are normalized to 0.00)).

    However, the normalization does not preserve relationships between values BETWEEN attributes (e.g. it would not be meaningful to compare the value for whitePerCap with the value for blackPerCap for a community)

    A limitation was that the LEMAS survey was of the police departments with at least 100 officers, plus a random sample of smaller departments. For our purposes, communities not found in both census and crime datasets were omitted. Many communities are missing LEMAS data.

    Attribute Information:

    '(125 predictive, 4 non-predictive, 18 potential goal) ', ' communityname: Community name - not predictive - for information only (string) ', ' state: US state (by 2 letter postal abbreviation)(nominal) ', ' countyCode: numeric code for county - not predictive, and many missing values (numeric) ', ' communityCode: numeric code for community - not predictive and many missing values (numeric) ', ' fold: fold number for non-random 10 fold cross validation, potentially useful for debugging, paired tests - not predictive (numeric - integer) ', ' population: population for community: (numeric - expected to be integer) ', ' householdsize: mean people per household (numeric - decimal) ', ' racepctblack: percentage of population that is african american (numeric - decimal) ', ' racePctWhite: percentage of population that is caucasian (numeric - decimal) ', ' racePctAsian: percentage of population that is of asian heritage (numeric - decimal) ', ' racePctHisp: percentage of population that is of hispanic heritage (numeric - decimal) ', ' agePct12t21: percentage of population that is 12-21 in age (numeric - decimal) ', ' agePct12t29: percentage of population that is 12-29 in age (numeric - decimal) ', ' agePct16t24: percentage of population that is 16-24 in age (numeric - decimal) ', ' agePct65up: percentage of population that is 65 and over in age (numeric - decimal) ', ' numbUrban: number of people living in areas classified as urban (numeric - expected to be integer) ', ' pctUrban: percentage of people living in areas classified as urban (numeric - decimal) ', ' medIncome: median household income (numeric - may be integer) ', ' pctWWage: percentage of households with wage or salary income in 1989 (numeric - decimal) ', ' pctWFarmSelf: percentage of households with farm or self employment income in 1989 (numeric - decimal) ', ' pctWInvInc: percentage of households with investment / rent income in 1989 (numeric - decimal) ', ' pctWSocSec: percentage of households with social security income in 1989 (numeric - decimal) ', ' pctWPubAsst: pe...

  4. o

    Uniform Crime Reporting Program Data: Offenses Known and Clearances by...

    • openicpsr.org
    • dx.doi.org
    Updated Jun 5, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Jacob Kaplan (2017). Uniform Crime Reporting Program Data: Offenses Known and Clearances by Arrest, 1960-2016 [Dataset]. http://doi.org/10.3886/E100707V6
    Explore at:
    Dataset updated
    Jun 5, 2017
    Dataset provided by
    University of Pennsylvania
    Authors
    Jacob Kaplan
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Time period covered
    1960 - 2016
    Area covered
    United States
    Description

    V6 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. V5 release notes: Changes the word "larceny" to "theft" in column names - eg. from "act_larceny" to "act_theft."Fixes bug where state abbrebation was NA for Washington D.C., Puerto Rico, Guam, and the Canal Zone.Fixes bug where officers_killed_by_accident was not appearing in yearly data. Note that 1979 does not have any officers killed (by felony or accident) or officers assaulted data.Adds aggravated assault columns to the monthly data. Aggravated assault is the sum of all assaults other than simple assault (assaults using gun, knife, hand/feet, and other weapon). Note that summing all crime columns to get a total crime count will double count aggravated assault as it is already the sum of existing columns. Reorder columns to put all month descriptors (e.g. "jan_month_included", "jan_card_1_type") before any crime data.Due to extremely irregular data in the unfounded columns for New Orleans (ORI = LANPD00) for years 2014-2016, I have change all unfounded column data for New Orleans for these years to NA. As an example, New Orleans reported about 45,000 unfounded total burglaries in 2016 (the 3rd highest they ever reported). This is 18 times largest than the number of actual total burglaries they reported that year (2,561) and nearly 8 times larger than the next largest reported unfounded total burglaries in any agency or year. Prior to 2014 there were no more than 10 unfounded total burglaries reported in New Orleans in any year. There were 10 obvious data entry errors in officers killed by felony/accident that I changed to NA.In 1974 the agency "Boston" (ORI = MA01301) reported 23 officers killed by accident during November.In 1978 the agency "Pittsburgh" (ORI = PAPPD00) reported 576 officers killed by accident during March.In 1978 the agency "Bronx Transit Authority" (ORI = NY06240) reported 56 officers killed by accident during April.In 1978 the agency "Bronx Transit Authority" (ORI = NY06240) reported 56 officers killed by accident during June.In 1978 the agency "Bronx Transit Authority" (ORI = NY06240) reported 56 officers killed by felony during April.In 1978 the agency "Bronx Transit Authority" (ORI = NY06240) reported 56 officers killed by felony during June.In 1978 the agency "Queens Transit Authority" (ORI = NY04040) reported 56 officers killed by accident during May.In 1978 the agency "Queens Transit Authority" (ORI = NY04040) reported 56 officers killed by felony during May.In 1996 the agency "Ruston" in Louisiana (ORI = LA03102) reported 30 officers killed by felony during September.In 1997 the agency "Washington University" in Missouri (ORI = MO0950E) reported 26 officers killed by felony during March.V4 release notes: Merges data with LEAIC data to add FIPS codes, census codes, agency type variables, and ORI9 variable.Makes all column names lowercase.Change some variable namesMakes values in character columns lowercase.Adds months_reported variable to yearly data.Combines monthly and yearly files into a single zip file (per data type).V3 release notes: fixes a bug in Version 2 where 1993 data did not properly deal with missing values, leading to enormous counts of crime being reported. Summary: This is a collection of Offenses Known and Clearances By Arrest data from 1960 to 2016. Each zip file contains monthly and yearly data files. The monthly files contain one data file per year (57 total, 1960-2016) as well as a codebook for each year. These files have been read into R using the ASCII and setup files from ICPSR (or from the FBI for 2016 data) using the package asciiSetupReader. The end of the zip folder's name says what data type (R, SPSS, SAS, Microsoft Excel CSV, Stata) the data is in. The files are lightly cleaned. What this means specifically is that column names and value labels are standardized. In the original data column names were different between years (e.g. the December burglaries cleared column is "DEC_TOT_CLR_BRGLRY_TOT" in 1975 and "DEC_TOT_CLR_BURG_TOTAL" in 1977). The data here have standardized columns so you can compare between years and combine years together. The same thing is done for values inside of columns. For example, the state column gave state names in some years, abbreviations in others. For the code uses to clean and read the data, please see my GitHub file h

  5. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
National Institute of Justice (2025). Quantifying the Size and Geographic Extent of CCTV's Impact on Reducing Crime in Philadelphia, Pennsylvania, 2003-2013 [Dataset]. https://catalog.data.gov/dataset/quantifying-the-size-and-geographic-extent-of-cctvs-impact-on-reducing-crime-in-phila-2003-d9f6e
Organization logo

Data from: Quantifying the Size and Geographic Extent of CCTV's Impact on Reducing Crime in Philadelphia, Pennsylvania, 2003-2013

Related Article
Explore at:
Dataset updated
Mar 12, 2025
Dataset provided by
National Institute of Justicehttp://nij.ojp.gov/
Area covered
Philadelphia, Pennsylvania
Description

These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. This study was designed to investigate whether the presence of CCTV cameras can reduce crime by studying the cameras and crime statistics of a controlled area. The viewsheds of over 100 CCTV cameras within the city of Philadelphia, Pennsylvania were defined and grouped into 13 clusters, and camera locations were digitally mapped. Crime data from 2003-2013 was collected from areas that were visible to the selected cameras, as well as data from control and displacement areas using an incident reporting database that records the location of crime events. Demographic information was also collected from the mapped areas, such as population density, household information, and data on the specific camera(s) in the area. This study also investigated the perception of CCTV cameras, and interviewed members of the public regarding topics such as what they thought the camera could see, who was watching the camera feed, and if they were concerned about being filmed.

Search
Clear search
Close search
Google apps
Main menu