Skip to main content
Geographic Information Systems

Return to Answer

Added example images for clarity.
Source Link
Chris W
Chris W
  • 15.8k
  • 2
  • 29
  • 47

The purpose of that box is to control how far generated polygons will extend beyond the outside edges of the network.

Consider a dense grid of streets as in a city. Service areas for facilities near the edge of the network may extend well beyond the range of your network with high enough break values. You are not concerned with areas beyond 'city limits', so you would check this box so that even if a polygon went hundreds of meters into the city, it would only extend a hundred (or whatever value you set) out of the city.

Consider a more rural network of roads that is sparse, such as a mountainous region, with many dead-ends or dangles (sort of like a plate of spaghetti). In this case your service areas will look very much like buffers of your road lines, and the value you input after checking the box will determine how far away from that edge (either side) the polygon will extend.

Two things to keep in mind:

  1. The way the software generates polygons considers all areas completely enclosed by network edges to be interior to the network. For this reason, particularly with sparse networks, you can end up with large areas included in your service area polygon that probably should not be (think of a large body of water in the middle of your city, or a mountain completely surrounded by roads but with no roads on or up the mountain itself). The trim polygons option will not affect these interior regions.
  2. The distance you set in the trim option has a relationship with your break values. If your trim distance is lower than your maximum break value, some areas will not be included in the polygons that otherwise would be if you did not use the option or set a higher value.

Because this is largely a graphical preference setting, and it is relatively easy to change, I would encourage you to experiment with it assuming the network solve itself doesn't take an extensive amount of time. All you have to do is solve your analysis with one setting, then go in and enable/disable or change the distance value and then resolve the network. If you make the value change large enough, you can quickly see the impacts it has.

Example Images:

Trim unchecked Trim Unchecked

Trim set to 300 ft Trim set to 300 ft

Trim set to 30 ft Trim set to 30 ft

Note: break values in the above images are based on drive time in minutes, and there are no areas on the network pictured that are not reachable within the maximum break value. However, because the trim distance is less than the max break value, as stated in point 2 it becomes increasingly difficult to actually see what polygon the network dangles in the lower left acutally fall in as the trim distance decreases. The images also show the issue with network interior regions - for my final map, I used lines instead of polygons for a more accurate representation.

The purpose of that box is to control how far generated polygons will extend beyond the outside edges of the network.

Consider a dense grid of streets as in a city. Service areas for facilities near the edge of the network may extend well beyond the range of your network with high enough break values. You are not concerned with areas beyond 'city limits', so you would check this box so that even if a polygon went hundreds of meters into the city, it would only extend a hundred (or whatever value you set) out of the city.

Consider a more rural network of roads that is sparse, such as a mountainous region, with many dead-ends or dangles (sort of like a plate of spaghetti). In this case your service areas will look very much like buffers of your road lines, and the value you input after checking the box will determine how far away from that edge (either side) the polygon will extend.

Two things to keep in mind:

  1. The way the software generates polygons considers all areas completely enclosed by network edges to be interior to the network. For this reason, particularly with sparse networks, you can end up with large areas included in your service area polygon that probably should not be (think of a large body of water in the middle of your city, or a mountain completely surrounded by roads but with no roads on or up the mountain itself). The trim polygons option will not affect these interior regions.
  2. The distance you set in the trim option has a relationship with your break values. If your trim distance is lower than your maximum break value, some areas will not be included in the polygons that otherwise would be if you did not use the option or set a higher value.

Because this is largely a graphical preference setting, and it is relatively easy to change, I would encourage you to experiment with it assuming the network solve itself doesn't take an extensive amount of time. All you have to do is solve your analysis with one setting, then go in and enable/disable or change the distance value and then resolve the network. If you make the value change large enough, you can quickly see the impacts it has.

The purpose of that box is to control how far generated polygons will extend beyond the outside edges of the network.

Consider a dense grid of streets as in a city. Service areas for facilities near the edge of the network may extend well beyond the range of your network with high enough break values. You are not concerned with areas beyond 'city limits', so you would check this box so that even if a polygon went hundreds of meters into the city, it would only extend a hundred (or whatever value you set) out of the city.

Consider a more rural network of roads that is sparse, such as a mountainous region, with many dead-ends or dangles (sort of like a plate of spaghetti). In this case your service areas will look very much like buffers of your road lines, and the value you input after checking the box will determine how far away from that edge (either side) the polygon will extend.

Two things to keep in mind:

  1. The way the software generates polygons considers all areas completely enclosed by network edges to be interior to the network. For this reason, particularly with sparse networks, you can end up with large areas included in your service area polygon that probably should not be (think of a large body of water in the middle of your city, or a mountain completely surrounded by roads but with no roads on or up the mountain itself). The trim polygons option will not affect these interior regions.
  2. The distance you set in the trim option has a relationship with your break values. If your trim distance is lower than your maximum break value, some areas will not be included in the polygons that otherwise would be if you did not use the option or set a higher value.

Because this is largely a graphical preference setting, and it is relatively easy to change, I would encourage you to experiment with it assuming the network solve itself doesn't take an extensive amount of time. All you have to do is solve your analysis with one setting, then go in and enable/disable or change the distance value and then resolve the network. If you make the value change large enough, you can quickly see the impacts it has.

Example Images:

Trim unchecked Trim Unchecked

Trim set to 300 ft Trim set to 300 ft

Trim set to 30 ft Trim set to 30 ft

Note: break values in the above images are based on drive time in minutes, and there are no areas on the network pictured that are not reachable within the maximum break value. However, because the trim distance is less than the max break value, as stated in point 2 it becomes increasingly difficult to actually see what polygon the network dangles in the lower left acutally fall in as the trim distance decreases. The images also show the issue with network interior regions - for my final map, I used lines instead of polygons for a more accurate representation.

Source Link
Chris W
Chris W
  • 15.8k
  • 2
  • 29
  • 47

The purpose of that box is to control how far generated polygons will extend beyond the outside edges of the network.

Consider a dense grid of streets as in a city. Service areas for facilities near the edge of the network may extend well beyond the range of your network with high enough break values. You are not concerned with areas beyond 'city limits', so you would check this box so that even if a polygon went hundreds of meters into the city, it would only extend a hundred (or whatever value you set) out of the city.

Consider a more rural network of roads that is sparse, such as a mountainous region, with many dead-ends or dangles (sort of like a plate of spaghetti). In this case your service areas will look very much like buffers of your road lines, and the value you input after checking the box will determine how far away from that edge (either side) the polygon will extend.

Two things to keep in mind:

  1. The way the software generates polygons considers all areas completely enclosed by network edges to be interior to the network. For this reason, particularly with sparse networks, you can end up with large areas included in your service area polygon that probably should not be (think of a large body of water in the middle of your city, or a mountain completely surrounded by roads but with no roads on or up the mountain itself). The trim polygons option will not affect these interior regions.
  2. The distance you set in the trim option has a relationship with your break values. If your trim distance is lower than your maximum break value, some areas will not be included in the polygons that otherwise would be if you did not use the option or set a higher value.

Because this is largely a graphical preference setting, and it is relatively easy to change, I would encourage you to experiment with it assuming the network solve itself doesn't take an extensive amount of time. All you have to do is solve your analysis with one setting, then go in and enable/disable or change the distance value and then resolve the network. If you make the value change large enough, you can quickly see the impacts it has.