Demand-Based Site Selection for Fire Stations Using a Network Allocation Model

Table of Contents

  1. Demand-Based Site Selection for Fire Stations Using a Network Allocation Model
  2. Setting up Your Workspace
  3. Preparing the Data
  4. Skill Drill: Clip the Roads Layer to the City of Arcata and McKinleyville
  5. Skill Drill: Add a Time Cost Attribute to the Roads Layer
  6. Skill Drill: Creating a CSV Table to Import As XY Data
  7. Skill Drill: Geocoding an Address  and Creating a CSV Table to Import As XY Data
  8. Skill Drill: Adding the Fire Incident History as XY Data
  9. Creating A Network Dataset
  10. Setting up a Network Allocation Model
  11. Loading Facilities into the Model
  12. Loading the Demand Points into the Model
  13. Adjusting the Analysis Setting of the Model
  14. Running the Network Allocation Model
  15. Skill Drill: Using the Maximize Attendance Problem Type
  16. Skill Drill: Adding Existing Fire Stations to the Model
  17. Skill Drill: Creating a Map of the Results

Loading the Demand Points into the Model

As you will recall from the lecture videos, Modeling Network Paths, the demand points are places served by the facility in some way. The exact nature of the demand points will depend on the service being provided. In this scenario, the history of incident responses serves as demand points for the proposed fire stations. The demand points have attributes that influence cost or place limitations on the model. In this model, the demand points need to be weighted so that certain types of incidents will have a higher priority. By default, each demand point has a value of 1 for weight. When determining which fire station will be chosen, the weights for all of the demand points within its time window cutoff are summed. The sum of the weights is called allocated weight. It represents the total demand allocated to the chosen facility. However, you will change the weights of certain types of calls by adding a weight field to the attribute table then populating the results with the following weights:

  • Assign a weight of 3 for incidents involving building fires, wildland fires, brush fire, and trash fires. In the incident history attribute table, the incident types are 111, 141, 142, and 151.
  • Assign a weight of 2 for incidents involving medical assistance and emergency medical services. In the incident history attribute table, the incident types are 311 and 3211.
  • Assign all other incident types a value of 1.

Start by adding a Weight field to the incident history layer. Use an attribute selection to select the records for each incident type. Then use the Field Calculator to populate weight value for the selected records. If you will recall from previous courses, you can access Field Calculator by right-clicking on the field name, Weight

In the Field Calculator, you need only enter the desired number to set the value. Click to view the image in a larger size.

Once the demand points are assigned the appropriate weights, you are ready to load them into the model. Right-click on Demand Points in the Network Analyst Window and select Load Locations. From the drop-down menu next to Load From, select the incident history layer. Facility parameters are defined under the Location Analysis Properties pane using two attributes, Field, and Default Value. If the layer does not have a field that matches the property, a default value may be entered instead.

An image of the Demand Point Load Locations Properties Window

Use the following values in the Location Analysis Properties. Keep the default values for any properties not listed here.

PropertyFieldDefault Value
CurbApproach Either side of vehicle

Once the values above are entered, click OK.