CRIME-RECOMMENDATION

Focus: Will be to update and recreate a crime analysis using an Transformer for learning purposes

1. Overview

Previously, the data is colled from from the LACITY website, uploaded it to an AWS database via Planet Scale. Recently, new documentation allows us to use API to fetch data from the source and upload into a SQL database.

2. Table of Contents

  1. Overview
  2. Table of Contents
  3. Background and Context
  4. Data Description
  5. Exploratory Data Analysis (EDA)
  6. Data Preprocessing
  7. Modeling and Analysis
  8. Model Evaluation
  9. Results and Discussion
  10. Conclusion and Future Work
  11. References and Acknowledgments

3. Background and Context

Los Angeles has recently experienced a perceived rise in both crime and homelessness, prompting a closer examination of the city’s crime data. This repository uses publicly available data from the LACITY website to investigate patterns, trends, and policy implications. By focusing on key metrics and visualizations, the analysis aims to provide actionable insights for residents, policymakers, and other stakeholders. Click her for link to source.

4. Data Description

Alt Text

  1. Data Source(s)
    • The primary dataset is from the LA City Crime Data (2020–Present) repository.
    • Additional socioeconomic or demographic data (if applicable) may be sourced from complementary public platforms, such as the U.S. Census Bureau.
  2. Data Format
    • The core crime dataset is available in CSV format, which can be easily imported into a variety of analytical tools and relational databases.
    • Any supplementary datasets may come in JSON, Excel, or API-based formats, depending on the source.
  3. Data Fields
    • DR Number: A unique identifier for each reported incident.
    • Date/Time: Specifies when the crime occurred and allows for temporal trend analysis.
    • Location: Includes address or coordinates (Latitude, Longitude) crucial for spatial mapping.
    • Crime Classification: Type or category of the crime (e.g., Burglary, Assault).
    • Reporting District: Police reporting area code, enabling analysis at the local precinct level.
    • Victim Age/Gender/Race (if available): Demographic details that help understand victim profiles.
    • Weapon Used (if available): Indicates whether a weapon was involved, aiding severity assessments.
  4. Data Size
    • The crime dataset is continually updated, leading to frequent changes in row counts. As of the latest retrieval, it includes tens of thousands of records spanning multiple crime categories.
    • With multiple fields in each record, the memory footprint can range from a few megabytes to larger, depending on the inclusion of geospatial data and historical depth.
  5. Potential Limitations
    • Reporting Bias: Certain crimes may be underreported, skewing perceived distribution and severity.
    • Missing or Incomplete Fields: Key attributes (e.g., demographic info, weapon usage) may not always be reported.
    • Contextual Factors: Data does not directly include socioeconomic or policy-related variables, which could be vital for interpreting crime trends.
    • Temporal Gaps: Depending on data collection intervals, some incidents may take time to appear in the dataset, potentially impacting real-time analyses.

5. Exploratory Data Analysis (EDA)

Use visuals and statistics to explore trends, patterns, and relationships. Summarize the key takeaways.

6. Data Preprocessing

Explain your cleaning, transformation, and feature engineering processes.

7. Modeling and Analysis

Discuss the algorithms or techniques applied and why you chose them.

8. Model Evaluation

Evaluate model performance using appropriate metrics and validation methods.

9. Results and Discussion

Present key findings, using tables and figures to illustrate model performance.

10. Conclusion and Future Work

Summarize the insights and recommend next steps.

DASHBOARD

Dashboard Preview

11. References and Acknowledgments

List relevant references and any resources that aided the project.