[Possible Bug] Intersect Geometries activity not working for multiple geometries

Terminée

Robin Lin

4 novembre 2025 22:37

We have a mature workflow in organization but failed to function recently. After trouble shooting, the Activity ‘Intersect Geometries’ is to blame. Workflow Version 5.47.0.

In my use case, Parameter 1 is a single geometry and parameter 2 is an array of geometries.

Two outputs: 'geometry' and ‘results’

 I believe the expected result (and according to help) should be:
‘geometry’ is the first valid intersection geometry and ‘results’ are all intersected area geometries. 

But the actual result is: ‘geometry’  = null

‘results’ = original input parameter 2 geometries

When both geometry1 and geometry 2 are single geometry, no issue. So I have to add another loop to iterate my geometry1 and each of my geometry2, solved the problem at least.

 

0

• 

  Ken Lyon

  13 novembre 2025 16:05 Modifié

  Robin Lin Thanks for reporting this. I can see where the behaviour of Intersect Geometries has changed.

  Workflow 5.47 included an upgrade to a new version of the ArcGIS Maps SDK for JavaScript, and one of the things we changed was to move from using the deprecated intersect method of geometryEngineAsync to the new execute method of intersectionOperator in the Intersect Geometries activity.

  The old method allowed you to intersect an array with a single geometry, but the new one only allows intersecting two geometries. It seems the way we adapted the code didn't quite retain the same behaviour as before.

  Consider using the Intersect Geometries activity with these inputs:

  geometry1 = [a, b, c];
  geometry2 = [d, e, f];

  The old code would have produced this output:

  [
    (intersection of a with d),
    (intersection of b with d),
    (intersection of c with d),
    (intersection of a with e),
    (intersection of b with e),
    (intersection of c with e),
    (intersection of a with f),
    (intersection of b with f),
    (intersection of c with f),
  ]

  The new code produces this output:

  [
    (intersection of a with d),
    (intersection of b with e),
    (intersection of c with f),
  ]

  Unfortunately our unit tests for this activity still passed and we failed to catch this as a regression. I will log a bug to address this and restore the previous behaviour.

   

   

  0
• 

  Ken Lyon

  18 novembre 2025 19:03

  Robin Lin This has been fixed in Workflow 5.48.1, which was released today. This should hopefully be included in the next release of VertiGIS Studio Web.

  1

Vous devez vous connecter pour laisser un commentaire.