If you publish routing services using configure routing services dialog box from ArcGIS Enterprise portal website, or publish using publish routing services command line utility, use the following endpoint to access the /locate direct request. The {{folder represents the folder in which the services are being published, and the {{network represents the name of the network dataset used when publishing the routing service.
GET https://{{machineName}}/{{serverWebAdaptorName}}/rest/services/{{folderName}}/NetworkAnalysis/NAServer/{{networkDatasetName}}/locateDescription
When performing analysis using routing services, the inputs to an analysis rarely fall exactly on top of the edges or junctions of the network dataset the service is using. For example, you may be using a network dataset constructed from street centerlines to power your routing services, and the input points you want to analyze are the centroids of parcels in your city. These parcel centroids do not fall on top of the street centerlines; rather, they are offset some distance from the streets. To successfully perform a network analysis using your routing services, the routing services must identify the location on the network dataset where each analysis input lies. This network location, rather than the input's original location, is used in the analysis. Typically, the longitude and latitude of the inputs are passed in and the routing services compute the location on the network during the solve operation. With the locate service, you can compute the locations on the network before calling the solve operation.
Learn more about locating inputs
The locate service is performed on a network dataset layer resource. You can provide arguments to the locate service as query parameters defined in the parameters table below. The locate service can be used in scenarios such as the following:
- Reuse location fields during the
solveoperation —You have a set of regularly serviced customers. You can use thelocateservice to calculate location fields, and use the located inputs in the routing services. This helps to speed up routing services since the service doesn't need to locate inputs again and you can reuse the locations in multiple places.
- Compute serviceability —Before you perform a routing request, you can call
locateto determine serviceability. For example, the mode of travel may only allow service inputs that are 500 meters off the streets. You can perform alocateservice with 500 meters as the search tolerance and determine which inputs cannot be serviced before you perform a more advanced routing service. - Use
Distanceto calculate service time —You can gain information from theTo Network In Meters locateservice response to fine-tune your routing service settings. For example, if you want to know how far each input is off network to perform delivery analysis, and it takes time to go from the parked vehicle location to the delivery location, you can use theDistancefield for each record in the response. Once you know how far away the actual location is from the network, you can use a speed factor to calculate a service time for each input based on its distance off the network.To Network In Meters - Query fields from the underlying source features —The
locateservice also supports returning additional field values from the source features where the inputs are located. For example, you can set different curb approaches on the inputs depending on the type of road on which they're located. If the input is located on a major road, you can set it to right or left side of the vehicle, depending on the driving side of the country where it's located. If the input is located on a local road, either side of curb approach will work since a vehicle can cross a local road for a delivery.
Parameters
| Name | Required | Type | Default | Description |
|---|---|---|---|---|
f | string | The request response format, either | ||
token | string | An access token with the required privileges. | ||
inputLocations | locations | feature | Specify input locations. | ||
travelMode | object | The mode of transportation for the analysis provided as a JSON object. | ||
locateSettings | object | Determines how input data are located. | ||
barriers | locations | feature | One or more points that act as temporary restrictions, additional time, or distance. | ||
polylineBarriers | feature | One ore more lines that prohibit travel anywhere the lines intersect the streets. | ||
polygonBarriers | feature | Polygons that either prohibit travel or proportionately scale the time or distance required to travel on the streets. | ||
returnBarriers | boolean |
| Returns barriers. | |
returnPolylineBarriers | boolean |
| Returns polyline barriers. | |
returnPolygonBarriers | boolean |
| Returns polygon barriers. | |
outputSourceFieldNames | string | Fields from which the located source feature values will be retrieved. |
Required parameters
inputLocations
Specify one or more locations to locate.
When specifying the input locations, you can set attributes for each as follows:
Show attributes for input locations
Attributes for input locations
ObjectIDinteger (non-negative)nullable
The object ID of the input.Objectis a unique identifier for each input. If theID Objectis not specified, a unique ID is automatically generated in the output.ID
-
SourceIDinteger (non-negative)nullable
The numeric identifier of the network dataset source feature class on which the input point is located.
-
SourceOIDinteger (non-negative)nullable
The object ID of the feature in the source on which the input point is located.
-
PosAlongnumber (non-negative)nullable
The position along the digitized direction of the source line feature. This value is stored as a ratio. This attribute is null if the network location references a junction.
-
SideOfEdgeint enumnullable
Allowed values:
1,2The side of the edge in relation to the digitized direction of the line feature.
This attribute is limited to a domain of two values:
1: Right Side2: Left Side
-
CurbApproachint enumdefault:0
Allowed values:
0,1,2,3Specifies the direction a vehicle may arrive at and depart from the input location. The field value is specified as one of the following integers:
0: Either side of vehicle. The vehicle can approach and depart the input location in either direction. U-turns are allowed. You should choose this setting if your vehicle can make a U-turn at the order or if it can pull into a driveway or parking lot and turn around.1: Right side of vehicle. When the vehicle approaches and departs the input location, the curb must be on the right side of the vehicle. A U-turn is prohibited.2: Left side of vehicle. When the vehicle approaches and departs the input location, the curb must be on the left side of the vehicle. A U-turn is prohibited.3: No U-turn. When the vehicle approaches the input location, the curb can be on either side of the vehicle; however, the vehicle must depart without turning around. Learn more about U-turn policies
Show illustration
Setting Coded value Description Either side of vehicle
0
The vehicle can approach and depart the input location in either direction, so a U-turn is allowed at the input location. This setting can be chosen if it is possible and desirable for a vehicle to turn around at the input location. This decision may depend on the width of the road and the amount of traffic or whether the location has a parking lot where vehicles can pull in and turn around.

All arrival and departure combinations are allowed with the Either side of vehicle curb approach.
Right side of vehicle
1
When the vehicle approaches and departs the input location, the input location 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 side.

The allowed arrival and departure combination for the Right side of vehicle curb approach is shown.
Left side of vehicle
2
When the vehicle approaches and departs the input location, the input location 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 side.

The allowed arrival and departure combination for the Left side of vehicle curb approach is shown.
No U-Turn
3
When the vehicle approaches the input location, the input location can be on either side of the vehicle; however, when it departs, the vehicle must continue in the same direction it arrived. A U-turn is prohibited.

The allowed arrival and departure combinations for the No U-Turn curb approach are shown.
The
Curbattribute is designed to work with both types of national driving standards: right-hand traffic (United States) and left-hand traffic (United Kingdom). First, consider an input location 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 an input location 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 an input location and not have a lane of traffic between the vehicle and the incident, choose 1 (Right side of vehicle) in the United States and 2 (Left side of vehicle) in the United Kingdom.Approach 
With right-hand traffic, the curb approach that leaves the vehicle closest to the input location is Right side of vehicle.

With left-hand traffic, the curb approach that leaves the vehicle closest to the input location is Left side of vehicle.
-
Bearingnumber (non-negative)nullable
The direction in which a point is moving. The units are degrees and are measured clockwise from true north.
This attribute is used in conjunction with the
Bearingattribute. 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 attribute 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 solver determine the side of the street that the point is on.Tol -
BearingTolnumber (range: 0 - 180)default:30nullable
The bearing tolerance value creates a range of acceptable bearing values when locating moving points on an edge using the
Bearingattribute.If the
Bearingattribute 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. 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. -
NavLatencynumber (non-negative)nullable
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.
This attribute is only used in the solve process if the
BearingandBearingfields also have values; however, providing aTol Navattribute value is optional, even when values are present in theLatency BearingandBearing.Tol
token
Specify a token that provides the identity of a user that has the permissions to access the service. The security and authentication page provides more information about how an access token can be obtained.
"token=<yourToken>"Optional parameters
travelMode
Choose the mode of transportation for the analysis.
Travel modes are managed and configured in ArcGIS Enterprise by the administrator of your organization to better reflect the organization's workflows.
locateSettings
Specify settings that affect how inputs are located, such as the maximum search distance to use when locating the inputs on the network or the network sources being used for locating.
Show examples
Examples for locate settings
Specify locate settings using a JSON structure
This example shows how to specify locate settings so inputs are only located within 500 meters of the specified location. A small search tolerance like this can be helpful if you are solving using a walking travel mode and don't want inputs to be located farther than 500 meters from the original point location.
{
"default": {
"tolerance": 500,
"toleranceUnits": "esriMeters",
"allowAutoRelocate": true,
"sources": [
{
"name": "Routing_Streets"
}
]
}
}barriers
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.
When specifying point barriers, you can set properties for each, such as its name or barrier type.
Show attributes for barriers
Attributes for barriers
-
Namestringnullable
The name of the barrier.
-
SourceIDinteger (non-negative)nullable
The numeric identifier of the network dataset source feature class on which the input point is located.
-
SourceOIDinteger (non-negative)nullable
The object ID of the feature in the source on which the input point is located.
-
PosAlongnumber (non-negative)nullable
The position along the digitized direction of the source line feature. This value is stored as a ratio. This attribute is null if the network location references a junction.
-
SideOfEdgeint enum
Allowed values:
1,2The side of the edge in relation to the digitized direction of the line feature.
This attribute is limited to a domain of two values:
1: Right Side2: Left Side
-
BarrierTypeint enumdefault:0
Allowed values:
0,2Specify 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:
-
0: Restriction. Prohibits travel through the barrier. The barrier is referred to as a restriction point barrier since it acts as a restriction.
The first map shows the shortest path between two stops without any restriction point barriers. The second map has a road that is blocked by a fallen tree, so the shortest path between the same points is longer.
2: Added Cost. Traveling through the barrier increases the travel time or distance by the amount specified in theAttrattributes. This barrier type is referred to as an added cost point barrier._[ Cost]
The map on the left shows the shortest path between two stops without any added cost point barrier. For the map on the right, the travel time from stop one to stop two would be the same whether going around the north end of the block or the south end; however, since crossing railroad tracks incurs a time penalty (modeled with added cost point barriers), the route with only one railroad crossing is chosen. The cost of crossing the barrier is added to the accumulated travel time of the resulting route.
-
-
FullEdgeint enumdefault:0
Allowed values:
0,1Specify how the restriction point barriers are applied to the edge elements during the analysis
0:False—Permits travel on the edge up to the barrier but not through it.1:True—Restricts travel anywhere on the associated edge.
-
Attr_[Cost]number (non-negative)default:0
Indicates how the cost (time or distance) is added when the barrier is traversed. This attribute is applicable only for added cost point barriers. The attribute value must be greater than or equal to zero.
polylineBarriers
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 first map displays the shortest path between two stops. The second map shows the shortest path when several streets are blocked by a polyline barrier.
When specifying line barriers, you can set the name of each barrier using the following attribute:
Show attributes for polyline Barriers
Attributes for polylineBarriers
-
Namestring (length: 500)nullable
The name of the barrier.
-
ObjectIDinteger (non-negative)nullable
The object ID of the line barrier.
Objectis a unique identifier for the line barrier. If you want to maintain a relationship between the input and output, setID preservetoObject ID true. TheObjectvalue of the input line barrier is included in the output line barrier (as theID Objectfield) and can be used to join additional information from analysis outputs to the attribute of the line barriers. If theID Objectvalue is not specified, a unique ID is automatically generated in the output.ID
-
SourceIDinteger (non-negative)nullable
The numeric identifier of the network dataset source feature class on which the input point is located.
-
SourceOIDinteger (non-negative)nullable
The object ID of the feature in the source on which the input point is located.
-
PosAlongnumber (non-negative)nullable
The position along the digitized direction of the source line feature. This value is stored as a ratio. This attribute is null if the network location references a junction.
-
SideOfEdgeint enum
Allowed values:
1,2The side of the edge in relation to the digitized direction of the line feature.
This attribute is limited to a domain of two values:
1: Right Side2: Left Side
-
BarrierTypeint enumdefault:0
Allowed values:
0,1Specify 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:
0: Restriction. Prohibits travel through the barrier. The barrier is referred to as a restriction line barrier since it acts as a restriction.1: Scaled Cost. Scales the time or distance required to travel the underlying streets by a factor specified using theAttrattribute._[ Cost]
-
Attr_[Cost]number (non-negative)default:0
This attribute is specific to scaled-cost barriers. It is the factor by which the cost of edges underlying the barrier are multiplied.
Show example
This example shows how to add two lines as polyline barriers to restrict travel on the streets intersected by the lines. Barrier 1 is a single-part line feature composed of two points. Barrier 2 is a two-part line feature. The first part is composed of three points, and the second part is composed of two points.
{
"spatialReference": {
"wkid": 102100
},
"features": [
{
"geometry": {
"paths": [
[
[-10804823.397, 3873688.372],
[-10804811.152, 3873025.945]
]
]
},
"attributes": {
"Name": "Barrier 1"
}
},
{
"geometry": {
polygonBarriers
Specify polygons that either completely restrict travel or proportionately scale the time or distance required to travel on the streets intersected by the polygons.
When specifying polygon barriers, you can set properties for each, such as its name or barrier type, using the following attributes:
Show attributes for polygon Barriers
Attributes for polygonBarriers
-
Namestringnullable
The name of the barrier.
-
ObjectIDinteger (non-negative)nullable
The object ID of the polygon barrier.
Objectis a unique identifier for the polygon barrier. If you want to maintain a relationship between the input and output, setID preservetoObject ID true. TheObjectvalue of the input polygon barrier is included in the output polygon barrier (as theID Objectfield) and can be used to join additional information from analysis outputs to the attribute of the polygon barriers. If theID Objectvalue is not specified, a unique ID is automatically generated in the output.ID
-
SourceIDinteger (non-negative)nullable
The numeric identifier of the network dataset source feature class on which the input point is located.
-
SourceOIDinteger (non-negative)nullable
The object ID of the feature in the source on which the input point is located.
-
PosAlongnumber (non-negative)nullable
The position along the digitized direction of the source line feature. This value is stored as a ratio. This attribute is null if the network location references a junction.
-
SideOfEdgeint enum
Allowed values:
1,2The side of the edge in relation to the digitized direction of the line feature.
This attribute is limited to a domain of two values:
1: Right Side2: Left Side
-
BarrierTypeint enumdefault:0
Allowed values:
0,1Specify polygons that either completely restrict travel or proportionately scale the time or distance required to travel on the streets intersected by the polygons.
The value for this attribute can be specified as one of the following integers:
-
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.
The first map depicts the shortest path between two stops. The second map shows a polygon barrier blocking flooded streets, so the shortest path between the same two stops is different.
-
1: Scaled Cost. Scales the cost (such as travel time or distance) required to travel the underlying streets by a factor specified using theAttrattributes._[ Cost] 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.
The first map shows a route that goes through inclement weather without regard for the effect that poor road conditions have on travel time. The second map shows a scaled polygon barrier that doubles the travel time of the roads covered by the storm. The route still passes through the southern tip of the storm since it is quicker to spend more time driving slowly through a small part of the storm rather than driving completely around it. The service uses the modified travel time in calculating the best route, and the modified travel time is reported as the total travel time in the response.
-
-
Attr_[Cost]number (non-negative)default:0
This is the factor by which the cost of the streets intersected by the barrier is multiplied. This attribute is applicable only for scaled cost barriers. The attribute value must be greater than zero.
Show example
This example shows how to add two polygons as barriers. The first polygon, Flood zone, is a restriction polygon barrier that prohibits travel on the underlying streets. The polygon is a single-part polygon feature composed of four points. The second polygon, Severe weather zone, is a scaled-cost polygon barrier that reduces the travel time on underlying streets to one-third of the original value. The polygon is a two-part polygon feature. Both parts are composed of four points.
{
"spatialReference": {
"wkid": 4326
},
"features": [
{
"geometry": {
"rings": [
[
[-97.0634, 32.8442],
[-97.0554, 32.84],
[-97.0558, 32.8327],
[-97.0638, 32.83],
[-97.0634, 32.8442]
]
]
},
"attributes": {
"Name": "Flood zone",
"BarrierType": 0
returnBarriers
Specify whether barriers will be returned by the service
true—The input point barriers are returned as part of thebarriersproperty in the JSON response.false—Point barriers are not returned.
For this parameter to take effect, you must also specify a value for the barriers parameter.
If you specified the barriers parameter value using a REST query request to any ArcGIS Server feature, map, or geoprocessing service that returns a JSON feature set, you can set the return parameter to true so you can draw the point barrier locations in the application. You can also set the return property to true to see where the barriers were located on the street network or, if they weren't located, understand what the problem was by reviewing the Status property in the JSON response.
returnPolylineBarriers
Specify whether polyline barriers will be returned by the service.
true—The input polyline barriers are returned as part of thepolylineproperty in the JSON response.Barriers false—Polyline barriers are not returned.
For this parameter to take effect, you must also specify a value for the polyline parameter.
If you specified the polyline parameter value using a REST query request to any ArcGIS Server feature, map, or geoprocessing service that returns a JSON feature set, you can set the return parameter to true so you can draw the polyline barrier locations in the application.
returnPolygonBarriers
Specify whether polygon barriers will be returned by the service.
true—The input polygon barriers are returned as part of thepolygonproperty in the JSON response.Barriers false—Polygon barriers are not returned.
For this parameter to take effect, you must also specify a value for the polygon parameter.
If you specified the polygon parameter value using a REST query request to any ArcGIS Server feature, map, or geoprocessing service that returns a JSON feature set, you can set the return parameter to true so you can draw the polygon barrier locations in the application.
outputSourceFieldNames
Specify the fields from which the located source feature values will be retrieved. The parameter is specified as a comma-separated list of names.
For example, you may want to know the road class for the feature where the inputs are located so you know whether the inputs are located on a local road, major road, or highway. This information can be helpful to set the curb approach for the input when you use other routing services to solve, so your drivers don't cross a major road or highway for a delivery. Another example is you know the street names where the inputs are supposed to locate, and you want to know the street name where the inputs located during the locate process so you can validate they locate on the correct feature. In this case, you can set output to the fields you are interested in. For example, if you want to return both road class and street name, you can specify output as " for the fields on the street source feature of the ArcGIS StreetMap Premium network dataset. (The fields may be different if you use other data for the service). You can find the field names for each source feature by querying network dataset layer resource.
If the feature where the input is located doesn't have the field you specified, it will not be included in the output. If you have multiple inputs that locate on different feature classes, some fields might exist on one feature but not the other. In those cases, the field will be included in the output, but the value may be empty.
outSR
This parameter contains additional settings that affect task operation, for example, the spatial reference of the output features.
Response objects
Upon successful completion, the service returns the located inputs and barriers if requested. The status field on the outputs indicates whether each feature is located. The service won't fail if the inputs are not located, so you need to inspect the status field to know which features are located and which features are not. The fields for each output are described below.
outputLocations
Provides access to the attributes of the locations located by the service. You can use the attributes from this parameter, such as the Status field, to determine whether a particular input was located.
Show attributes for output locations
-
ObjectIDinteger
The value for this field will be the ObjectID of the associated input. If the ObjectID is not specified on the input, a unique ID is automatically generated in the output.
-
SourceIDinteger (non-negative)nullable
The numeric identifier of the network dataset source feature class on which the input point is located.
-
SourceOIDinteger (non-negative)nullable
The object ID of the feature in the source on which the input point is located.
-
PosAlongnumber (non-negative)nullable
The position along the digitized direction of the source line feature. This value is stored as a ratio. This attribute is null if the network location references a junction.
-
SideOfEdgeint enumnullable
Allowed values:
1,2The side of the edge in relation to the digitized direction of the line feature.
This attribute is limited to a domain of two values:
1: Right Side2: Left Side
-
CurbApproachintegernullable
The direction a vehicle may arrive at and depart from the location. The values for this field are copied from the
Curbfield on the input locations.Approach
-
Statusint enum
Indicates the status of the point with respect to its location on the network and the outcome of the analysis.
Possible values:
0: OK.The point was located on the network.1: Not Located. The point was not located on the network and was not included in the analysis.2: Network element not located. The network element identified by the point's network location fields cannot be found. This can occur when a network element where the point should be was deleted, and the network location was not recalculated.3: Element not traversable. The network element that the point is located on is not traversable. This can occur when the element is restricted by a restriction attribute.4: Invalid Field Values. Field values fall outside a range or coded-value domain. For example, a negative number exists where positive numbers are required.5: Not reached. The point cannot be reached by the solver. The point may be on a separate, disconnected area of the network from the other inputs, or barriers or restrictions prevent travel to or from the point.6: Time window violation. The point could not be reached within the designated time windows. This status only applies to network analysis types that support time windows.7: Not located on closest. The closest network location to the point is not traversable because of a restriction or barrier, so the point has been located on the closest traversable network feature instead. If time windows are used and the route arrives early or late, the value changes to 6 (Time window violation)
-
SnapXnumber (non-negative)
The x-coordinate of the position on the network dataset where the point was located, in the coordinate system of the network dataset.
-
SnapYnumber (non-negative)
The y-coordinate of the position on the network dataset where the point was located, in the coordinate system of the network dataset.
-
SnapZnumber (non-negative)
The z-coordinate of the position on the network dataset where the point was located, in the coordinate system of the network dataset. The
Snapattribute is 0 if the network is two-dimensional.Z -
DistanceToNetworkInMetersnumber (non-negative)
The distance in meters between the point's geographic location and the position where it was located on the network.
-
BuildTimestring
The build timestamp of the network dataset used by the locating service.
-
BearingTolnumber (non-negative)nullable
The values for this field are copied from the
Bearingfield on the input facilities.Tol -
NavLatencynumber (non-negative)nullable
The values for this field are copied from the
Navfield on the input facilities.Latency
barriers
Provides access to points that act as temporary restrictions or represent additional time or distance that may be required to travel on the underlying streets.
Show attributes for barriers output parameter
-
ObjectIDinteger
If you specify
preserve, the value for this field will be a system-generated ID. IfObject I D=false preserve, the value for this field will be theObject I D= True Objectof your associated input.ID -
Namestring (length: 500)
The name of the barrier.
-
SourceIDinteger (non-negative)nullable
The numeric identifier of the network dataset source feature class on which the input point is located.
-
SourceOIDinteger (non-negative)nullable
The object ID of the feature in the source on which the input point is located.
-
PosAlongnumber (non-negative)nullable
The position along the digitized direction of the source line feature. This value is stored as a ratio. This attribute is null if the network location references a junction.
-
SideOfEdgeint enumnullable
Allowed values:
1,2The side of the edge in relation to the digitized direction of the line feature.
This attribute is limited to a domain of two values:
1: Right Side2: Left Side
-
CurbApproachint enumdefault:0
Possible values:
0,1,2The direction of traffic that is affected by the barrier. The field value is specified as one of the following integers:
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: 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.
-
Statusint enum
Indicates the status of the point with respect to its location on the network and the outcome of the analysis.
Possible values:
0: OK.The point was located on the network.1: Not Located. The point was not located on the network and was not included in the analysis.2: Network element not located. The network element identified by the point's network location fields cannot be found. This can occur when a network element where the point should be was deleted, and the network location was not recalculated.3: Element not traversable. The network element that the point is located on is not traversable. This can occur when the element is restricted by a restriction attribute.4: Invalid Field Values. Field values fall outside a range or coded-value domain. For example, a negative number exists where positive numbers are required.5: Not reached. The point cannot be reached by the solver. The point may be on a separate, disconnected area of the network from the other inputs, or barriers or restrictions prevent travel to or from the point.6: Time window violation. The point could not be reached within the designated time windows. This status only applies to network analysis types that support time windows.7: Not located on closest. The closest network location to the point is not traversable because of a restriction or barrier, so the point has been located on the closest traversable network feature instead. If time windows are used and the route arrives early or late, the value changes to 6 (Time window violation)
-
FullEdgeint enum
Possible values:
0,1Point barriers are applied to the edge elements during the analysis. The field value is specified as one of the following integers
0:False. Permits travel on the edge up to the barrier but not through it.1:True. Restricts travel anywhere on the associated edge.
-
BarrierTypeint enum
Possible values:
0,2Specify 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:
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 theAttrattribute._[ Cost]
-
Attr_[Cost]number (non-negative)default:0
This attribute is specific to added-cost barriers and is limited to values that are greater than or equal to zero. It indicates how much cost is added when the barrier is traversed.
polylineBarriers
Provides access to one or more lines that prohibit travel anywhere the lines intersect the streets.
Show attributes for polyline Barriers output parameter
-
ObjectIDinteger
If you specify
preserve, the value for this field will be a system-generated ID. IfObject I D=false preserve, the value for this field will be theObject I D= True Objectof your associated input.ID -
Namestring (length: 500)nullable
The name of the barrier.
-
BarrierTypeint enum
Possible values:
0,1Indicates whether the barrier restricts travel completely or scales time or distance when it is crossed. The value for this attribute is specified as one of the following integers:
0:Restriction. Prohibits travel through the barrier. The barrier is referred to as a restriction point barrier since it acts as a restriction.1:Scaled Cost. Scales the time or distance required to travel the underlying streets by a factor specified using theAttrattribute._[ Cost]
-
Attr_[Cost]number (non-negative)
This attribute is specific to scaled-cost barriers. It is the factor by which the cost of edges underlying the barrier are multiplied.
polygonBarriers
Provides access to polygons that either completely restrict travel or proportionately scale the time or distance required to travel on the streets intersected by the polygons.
Show attributes for polygon Barriers output parameter
-
ObjectIDinteger
If you specify
preserve, the value for this field will be a system-generated ID. IfObject I D=false preserve, the value for this field will be theObject I D= True Objectof your associated input.ID -
Namestring (length: 500)nullable
The name of the barrier.
-
BarrierTypeint enum
Possible values:
0,1Indicates whether the barrier restricts travel completely or scales time or distance when it is crossed. The value for this attribute is specified as one of the following integers:
0:Restriction. Prohibits travel through the barrier. The barrier is referred to as a restriction point barrier since it acts as a restriction.1:Scaled Cost. Scales the time or distance required to travel the underlying streets by a factor specified using theAttrattribute._[ Cost]
-
Attr_[Cost]number (non-negative)
This attribute is specific to scaled-cost barriers. It is the factor by which the cost of edges underlying the barrier are multiplied.