ArcGIS REST Services Directory Login
JSON | SOAP

fire/FireStationRelocationModels (MapServer)

View In:   ArcGIS JavaScript   ArcGIS Online Map Viewer   ArcGIS Earth   ArcGIS Pro

Service Description:

Background

There are two fire stations within the City of Boulder that do not meet space requirements for expanding fleets. These are Station 2, located in Central Boulder at Broadway and Baseline, and Station 4, located in South Boulder at Broadway and Darley Ave. Boulder Fire Rescue (BFR) wants to relocate these stations, and they asked the Enterprise Data Team (EDT) to build a tool to help visualize how moving a station would affect incident travel times. So, while space requirements are the original reason to relocate, BFR sees an opportunity to reduce incident travel times throughout the city while simultaneously equalizing response workload between stations.

Data

After developing a linear regression model to predict travel times for different station configurations on an incident-by-incident basis, the EDT aggregated those results to Uber H3 hexes at Resolution 9. Some metrics include:

- Location of each station under a given configuration

- The total number of incidents that occurred within the hex between 2018-2022

- The number/percentage of incidents within the hex predicted to be within 4 minutes of a station

- The most frequently predicted responding station

The repository containing the analysis pipeline can be found here.



Map Name: FireStationRelocationModels

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers: Description:

Background

There are two fire stations within the City of Boulder that do not meet space requirements for expanding fleets. These are Station 2, located in Central Boulder at Broadway and Baseline, and Station 4, located in South Boulder at Broadway and Darley Ave. Boulder Fire Rescue (BFR) wants to relocate these stations, and they asked the Enterprise Data Team (EDT) to build a tool to help visualize how moving a station would affect incident travel times. So, while space requirements are the original reason to relocate, BFR sees an opportunity to reduce incident travel times throughout the city while simultaneously equalizing response workload between stations.

Data

After developing a linear regression model to predict travel times for different station configurations on an incident-by-incident basis, the EDT aggregated those results to Uber H3 hexes at Resolution 9. Some metrics include:

- Location of each station under a given configuration

- The total number of incidents that occurred within the hex between 2018-2022

- The number/percentage of incidents within the hex predicted to be within 4 minutes of a station

- The most frequently predicted responding station

The repository containing the analysis pipeline can be found here.



Service Item Id: d8b223589bbe451496818b6833ed3f78

Copyright Text: City of Boulder

Spatial Reference: 102100  (3857)


Single Fused Map Cache: false

Initial Extent: Full Extent: Units: esriMeters

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info: Supports Dynamic Layers: true

MaxRecordCount: 4000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, geoJSON, PBF

Supports Query Data Elements: true

Min Scale: 0

Max Scale: 0

Supports Datum Transformation: true



Child Resources:   Info   Dynamic Layer

Supported Operations:   Export Map   Identify   QueryLegends   QueryDomains   Find   Return Updates