Latest Contributions by SergueiSokolov

The requirement is to replicate what the GP "Annotate Selected Features" does in Pro using REST API call(s). The fact that there is an Apply Edits operation available on the Annotation Layer suggests that it should be possible to create annotations directly via the rest service. Configuration: AGE10.9.1, ArcGIS Pro 2.9.4, Electric Utility Network Foundation dataset. We have completed the following steps: - created a feature-linked annotation class referencing the Utility Network dataset, published as the Feature Layer service - tested adding a new UN feature using REST API (Add Feature and Apply Edits). Worked as expected, both calls created new UN features with the respective feature-linked annotations.  - tested adding Annotation to the existing features in Pro using GP Annotate Selected Features . Created a map referencing the UN feature layer, executed GP Annotate Selected Features. Worked as expected, a feature-linked annotation was created for the selected feature. - tried to use REST API (..server/rest/services/Electric_UN_Annotation/FeatureServer/14/applyEdits) to add feature linked annotations to existing features. The operation doesn’t fail (i.e. it claims success as a result of the post) but the annotation is not created / doesn’t show up. I’m passing the following edits to the Apply Edits of the Annotation feature service [{"attributes":{ "TextString":"test annotation, N,", "FeatureGlobalID":"{15D74B0A-B823-436D-B115-9FEBE969A0D5}", "AnnotationClassID":1, "Status":0, "Angle":358.059 }, "geometry":{"rings":[[[356112.8754,198283.8749],[356146.1860,198282.7461],[356146.4548,198191.6771],[356113.1442,198192.8060],[356112.8754,198283.8749]]]} }] And the result is { "addResults": [{   "objectId": 34040,   "globalId": "{54F518C3-1B6D-418F-B4B9-9A3A975C14D1}",   "success": true }], "updateResults": [], "deleteResults": [] } What additional steps should be done to create a feature linked annotation for the selected features using REST API? Basically we would like to replicate what GP Annotate Selected Features does but using the REST calls. Please advise thank you ... View more

We suggest adding a capability to return an aggregated geometry that has the exact length as defined by a Function Barrier condition. By default, when we trace fiber strands (non-spatial Communication edge objects) the trace returns the concatenated geometries of the traced parent features (i.e. the entire line features representing fiber cables) not a partial feature result as per the Function Barrier. Example use case is a Fiber OTDR Trace. The OTDR (Optical Time Domain Reflectometer) device provides a distance to the location of a problem. The User should be able to select a specific fiber strand to trace, set a Function Barrier condition to the OTDR distance value and set Result Type to “Aggregated Geometry”. The key is that the returned by the Trace aggregated geometry should be “trimmed” to the exact value set by the Function Barrier (i.e. provide partial feature result). This will allow a precise location of the problem to be graphically indicated. ... View more

We are developing an add-in for ArcGIS Pro 2.6.4 to update Utility Network features. The add-in uses a Feature Service to update the Enterprise geodatabase (ArcGIS Enterprise 10.8.1, Utility Network Communications Data Management v1 geodatabse in SQL Server). The logic we are trying to implement in the add-in conflicts with the logic of features' creation that was implemented in the Attribute Rules. We would like to disable selected Attribute Rules for duration of the update transaction. Is it possible to disable an attribute rule temporarily (in a session) using a feature service API?  There are GP tools to enable/disable Attribute Rules in the Attribute Rules toolset. However, we have observed that disabling / altering an attribute rule using GP tools has the geodatabase scope and requires an exclusive lock on the dataset. Any active connections to the dataset should be closed and disabling requires stopping of the feature services. Hence we cannot use the provided GP tools for our use case.  PS: I do understand that Attribute Rules were invented to address consistency and integrity of the data concerns. The challenge is that attribute rules can also be used to automate editing of data in Pro thus enforcing only certain logic/ order of data editing steps. Hence it would be desirable to bypass / disable certain Attribute rules at runtime via API in add-ins that implement a different logic of editing features & relationships.   ... View more