POST
|
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) .
... View more
05-26-2023
09:23 AM
|
0
|
0
|
730
|
POST
|
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.
... View more
05-11-2023
02:51 PM
|
0
|
1
|
1247
|
POST
|
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.
... View more
04-28-2023
10:45 AM
|
0
|
0
|
676
|
POST
|
@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)?
... View more
04-24-2023
11:36 AM
|
0
|
1
|
695
|
DOC
|
@JohnAnderson1The current plan is to create new versions of the Flag Missing Features and Browse Features commands to support visual review of features and storage of errors in the Attribute rule error layers. The existing commands will be removed from the default Manage Quality ribbon, but will continue to be available for use in a customized ribbon to support users that leverage the legacy Data Reviewer error schema.
... View more
04-18-2023
05:00 PM
|
0
|
0
|
1882
|
DOC
|
@AndrewQuee Great questions! The features/enhancements identified for mid/long-term releases are (by design) fairly vague in order to elicit feedback/discussion from users. If there are ideas for features/enhancements that you would like to see in Data Reviewer, then I would suggest submitting them to the Data Reviewer Ideas board. That said, some of the requests that we have received from users include those exposed through the Error Inspector in ArcGIS Pro and operations available from ArcGIS Enterprise. In ArcGIS Pro, these enhancement ideas include support for exporting error features to Excel, extending attribute filtering to include additional error properties (such as error title, error source), and life-cycle management for errors created through visual review workflows. In ArcGIS Enterprise, new REST operations will be created and existing operations (updateErrors) updated to support lifecycle management of errors created during visual review workflows. These capabilities will replace those previously available in the ArcMap runtime-based server object extension (now deprecated) for identifying missing features and identifying errors on existing features.
... View more
04-18-2023
04:44 PM
|
0
|
0
|
1884
|
POST
|
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!
... View more
03-22-2023
05:38 PM
|
0
|
0
|
549
|
DOC
|
ArcGIS Data Reviewer provides capabilities that enable you to automate and simplify data quality workflows that lower data management costs and create high quality data. The purpose of the ArcGIS Data Reviewer Roadmap is to provide you with an estimate of when new capabilities will be released in the near, mid and long-term. Near-term goals include those capabilities planned over the next couple of releases. Mid-term goals include those capabilities planned for subsequent releases and long-term capabilities are in the product plan, but we do not have a specific release in mind yet. What would you like to see next in ArcGIS Data Reviewer? Share your ideas in the ArcGIS Data Reviewer Ideas board. Near-term goals for ArcGIS Data Reviewer Integrating Data Reviewer capabilities into Attribute rule workflows Near-term goals for automated review workflows Near-term goals for semiautomated review workflows Near-term goals for error management workflows Near-term goals for adhoc data validation Mid-term goals for ArcGIS Data Reviewer Long-term goals for ArcGIS Data Reviewer As with any roadmap, capabilities are tentative and may evolve, be delayed, or removed from the roadmap as priorities change. The continued development or release is at the sole discretion of Esri. For more information on the latest release of ArcGIS Data Reviewer see the What's New in ArcGIS Data Reviewer blog.
... View more
03-15-2023
01:27 PM
|
4
|
6
|
2226
|
IDEA
|
03-09-2023
09:09 AM
|
0
|
0
|
777
|
POST
|
The Error Inspector is "generic" pane used to manage error features created when validating data using ArcGIS capabilities such as Topology Rules and Attribute Rules. These errors are stored in a schema that are specific to the capability. The Reviewer Results pane is used to manage error features created when validating data using ArcMap-based automated checks (Reviewer Batch Jobs), visual review tools and automated workflows using the Write to Reviewer Table geoprocessing tool. These errors are stored in a schema that is specific to Data Reviewer. This capability should be considered a legacy workflow to support deployments that contain both ArcMap and ArcGIS Pro clients. Data Reviewer customers are encouraged to migrate their QC workflows to Attribute Rules (and the Error Inspector) when they are ready to move from ArcMap.
... View more
02-24-2023
03:04 PM
|
1
|
3
|
1172
|
POST
|
@LauraPhoebusThis is a great question! Regarding licensing, the Methods to implement automated review topic is getting an update in the next release to address licensing requirements for Reviewer-based validation attribute rules. Here is a preview of this update: Consider the following licensing requirements when implementing Reviewer-based attribute rule workflows: A Data Reviewer license for ArcGIS Pro and an ArcGIS Pro Standard or Advanced license are both required to create or modify a Reviewer-based attribute rule. A Data Reviewer license for ArcGIS Pro and an ArcGIS Pro Standard or Advanced license are both required to evaluate a Reviewer-based validation attribute rule in a file or mobile geodatabase. A Data Reviewer license for Enterprise and an ArcGIS Server Standard or Advanced license are both required to evaluate a Reviewer-based validation attribute rule in a branch versioned enterprise geodatabase. Hope this update provides clarity around the licensing requirements.
... View more
01-25-2023
11:48 AM
|
0
|
0
|
718
|
POST
|
@ammsgis: Thanks for sharing your results and environment. This feature is flagged as an error since a node is within the dangle tolerance and not connected to another feature in the feature class. To all: Would appreciate thoughts on whether polylines that close on themselves should be handled in a different way by the Find Dangles check. Note: The Polyline or Path Closes on Self can be used to find self-closing polylines.
... View more
01-25-2023
10:58 AM
|
1
|
0
|
1472
|
POST
|
Can you share the details of your configuration? For example, the check settings (input filters, dangle tolerance, dangle tolerance unit of measure, additional features to compare) and spatial reference of the input dataset. You may want to also verify that the polylines are actually snapped to another feature and do not have micro-gaps.
... View more
01-18-2023
11:16 AM
|
0
|
0
|
1537
|
Title | Kudos | Posted |
---|---|---|
1 | 02-23-2024 02:34 PM | |
1 | 10-31-2023 08:59 AM | |
1 | 02-24-2023 03:04 PM | |
1 | 01-25-2023 10:58 AM | |
1 | 11-01-2022 11:58 AM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|