GithubHelp home page GithubHelp logo

zuliani99 / fire_incident_dispatch_data_analysis Goto Github PK

View Code? Open in Web Editor NEW
0.0 1.0 0.0 33.73 MB

This project has the aim to analise and study some behavoiur under the Fire Incident Dispatch Dataset

HTML 100.00%
rstudio mapview fire-dataset

fire_incident_dispatch_data_analysis's Introduction

Fire Incident Dispatch Data Analysis

The Fire Incident Dispatch Data file contains data that is generated by the Starfire Computer Aided Dispatch System. The data spans from the time the incident is created in the system to the time the incident is closed in the system. It covers information about the incident as it relates to the assignment of resources and the Fire Department’s response to the emergency. To protect personal identifying information in accordance with the Health Insurance Portability and Accountability Act (HIPAA), specific locations of incidents are not included and have been aggregated to a higher level of detail.

In this analysis we have restricted the number of observations to the last 50.000, from 5th of September to 30th of the same month.

Dataset Desciption

The dataset is formed by the following columns:

  1. STARFIRE_INCIDENT_ID: An incident identifier comprising the 5 character julian date, 4 character alarm box number, 2 character number of incidents at the box so far for the day, 1 character borough code , 4 character sequence number.

  2. INCIDENT_DATETIME: The date and time of the incident.

  3. ALARM_BOX_BOROUGH: The borough of the alarm box.

  4. ALARM_BOX_LOCATION: The location of the alarm box.

  5. ALARM_BOX: The alarm box number.

  6. INCIDENT_BOROUGH: The borough of the incident.

  7. ZIPCODE: The zip code of the incident.

  8. POLICEPRECINCT: The police precinct of the incident.

  9. CITYCOUNCILDISTRICT: The city council district.

  10. COMMUNITYDISTRICT: The community district.

  11. COMMUNITYSCHOOLDISTRICT: The community school district.

  12. CONGRESSIONALDISTRICT: The congressional district.

  13. ALARM_SOURCE_DESCRIPTION_TX: The description of the alarm source.

  14. ALARM_LEVEL_INDEX_DESCRIPTION: The alarm level index.

  15. HIGHEST_ALARM_LEVEL: The highest alarm level.

  16. INCIDENT_CLASSIFICATION: The incident classification.

  17. INCIDENT_CLASSIFICATION_GROUP: The incident classification roll up group.

  18. FIRST_ASSIGNMENT_DATETIME: The date and time of the first unit assignment.

  19. FIRST_ACTIVATION_DATETIME: The date and time of the first unit acknowledgement of the assignment.

  20. FIRST_ON_SCENE_DATETIME: The date and time of the first unit at the scene of the incident.

  21. INCIDENT_CLOSE_DATETIME: The date and time that the incident was closed in the dispatch system.

  22. VALID_DISPATCH_RSPNS_TIME_INDC: Indicates that the components comprising the generation of the DISPATCH_RESPONSE_SECONDS_QY are valid.

  23. DISPATCH_RESPONSE_SECONDS_QY: The elapsed time in seconds between the INCIDENT_DATETIME and the FIRST_ASSIGNMENT_DATETIME.

  24. VALID_INCIDENT_RSPNS_TIME_INDC: Indicates that the components comprising the generation of the INCIDENT_RESPONSE_SECONDS_QY are valid.

  25. INCIDENT_RESPONSE_SECONDS_QY: The elapsed time in seconds between the INCIDENT_DATETIME and the FIRST_ON_SCENE_DATETIME.

  26. INCIDENT_TRAVEL_TM_SECONDS_QY: The elapsed time in seconds between the FIRST_ASSIGNMENT_DATETIME and the FIRST_ON_SCENE_DATETIME.

  27. ENGINES_ASSIGNED_QUANTITY: The number of engine units assigned to the incident.

  28. LADDERS_ASSIGNED_QUANTITY: The number of ladder units assigned to the incident.

  29. OTHER_UNITS_ASSIGNED_QUANTITY: The number of units that are not engines or ladders that were assigned to the incident.

Analysis Description

We will try to create two different analyses.

  1. The aim to predict the INCIDENT_RESPONSE_SECONDS_QY which is the time difference between the FIRST_ON_SCENE_DATETIME and INCIDENT_DATETIME.
  2. The focus is to predict the EMERGENCY_TIME which is the time difference between the FIRST_ON_SCENE_DATETIME and INCIDENT_CLOSE_DATETIME.

In both analyses we tried to use a linear regression model, however we will see that the assumptions for applying the linear regression are not met, thus we will simplify our project moving into classification, dividing in two or more ranges the two responses. In addition to this we will perform data exploration and cleaning, studying the presence or not of patterns of NA values and invalid values.

Note

If you want to execute the .Rmd file remember to change the working directory with the corresponding path.

Analysis Subdivision

  1. Part 1 - Dataset Analysis and Cleaning: here we explore and cleand the dataset
  2. Part 2 - Linear Regreasion: we try to fit a linear regression model
  3. Part 3 - Classification: cast the analysis to a classification task

fire_incident_dispatch_data_analysis's People

Contributors

zuliani99 avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.