Latest Contributions by JayCary

‎10-31-2023

You might want to start your investigation by identifying those rules in the Reviewer Batch Job that are taking the most time to complete. Reviewing the contents of the log file that is created when running the Execute Reviewer Batch Job geoprocessing tool is a good place to start. The file is stored in the %localappdata%\Esri\DataReviewer folder and will contain summary messages of the rules run when using the tool. On a related note, this tool was directly migrated from ArcMap to ArcGIS Pro. It is provided to enable users in a mixed desktop environment (ArcMap and ArcGIS Pro) to work together. I would suggest evaluating Data Reviewer's "native" data validation capabilities for those organizations who are migrating to ArcGIS Pro.

‎09-14-2023

As @PaulinaKarkauskaite pointed-out, some of the basic tools used in visual QC review are already available in ArcGIS Pro and there are additional tools planned for future releases. That said, I'd be interested in getting feedback on QC requirements your customer envisions needing after their migration to ArcGIS Pro. This input would help the team ensure that Pro-based workflows reflect current needs of data production workflows and improve over those created in the past. Feel free to send me a message if you'd like to schedule a meet-up!

‎09-08-2023

You might want to investigate the use of an input filter on this check. Filters can be applied to the Find Dangles check to only evaluate those features within a specific geodatabase subtype (Subtype parameter) and/or features that match a SQL WHERE clause (Attribute parameter).

‎08-29-2023

There are a couple of options available in ArcGIS Pro that support a similar workflow as ArcMap's Commit To Reviewer Table tool. The Browse Features tool supports the interactive review of a selection of features and creation of error results for those features that fail review. Alternatively, the Write to Reviewer Table geoprocessing tool supports the creation of error features based on an input feature layer.

‎07-20-2023

Does this help? The Data Reviewer based tools (DR itself and "Missing Features" and "Browse Features" of Manage Data Quality) use only the DR schema and that evaluate data quality step (from error inspector or the work flow manager step) only the error layers. For clarification, the following tools in ArcGIS Pro support the Reviewer Workspace: Flag Missing Features Browse Features GP tools (Execute Reviewer Batch Job, Write To Reviewer Table, Create Reviewer Session, Delete Reviewer Session, Enable Data Reviewer) Can you have both the DR schema and error layers in the same database? Is this possible with a Branch Versioned gdb? In enterprise? In file/mobile geodatabase, the Reviewer Workspace and attribute rule (AR) error layers should co-exist peacefully. Note: Implementing attribute rules will impact backward compatibility with ArcMap and older versions of ArcGIS Pro. More info can be found here. Reviewer Workspace is not supported in branch versioned enterprise geodatabase and AR error layers are not supported in traditional versioned enterprise geodatabase. In Pro, Data Reviewer requires the setting up a workspace on the database == a schema with tables for track errors e.g. Enable Data Reviewer. I assume the resulting schema tables are just like the tables set-up with Data Reviewer with ArcMap. A Reviewer Workspace created in ArcGIS Pro is compatible with ArcMap 10.8x. To use the Data Quality "Missing Features" and Browse Features tools you need the Data Reviewer license. My understanding is that any errors generated by these 2 tools are written only to the DR schema tables. Correct What are called "Data Reviewer Checks" are equivalent to the "ready to use rules" that show up in the "Attribute Rules tab"? Data Reviewer's checks (documented here) can be configured to implement constraint and validation attribute rules. They are access from the "Ready to Use Rules" gallery in Attribute rules view as outlined here. Can Data Reviewer run standard attribute rules (written in Arcade) rather than the Reviewer checks? If so where are the errors written; DR schema, or the error layers? In validation attribute rules, there are two implementation patterns (Arcade and Data Reviewer). Regardless of the implementation, rules are evaluated together with resultant error features created in the AR error layers. Note: To evaluate Data Reviewer-based validation attribute rules a Data Reviewer for ArcGIS Pro (file/mobile geodatabase) or a Data Reviewer for ArcGIS Enterprise license (branch versioned enterprise geodatabase) is required. From the Error Inspector running the evaluate data quality command the output for either a ready to use rule or a standard arcade validation rule are written to the error layers. They have different life cycle behavior. This is as-designed. Is there a way to import/export they error layers into the DR schema or visa versa? Importing AR error features to a Reviewer Workspace should be possible using the Write to Reviewer Table GP tool. Custom code will be required to translate an AR error feature's FeatureClassID value to the corresponding Feature/object class name. Importing Reviewer Workspace error features to AR error layers is not supported since these tables are system-managed to maintain consistency between rules and their error features.

‎06-23-2023

In the above web course, the Feature on Feature check is used to identify overlaps between features in the same feature class (AP_LandUse). In this configuration, it is expected that an error feature will be created for each feature that contains an overlap with features from the Feature to Compare data source. Removing the overlap should automatically resolve both error features on the next evaluation of the validation rule.

