Location information for Austin Fire stations

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

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

Fire Incidents in City of Austin Full Purpose which AFD responded on (does not include medical calls).

See Attachment for Metadata PDF.

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

Community Wildfire Protection Plan

The City of Austin’s Wildfire Database and Risk Models were developed to support wildfire planning and mitigation efforts in the City of Austin. The areas in Austin most likely to be impacted by wildfire are referred to as the Wildland Urban Interface. This data helps identify the potential impacts of wildfire to a diverse set of values ranging from the built environment and Critical Infrastructure to habitat and green infrastructure. A full description of the Risk model can be access through this link. http://www.austintexas.gov/sites/default/files/files/hsem/Section_4_-_Risk_Assessment.pdf

The Data was collected and analyzed by Joseph White Fire Behavior Researcher with Baylor University. It was derived from numerous sources as listed in the CWPP Risk Assessment Guide http://www.austintexas.gov/sites/default/files/files/hsem/Section_9_-_References.pdf

The data was created during the CWPP development process starting in April of 2013 and was refined up to the adoption of the CWPP and data in November of 2014.

The goal is to update the data every 5 years or as more updated data becomes available.

The dataset contains AFD dispatched fire incident records from calendar year 2021-2023.

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.

Future Fire Station Map - areas within City of Austin (full purpose) which are in need of a fire station.

Analysis takes into account: population, building sq footage, development, response times, incident volume, homes at risk for wildfire and flooding, and ISO ratings.

Areas in BLUE are immediate/urgent needs. These areas have significant development, increased population, and
response times which are substantially below AFD's goal of
8 mins (call receipt to on-scene, 90%).

Areas in GOLD are defined as 'horizon areas'. These area have development, increased population, and response
times which are below AFD's goal of 8 mins (call receipt to
on-scene, 90%). If additional development or population occur,
area's ranking could increase.

Analysis performed by Austin Fire Department and utilized 2017 data. Map finalized January 2018.

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

Standard of Coverage for Calendar Year 2016 (January 2016 - December 2016). AFD's goal is to reach the resident/incident within 8 mins (from phone pickup to first arriving unit), 90% of the time. Info is grouped by Response Area Polygon (RAP) --- this is a geographical boundary which often reflects the area the station/unit would be the first responding unit. This data can be joined to the AFD RAP layer, which is in GIS format.

Standard of Coverage for Calendar Year 2017 (January 2017 - December 2017). AFD's goal is to reach the resident/incident within 8 mins (from phone pickup to first arriving unit), 90% of the time. Info is grouped by Response Area Polygon (RAP) --- this is a geographical boundary which often reflects the area the station/unit would be the first responding unit. This data can be joined to the AFD RAP layer, which is in GIS format.