ServiceArea input data types

The input data types that can be specified when performing a service area analysis are described below.

Facilities

The input locations around which service areas are generated.

All fields from the input facilities are included in the output polygons when the geometryAtOverlap property of the analysis object is set to ServiceAreaOverlapGeometry.Overlap or ServiceAreaOverlapGeometry.Split.

The data type supports the following fields:

Field	Description	Data type
Name	The name of the facility. If the name is not specified, a name is automatically generated at solve time.	Text
Breaks	Specify the extent of the service area to be calculated on a per facility basis. This attribute allows you to specify a different service area break value for each facility. For example, with two facilities, you can generate 5- and 10-minute service area polygons for one facility and 6-, 9-, and 12-minute polygons for the other facility. Separate multiple break values with a space, and specify the numeric values using the dot character as your decimal separator, even if the locale of your computer defines a different decimal separator. For example, the value 5.5 10 15.5 specifies three break values around a facility. If the travel mode set for the analysis uses a time-based impedance attribute, the values are interpreted to be in the units specified by the timeUnits property. If the travel mode set for the analysis uses a distance-based impedance attribute, the values are interpreted to be in the units specified by the distanceUnits property. If the travel mode set for the analysis uses an impedance attribute that is neither time based nor distance based, the values are interpreted to be in unknown units. A value for this attribute overrides the default set for the analysis using the defaultImpedanceCutoffs property. The default value is Null, which results in using the default value set by the defaultImpedanceCutoffs property for all the facilities. Caution: Per-facility breaks are ignored if the geometryAtOverlap property of the analysis object is set to ServiceAreaOverlapGeometry.Dissolve. Legacy: Routing services based on portals running versions of ArcGIS Enterprise earlier than 10.8 do not support per-facility break values and will ignore values in this field.	Text
AdditionalTime	The amount of time spent at the facility, which reduces the extent of the service area calculated for the given facility. The default value is 0. For example, when calculating service areas that represent fire station response times, AdditionalTime 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 is 4 minutes (since 1 of the 5 minutes is required as turnout time). Similarly, Fire Station 2 has a service area of only 2 minutes from the fire station. The units for this attribute value are specified by the timeUnits property of the analysis object.	Double
AdditionalDistance	The extra distance traveled to reach the facility before the service is calculated. This attribute reduces the extent of the service area calculated for the given facility. The default value is 0. Generally, the location of a facility, such as a store location, isn't exactly on the street; it is set back somewhat from the road. This attribute value can be used to model the distance between the actual facility location and its location on the street if it is important to include that distance when calculating the service areas for the facility. The units for this attribute value are specified by the distanceUnits property of the analysis object.	Double
AdditionalCost	The extra cost spent at the facility, which reduces the extent of the service area calculated for the given facility. The default value is 0. Use this attribute value when the travel mode for the analysis uses an impedance attribute that is neither time based nor distance based The units for the attribute values are interpreted to be in unknown units.	Double
CurbApproach	Specifies the direction a vehicle may arrive at and depart from the facility. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (Either side of vehicle)—The vehicle can approach and depart the facility in either direction, so a U-turn is allowed at the facility. This setting can be chosen if it is possible and practical for a vehicle to turn around at the facility. This decision may depend on the width of the road and the amount of traffic or whether the facility has a parking lot where vehicles can enter and turn around. 1 (Right side of vehicle)—When the vehicle approaches and departs the facility, the curb must be on the right side of the vehicle. A U-turn is prohibited. This is typically used for vehicles such as buses that must arrive with the bus stop on the right-hand side. 2 (Left side of vehicle)—When the vehicle approaches and departs the facility, the curb must be on the left side of the vehicle. A U-turn is prohibited. This is typically used for vehicles such as buses that must arrive with the bus stop on the left-hand side. 3 (No U-Turn)—When the vehicle approaches the facility, the curb can be on either side of the vehicle, however, the vehicle must depart without turning around. The CurbApproach attribute is designed to work with both types of national driving standards: right-hand traffic (United States) and left-hand traffic (United Kingdom). First, consider a facility on the left side of a vehicle. It is always on the left side regardless of whether the vehicle travels on the left or right half of the road. What may change with national driving standards is your decision to approach a facility from one of two directions; that is, so it ends up on the right or left side of the vehicle. For example, if you want to arrive at a facility and not have a lane of traffic between the vehicle and the facility, choose 1 (Right side of vehicle) in the United States and 2 (Left side of vehicle) in the United Kingdom.	Long
Bearing	The direction in which a point is moving. The units are degrees and are measured clockwise from true north. This field is used in conjunction with the BearingTol field. Bearing data is usually sent automatically from a mobile device equipped with a GPS receiver. Try to include bearing data if you are loading an input location that is moving, such as a pedestrian or a vehicle. Using this field tends to prevent adding locations to the wrong edges, which can occur when a vehicle is near an intersection or an overpass, for example. Bearing also helps the tool determine on which side of the street the point is. Learn more about bearing and bearing tolerance	Double
BearingTol	The bearing tolerance value creates a range of acceptable bearing values when locating moving points on an edge using the Bearing field. If the Bearing field value is within the range of acceptable values that are generated from the bearing tolerance on an edge, the point can be added as a network location there; otherwise, the closest point on the next-nearest edge is evaluated. The units are in degrees, and the default value is 30. Values must be greater than 0 and less than 180. A value of 30 means that when Network Analyst attempts to add a network location on an edge, a range of acceptable bearing values is generated 15 degrees to either side of the edge (left and right) and in both digitized directions of the edge. Learn more about bearing and bearing tolerance	Double
NavLatency	This field is only used in the solve process if the Bearing and BearingTol fields also have values; however, entering a NavLatency field value is optional, even when values are present in Bearing and BearingTol. NavLatency indicates how much cost is expected to elapse from the moment GPS information is sent from a moving vehicle to a server and the moment the processed route is received by the vehicle's navigation device. The units of NavLatency are the same as the units of the impedance attribute.	Double
Network location fields SourceID SourceOID PosAlong SideOfEdge	Together, these properties describe the point on the network where the object is located. Learn more about locating inputs on a network

