Fire Incidents in City of Austin Full Purpose which AFD responded on (does not include medical calls). Metadata below: Data Descriptions MasterIncidentNumber = unique identifier for individual incidents. If you encounter multiple rows with same MasterIncident number, it is b/c that incident had a multi-unit response. Please refer to RespondingUnit to determine the number of units responding to the individual incident. CalendarYear = calendar year in which individual incident occurred Month = month in which individual incident occurred DayOfMonth = calendar date in which individual incident occurred (Ex: 10 = 10th day in month) Call_Type = generalized description of incident type for individual incidents. Battalion = Battalion in which individual incident occurred. A Battalion is a geographic boundary used for management of stations (Ex: Station 1, 2, 3, 4 are in Battalion 1) Jurisdiction = Boundary of jurisdiction/department in which individual incident occurred. AFD = City of Austin Full Purpose ResponseArea = Small geographic boundary (often tied to a specific stations) in which individual incident occurred. Ex: 00-0101 is a ResponseArea for Station 1. Also referred to as Fire Box. TSUPResponseStatus = Level of response. Code 1 = no lights/sirens, travels speedlimit. Code 3 = lights/sirens, will travel faster than speedlimit. Priority Description = Level of Priority of incident. Number equals priority (3 = Priority 3), letter equals general incident type (F=Fire) Responding Unit = Units which responded to individual incident District = Boundary of City Council single-member district in which individual incident occurred Latitude = non-decimal latitude. Please use this formula to calculate for GIS geolocating = latitude *0.000001 Longitude = non-decimal longitude. Please use this formula to calculate for GIS geolocating = longitude * -.000001

Fire Incident data within City of Austin. Fire Incidents ONLY - no medical, hazmat, rescues, or other problem types. Calendar Year 2014

This dataset contains AFD's Standard of Coverage (SOC) results for calendar years 2022-2024. AFD's goal is to reach the resident/incident within 8 mins (from phone pickup to first arriving unit), 90% of the time. The dataset only includes emergency incidents (priority 1-3, 4M) that fell within AFD's service area (City of Austin full purpose and contracts for service). Response time results are grouped by Response Area Polygons (RAP) --- this is a geographical boundary which often reflects the area the station/unit would be the first responding unit. Disclaimer: The Austin Fire Department does not assume liability for any errors in the data or decisions taken by the recipient. The information provided should be used for general purposes only

,This dataset contains all Fire Department incidents responded to by the Town of Cary from January 1, 2016 to January 31, 2021. The dataset only contains calls that have been completed and reviewed. As a result, incident reports may take 1 - 5 business days to complete, based on the complexity of the call.,Incidents are reported in accordance with the National Fire Incident Reporting System (NFIRS).,This dataset is an archive - it is not being updated.,

The 2001 US Fire Administration Fire (USFA) Fire Incident & Cause Data was provided by the U.S. Fire Administration's (USFA) National Fire Data Center's (NFDC's) National Fire Incident Reporting System has numerous data elements that detail fire incidents for example the fire department fire incident the occupants structure and equipment used hazard material involved and casualty details.

This dataset contains the monthly summary data indicating incident occurred in each fire station response area. The summary data is the incident count broken down by call type group for each fire station response area. Update Frequency - Twice a month on the 1st and 15th date each month.

The 2004 US Fire Administration Fire (USFA) Fire Incident & Cause Data was provided by the U.S. Fire Administration's (USFA) National Fire Data Center's (NFDC's) National Fire Incident Reporting System has numerous data elements that detail fire incidents for example the fire department fire incident the occupants structure and equipment used hazard material involved and casualty details.

The 1999 US Fire Administration Fire (USFA) Fire Incident & Cause Data was provided by the U.S. Fire Administration's (USFA) National Fire Data Center's (NFDC's) National Fire Incident Reporting System has numerous data elements that detail fire incidents for example the fire department fire incident the occupants structure and equipment used hazard material involved and casualty details.

The 2007 US Fire Administration Fire (USFA) Fire Incident & Cause Data was provided by the U.S. Fire Administration's (USFA) National Fire Data Center's (NFDC's) National Fire Incident Reporting System has numerous data elements that detail fire incidents for example the fire department fire incident the occupants structure and equipment used hazard material involved and casualty details.