applyEdits creates multiple copies of routes along with calibration points as passed in edits JSON

Sergio

Hello!

I see very strange behavior of the applyEdits endpoint when trying to upload set of calibration points. It creates not just calibration points but set of routes copies to which I'm trying to apply calibration points. Here is the example of JSON I pass to the endpoint:

[

    {

        "id": 1,

        "addCalibrationPoints": [

            {

                "networkLayerId": 33,

                "routeId": "{RouteNo1}",

                "geometry": {

                    "x": 7933907.5401063189,

                    "y": 7793303.80977148,

                    "z": -24,

                    "spatialReference": {

                        "latestWkid": 3857,

                        "wkid": 102100

                    }

                },

                "fromDate": 1170374400,

                "toDate": 1170460800,

                "measure": 134.07499999999999,

                "recalibrateRouteDownstream": 0,

                "retire": 0

            },

            {

                "networkLayerId": 33,

                "routeId": "{RouteNo1}",

                "geometry": {

                    "x": 7933929.4377417713,

                    "y": 7793317.261703142,

                    "z": -24,

                    "spatialReference": {

                        "latestWkid": 3857,

                        "wkid": 102100

                    }

                },

                "fromDate": 1170374400,

                "toDate": 1170460800,

                "measure": 155.857,

                "recalibrateRouteDownstream": 0,

                "retire": 0

            },

            {

                "networkLayerId": 33,

                "routeId": "{RouteNo1}",

                "geometry": {

                    "x": 7934213.5078702234,

                    "y": 7793274.3926343555,

                    "z": -25,

                    "spatialReference": {

                        "latestWkid": 3857,

                        "wkid": 102100

                    }

                },

                "fromDate": 1170374400,

                "toDate": 1170460800,

                "measure": 355.46199999999999,

                "recalibrateRouteDownstream": 0,

                "retire": 0

            }

        ]

    }

]

 

In response I get JSON log that apart from calibration points polylines were created and when I go to my version I see all these lines created as routes. Anyone saw such behaviour? Maybe something with my query parameters? But I pass only "edits", "gdbVersion" and "sessionId" and all this passes (otherwise I would get error with reference to invalid parameter).

Ayan Palit

@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