Optimizing Organic Waste Diversion Using a Vehicle Routing Model

Table of Contents

  1. Optimizing Organic Waste Diversion Using a Vehicle Routing Model
  2. Setting up Your Workspace
  3. Preparing the Data
  4. Skill Drill: Clip the Roads Layer to the City of Eureka
  5. Skill Drill: Add a Time Cost Attribute to the Roads Layer
  6. Skill Drill: Adding XY Data
  7. Skill Drill: Geocoding an Address  and Creating a CSV Table to Import As XY Data
  8. Creating A Network Dataset
  9. Setting up a Vehicle Routing Problem (VRP)
  10. Loading Orders into the Model
  11. Loading the Depot into the Model
  12. Adding Route Parameters into the Model
  13. Adding a Route Renewal into the Model
  14. Adjusting the Analysis Setting of Model
  15. Running the Vehicle Routing Model
  16. Skill Drill: Adding a Second Garbage Truck to the Model
  17. Skill Drill: Adjusting the Model to include Rear-Loading Trucks
  18. Skill Drill: Creating a Map of the Results

Loading Orders into the Model

As you will recall from the lecture videos, Modeling Network Paths, the orders are a network class that represents places where something is picked up or delivered. In this scenario, organic waste will be picked up from participating businesses. The participating businesses represent our ordersOrders also have attributes that influence cost or place limitations on the model. In this model, our orders have attributes that include a time window which indicates when organic waste pickups are allowed.  The service time attribute indicates the average time, in minutes, spent at each location during a pickup. The pickup quantities attribute indicates the average weight of the organic waste in pounds. Finally, the curb approach attribute limits the route direction at the order location. Right-click on Orders in the Network Analyst window and select Load Locations. From the drop-down menu next to Load From, select the businesses layer. Order 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 a right click and load locations.

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

An image of the load locations window.

Once the values above are entered, click OK.

PropertyFieldDefault Value
CurbApproach Right side of vehicle

The orders should now be loaded in two places. The orders in the Network Analyst window represent our model parameters. Any modification of the model parameters, or input to the model, are entered here. In the Table of Contents, the memory feature class, also named Orders, is now populated with the order attributes, the output from the model.

An image of the orders loaded in the model.
On the right, the model parameters (input) for the Orders are to the Network Analyst Window. On the left, empty memory feature classes in the Table of Contents are populated with attributes (output) from the model.

Take a moment to open the attribute table for the Orders memory feature class in the Table of Contents and inspect the information. The attribute table should look very similar to the businesses shapefile, but with some additional attribute fields. In many ways, memory feature classes look and behave like shapefiles. However, it is important to remember that the information in the attribute table of a memory feature class is temporary. Any changes to the model in the Network Analyst Window will also change the attributes in the memory feature class. To make any information from a memory feature class permanent, it must be exported. Close the attribute table for the Orders memory feature class. Next, you will load the Depot into the model.

An image of the orders attribute table
Some of the NULL values in the memory feature class attribute table will be replaced with data once the model is run.