Driving or walking time areas created for a location using the routing service
What is a service area?
A service area, also known as an isochrone, is a polygon that represents the distance that can be reached when driving or walking on a street network. This type of analysis is common in real estate search or determining the driving proximity to schools, businesses, or other facilities. For example, you can create a drive time polygon that represents how far you can drive in any direction from the center of a city in 20 minutes.
You can use service areas to build applications that:
Visualize and measure the accessibility of locations that provide some kind of service. For example, a three-minute drive-time polygon around a grocery store can determine which residents are able to reach the store within three minutes and are thus more likely to shop there.
By generating multiple service areas around one or more locations that can show how accessibility changes with an increase in travel time or travel distance. It can be used, for example, to determine how many hospitals are within 5, 10, and 15 minute drive times of schools.
When creating service areas based on travel times, the service can make use of traffic data, which can influence the area that can be reached during different times of the day.
How service areas work
The typical workflow for creating service areas is to define:
One or more locations around which service areas are generated (facilities).
The size and number of service areas to generate for each facility.
Define the type of travel for the analysis.
Call the service to generate service areas around facilities.
URL requests
You can generate service areas by making an HTTPS request to the Service Area service solveServiceArea operation or by using client APIs. Specify the one or more input facilities, and optionally, additional parameters to refine the operation. Some of the most common parameters are described provided below.
Request limits
Limit
Direct
Job
Maximum number of facilities:
100
1,000
Maximum transaction time:
5 minutes
2 hours
Maximum number of breaks:
No limit
No limit
Maximum travel time:
9 hours when walking 5 hours for all other travel modes
9 hours when walking 5 hours for all other travel modes
Maximum travel distance:
27 miles (43.45 kilometers) when walking 300 miles (482.80 kilometers) for all other travel modes
27 miles (43.45 kilometers) when walking 300 miles (482.80 kilometers) for all other travel modes
Maximum travel time when generating detailed polygons:
5 hours when walking 15 minutes for all other travel modes
5 hours when walking 15 minutes for all other travel modes
Maximum travel distance when generating detailed polygons:
15 miles (24.14 kilometers) for all travel modes
15 miles (24.14 kilometers) for all travel modes
Maximum travel time when generating service area lines:
5 hours when walking 15 minutes for all other travel modes
5 hours when walking 15 minutes for all other travel modes
Maximum travel distance when generating service area lines:
15 miles (24.14 kilometers) for all travel modes
15 miles (24.14 kilometers) for all travel modes
Maximum number of point barriers:
250
250
Maximum number of street features intersected by polyline barriers:
500
500
Maximum number of street features intersected by polygon barriers:
2,000
2,000
Force hierarchy beyond a travel time of:
(If you specify a drive time that exceeds the limit shown here, the analysis uses the hierarchy even if the travel mode defines not to use hierarchy)
60 minutes
The 60-minute limit applies when generating polygons with standard level of detail. (outputPolygons = esriNAOutputPolygonSimplified).
When walking, the analysis does not force hierarchy even when this limit is exceeded and always returns polygons with standard level of detail.
4 hours
The 4-hour limit applies when generating polygons with standard level of detail. (polygon_detail = Standard).
When walking, the analysis does not force hierarchy even when this limit is exceeded and always returns polygons with standard level of detail.
Force hierarchy beyond a travel distance of:
(If you specify a drive distance that exceeds the limit shown here, the analysis uses the hierarchy even if the travel mode defines not to use hierarchy)
60 miles (96.56 kilometers)
The 60-mile limit applies when generating polygons with standard level of detail. (outputPolygons = esriNAOutputPolygonSimplified).
When walking, the analysis does not force hierarchy even when this limit is exceeded and always returns polygons with standard level of detail.
240 miles (386.24 kilometers)
The 240-mile limit applies when generating polygons with standard level of detail. (polygon_detail = Standard).
When walking, the analysis does not force hierarchy even when this limit is exceeded and always returns polygons with standard level of detail.
Maximum polygon trim distance:
500 meters
500 meters
Maximum snap tolerance:
(If the distance between an input point and its nearest traversable street is greater than the distance specified here, the point is excluded from the analysis.)
12.42 miles (20 kilometers)
12.42 miles (20 kilometers)
Maximum number of polygon features that can be returned by the service:
The direction of travel (away from facility or towards facility) that should be used when generating service areas.
travelDirection=esriNATravelDirectionFromFacility
timeOfDay
The time to depart from or arrive at facilities. You can also specify a value of now, to set the depart or arrive time to current time.
timeOfDay=now
Additional parameters: Exercise fine-grained control on how the service area polygons are generated by specifying outputPolygons, splitPolygonAtBreaks, overlapPolygons, and mergeSimilarPolygonRanges parameters.
Job
Use for longer transactions with up to 1,000 facilities that will complete in less than 2 hours.
The direction of travel (away from facility or towards facility) that should be used when generating service areas.
travel_direction=Away From Facility
time_of_day
The time to depart from or arrive at facilities.
time_of_day=1608022800000
Additional parameters: Exercise fine-grained control on how the service area polygons are generated by specifying polygon_detail, polygon_overlap_type, and polygons_for_multiple_facilities parameters.
Code examples
Direct: Find walk distance areas
In this example, use the Service area service to find an area that is within 2.5 kilometers (1.55 miles) of walking distance from an elementary school. Such an area can be used to determine which students are eligible for the school bus service as the students that live within 1.5 miles of walking distance from the school are not eligible.
To find service areas, you need to define one or more facilities around which service areas are generated. The default travelMode is driving time, so in this case the travel mode is set to walking distance. The defaultBreaks are set to 2.5 which is interpreted by the service to be in kilometers since the distance unit of the travel mode's impedance attribute is kilometers. The travel direction is set to esriNATravelDirectionToFacility to calculate the walk area as students walk towards the school.
The response contains a polygon of the walk area with 1.55 miles that does not qualify for bus transportation.
APIs
ArcGIS Maps SDK for JavaScriptArcGIS Maps SDK for JavaScriptArcGIS Maps SDK for .NETArcGIS Maps SDK for JavaArcGIS Maps SDK for Qt (C++)ArcGIS Maps SDK for Qt (QML)ArcGIS API for PythonArcGIS REST JSEsri LeafletMapLibre GL JSOpenLayersCesiumJS
In this example, you will find the 5, 10, and 15 minute drive-time polygons around all locations of a grocery store chain in a city. The chain wants to use these drive-time areas to see how many customers can easily drive to their stores and thus are more likely to shop there.
The example illustrates how to measure the time it takes potential customers to reach each store. To do so, the travel_direction is set to Towards Facility. Attributes for each store are also provided such as the StoreId, StoreName, and Address. These will be appended to the drive-time areas to correlate the output drive-time area with the store.
Unlike Direct request type which allows you to make a request and get back all the results in the response, when working with a Job request type, you need to follow a three step workflow:
Make the submitJob request with the appropriate request parameters to get a job id.
Using the job id, check the job status to see if the job completed successfully.
Use the job id to get one or more results.
cURLcURLHTTP
Use dark colors for code blocksCopy
1
2
3
4
5
6
curl https://logistics.arcgis.com/arcgis/rest/services/World/ServiceAreas/GPServer/GenerateServiceAreas/submitJob? \
-d"f=json" \
-d"token=<ACCESS_TOKEN>" \
-d"facilities={'displayFieldName':'','fieldAliases':{'StoreName':'Store Name','Address':'Address','StoreId':'Store ID'},'geometryType':'esriGeometryPoint','spatialReference':{'wkid':4326,'latestWkid':4326},'fields':[{'name':'StoreName','type':'esriFieldTypeString','alias':'Name','length':50},{'name':'Address','type':'esriFieldTypeString','alias':'Name','length':256},{'name':'StoreId','type':'esriFieldTypeString','alias':'Store ID','length':16}],'features':[{'attributes':{'StoreName':'Store 1','Address':'1775 E Lugonia Ave, Redlands, CA 92374','StoreId':'120'},'geometry':{'x':-117.14002999994386,'y':34.071219999994128}},{'attributes':{'StoreName':'Store 2','Address':'1536 Barton Rd, Redlands, CA 92373','StoreId':'130'},'geometry':{'x':-117.207329999671,'y':34.047980000203609}},{'attributes':{'StoreName':'Store 3','Address':'11 E Colton Ave, Redlands, CA 92374','StoreId':'121'},'geometry':{'x':-117.18194000041973,'y':34.06351999976232}}]}" \
-d"break_values=5 10 15" \
-d"travel_direction='Towards Facility'"