PointBarriers

Use this parameter to specify one or more points that will act as temporary restrictions or represent additional time or distance that may be required to travel on the underlying streets. For example, a point barrier can be used to represent a fallen tree along a street or a time delay spent at a railroad crossing.

The data type supports the following fields:

Field	Description	Data type
Name	The name of the barrier.	Text
BarrierType	Specifies whether the point barrier restricts travel completely or adds time or distance when it is crossed. The value for this attribute is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (Restriction)—Prohibits travel through the barrier. The barrier is referred to as a restriction point barrier since it acts as a restriction. 2 (Added Cost)—Traveling through the barrier increases the travel time or distance by the amount specified in the Additional_Time, Additional_Distance, or AdditionalCost field. This barrier type is referred to as an added cost point barrier.	Long
Additional_Time	The added travel time when the barrier is traversed. This field value must be greater than or equal to zero, and the values are interpreted to be in the units specified by the timeUnits property.	Double
Additional_Distance	The added distance when the barrier is traversed. This field value must be greater than or equal to zero, and the values are interpreted to be in the units specified by the distanceUnits property.	Double
AdditionalCost	The added cost when the barrier is traversed. This field value must be greater than or equal to zero, and the values are interpreted to be in unknown units.	Double
FullEdge	Specifies how the restriction point barriers are applied to the edge elements during the analysis. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (False)—Permits travel on the edge up to the barrier but not through it. This is the default value. 1 (True)—Restricts travel anywhere on the associated edge.	Long
CurbApproach	Specifies the direction of traffic that is affected by the barrier. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (Either side of vehicle)—The barrier affects travel over the edge in both directions. 1 (Right side of vehicle)—Vehicles are only affected if the barrier is on their right side during the approach. Vehicles that traverse the same edge but approach the barrier on their left side are not affected by the barrier. 2 (Left side of vehicle)—Vehicles are only affected if the barrier is on their left side during the approach. Vehicles that traverse the same edge but approach the barrier on their right side are not affected by the barrier. Because junctions are points and don't have a side, barriers on junctions affect all vehicles regardless of the curb approach. The CurbApproach attribute works with both types of national driving standards: right-hand traffic (United States) and left-hand traffic (United Kingdom). First, consider a facility on the left side of a vehicle. It is always on the left side regardless of whether the vehicle travels on the left or right half of the road. What may change with national driving standards is your decision to approach a facility from one of two directions, that is, so it ends up on the right or left side of the vehicle. For example, to arrive at a facility and not have a lane of traffic between the vehicle and the facility, choose 1 (Right side of vehicle) in the United States and 2 (Left side of vehicle) in the United Kingdom.	Long
Bearing	The direction in which a point is moving. The units are degrees and are measured clockwise from true north. This field is used in conjunction with the BearingTol field. Bearing data is usually sent automatically from a mobile device equipped with a GPS receiver. Try to include bearing data if you are loading an input location that is moving, such as a pedestrian or a vehicle. Using this field tends to prevent adding locations to the wrong edges, which can occur when a vehicle is near an intersection or an overpass, for example. Bearing also helps the tool determine on which side of the street the point is. Learn more about bearing and bearing tolerance	Double
BearingTol	The bearing tolerance value creates a range of acceptable bearing values when locating moving points on an edge using the Bearing field. If the Bearing field value is within the range of acceptable values that are generated from the bearing tolerance on an edge, the point can be added as a network location there; otherwise, the closest point on the next-nearest edge is evaluated. The units are in degrees, and the default value is 30. Values must be greater than 0 and less than 180. A value of 30 means that when Network Analyst attempts to add a network location on an edge, a range of acceptable bearing values is generated 15 degrees to either side of the edge (left and right) and in both digitized directions of the edge. Learn more about bearing and bearing tolerance	Double
NavLatency	This field is only used in the solve process if the Bearing and BearingTol fields also have values; however, entering a NavLatency field value is optional, even when values are present in Bearing and BearingTol. NavLatency indicates how much cost is expected to elapse from the moment GPS information is sent from a moving vehicle to a server and the moment the processed route is received by the vehicle's navigation device. The units of NavLatency are the same as the units of the impedance attribute.	Double
Network location fields SourceID SourceOID PosAlong SideOfEdge	Together, these properties describe the point on the network where the object is located. Learn more about locating inputs on a network

