- URL:
- https://<network-layer-url>/overlayEvents
- Methods:
GET- Required Capability:
- The ArcGIS Location Referencing license is required to use this resource.
- Version Introduced:
- 12.0
Description
The overlay operation segments event layers for selected routes where any measures change across the attribute set based on different measures or measure ranges. The result of this operation is a zipped file geodatabase that contains either a table or feature class with the values for the fields included in an attribute set and some additional fields that contain the route ID and measures from the network on which the query is performed. The include parameter determines whether a feature class or table is included in the zipped file geodatabase.
Request parameters
| Parameter | Details |
|---|---|
(Optional) |
Specifies the response format. The default response format is Values: |
(Required) | A list of routes and measure values used to segment event layers. The list can be either all single measures or all measure ranges; it can't mix single measures and measure ranges. Each route can have one or more different measures. If only a Syntax: |
| An attribute set that contains the point and linear event layers to query and fields to include in the result. The linear event layer can also be a Utility Network pipeline layer that has been configured as an LRS centerline using the Configure Utility Network Feature Class geoprocessing tool, or an address block range layer that has been configured as an LRS centerline using the Configure Address Feature Classes geoprocessing tool. When the centerline layer is an Address feature, the centerline direction is honored in the output. The object ID field for each layer specified will always be included in the results. If a field name already exists across all layers, it is renamed. If the input layer has address range fields from an Address Data Management configuration, and is configured as an address feature class in an LRS, the values in the address range fields will be updated for each segment in the output. Syntax: |
(Optional) | Specifies how address range will be updated for each segment of the output.
The default value is Values: |
(Optional) | Determines whether the output will include event geometry. The default value is Values: |
|
The time instant to use as a temporal view date when locating route features. If this parameter is not specified, the current date is used. The parameter value is a number that represents the number of milliseconds since epoch (January 1, 1970) in UTC. Syntax: Example: |
|
The spatial reference of the returned geometry. The spatial reference can be specified as either a Well-Known ID (WKID) or a spatial reference JSON object. If |
(Optional) |
Specifies the geodatabase version to use. If this parameter is not specified, the published map's version is used. Syntax: Example: |
(Optional) |
Specifies the historic moment to query. This parameter applies only if the layer is branch versioned and refers to geodatabase time (separate from LRS time). If this parameter is not specified, the query applies to the current features. Syntax: Example: |
Output file format
The output table or feature class will be in a zipped file geodatabase.
Example usage
Example 1
URL for segmenting a linear event layer with single measures.
https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/networkLayers/0/overlayEvents?f=json&locations=\[{'{'}"routeId":"I90","measure":25{'}'}]&attributeSet=\[{'{'}"layerId":1,"fields":\["aadt"]{'}'}]&outSR=102100Example 2
URL for segmenting a linear event layer with a measure range.
https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/networkLayers/0/overlayEvents?f=json&locations=\[{'{'}"routeId":"I90","fromMeasure":25.1,"toMeasure":26.8{'}'}]&attributeSet=\[{'{'}"layerId":1,"fields":\["aadt"]{'}'}]&outSR=102100Example 3
URL for segmenting a linear event layer with different routes and measures.
https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/networkLayers/0/overlayEvents?f=json&locations=\[{'{'}"routeId":"I90","measure":25.0{'}'},{'{'}"routeId":"US20","measure":72.6{'}'}]&attributeSet=\[{'{'}"layerId":1,"fields":\["aadt"]{'}'}]&outSR=102100Example 4
URL for segmenting a linear event layer with different measure ranges.
https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/networkLayers/0/overlayEvents?f=json&locations=\[{'{'}"routeId":"I90","fromMeasure":25.1,"toMeasure":26.8{'}'},{'{'}"routeId":"I90","fromMeasure":72.6,"toMeasure":80.5]&attributeSet=\[{'{'}"layerId":1,"fields":\["aadt"]{'}'}]&outSR=102100Example 5
URL for segmenting multiple linear event layers with different routes and measure ranges.
https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/networkLayers/0/overlayEvents?f=json&locations=\[{'{'}"routeId":"I90","fromMeasure":25.1,"toMeasure":26.8{'}'},{'{'}"routeId":"US20","fromMeasure":72.6,"toMeasure":80.5]&attributeSet=\[{'{'}"layerId":1,"fields":\["aadt"]{'}'},{'{'}"layerId":2,"fields":\["functional_class"]{'}'}]&outSR=102100Example 6
URL for segmenting a linear event layer for the entire route.
https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/networkLayers/0/overlayEvents?f=json&locations=\[{'{'}"routeId":"I90"{'}'},{'{'}“routeId”:”US20”{'}'}]&attributeSet=\[{'{'}"layerId":1,"fields":\["aadt"]{'}'}]&outSR=102100JSON Response syntax
The following is an example of response syntax for a status:
{
"statusURL": <jobIdURL>
}JSON Response example
Initial status response
The following is an example status returned with a job, which is used to make additional status calls:
{"statusURL":"https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/jobs/je9b6aa1da1904a23ab0d1a5513fba6f5"}Subsequent status response
The subsequent call uses the job returned above.
{
"status": "esriJobSucceeded",
"percentComplete": 100,
"overlayEventsJobResult":
{
"url": <URL>
}
}The following example demonstrates a response for calls using the job returned above:
{
"status": "esriJobSucceeded",
"percentComplete": 100,
"overlayEventsJobResult":
{
"url": https://organization.example.com/server/rest/directories/arcgisoutput/_ags_lrs_429B4209-7B0B-4A15-B7FD-2696DB757706.zip
}
}