Latest Contributions by AyanPalit

@mshanaghan  The Utility Network has special requirements, given the unique capabilities it offers over simple features. The utility network owner must be a database-authenticated user. The user must have database privileges to create content and cannot be an OS-authenticated user, a database administrator, or the geodatabase administrator account. The input feature dataset must be from a database connection established and the connected user will become the database utility network owner. When working with a utility network stored in an enterprise geodatabase, there are two owners for a utility network dataset: the database owner and the portal owner. The database utility network owner is determined by the database user used in the data source when a utility network is created. You must access the utility network as the database utility network owner for configuration and publishing tasks. REFERENCE: Create a utility network ... View more

@Seshanth_R  The typical user needs the ArcGIS Pro app to properly process, review and edit the centerline geometry that is an input to route creation. Validating and correcting the centerline geometry is a pre-requisite to ensure a well formed, calibrated route. This is best achieved in ArcGIS Pro, using the full editing tools, snapping, and geometry methods available. Hence, the APR Create Route tool in the Location Referencing ribbon is best suited for this workflow. Having said this, majority of the APR operations leverage the services-based pattern and the REST API is well documented: REST API developer guide, for services published from ArcGIS Pro    Specifically, Apply Edits  > Network layer > createRoute    [ { "id": <networkLayerId>, "createRoute": [ {"centerlineObjectIds": [<objectId1>, <objectId2>, ...], "flippedCenterlineObjectIds": [<objectId2>, ...], "fromMeasure": <measure>, "toMeasure": <measure>, "attributes": { "<fieldName1>": <value1>, "<fieldName2>": <value2>, ... } } ] } ]   Given the above capability, system implementers have the option to use the linear referencing REST API and create a custom widget to meet customer specific requirements. LRS Event editing is already available as ExB widgets: Add Point Event Add Line Event Split Events Merge Events     Recommend the customer to log an enhancement request trough their Esri Account Manager and/or at Pipeline Referencing Ideas It always helps to learn unique use cases and why the current tool capability does not meet the requirement.   ... View more

Updating this old thread for tracking and community documentation. The Generate Schema Report geoprocessing tool documents the LRS configuration. This includes the Event Behavior rules listed for the LRS events configured. A sample can be downloaded at: Pipeline Referencing Information Model ... View more

@Sergio My understanding on the issue is set of routes copies created when adding calibration points. This is likely due to the From Date/To Date mismatch between  calibration point records and the corresponding route records. LRS is natively time aware and based on the data (Date/Time attribution) may introduce time slices. Users not aware of this are thrown off-guard and puzzled with the duplicate records as in your case. Note the From Date/To Date of the route {RouteNo1} Use the same From Date/To Date for the calibration points to be added on {RouteNo1} Review the attribute table of the layers after the data load. Generate Routes and QC ... View more