Select to view content in your preferred language

Error 500: unable to complete operation on create calibration point via REST API

608
3
Jump to solution
10-31-2024 06:27 AM
Sergio
by
Emerging Contributor

Hi all,

I get error 500 on attempt to create calibration points via LRS REST API like this:

{"error":{"code":500,"message":"Unable to complete operation.","details":[]}}

I'm using applyEdits endpoint like described here: Apply Edits | ArcGIS REST APIs | ArcGIS Developers.

The JSON file I'm passing as "edits"  via "multipart/form data" parameter is 100% correct and valid. Here it is:

[
    {
        "id": 1,
        "addCalibrationPoints": [
            {
                "networkLayerId": 33,
                "routeId": "{GUID}",
                "geometry": {
                    "x": 225636.17500000005,
                    "y": 995688.0829999996
                },
                "fromDate": "1170356400",
                "measure": 2636.8490000000002,
                "recalibrateRouteDownstream": false,
                "retire": false
            }
        ]
    }
]
 

I'm adding calibration points on newly created routes in newly created version under separate session. I can create routes without any issues but calibration points won't apply.

What may cause such issues? Where can I see extended description of what is happening?

Thank you in advance!

0 Kudos
1 Solution

Accepted Solutions
AyanPalit
Esri Regular Contributor

@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.
Ayan Palit | Principal Consultant Esri

View solution in original post

3 Replies
AyanPalit
Esri Regular Contributor

@Sergio Have you tried adding calibration points on this route using 'Add Point' tool in Location Referencing ribbon in ArcGIS Pro? This is the preferred APR tool for adding calibration point to routes interactively. Perhaps, trying in Pro will provide additional details. 

Please state the Enterprise and Pro versions being used. It will help to know your preference for using the LRS REST API for this step - are you trying to develop a programmatic too to automate a process?    

Ayan Palit | Principal Consultant Esri
0 Kudos
Sergio
by
Emerging Contributor

Hi @AyanPalit ,

Thank you for your input.

The version of Enterprise is 10.9.1 and Pro is 3.2.2. You are right - I'm trying to automate the bulk loading of routes (pipelines) and calibration points. I'm using FME Flow for this and there is no issues with creation of routes using the same applyEdits endpoint. After creation of routes I pass route Ids to create JSON for loading calibration points. Tried just one point as well - same result. Same results I get in Postman with hardcoded JSON. Also I'm using PODS model rather than clean APR. 

I'll try to load calibration points via Pro as you suggested and maybe this will give more information on the error. Anyway, maybe it is possible to check some Server or Portal logs?

Thank you!

0 Kudos
AyanPalit
Esri Regular Contributor

@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.
Ayan Palit | Principal Consultant Esri