Introduction
Many arsons go unresolved due to a lack of data sharing, primarily because information on these crimes tends to be isolated and uncorrelated. This leads to an inability to process cross-jurisdictional and cross-locale data as a whole, as data sharing and mining is less than ideal. The goal of the Fire Mapping project is to provide Volusia County Fire Services with a convenient and optimized means of sharing and processing arson data - helping to increase arrests, identifying the cause/origin of fires, and allowing improved reporting and ease of use. This should lead to an increased number of reporting agencies and reported incidents, allowing for better data and better predictions.
Implementation
The Fire Mapping system is to provide a means of investigating, tracking, projecting, and analyzing arson and accidental fires. The product combined with geomapping functions provides for extensive reporting ability, identification and analysis of arson-related patterns, predictive modeling for wild fires and fire investigations, suspect profiling and criminal activity predictions, tactical management tools to predict resource requirements for resource utilization, and more.
The interface provides for easy incident data entry and reporting, and optional linkage of supplemental data to incidents. Current categories for this data include arsons, casualties, equipment involved in ignition, fire data, structure fire data, involved mobile property, related arsonist profiles, and manpower per incident. Arsonist profiles can also be linked explicitly to incident data, and search capabilities will allow a predictive means of finding other possibly related arsonists.
Data Elements
1) Incident data
The primary segment of data elements consists of incident related data, which answers basic questions about individual fire incidents. One has the option of linking supplemental data to existing incidents via the incident linkage interface. Examples of supplemental elements include fire, structure fire, arson, related arsonist, involved mobile property, and manpower data.
Elements used in the incident segment correspond with data classifications provided by NFPA 901 (Uniform Coding for Fire Protection) as defined in the Fire Incident Coding Guide, and with additional items found on the Florida Fire Incident Report 902F.
|
§ Incident number (Primary Key)
§ Fire Department ID
§ Fire Department
§ Fire Chief
§ Exp. Num.
§ Date of incident
§ Day of week
§ Time of initial alarm
§ Arrival time
§ Time in service
§ Situation type found
§ Action taken
§ Mutual aid (Given, Received)
§ Fixed property use
§ Ignition factor
§ Correct address
§ Zip code
|
§ Census tract
§ Name of occupant (Last, First, Middle Initial)
§ Occupant’s telephone number
§ Method of alarm
§ District or station
§ Shift
§ Number of alarms
§ Number of responding personnel
§ Number of responding engines
§ Number of responding aerial apparatus
§ Number of responding apparatus – other
§ Officer in charge
§ Officer in charge - date of report entry
§ Member making report (if different from officer in charge)
§ Member making report - date of report entry
§ Additional remarks
|
1b) Status Flags
Status flags are available which serve to indicate whether or not an incident has supplemental data linked to it.
They answer the following questions:
§ Was this a fire?
§ Was this a structure fire?
§ Did casualties occur?
§ Was mobile property involved?
§ Was there equipment involved in the ignition?
§ Are there arsonists related to this incident?
2) Supplemental Incident data
Supplemental incident data elements correspond with the status flags listed in 1b. The incident number key allows linking back to the primary incident data.
Below the elements of these items are enumerated:
|
Arson
§ Property Owner
§ Time of Day
§ Latitude
§ Longitude
§ Area demographics
§ Property type
|
Casualties
§ Injuries - Fire service
§ Injuries - Other
§ Fatalities - Fire service
§ Fatalities – Other
|
|
Mobile Property Involved
§ License number
§ Year
§ Make
§ Model
§ Serial Number
|
Equipment Involved in Ignition
§ Year
§ Make
§ Model
§ Serial Number
|
|
Fire
§ Complex
§ Mobile property type
§ Area of fire origin
§ Equipment involved in ignition
§ Form of heat of ignition
§ Type of material ignited
§ Form of material ignited
§ Method of extinguishment
§ Level of fire origin
§ Estimated dollar loss
§ Property damage class
|
Structure Fire
§ Number of stories
§ Construction type
§ Extent of damage by flame
§ Extent of damage by smoke
§ Detector performance
§ Sprinkler performance
§ Type of material generating most smoke
§ Avenue of smoke travel
§ Form of material generating most smoke
|
Manpower per Apparatus
|
§ Engine
§ Tanker engine
§ Brush
§ Tanker
§ Rescue
§ Others
§ Mutual aid units
§ District (Station Number)
|
§ Engine manpower
§ Tanker engine manpower
§ Brush manpower
§ Tanker manpower
§ Rescue manpower
§ Others manpower
§ Mutual aid manpower
|
Arsonist Profile - may have more elements added, and existing elements broken into component attributes to facilitate extended searching capabilities.
|
§ Full Name
|
|
§ Address
|
|
§ Event Related (can be multiple)
|
|
§ Method of operation
|
|
§ Physical Description
|
|
§ Personal Information
|
|
§ Arsonist Number
|
Water Supply - These elements are linked to incidents for reporting purposes, and eventual predictive modeling of water supply needs.
|
§ Fire Hydrant
|
|
§ Horizontal Unit
|
|
§ Drafting Site
|
|
§ Tanks
|
|
§ Dry Hydrant
|
|
§ Tankers
|
Related Arsonist
Links incident to arsonist profile, and contains information about an arsonist's relation to an incident. This is a separate element because it is possible that multiple arsonists may be suspects for a particular incident, and a single arsonist may be related to multiple incidents as well. This will allow the system to retain unique relationship information for these cases.
3) Incident map data - These data elements correspond with items listed in the DSTATS table provided by VCFS. They allow linkage of incidents to corresponding map data.
|
§ Longitude
|
|
§ Latitude
|
|
§ Grid
|
|
§ Code
|
|
§ Call Taker Initials
|
|
§ Fire Area
|
|
§ Dispatcher
|
|
§ Hour of Day
|
|
§ Building
|
|
§ Map Info ID
|
4) Code and label data - These tables contain code and label pairs for use in detailed reports and for reference in form entry. Codes and labels correspond with elements outlined in NFPA 901, and allow for easy classification of fire incident data.
§ Fixed property use - codes and descriptions
§ Situation types - codes and descriptions of situation classifications
In addition, another code and label element is available which serves to allow recognition of district names and quadrants by reference number.
§ Districts - station numbers, names, and quadrants
5) Audit Trail - This table data is used for logging purposes. It allows for the ability to see who has changed what incident data, and when they did so.
§ Event Date - Date and time of operation
§ DML Type - Select, Insert, or Update operation
§ Username - User responsible for operation on database
All of these data items correspond with tables that will be modified to include and exclude elements as we decide upon what will be necessary for the purposes of this project.
6) References - These are references for the necessary system development.
§
§
Comments (0)
You don't have permission to comment on this page.