Hi all,
I get the following message when trying to apply a set of calibration points on newly created routes:
Provided measure 355.462000 will result in a non monotonic route for routeId {RouteNo1}
Here is the dataset I'm trying to apply:
fromDate | measure | routeId |
1170374400 | 134.075 | {RouteNo1} |
1170374400 | 155.857 | {RouteNo1} |
1170374400 | 355.462 | {RouteNo1} |
1170374400 | 370.061 | {RouteNo1} |
1170374400 | 602.918 | {RouteNo1} |
1170374400 | 626.097 | {RouteNo1} |
1170374400 | 1089.544 | {RouteNo1} |
1170374400 | 1100.629 | {RouteNo1} |
1170374400 | 1540.883 | {RouteNo1} |
1170374400 | 1576.177 | {RouteNo1} |
1170374400 | 2022.328 | {RouteNo1} |
1170374400 | 2032.482 | {RouteNo1} |
1170374400 | 2466.008 | {RouteNo1} |
1170374400 | 2505.28 | {RouteNo1} |
1170374400 | 2636.849 | {RouteNo1} |
In my understanding there should be no issues with this dataset as measures are going consequently along the stream. On lines points are going along the stream as well (in terms of geometry).
I'm trying to upload this data via LRS API applyEdits query with following JSON (I'm showing only three records for shortness):
Solved! Go to Solution.
@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.
@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.
Hi @AyanPalit , Thank you for your help and input. You are right - in my case it was related to geometry of the points - it was duplicates in terms of coordinates. Getting rid of such duplicates solved the issue. And you are absolutely right saying that bulk load through API expects pre-processed and carefully checked datasets - one mistake and all transaction will be rolled back with error.
Glad you were able to isolate the culprit points!