Latest Contributions by AyanPalit

@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

@Sergio The sequence of measures, dates and Route look correct from the table posted. However, you will have to validate the location of the points (X,Y) along the route. There are various tools in ArcGIS Pro to validate and align the point data before adding them as calibration points.  In my experience, the APR tools expect the data to be pre-processed ahead of any bulk load operation through REST or other means. I typically will QC the data in ArcGIS Pro, make corrections as needed and simply load through Pro, while I am there. It is not efficient to go back and forth between Pro and REST if the data is not perfectly aligned with LRS requirements.     ... View more

Here are some samples from my sandbox environment intended to demonstrate the REST API calls. User specific LRS model, LRS attributes need to be factored in and modify parameters to make it work. Query locks: Home > services > Pipeline (MapServer) > LRServer > locks > query  - where 1=1  The response gives you the format sample      Acquire locks: Home > services > Pipeline (MapServer) > LRServer > locks > acquire  - ADMIN.Ayan_APR | [{"lineId":"{06207673-6B1F-45A7-98FA-264AD4489804}","layerId" : 911},{"lineId":"{0E025F44-A0B5-435D-9827-AD1A871C8940}","layerId" : 911}] First attempt executed but no locks acquire as reconcile was needed.        Acquire locks: Home > services > Pipeline (MapServer) > LRServer > locks > acquire  - ADMIN.Ayan_APR | [{"lineId":"{06207673-6B1F-45A7-98FA-264AD4489804}","layerId" : 911},{"lineId":"{0E025F44-A0B5-435D-9827-AD1A871C8940}","layerId" : 911}] Reconciled versions and acquired locks        Release locks: Home > services > Pipeline (MapServer) > LRServer > locks > release  - [{"lineId":"{06207673-6B1F-45A7-98FA-264AD4489804}","layerId" : 911},{"lineId":"{0E025F44-A0B5-435D-9827-AD1A871C8940}","layerId" : 911}]     ... View more

@Sergio  Thanks for specifying the versions. If you must stay at ArcGIS Enterprise 10.9.1, it's recommended to use the compatible version of ArcGIS Pro 2.9. Reference Compatibility with ArcGIS Pro Here are some alternate methods for you to bulk load: Use Append Routes to  bulk load routes (pipelines)  Use Append to  bulk load calibration points, followed by Generate Routes It is expected that you have pre-processed and validated the geometries and attributes of the data to be bulk loaded. Failing to prepare the data, will result in errors. Usually the geoprocessing tool will provide a log with information in such cases. ... View more