Data
This dataset is the Fire Department Calls for Service fom DataSF. This dataset includes many aspects of the calls for services from response time to location of the call. The license for the data is as follows:
"This data is made available under the Public Domain Dedication and License v1.0 whose full text can be found at: www.opendatacommons.org/licenses/pddl/1.0/"
OpenData. 2020. Fire Department Calls for Service [CSV File]. Retrieved from https://data.sfgov.org/Public-Safety/Fire-Department-Calls-for-Service/nuek-vuh3 on Feb 12, 2020.
Some quick stats about the data defined from the website are:
**Note that this dataset is constantly being updated, so number like the rows, size of file, and checksum will be different depending on your retrieval time.
The columns defined on the site for the data shown below. Note that highlighted columns will be emphasized columns in the visualizations.
| # | Column | Description | Type | Values |
|---|---|---|---|---|
| 1 | Call Number | A unique 9-digit number assigned by the 911 Dispatch Center (DEM) to this call. These number are used for both Police and Fire calls. | Text | [200430004, 200424369,...] |
| 2 | Unit ID | Unit Identifier. For example E01 for Engine 1 or T01 for Truck 1. | Text | [66, E32, D2,...] |
| 3 | Incident Number | A unique 8-digit number assigned by DEM to this Fire incident. | Text | [10018420, 20018419,...] |
| 4 | Call Type | Type of call the incident falls into. See the list below. | Text | [Medical Incident, Alarms, Citizen Assist/Service Call, Odor (Strange / Unknown), Structure Fire, Electrical Hazard, Other] |
| 5 | Call Date | Date the call is received at the 911 Dispatch Center. Used for reporting purposes. | Date & Time | [04/12/2000-02/12/2020] |
| 6 | Watch Date | Watch date when the call is received. Watch date starts at 0800 each morning and ends at 0800 the next day. | Date & Time | [04/12/2020-02/12/2020] |
| 7 | Received DtTm | Date and time of call is received at the 911 Dispatch Center. | Date & Time | [2000 Apr 12 09:00:29 PM - 2020 Feb 11 11:59:15 PM] |
| 8 | Entry DtTm | Date and time the 911 operator submits the entry of the initical call information into the CAD system | Date & Time | [2000 Apr 12 09:01:40 PM - 2020 Feb 12 11:58:02 PM] |
| 9 | Dispatch DtTm | Date and time the 911 operator dispatches this unit to the call. | Date & Time | [2000 Apr 12 09:02:00 PM - 2020 Feb 12 11:59:22 PM] |
| 10 | Response DtTm | Date and time this unit acknowledges the dispatch and records that the unit is en route to the location of the call. | Date & Time | [2000 Apr 12 09:11:51 PM ...] (Includes Blanks) |
| 11 | On Scene DtTm | Date and time the unit records arriving to the location of the incident | Date & Time | [2000 Apr 12 09:14:11 PM ...] (Included Blanks) |
| 12 | Transport DtTm | If this unit is an ambulance, date and time the unit begins the transport unit arrives to hospital | Date & Time | [2000 Apr 12 09:38:18 PM ...] (Includes Blanks) |
| 13 | Hospital DtTm | If this unit is an ambulance, date and time the unit arrives to the hospital. | Date & Time | [2000 Apr 12 09:48:13 PM ...] (Includes Blanks) |
| 14 | Call Final Disposition | Disposition of the call (Code). For example TH2: Transport to Hospital - Code 2, FIR: Resolved by Fire Department | Text | [Other, Fire, Unable to Locate, SFPD, Patient Declined Transport, No Merit, Code 2 Transport, Cancelled, Against Medical Advice, Gone on Arrival, Code 3 Transport, ] |
| 15 | Available DtTm | Date and time this unit is not longer assigned to this call and it is available for another dispatch. | Date & Time | [2000 Apr 12 09:20:36 PM ...] (Includes Blanks) |
| 16 | Address | Address of midblock point associated with incident (obfuscated address to protect caller privacy) | Text | [800 Block of MARKET ST, 3200 Block of TARAVAL ST, 3400 Block of ALEMANY BLVD,...] |
| 17 | City | City of incident | Text | [San Francisco, SAN FRANCISCO, Yerba Buena, Presidio, PRESIDIO, Hunters Point,...] (Includes Blanks) |
| 18 | Zipcode of Incident | Zipcode of incident | Text | [94130, 94134,...] |
| 19 | Battalion | Emergency Response District (There are 9 Fire Emergency Response Districts) | Text | [B99, B03, B02,...] |
| 20 | Station Area | Fire Station First Response Area associated with the address of the incident | Text | [51, 48, 01,...] |
| 21 | Box | Fire box associated with the address of the incident. A box is the smallest area used to divide the City. Each box is associated with a unique unit dispatch order. The City is divided into more than 2,400 boxes. | Text | [4625, 2951, 2314,...] |
| 22 | Original Priority | Initial call priority (Code 2: Non-Emergency or Code 3:Emergency). | Text | [E, 2, 1, 3,...] |
| 23 | Priority | Call priority (Code 2: Non-Emergency or Code 3:Emergency). | Text | [3, 2, 1] |
| 24 | Final Priority | Final call priority (Code 2: Non-Emergency or Code 3:Emergency). | Text | [3, 2, 1] |
| 25 | ALS Unit | Does this unit includes ALS (Advance Life Support) resources? Is there a paramedic in this unit? | Boolean (True/False) | [True, False] |
| 26 | Call Type Group | Call types are divided into four main groups: Fire, Alarm, Potential Life Threatening and Non Life Threatening. | Text | [Non Life-threatening, Potentially Life-Threatening, Alarm, Fire,...] |
| 27 | Number of Alarms | Number of alarms associated with the incident. This is a number between 1 and 5. | Numeric | [1,...] |
| 28 | Unit Type | Unit type | Text | [ENGINE, MEDIC, TRUCK, PRIVATE, CHIEF, RESCUE SQUAD] |
| 29 | Unit sequence in call dispatch | A number that indicates the order this unit was assigned to this call | Numeric | [1, 2, 3, 4, 5, 7, 9, 10, 83, None...] |
| 30 | Location | Latitude and longitude of address obfuscated either to the midblock, intersection or call box | Coordinates | [(37.708085729939°, -122.485723865524°), (37.747591219936°, -122.387182780653°),...] |
| 31 | Fire Prevention District | Bureau of Fire Prevention District associated with this address | Text | [None, 1, 2, 5, 4,...] |
| 32 | Supervisor District | Supervisor District associated with this address | Text | [5, 6, 8, 1, 9,...] |
| 33 | Neighborhoods - Analysis Boundaries | Neighborhood District associated with this address, boundaries available here: https://data.sfgov.org/d/p5b7-5n3h | Text | [Western Addition, South of Market, Haigh Ashbury, Mission, Nob Hill, Tenderloin, Golden Gate Park,...] |
| 34 | RowID | Unique identifier used for managing data updates. It is the concatenation of Call Number and Unit ID separated by a dash | Text | [180291187-KM14, 180200966-E31,...] |
Filtering
The dataset was reduced to the last 5 years using the DataSF web interface. Data that is used the visualizations do not use null or malformed entries. No additional filtering or wrangling was done to the data for the visualizations.
Used rows
The fields of the dataset that were used for the visualizations are higlighted in the table above.
Additional Information
If anyone is interested in how the table was generated, feel free to look here. It is just a simple Python program that reads from a file called labels. The labels file is just the descriptions copied from the webpage.