Latest Contributions by JayCary

@CarsonGThis enhancement to the Browse Features pane is planned for the next release. ... View more

@BethanyHodge and others who find this idea, see the following ArcGIS Pro ideas requesting this functionality and add your specific use-case and kudos to show your support: ArcGIS Pro Topology Error Inspector - Sort Headers Error Inspector Enhancement Note: The Error Inspector supports error management for multiple workflows including Topology rules and Attribute rules (where Data Reviewer error features live). Enhancements to the Error Inspector are typically shared across these workflows. Thanks! ... View more

Wouldn't the Differences view support the workflow identified above? ... View more

Thanks-much for the feedback. Unfortunately, support for data validation workflows which leverage Reviewer Batch Jobs is planned for deprecation in a future release of ArcGIS Pro. ... View more

This scenario may be supported depending on how attribute values are stored in the participating features. Please feel free to update your idea if the below does not work! The Feature on Feature check can be configured to identify points with attribute values that do not match nearby line features. Using the Esri local government schema, the following configuration of the check identifies Site Address Points that contain Full Road Name (FullName) values that do not match the Full Road Name (FullName) values of nearby Road Centerline features. Feature on Feature check configuration Input feature class: SiteAddressPoints Features to Compare: RoadCenterline Features to Compare Filter (optional): Roadclass includes the value(s) 'Minor Arterial','Major Arterial','Local' Spatial Relationship: Intersects Horizontal Search Distance (may vary): 500 US Feet Attribute Relationship:  FullName is equal to FullName Invert Relationship: True Depending on your schema, a similar configuration may also support evaluation of address numbers against road centerline address ranges.  ... View more

Hi, Can you share some additional details on the workflow/environment that you configured your Evaluate Polygon Perimeter and Area check? Was the validation attribute rule created manually from the Ready to Use Rules gallery or exported/imported from a Reviewer Batch Job file. The geodatabase type and the spatial reference of input dataset This would be helpful in troubleshooting Thanks! ... View more

Thanks-much for sharing the details of your configuration! There appears to be an issue during evaluation when a dataset contains multiple Query Attributes-based rules and one of those rules contains an Attribute Filter. The development team has been able to reproduce this behavior and have logged a bug to address the issue. Thanks again for the heads-up! ... View more

Hi, Can you share some additional details on how you have configured your Query Attributes checks? For example, the type of geodatabase used, filters (Subtype, Attribute) and Search Goal configuration would be helpful in troubleshooting. Thanks! ... View more

@cordtsraThanks for the clarification. The Table to Table Attribute check requires that the data source referenced by the Features/Rows to Compare parameter must include a global ID field. Can you confirm that your table include a global ID? ... View more

@cordtsra wrote: I am currently working on converting RBJs to Attribute Rules. One issue I noticed is that I can't run a standalone check, or a composite check with a non-spatial table. I can create attribute rules for the non-spatial table, but there is no way to run those rules as you cannot add error layers for that table. Also, if I want to reference the non-spatial table in another feature class's attribute rules it doesn't appear in the drop down. For clarification, which Data Reviewer check(s) are you trying to use with your table? ... View more

Not Arcade, but Data Reviewer's Feature on Feature check can be used to implement a validation attribute rule which identifies the above scenario (spatial relationship: intersects, Compare Attributes: Network Level ≠ Network Level). Unfortunately, the same check used as a constraint attribute rule lacks the ability to compare attributes of features that intersect. ... View more