You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps this is already an option, and I have been unable to find it. I have set up INTERSECTING_FEATURES method to run on the same field in a featureclass multiple times. For instance:
Table Name: BuildingSpace
Field Name: Occupant
Value Info: PolygonLayer|Occupant|C|True
And
Table Name: BuildingSpace
Field Name: Occupant
Value Info: PointLayer|Occupant|F|True
Ideally, I would like to see if the centroid of BuildingSpace intersects a feature in PolygonLayer, if so copy values, then see if it intersects PointLayer, and then if so, copy values from the first feature. However, regardless of how the rules appear in DynamicValue table, only one is executed. If one rule is weighted over the other, it appears that the higher weighted rule will run.
The text was updated successfully, but these errors were encountered:
Thanks for the reply @MikeMillerGIS. This doesn't appear to work, as the newly created feature's centroid doesn't intersect the PointLayer. If both intersecting features are polygons, and the centroid intersects both, it works as expected. Any other suggestions?
Something like the following would be nice, but after looking at the source, I don't this is possible:
Perhaps this is already an option, and I have been unable to find it. I have set up INTERSECTING_FEATURES method to run on the same field in a featureclass multiple times. For instance:
And
Ideally, I would like to see if the centroid of BuildingSpace intersects a feature in PolygonLayer, if so copy values, then see if it intersects PointLayer, and then if so, copy values from the first feature. However, regardless of how the rules appear in DynamicValue table, only one is executed. If one rule is weighted over the other, it appears that the higher weighted rule will run.
The text was updated successfully, but these errors were encountered: