- Version Introduced:10.8.1
The ArcGIS Location Referencing license is required to use this resource.
This operation generates intersection points between the parent LRS Network layer and each of the intersecting layers of an LRS Intersection. Internally, it calls the Generate Intersections geoprocessing tool.
Description: Optional parameter to specify the response format. The default response format is html.
Values: html | json
Optional parameter to specify a list of Object IDs or a SQL WHERE clause defining the parent network routes on which the operation will be performed. If this parameter is not specified, the operation will be run across the entire network feature class. The operation is not time aware, so considers all time ranges of the input routes.
Description: Optional parameter to specify the epoch date, which acts as a filter on the Edit Date field of the parent network feature class. Parent network routes edited on or after this date are considered for the operation. The default value is the current date.
Syntax: startDate=<epoch date>
Description: Optional boolean parameter to only consider the parent network routes that were edited by the logged in portal user. The user name is used as a filter on the Editor field of the parent network feature class. The default value is true.
Description: Optional parameter to specify the geodatabase version to use. If this parameter is not specified, the published map's version is used.
Description: Optional parameter set by a client during long transaction editing on a branch version. The sessionId is a guid value that clients establish at the beginning and use throughout the edit session. The sessonId ensures isolation during the edit session.
Description: Optional parameter to specify whether the response will report the time edits that were applied. If returnEditMoment=true, the server will return the time edits that were applied in the response's editMoment key. The default value for this parameter is false.
Description: Optional parameter that returns features edited due to the geodatabase behavior that results from applying the edits. For example, if a feature is deleted and it is the origin in a composite relationship, the destination feature is automatically deleted in the geodatabase. If returnServiceEditsOption is set to originalAndCurrentFeatures, the deleted destination feature is returned along with a reference to the deleted origin feature in the response. Note that, even for deletes, the geometry and attributes of the edited feature are returned.
Results returned from applyEdits are organized in layer-by-layer fashion. If the returnServiceEditsOption is set to originalAndCurrentFeatures, each layer may have edited features returned in an editedFeatures object.
Service-level applyEdits response structure:
The editedFeatures object returns full features, including the original features prior to delete, the original and current features for updates, and the current rows for inserts that may contain implicit changes (for example, as a result of a calculation rule).
editedFeatures response structure:
The response includes no editedFeatures and exceededTransferLimit=true if the count of edited features to return is more than the maxRecordCount. If clients are using this parameter to maintain a cache, they should invalidate the cache when exceededTransferLimit = true is returned. If the server encounters an error when generating the list of edits in the response, exceededTransferLimit = true is also returned.
Edited features are returned in the spatial reference of the feature service as defined by the services spatialReference object or by the spatialReference of the layers extent object.
The default for this parameter is none, which will not include editedFeatures.
Use the following example calls to generate all intersections or to specify a selection set for which to generate intersections.
URL to call to generate all possible intersections:
URL to call to generate intersections on a selection set:
JSON Response syntax
Query this job URL to get progress updates and results of the
JSON Response example