This topic describes about the credit consumption and analysis limits when network analysis is performed in ArcGIS Online
Credit consumption
Credits are the currency used across ArcGIS and are consumed for specific transactions and types of storage, such as storing features, performing analysis, and using premium content.
Learn more about credits and how they are administered.
When are credits consumed
Credits are consumed while performing network analysis in the following situations:
- Network analysis network data source is hosted in ArcGIS Online.
- Your ArcGIS Enterprise portal routing services are configured using ArcGIS Online.
Note:
The analysis does not consume any credits if the network data source is a network dataset stored on a local machine or you are using your own routing services published on your ArcGIS Enterprise portal.
Network analysis type and credits
The table below describes the number of credits each network analysis type consumes.
Caution:
Credit rates may change. See Credits by capability for current rates.
| Analysis type | Credit consumption | Example |
|---|---|---|
Closest facility | Uses 0.5 credits per closest facilities route. | If there are 10 incident points and 2 facilities, the cost will be 5 credits if all 10 incident points can be successfully routed to a facility. |
Route | Uses 0.005 credits per simple route. Uses 0.5 credits per optimized route. | If there are 2 stops, the cost of the route will be 0.005 credits. If there are 10 stops, the cost of the route remains 0.005 credits. For these routes, the order of stops is determined by the order of the records in the stops table. If you choose the option to reorder the stops to optimize travel time, the cost will be 0.5 credits. |
Service area | Uses 0.5 credits per service area or drive time. | If there are 10 facilities and you specify drive times of 5 and 10 minutes, the cost will be 10 credits. |
OD cost matrix | Uses 0.0005 credits per input origin and destination pair. | If there are 100 origins and 200 destinations, the cost will be 10 credits. If you specify a cutoff, or limit the number of destinations, such as to find only the 5 closest destinations within 10 minutes of every origin, the cost will still be 10 credits, as the credits depend on the number of input origin-destination pairs. |
Location-allocation | Uses 0.1 credits per demand point. | If there are 5 facilities to evaluate and 100 demand points to allocate to those facilities, the cost will be 10 credits. |
Vehicle routing problem | Uses 1 credit per VRP route. | If you're routing 5 vehicles through 100 total stops, the cost will be 5 credits. |
Estimate credits
When performing analysis using a network analysis layer, you can estimate credit usage as follows:
-
Estimate Credits button—Each network analysis layer ribbon has an Estimate Credits button
. Click this button to estimate the number of credits that will be consumed by the analysis. Learn more about estimate credits. - Geoprocessing tool window—At the top of the Solve geoprocessing tool window, click the Click to estimate credits link in the banner to estimate the number of credits that will be consumed when solving the input network analysis layer. The credit estimation banner does not appear if solving the input network analysis layer does not consume credits.
Analysis limits
When a network analysis uses the ArcGIS Online routing services as the network data source, some limits are imposed on the analysis for better performance. For example, you cannot exceed a specified number of allowed inputs for each analysis type. If you need to solve an analysis of a size that exceeds the analysis limits, consider using one of the following approaches:
- To solve a large problem, split it into smaller sections first.
- For better performance and to avoid overloading the server, eliminate any irrelevant data. For example, if you are solving an OD Cost Matrix analysis with a travel distance limit of 10 miles, use the Select Layer By Location tool to preselect only destinations that fall within a 10-mile straight-line distance of origins.
To learn more, see tools and code samples for solving large network analysis problems in ArcGIS Pro.
- Use a local network dataset or your own routing services published on your ArcGIS Enterprise portal as the network data source instead of ArcGIS Online routing services.
The following sections describe the usage limits for each solver:
Note:
When performing analysis in Python using the Network Analyst module, arcpy.nax, use the GetWebToolInfo function to retrieve the analysis limits for a solver in the routing utility services registered with your portal.
Route
Caution:
Analysis limits may change. See Usage limits for current limits.
| Limit description | Limit value |
|---|---|
Maximum number of stops | 10,000 |
Maximum number of stops per route | 150 |
Maximum number of point barriers | 250 |
Maximum number of street features intersected by polyline barriers | 500 |
Maximum number of street features intersected by polygon barriers | 2,000 |
Maximum straight-line distance for the walking travel mode (If the straight-line distance between any two stops is greater than this limit, the analysis fails when the walking option for travel mode is used.) | 27 miles (43.45 kilometers) |
Force hierarchy beyond a straight-line distance of (If the straight-line distance between any two stops is greater than the limit shown here, the analysis uses hierarchy, even if hierarchy is not being used for the analysis.) | 50 miles (80.46 kilometers) |
Maximum time a client can use this route service | 1 hour (3,600 seconds) |
Maximum number of directions features that can be returned | 1,000,000 |
Maximum number of route edges that can be returned | 1,000,000 |
Closest facility
Caution:
Analysis limits may change. See Usage limits for current limits.
| Limit description | Limit value |
|---|---|
Maximum number of incidents | 5,000 |
Maximum number of facilities | 5,000 |
Maximum number of facilities to find (per incident) | 100 |
Maximum number of point barriers | 250 |
Maximum number of street features intersected by polyline barriers | 500 |
Maximum number of street features intersected by polygon barriers | 2,000 |
Maximum straight-line distance for the walking travel mode (If the straight-line distance between any facility and incident is greater than this limit, the analysis fails when the walking option for travel mode is used.) | 27 miles (43.45 kilometers) |
Force hierarchy beyond a straight-line distance of (If the straight-line distance between any facility and incident is greater than the limit shown here, the analysis uses hierarchy, even if hierarchy is not being used for the analysis.) | 50 miles (80.46 kilometers) |
Maximum number of directions features that can be returned | 100,000 |
Maximum time a client can use the job request closest facility service | 1 hour (3,600 seconds) |
Location-allocation
Caution:
Analysis limits may change. See Usage limits for current limits.
| Limit description | Limit value |
|---|---|
Maximum number of facilities | 1,000 |
Maximum number of facilities to find | 100 |
Maximum number of demand points | 10,000 |
Maximum number of point barriers | 250 |
Maximum number of street features intersected by polyline barriers | 500 |
Maximum number of street features intersected by polygon barriers | 2,000 |
Force hierarchy beyond a straight-line distance of (If the straight-line distance between any facility and demand point is greater than the limit shown here, the analysis uses hierarchy, even if hierarchy is not being used for the analysis.) | 50 miles (80.46 kilometers) |
Maximum time a client can use the job request service | 1 hour (3,600 seconds) |
Service area
Caution:
Analysis limits may change. See Usage limits for current limits.
| Limit description | Limit value |
|---|---|
Maximum number of facilities | 1,000 |
Maximum number of point barriers | 250 |
Maximum number of street features intersected by polyline barriers | 500 |
Maximum number of street features intersected by polygon barriers | 2,000 |
Maximum number of cutoffs (break value) | No limit |
Maximum travel time | 9 hours (540 minutes) or 5 hours (300 minutes) When walking, the maximum travel time can be 9 hours (540 minutes). For all other travel modes, the maximum travel time can be 5 hours (300 minutes). |
Maximum travel distance | 27 miles (43.45 kilometers) or 300 miles (482.80 kilometers) When walking, the maximum travel distance can be 27 miles (43.45 kilometers). For all other travel modes, the maximum travel distance can be 300 miles (482.80 kilometers). |
Maximum travel time when generating detailed polygons | 5 hours (300 minutes) or 15 minutes When walking, the maximum travel time can be 5 hours (300 minutes). For all other travel modes, the maximum travel time can be 15 minutes. |
Maximum travel distance when generating detailed polygons | 15 miles (24.14 kilometers) For all travel modes, including walking, the maximum travel distance can be 15 miles (24.14 kilometers). |
Maximum travel time when generating service area lines | 5 hours (300 minutes) or 15 minutes When walking, the maximum travel time can be 5 hours (300 minutes). For all other travel modes, the maximum travel time can be 15 minutes. |
Maximum travel distance when generating service area lines | 15 miles (24.14 kilometers) For all travel modes, including walking, the maximum travel distance can be 15 miles (24.14 kilometers). |
Force hierarchy beyond a default cutoffs (break value) time of (If you specify drive time that exceeds the limit shown here, the analysis steps up the hierarchy even if hierarchy is not being used for the analysis.) | 240 minutes |
Force hierarchy beyond a default cutoffs (break value) distance of (If you specify drive distance that exceeds the limit shown here, the analysis steps up the hierarchy even if hierarchy is not being used for the analysis.) | 240 miles (386.24 kilometers) |
Maximum polygon trim distance | 500 meters |
Maximum number of polygon features that can be returned by job request service | 10,000 |
Maximum time a client can use the job request service area service | 2 hour (7,200 seconds) |
OD cost matrix
Caution:
Analysis limits may change. See Usage limits for current limits.
| Limit description | Limit value |
|---|---|
Maximum number of origins | 1000 |
Maximum number of destinations | 1000 |
Maximum number of point barriers | 250 |
Maximum number of street features intersected by polyline barriers | 500 |
Maximum number of street features intersected by polygon barriers | 2,000 |
Force hierarchy beyond a straight-line distance of (If the straight-line distance between any facility and demand point is greater than the limit shown here, the analysis uses hierarchy, even if hierarchy is not being used for the analysis.) | 50 miles (80.46 kilometers) |
Maximum time a client can use the job request service | 1 hour (3,600 seconds) |
Vehicle routing problem
Caution:
Analysis limits may change. See Usage limits for current limits.
| Limit description | Limit value |
|---|---|
Maximum number of orders | 2,000 |
Maximum number of routes | 100 |
Maximum number of orders per route | 200 |
Maximum number of point barriers | 250 |
Maximum number of street features intersected by polyline barriers | 500 |
Maximum number of street features intersected by polygon barriers | 2,000 |
Maximum straight-line distance for the walking travel mode (If the straight-line distance between any orders or depots is greater than this limit, the analysis fails when the walking restriction is used.) | 27 miles (43.45 kilometers) |
Force hierarchy beyond a straight-line distance of (If the straight-line distance between any orders or depots is greater than the limit shown here, the analysis uses hierarchy, even if hierarchy is not being used for the analysis.) | 50 miles (80.46 kilometers) |
Maximum number of directions features that can be returned | 200,000 |
Maximum time a client can use the fleet routing services | 4 hours (14,400 seconds) |