<p>Fire Department responses to calls for service</p> <b>Import Dataset Updates - Jan. 19, 2024!</b> <p>The Bloomington Fire Department switched to a new RMS starting July 1st 2023. The ITS Applications team preserved continuity between the new and old system. This means new data will be found in this dataset and updated daily but slight tweaks have been made to union the old with the new.</p> <p>Column notes:</p> <p>Response_time is the difference between arrived_at and alarm_at in minutes.</p> <p>Please reach out to <a href="mailto:jeremy.schneider@bloomington.in.gov">jeremy.schneider@bloomington.in.gov</a> for any questions regarding data management of the Fire Incidents dataset.</p>
This dataset has the following 19 columns:
| Column Name | API Column Name | Data Type | Description | Sample Values |
|---|---|---|---|---|
| incident_number | inci_no | text | Incident number: System-generated unique identifier assigned to a response to a call for service. The format is 'YY-#######' where YY= last two digits of the 'notif_datetime' field's year; #######= the unique sequence number associated with the incident. For example, the first incident recorded in 2021 would have an inci_no of '21-0000001'. | 23-2300306 23-2301597 20-2000102 BFD-2024-BF00818 23-2302480 view top 100 |
| unit | unit | text | The fire apparatus that responded to the call. The values are entered manually. | T-1 E-1 E-3 E-5 E-4 view top 100 |
| incident_type | inci_type | number | Incident type: A 3-digit code defined by the National Fire Incident Reporting System that automatically correlates to the 'inci_desc' field | 311 321 743 745 611 view top 100 |
| incident_type_description | inci_desc | text | Incident description: The description of the type of incident to which crews responded. The descriptions are correlated with the field 'inci_type'. | Medical assist, assist EMS crew EMS call, excluding vehicle accident with injury Smoke detector activation, no fire - unintentional Alarm system activation, no fire - unintentional Dispatched & cancelled en route view top 100 |
| alarm_at | alm_datetime | calendar_date | Alarm date-time: Dispatch system-generated timestamp of when dispatch received the call for service. The validity of this field is in question as it equals 'notif_datetime' 100% of the time. | 2023-01-18T10:31:21.000 2023-04-05T10:25:29.000 2020-01-10T12:03:53.000 2024-02-14T14:57:16.000 2022-11-11T00:03:43.000 view top 100 |
| created_at | created_at | calendar_date | 2024-02-14T17:39:42.000 2024-05-06T23:06:59.000 2023-08-30T05:45:57.000 2024-04-02T13:40:51.000 2024-05-24T22:16:09.000 view top 100 | |
| updated_at | updated_at | calendar_date | 2024-02-14T20:39:01.000 2024-05-07T00:06:01.000 2024-03-19T22:48:22.000 2024-05-25T00:26:26.000 2024-04-02T18:46:02.000 view top 100 | |
| dispatch_notified_at | notif_datetime | calendar_date | Notification date-time: Dispatch system-generated timestamp that contains the date and time when dispatch notified the Fire Department of the incident. This timestamp starts the clock for all of the time-based metrics for the department. | 2024-02-14T14:57:16.000 2024-05-06T22:12:20.000 2018-05-18T09:20:24.000 2023-12-02T19:28:23.000 2024-03-19T10:30:41.000 view top 100 |
| address | address | text | Address: Dispatch system-generated exact address for the location of the incident. | 3100 S WALNUT STREET 1725 E 3RD 215 S WESTPLEX W 3RD 2440 S HENDERSON view top 100 |
| city | city | text | City: Dispatch system-generated city in which the incident occurs. | BLOOMINGTON Bloomington ELLETTSVILLE Bedford Bloomingto view top 100 |
| state | state | text | State: Dispatch system-generated state in which the incident occurs. | IN view top 100 |
| zip | zip | text | Zipcode: Dispatch system-generated zipcode in which the incident occurs. | 47408.0 47401.0 47404.0 47403.0 47402.0 view top 100 |
| response_time | resp_time | number | Response time in minutes: Calculated field that subtracts the value in 'notif_datetime' from the value in 'arv_datetime' and rounds to the nearest whole minute. | 4 3 5 6 7 view top 100 |
| latitude | latitude | number | 39.16494700 39.15112770 39.18456050 39.15857970 39.12818960 view top 100 | |
| longitude | longitude | number | -86.51239420 -86.49238910 -86.53744900 -86.53403510 -86.52720000 view top 100 | |
| dispatch_at | dispatch_at | calendar_date | 2023-12-02T19:30:01.000 2023-07-27T18:46:28.000 2024-04-28T22:40:48.000 2023-08-26T10:24:09.000 2024-02-20T01:03:09.000 view top 100 | |
| enroute_at | roll_datetime | calendar_date | Roll date-time: How generated? Timestamp of when the front tires of the fire apparatus are out of the station doors. | 2024-02-21T07:00:00.000 2017-06-12T21:31:11.000 2022-01-03T22:47:02.000 2020-01-10T12:06:57.000 2018-10-27T01:45:02.000 view top 100 |
| arrived_at | arv_datetime | calendar_date | Arrival date-time: How generated? Timestamp of when the fire apparatus is at a complete stop at the incident destination. | 2024-01-18T07:00:00.000 2024-01-23T07:00:00.000 2017-07-17T07:37:35.000 2024-04-05T08:00:00.000 2024-01-20T07:00:00.000 view top 100 |
| cleared_at | cleared_at | calendar_date | 2024-03-14T08:00:00.000 2024-05-06T08:00:00.000 2024-02-21T14:56:38.000 2023-10-28T19:40:00.000 2024-05-24T08:00:00.000 view top 100 |