LineBarriers

Use this parameter to specify one or more lines that prohibit travel anywhere the lines intersect the streets. For example, a parade or protest that blocks traffic across several street segments can be modeled with a line barrier. A line barrier can also quickly fence off several roads from being traversed, thereby channeling possible routes away from undesirable parts of the street network.

The data type supports the following fields:

Field	Description	Data type
Name	The name of the barrier.	Text
BarrierType	Specifies whether the barrier restricts travel completely or scales the cost (such as time or distance) for traveling through it. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (Restriction)—Prohibits travel anywhere the barrier intersects the transportation network. The barrier is referred to as a restriction line barrier. 1 (Scaled Cost)—Scales the cost (such as travel time or distance) required to travel the underlying streets by a factor specified using the ScaledTimeFactor or ScaledDistanceFactor field. If the streets are partially covered by the barrier, the travel time or distance is apportioned and then scaled. For example, a factor of 0.25 means that travel on underlying streets is expected to be four times faster than normal. A factor of 3.0 means it is expected to take three times longer than normal to travel on underlying streets. This barrier type is referred to as a scaled-cost line barrier. It can be used to model slowdowns due to closure of traffic lanes during construction, for example.	Long
ScaledTimeFactor	This is the factor by which the travel time of the streets intersected by the barrier is multiplied. The field value must be greater than zero.	Double
ScaledDistanceFactor	This is the factor by which the distance of the streets intersected by the barrier is multiplied. The field value must be greater than zero.	Double
ScaledCostFactor	This is the factor by which the cost of the streets intersected by the barrier is multiplied. The field value must be greater than zero.	Double
Locations	The information in this field defines which network edges and junctions are covered by the line or polygon and the portion of each edge element that is covered. You cannot directly read or edit the information contained in this field, but Network Analyst interprets it when solving an analysis. Learn more about locating inputs on a network	BLOB

PolygonBarriers

Use this parameter to specify polygons that either completely restrict travel or proportionately scale the time or distance required to travel on the streets intersected by the polygons.

The data type supports the following fields:

Field	Description	Data type
Name	The name of the barrier.	Text
BarrierType	Specifies whether the barrier restricts travel completely or scales the cost (such as time or distance) for traveling through it. The field value is specified as one of the following integers (use the numeric code, not the name in parentheses): 0 (Restriction)—Prohibits traveling through any part of the barrier. The barrier is referred to as a restriction polygon barrier since it prohibits traveling on streets intersected by the barrier. One use of this type of barrier is to model floods covering areas of the street that make traveling on those streets impossible. 1 (Scaled Cost)—Scales the cost (such as travel time or distance) required to travel the underlying streets by a factor specified using the ScaledTimeFactor or ScaledDistanceFactor field. If the streets are partially covered by the barrier, the travel time or distance is apportioned and then scaled. For example, a factor of 0.25 means that travel on underlying streets is expected to be four times faster than normal. A factor of 3.0 means it is expected to take three times longer than normal to travel on underlying streets. This barrier type is referred to as a scaled-cost polygon barrier. It can be used to model storms that reduce travel speeds in specific regions, for example.	Long
ScaledTimeFactor	This is the factor by which the travel time of the streets intersected by the barrier is multiplied. The field value must be greater than zero.	Double
ScaledDistanceFactor	This is the factor by which the distance of the streets intersected by the barrier is multiplied. The field value must be greater than zero.	Double
ScaledCostFactor	This is the factor by which the cost of the streets intersected by the barrier is multiplied. The field value must be greater than zero.	Double
Locations	The information in this field defines which network edges and junctions are covered by the line or polygon and the portion of each edge element that is covered. You cannot directly read or edit the information contained in this field, but Network Analyst interprets it when solving an analysis. Learn more about locating inputs on a network	BLOB