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 overlayEvents 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 includeGeometry parameter determines whether a feature class or table is included in the zipped file geodatabase.

Request parameters

ParameterDetails

f

(Optional)

Specifies the response format. The default response format is html.

Values: html | json

locations

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 routeId is provided, the entire route is returned.

Syntax:

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
// syntax of a single measure
[
  {
    "routeId": "<routeId1>",
    "measure": <measure1>
  },
  {
    "routeId": "<routeId1>",
    "measure": <measure2>
  }
  ...
]

// syntax of a measure range
[
  {
    "routeId": "<routeId1>",
    "fromMeasure": <measure1>,
    "toMeasure": <measure2>
  },
  {
    "routeId": "<routeId1>",
    "fromMeasure": <measure3>,
    "toMeasure": <measure4>
  }
  ...
]

// syntax to return the entire route
[
  {
    "routeId": "<routeId1>"
  },
  {
    "routeId": "<routeId2>"
  }
  ...
]

attributeSet

An attribute set that contains the event layers to query and fields to include in the result. The event layers can also be one of the following:

If the input layer has address range fields from an Address Data Management configuration, and is configured as an Address Range feature class in an LRS, the values in the address range fields will be updated for each segment in the output.

Syntax:

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
[
  {
    "layerId" : "<layerId1>",
    "fields" : [ "<field1>", "<field2>", "<field3>", ... ]
  },
  {
    "layerId" : "<layerId2>",
    "fields" : [ "<field1>", "<field2>", ... ]
  },
  ...
]

addressBlockSplitType

(Optional)

Specifies how address range will be updated for each segment of the output.

  • nearest—Address ranges will be updated for each segment in the output based on the nearest upstream and downstream address values.

  • proportional—Address ranges will be updated for each segment in the output proportionally from the split location.

The default value is proportional.

Values: nearest | proportional

includeGeometry

(Optional)

Determines whether the output will include event geometry.

The default value is false.

Values: true | false

temporalViewDate

(Optional)

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:

Use dark colors for code blocksCopy
1
temporalViewDate=<timeInstant>

Example:

Use dark colors for code blocksCopy
1
temporalViewDate=1230768000000 (1 Jan 2009 00:00:00 GMT)

outSR

(Optional)

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 outSR is not specified, the geometry is returned in the spatial reference of the map service.

gdbVersion

(Optional)

Specifies the geodatabase version to use. If this parameter is not specified, the published map's version is used.

Syntax:

Use dark colors for code blocksCopy
1
gdbVersion=<version>

Example:

Use dark colors for code blocksCopy
1
gdbVersion="user1.version1"

historicMoment

(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:

Use dark colors for code blocksCopy
1
historicMoment=<epoch time in milliseconds>

Example:

Use dark colors for code blocksCopy
1
historicMoment=1514764800000

parallelFactor

(Optional)

Specifies the number or percentage of processes that will be used for the analysis. This parameter applies only to events that span multiple routes and nonspanning events that are not registered with the target network.

The default value, if left blank, is 0%. Any absolute value is always clamped between 0 and the number of logical cores on your machine.

Syntax:

Use dark colors for code blocksCopy
1
parallelFactor=<value>

Example:

Use dark colors for code blocksCopy
1
parallelFactor=8

Output file format

The output table or feature class will be in a zipped file geodatabase.

Example usage

Example 1

URL for segmenting a line event layer with single measures.

Use dark colors for code blocksCopy
1
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=102100

Example 2

URL for segmenting a line event layer with a measure range.

Use dark colors for code blocksCopy
1
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=102100

Example 3

URL for segmenting a line event layer with different routes and measures.

Use dark colors for code blocksCopy
1
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=102100

Example 4

URL for segmenting a line event layer with different measure ranges.

Use dark colors for code blocksCopy
1
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=102100

Example 5

URL for segmenting multiple line event layers with different routes and measure ranges.

Use dark colors for code blocksCopy
1
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=102100

Example 6

URL for segmenting a line event layer for the entire route.

Use dark colors for code blocksCopy
1
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=102100

JSON Response syntax

The following is an example of response syntax for a statusURL:

Use dark colors for code blocksCopy
1
2
3
{
  "statusURL": <jobIdURL>
}

JSON Response example

Initial status response

The following is an example statusURL returned with a jobIdURL, which is used to make additional status calls:

Use dark colors for code blocksCopy
1
{"statusURL":"https://organization.example.com/server/rest/services/MyLRS/MapServer/exts/LRServer/jobs/je9b6aa1da1904a23ab0d1a5513fba6f5"}

Subsequent status response

The subsequent call uses the jobIdURL returned above.

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
{
  "status": "esriJobSucceeded",
  "percentComplete": 100,
  "overlayEventsJobResult":
  {
    "url": <URL>
  }
}

The following example demonstrates a response for calls using the jobIdURL returned above:

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
{
  "status": "esriJobSucceeded",
  "percentComplete": 100,
  "overlayEventsJobResult":
  {
    "url": https://organization.example.com/server/rest/directories/arcgisoutput/_ags_lrs_429B4209-7B0B-4A15-B7FD-2696DB757706.zip
  }
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.