|
POST
|
From the Duplicate Feature check doc: The purpose of the Duplicate Feature check is to find features that contain duplicated geometry and attribute values. By default, this check compares a feature's geometry and attribute values (in matching/user-editable fields) to determine whether a feature is duplicate. System-maintained fields (i.e. ObjectID, GlobalID, etc) are ignored. In this example, OID 342 and 343 are not duplicates since they do not have matching StreetNumber values.
... View more
09-20-2022
04:16 PM
|
1
|
0
|
1555
|
|
POST
|
The Duplicate Feature check and the Must Not Overlap topology rule are used to detect completely different error scenarios and their results cannot be compared. Could you clarify your goal in comparing these two workflows?
... View more
09-19-2022
04:43 PM
|
1
|
0
|
1570
|
|
POST
|
Hi, The Unique Field Value check appears to be working as expected (ArcGIS Pro 3.0.1) when used with the sample data (Z91.zip). Note: The data contained in Z91.zip does not appear to be the same as that depicted in the above screenshot. For example, the AlTirahStreets feature class contained only one rule (New Duplicate Feature Rule) and the features with duplicate STREETNUMBER values are different. I completed the following steps to verify that the check is correctly ignoring the VALIDATIONSTATUS field during evaluation: Modify a feature (oid 348) to create a duplicate STREETNUMBER (<NULL> to 1) value. Modified feature's VALIDATIONSTATUS changes from NO VALIDATION REQUIRED to VALIDATION REQUIRED. Click Evaluate features command (using Full Extent option). New errors identified where feature contains STREETNUMBER = 1 and VALIDATIONSTATUS equal either NO VALIDATION REQUIRED or VALIDATION REQUIRED VALIDATIONSTATUS updated to NO VALIDATION REQUIRED, HAS ERROR(S) If your results are different, I would suggest contacting technical support for additional troubleshooting. Thanks!
... View more
09-19-2022
09:45 AM
|
1
|
0
|
896
|
|
POST
|
Hi, The values used in the REVIEWERCODE field is not currently documented. Could you provide some background/examples of how you are using them in your workflow? Thanks in advance for the feedback!
... View more
09-19-2022
09:00 AM
|
0
|
1
|
979
|
|
POST
|
Thanks-much for the clarification! I would suggest turning-off your error layers to ensure that you are not accidentally deleting the error feature during your edit.
... View more
09-16-2022
04:07 PM
|
1
|
0
|
1642
|
|
POST
|
Is the error result actually still in the database or is the error result being moved out of the current view due to the sort currently applied to the pane?
... View more
09-15-2022
12:04 PM
|
1
|
0
|
1656
|
|
POST
|
The team has logged an internal bug for this issue and it will be fixed in the next release of ArcGIS Pro. If needed, please contact technical support to start an incident to document this issue. This will enable you to track the progress of this incident.
... View more
09-14-2022
05:07 PM
|
2
|
0
|
676
|
|
POST
|
Is this still an issue you are seeing with the Unique Field Value check? If so, you may want to verify whether these features require validation or not. This information can be found in the validation status field.
... View more
09-14-2022
11:07 AM
|
1
|
0
|
916
|
|
POST
|
Here is a topic that outlines how to configure the Error Inspector pane to display the Data Reviewer error phase and status properties.
... View more
09-14-2022
11:00 AM
|
1
|
0
|
476
|
|
POST
|
In ArcMap and ArcGIS Pro, sessions are managed/organized by the session name property. The session user property is optional and is not used in ArcGIS Pro. Here is a topic that outlines the workflow for adding Reviewer sessions to an ArcGIS Pro project.
... View more
09-14-2022
10:56 AM
|
1
|
0
|
556
|
|
POST
|
Here is a topic that outlines the workflow for adding Reviewer sessions to an ArcGIS Pro project.
... View more
09-14-2022
10:45 AM
|
1
|
0
|
530
|
|
POST
|
Thanks for the heads-up on this issue. The development team has reproduced this workflow in ArcGIS Pro 3.0.1 and found that the issue is related to the missing Menu command in the Reviewer Results pane. Here is a topic that outlines how to configure the Reviewer Results pane to display different error types and their related attributes.
... View more
09-14-2022
10:42 AM
|
1
|
0
|
680
|
|
POST
|
Thanks-much for clarifying what you're seeing. Based on the info provided above, the dev team has been unable to reproduce this issue using Pro 3.0.1 and there have not been any bugs addressed since the check's release that would change its behavior. I would suggest starting an incident with the technical support team to capture the details of the rule configuration and associated relationship class.
... View more
09-12-2022
03:26 PM
|
1
|
0
|
1481
|
|
POST
|
The lifecycle management workflow for Reviewer-created errors (in both Batch Job and validation attribute rule workflows) is the same as it was in ArcMap (albeit in a different user experience). This topic outlines the various "paths" that are available in the different phases.
... View more
09-12-2022
11:25 AM
|
1
|
0
|
873
|
|
POST
|
Is the phase/status values of the error feature not changing when evaluating the feature again after the edit in the destination datasource? On the second evaluation, the expected result is for the error feature's phase/status values to change from Review/Reviewed to Verification/Acceptable. By default, these columns are not turned-on in the Error Inspector pane.
... View more
09-09-2022
03:19 PM
|
0
|
1
|
1502
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-05-2025 10:53 AM | |
| 1 | 07-10-2025 05:23 PM | |
| 1 | 07-10-2025 10:43 AM | |
| 1 | 10-15-2024 04:47 PM | |
| 1 | 08-30-2024 09:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|