This topic describes the service area analysis layer's feature classes and analysis properties.
Facilities feature class
The Facilities feature class stores the input facilities around which the output service area polygons are created. You can provide input field values that the service area analysis layer will reference when solving the analysis; the feature class also stores output field values once the analysis is complete.
The following tables describe the input fields and input/output fields of the Facilities feature class:
Facilities: Input fields
The system-managed ID field.
The geometry field indicating the geographic location of the network analysis object.
The name of the network analysis object.
(For instance, Attr_Minutes, where Minutes is the travel cost)
This field stores the additional time, distance, or other travel cost for the facility. Adding a value to this field reduces the reach of the service area.
If you're finding the service areas for three facilities using drive time as the cost, the field Attr_ DriveTime can be used to store the amount of time spent at the facility.
For example, when calculating service areas that represent fire station response times, Attr_ DriveTime can store the turnout time, which is the time it takes a crew to put on the appropriate protective equipment and exit the fire station, for each fire station. Assume Fire Station 1 has a turnout time of 1 minute and Fire Station 2 has a turnout time of 3 minutes. If a 5-minute service area is calculated for both fire stations, the actual service area for Fire Station 1 would be 4 minutes (since 1 of the 5 minutes would be required as turnout time). Similarly, Fire Station 2 would have a service area of only 2 minutes from the fire station.
The value you enter affects the analysis only when the [Cost] part of the field name (Attr_[Cost]) matches the cost attribute chosen for the analysis layer or travel mode. For example, if you add a 5 to Attr_DriveMinutes, but the cost attribute used in the analysis is TruckTime, the additional 5 minutes aren't included in the analysis results; however, if you change the network cost attribute to DriveMinutes, which corresponds with Attr_DriveMinutes, the 5 minutes you entered are added to the results.
(For instance, Breaks_DriveTime, where DriveTime is the travel cost for the network)
You can store different polygon break values for each service area facility in the Breaks_[Cost] field. Given two facilities, this means you can generate 5- and 10-minute service area polygons for one facility and 6-, 9-, and 12-minute polygons for another facility.
Multiple breaks should be specified using a space-separated string. For example, to specify 6-, 9-, and 12-minute polygons for a given facility, the field value should be 6 9 12.
The value specified in the Breaks_[Cost] field overrides the Cutoffs analysis layer setting. If no value for the Breaks_[Cost] field is specified, service area polygons are generated for the facility based on the Cutoffs setting.
Network location fields
Together, these properties describe the point on the network where the object is located.
The CurbApproach field specifies the direction a vehicle may arrive at and depart from the facility. If the curb approach is confined to one side of the vehicle, it could further limit the reach of the service area.
There are four options for the CurbApproach value:
Facilities: Input/output fields
Indicates the status of the point with respect to its location on the network and the outcome of the analysis. The possible values are the following:
Polygons feature class
The Polygons feature class stores the resultant service area polygons, which cover the areas of the network that can be reached within the given time, distance, or other travel-cost cutoff. This feature class doesn't provide any inputs to the analysis layer—it stores output information only.
To generate the Polygons feature class, on the Service Area Layer tab, in the Output Geometry group, set Output Shape Type to Polygons or Polygons and Lines .
Polygons: Output fields
The following table lists the output fields of the Polygons feature class:
The system-managed ID field.
The geometry of the polygon, which is stored internally.
The name of the service area polygon is based on the name of the associated facility and the cutoff range; for instance, Headquarters : 0.0 – 5.0 would represent a polygon that covers all traversable edges within 5 minutes from the facility, Headquarters.
The unique ID of the associated facility.
The lower bound of the polygon's break range.
The upper bound of the polygon's break range.
Lines feature class
The Lines feature class stores the resultant service areas as linear features and covers the streets, or network edges, that can be reached within the given time, distance, or other travel-cost cutoff. Lines are a truer representation of a service area than polygons since service area analyses are based on measurements along the network lines.
The Lines feature class doesn't provide any inputs to the analysis layer; it serves to store outputs only.
Service area lines are not generated by default during a service area analysis, but you can choose to generate them. On the Service Area Layer tab, in the Output Geometry group, set Output Shape Type to Lines or Polygons and Lines .
Lines: Output fields
The following table lists the output fields of the Lines feature class:
The system-managed ID field.
The geometry of the line, which is stored internally.
The unique ID of the associated facility.
(for instance, FromCumul_Miles, where Miles is the travel cost)
This field contains the cumulative cost of the path from the facility to the beginning of the line feature. The cost of the adjacent junction at the beginning of the line is included in this value. This field is generated for the cost attribute and any accumulation attributes.
(for instance, ToCumul_Miles, where Miles is the travel cost)
This field contains the cumulative cost of the path from the facility to the end of the line feature. The cost of the adjacent junction at the end of the line is excluded from this value. This field is generated for the cost attribute and any accumulation attributes.
Each service area line traverses a feature from a network source feature class—a feature class used to create the network dataset on which the service area analysis is performed. This field specifies the unique ID of the source feature class the traversed feature is a part of.
The ObjectID of the underlying source feature that is traversed by the service area.
Specifies where along the underlying source feature the service area line begins.
Specifies where along the underlying source feature the service area line ends.
Service area analysis layer properties
The following subsections list properties you can set on the analysis layer. They are on the Service Area Layer tab, which is available only if your service area layer or one of its sublayers is selected in the Contents pane.
Run is in the Analysis group. Click it, after you load input features and set analysis properties, to solve the service area analysis.
Import Facilities is in the Input Data group. Click it to load features from another data source, such as a point feature layer, into the Facilities feature class.
Click Import Point Barriers , Import Line Barriers , or Import Polygon Barriers to load features from another data source, such as another feature layer, into one of the barriers feature classes (point barriers, line barriers, or polygon barriers).
Click the Create Features button to open the Create Features pane. Select from the available templates to create features in the current map.
The Mode drop-down list allows you to choose a travel mode, which is a group of settings that together model the movement of pedestrians, cars, trucks, or another travel mode. The choices available in the drop-down list depend on the travel modes that are configured on the network data source that the network analysis layer is referencing.
You can choose to create a service area by accumulating travel time or other cost in the direction away from or toward the facility, as follows:
- Away From Facility—The service areas are measured from the facility out to the periphery.
- Towards Facility—The service areas are measured from the periphery in toward the facility.
On a network with one-way restrictions and different travel times based on direction of travel, this would result in different service areas. The direction you should choose depends on the nature of your service area analysis. The service area for a pizza delivery store, for example, should be created for travel that spans out from the facility (Away from Facilities) since pizzas are delivered from the store to the customer. Alternatively, a hospital would choose Towards Facilities since the urgent part of the trip for a patient is going to the hospital, not returning home afterward.
The Direction setting affects how Network Analyst interprets the time and date you specify in Type, Time, and Date.
- Away From Facility—The time and date indicate when the service area starts at the facility.
- If Direction is set to Towards Facility, the time and date indicate when the service area finishes at the facility.
If there is any service time at a facility (that is, the facility's Attr_[Cost] field has a positive value), the service time is included in the results immediately before the finish time when travel is toward facilities, or immediately after the start time when travel is away from facilities.
The extent of the service area to be calculated is specified with the Cutoffs text box. For instance, a cutoff of 10 creates service areas of 10 units (for instance, 10 minutes or 10 miles) from the facilities. The unit for the chosen travel mode is indicated to the right of the Mode drop-down list.
The Cutoffs property is used when a facility's Breaks_[Cost] field value is null. Suppose you have two facilities, A and B, for which you want to find a drive-time area. Facility A has a Breaks_DriveTime value of 3. Facility B has no value for its Breaks_DriveTime field. When you find the service area with Cutoffs set to 5 (minutes), facility A will have a 3-minute service area, and facility B will have a 5-minute service area.
Cutoffs assigns default values to facilities that do not have numeric values stored in the Break_[Cost] field.
Multiple polygon breaks can be set to create concentric service areas. For instance, if you want to find 2-, 3-, and 4-minute service areas for each facility, you would type 2, 3, 4 in the Cutoffs text box.
Accumulate Cost Attributes
The Accumulate Cost Attributes drop-down menu in the Travel Settings group can be used to configure accumulated cost attributes. The drop-down menu is unavailable if the network data source is a service, the output geometry types do not include lines, or there are no cost attributes. The attributes are grouped by unit domain shown as the group header (for example, Time or Distance). A checked check box indicates that the analysis layer will accumulate the checked attribute during the solve.
When multiple analysis layers of the same layer type are selected, the check box shows a mixed state if all layers do not share the same checked status for one attribute. In the following image, the WeekendFallbackTravelTime attribute is selected for multiple layers, so it has a check mark.
If all selected layers share the checked status for an attribute, the check box shows that state.
Date and Time
The Arrive Depart Date-Time Type drop-down list in the Date and Time group is available when the cost units are time based. From the drop-down list, choose whether a specific time and date value is given to indicate the time that the route or routes depart from their first stop. The primary reason for setting a specific time and date is to solve the analysis using dynamic traffic conditions or public transit schedules; however, to use traffic or public transit in the analysis, the network dataset or route service must include traffic data or public transit.
The options in the drop-down list are as follows:
Not Using Time—Regardless of whether the network data source includes time-based data, the results are based on static travel times—the travel times on a network edge don't vary throughout the day. The Time of Day and Date text boxes are unavailable.
Date & Time—Specify the time as a time of day and calendar date. The Time of Day and Date text boxes are available to provide this information.
Day of Week—Specify a time of day and day of the week. The Time of Day and Date text boxes are available to provide this information. Set the day of the week by typing one of the following values in the Date text box:
Today—Specify a time, and the day is assumed to be the current date. The Time of Day text box is available to provide the time of day, and the Date text box is set to Today and is unavailable so it can't be changed.
Now—When you run the analysis, the time and date are set to the current time and date. This is useful if your network dataset is configured with live traffic data, and the routes are distributed to drivers for implementing immediately after running the analysis. The Time of Day and the Date text boxes are unavailable so they can't be changed.
From the Reference Time Zone drop-down list you can choose which time zone should be used in the analysis. The options are as follows:
- Local Time at Locations
- UTC (Universal Coordinated Time)
Polygons, lines, and polygons and lines
Choose whether to generate polygons , lines , or polygons and lines as output.
Lines and Polygon and Lines output is not available if the network data source is a service on a version of Portal for ArcGIS which does not support generating lines
Polygon detail level
You can specify the level of detail you want for output polygons by setting the Polygon Detail Level property.
Generalized—This option is available when your network dataset includes a hierarchy attribute.
In a hierarchical service area analysis, the solver prefers higher-order edges to the lowest-order edges. This means that if a facility is located on a local road (the lowest level in a hierarchy), the solver spans out on the local roads in that area, but it tries to step up the hierarchy to secondary and primary roads. Once on secondary and primary roads, the solver ignores local roads throughout the rest of the service area. It ignores secondary and local roads once it has stepped up to primary roads. Mainly because of this hierarchical approach, nonhierarchical service areas tend to be superior in quality to their hierarchical counterparts.
Standard Precision—Standard polygons are generated quickly and are fairly accurate, but quality deteriorates somewhat as you move toward the borders of the service area polygons. Outputting standard-detail polygons may result in islands of unreached network elements, such as roads, being covered.
High Precision—Choose this option to get the most detailed polygons. Holes within the polygon may exist; they represent islands of network elements that couldn't be reached without exceeding the cutoff impedance or due to travel restrictions. Expect high-precision polygons to take the longest amount of time to generate.
You will get holes only if you use High Precision polygons and the Overlap or Dissolve output geometry setting. The Split setting will not generate holes within the polygons.
Creating a service-area index on your network dataset can optimize processing time and improve the quality of standard- and high-precision polygons.
There are several options available for generating polygons or lines for multiple facilities:
- Overlap—This option creates individual polygons for each facility. The polygons can overlap each other.For overlapping lines, portions of the network that are within reach of more than one facility will have a line for each facility.
- Dissolve—This option merges the polygons of multiple facilities that have the same cutoff values into one polygon. If the polygons of a given break value don't touch, they are nonetheless merged into one multipart polygon. This option does not apply to lines.
- Split—This option creates individual polygons that are closest for each facility. The polygons do not overlap each other. For split lines, none of the lines overlap each other, and a line is always assigned to the nearest facility even if more than one facility can reach it.
Polygon rings or disks
You can choose to create concentric service area polygons as disks or rings.
- Rings—Output polygons extend between the nearest cutoff values only. They do not include the area of smaller breaks. This creates polygons between consecutive breaks.
- Disks—Output polygons extend from the facility to the cutoff. If you create 5- and 10-minute service areas, the 10-minute service area polygon will include the area under the 5-minute service area polygon as well as the area from the 5-minute to the 10-minute break.
Exclude edge sources
You can use the Exclude Edge Sources drop-down menu and choose to exclude certain network dataset edge sources when generating service area polygons. Polygons will not be generated around the excluded sources, even though they are traversed in the analysis.
Excluding a network source from service area polygons does not prevent those sources from being traversed. Excluding sources from service area polygons only influences the polygon shape of the service areas. To prevent traversal of a given network source, you must create an appropriate restriction when defining your network dataset.
This is useful if you have some network sources that you don't want to be included in the polygon generation because they create less accurate polygons or are inconsequential for the service area analysis. For example, while creating a walk-time service area in a multimodal network that includes streets and metro lines, you should choose to exclude the metro lines from polygon generation. Although the traveler can use the metro lines, they cannot stop partway along a metro line and enter a nearby building. Instead, they must travel the full length of the metro line, exit the metro system at a station, then use the streets to walk to the building. It would be inaccurate to generate a polygon feature around a metro line.
This parameter is not available when the output geometry types do not include polygons, there are less than two edge sources in the network, the network data source is an ArcGIS Online service, or the network data source is a service on a version of Portal for ArcGIS which does not support excluding sources.
Polygon trim distance
Polygon Trim Distance controls how close service area polygons should be from the reached network edges. The trim distance refers to the distance from the road the service area polygon should extend when no other reachable roads are nearby, similar to a line buffer size. It roughly models how far back from the road centerlines is considered reachable from the road. This is useful if the network is very sparse and you don't want the service area to cover large areas where there are no features.
The parameter includes a value and units for the distance. The default value is 100 meters. This parameter is disabled if:
- The Output Shape Types is set to Lines.
- The Polygon Detail Level is set to Generalized.