How does ArcGIS Online credit consumption work when running the Generate Threshold Drive Times geoprocessing tool?

Answer

In ArcGIS Pro 2.5, the Generate Threshold Drive Times geoprocessing tool was introduced as part of the Business Analyst extension. The tool works by creating polygons that expand outward along network routes, until they reach a specified threshold variable, for example, 100,000 households around my store location.

When connected to online data, threshold values are calculated using ArcGIS Online geoprocessing services that consume credits . The algorithm that builds the Threshold Drive Time boundary is iterative and loops through scenarios before stopping when the threshold variable is accurately met.

• Typically, a Threshold Drive Time takes about six to twelve iterations to complete - each iteration counts as one drive time polygon (0.5 credits per polygon).
• Each iteration results in one Infographic View (0.01 credits per view).
• A GeoEnrichment Request is used to retrieve the demographic threshold variable on the final iteration (0.01 credits per view).

• Each store location may have one or more rings (for example, 1, 3, and 5-minute drive times) – each ring is considered a separate drive-time polygon.
• The street network density and demographic variable distribution around the store location(s) impacts the outcome.

It is not possible to predict how many iterations will be required to meet the threshold value.

Credit consumption is calculated for each individual trade area for N input location(s). (N input locations times number of rings per site, times the number of iterations per site, times the Infographic views per iteration, times GeoEnrichment of final polygons).

There are no ArcGIS Online credits consumed in this scenario when the Business Analyst Data Source is set to a locally installed dataset. The local dataset contains the street network, routing solvers, and demographic variables to complete the operation with the same results as using online data.