‎06-01-2023

Correct. The ability to track errors after they have been corrected is only available when using Data Reviewer-based validation attribute rules. Error features created when using Arcade-based validation attribute rules are automatically removed once the error condition is resolved. That said, I have had Data Reviewer customers indicate that they would like to have all errors (regardless of whether they were created based on an Arcade script or a Data Reviewer check) follow the same life cycle process. If this is something you'd be interested in seeing in a future release, I would ask that you take a moment and create an idea for this in the Data Reviewer Ideas board.

‎05-26-2023

@Anonymous UserSee my feedback on this behavior here.

‎05-26-2023

This is the expected behavior when error features are created using Arcade-based validation attribute rules. The lifecycle management of error features is limited to those created using Data Reviewer-based validation attribute rules. Unlike the ArcMap workflow, when an error condition has been resolved the error feature's Phase and Status values are automatically updated when the feature is re-evaluated.

‎05-26-2023

In general, that error usually means a field in the data is being edited with an invalid value. For example, if you try to insert a 36-character string into a field with a max of 35 characters you'll get that error. For Reviewer-based validation attribute rules, you may want to verify that the Name and Description properties of your rules do not exceed 64/256 characters in length, respectively.

‎05-26-2023

The need to re-publish the service depends on the nature of the change being made to the participating feature class validation attribute rules. For Data Reviewer-based rules, changes that include the use of a new data source (such as the data source of the Features to Compare parameter in the Feature on Feature check) will require re-publishing if that data source is not already included in the service. The same condition would apply when creating a new rule that includes a data source that is not already included in the service (such as including the destination data source when using the Relationship check) .

‎05-11-2023

A couple of things to check when you encounter this error: Verify that all data sources configured in the validation attribute rules are included in the published service. For example, several check types include additional data sources (such as the Features to Compare data source found in the Feature on Feature check) that must also be included in the published service. Review the server logs (in verbose mode) of your federated server(s) to identify any errors related to Reviewer check executions. Note: The installation of the Data Reviewer SOE is not required when using ArcGIS Pro-based workflows such as Attribute rules.

‎04-28-2023

I notice that, unlike the tutorial, there was no option to select a study area, and error layers don't line up on the map with the other layers like it did in the tutorial which had a different datum to that of the error layers as well. You may want to check the Transformation settings configured in your map to see if this is the reason the error features are not aligned with the related feature. Here is some additional info on these settings. After running the Evaluate rules they show up in the Error Inspector without the green pass marks or red error marks. What could be the issue? Were the error features created using a Data Reviewer-based validation rule? If so, the error should include life cycle status information (stored in the Error phase and Error status fields). Errors created using Arcade-based validation rules will not have values in these fields.

‎04-24-2023

@SarahMcLellan Attribute rule error layers are based on the WGS84 spatial reference. Could you provide some background on how the error features were created? For example, were the error features created by evaluating rules using the Error Inspector or the Evaluate Rules GP tool (in Pro or from a stand-alone script)?

‎03-22-2023

Unfortunately, the workflow in ArcMap for ensuring that edits correct the error condition is not an automated process as they are Data Reviewer-based validation attribute rules in ArcGIS Pro. In ArcMap, error results must be manually updated to indicate whether they have been fixed or should be marked as an exception. Here is a link to the documentation that outlines the process. A couple of workflows that I've seen customers use: Create a new Reviewer session and re-run the Reviewer batch job or individual check on the edited features and see what errors are returned. Using the existing Reviewer session, re-run the Reviewer batch job or individual check on the selected feature and see if errors are still returned. If no error is returned, then update the correction status as "Resolved". Hope this is helpful!

Online Status	Online
Date Last Visited	6 hours ago

My Ideas

Latest Contributions by JayCary

Re: ArcGIS Pro Data Reviewer Performance

Re: Notepad function in ArcGIS Pro?

Re: Finding dangles

Re: Commit to Reviewer Table Tool in ArcGIS Pro?

Re: What is the relationship between the Error Inspector and Data Reviewer?

Re: Feature on Feature check returns duplicate errors

Re: Branch Version Error Inspector - Status Field?

Re: Error Inspector

Re: Branch Version Error Inspector - Status Field?

Re: Error inspector

Re: Attribute Rule Changes, do they require republish of feature service?

Re: Evaluate Rules: Edit Operation Failed: ERROR: Operation failed to execute due to data not available.

Re: Data Reviewer Error Layer Spatial Reference discrepancy

Re: Data Reviewer Error Layer Spatial Reference discrepancy

Re: ArcMap + data reviewer

Re: Attribute Rule Import Fails (FGDB, Pro 3.5.2)

Re: How to track transportation assets as events i...

Re: Constraint or validation rule to check that te...

Re: Export Query Attributtes rules

Re: Error of reviewer results

Roads and Highways User Group (RHUG)