Managing Exceptions in VEP | Editing Exceptions Outside of VEP
Validation runs produce potential errors, referred to as anomalies in VEP. While all anomalies may be errors in the validation system, there may be cases where the anomaly may reflect the true state of a feature and is considered an exception to the rule. Once an exception is identified in DATAMARK VEP, that anomaly will no longer persist in subsequent validation runs – these are referred to as marked exceptions in VEP.
Managing Exceptions in VEP
1. Select Validate from the Navigation Menu
2. Click Manage Anomalies.
3. Configure the following fields to query anomalies:
External NGUID - If the unique identifier of the anomaly is known, use it to narrow down results.
Type - Use the dropdown to filter anomalies by Markup Layer.
Validation ID - Enter a validation ID to only view that kind of anomaly.
To/From Date Range - Sort anomalies by a validation date range.
Show Marked - Check this box to include previously marked exceptions.
4. Click Search.
5. Check the Exception checkbox to mark an anomaly as an exception.
6. Utilize the Status, Justification, and Comments fields as desired for user workflows.
7. Click Save Changes before navigating to a different page to retain any changes.
8. Use the navigation tools to search through anomalies:
- Use the arrows to move the next and previous pages. Double arrows will navigate to the first or last page.
- Enter a page number to jump to a specific page.
- Use the reset button to undo any unsaved changes.
Did you know? Searching for a Validation ID does not require an exact match. Enter a partial string and VEP will return all matching results.
Note: Anomalies from every Validation Run will be present in this table, so there may be multiple records for the same feature/validation. Use the Date Created field to sort for the most recent run.
Editing Exceptions Outside of VEP
Users can mark/unmark exceptions outside of VEP in ArcGIS or other GIS editing software. This can be done by editing the Exception field in any of the markup feature classes or tables. The Exception field is automatically populated with a value of Null, indicating that the anomaly is not an exception. Change the value to 1 to indicate that the anomaly is an exception. To unmark a previously marked exception, change the 1 to a 0. To reflect these changes in VEP. The exceptions must be uploaded into VEP as an Exception Upload to be applied to the data.
Prior to uploading, zip the Markups folder. To upload exceptions, only the Markup data can be in the folder.
1. Select Uploads from the Navigation Menu.
2. Click Upload Data.
3. Choose Exceptions Upload from the Upload Type drop-down.
4. Select the file with the markups to upload.
5. Select the File Type that applies to the zipped Markups.
6. Click Next to proceed with the upload. For more information on the upload workflow, check out our Upload Data article.
Note: Unlike Data and Detached Editing uploads, Exception uploads will not need Admin approval to be applied to the data.Caution: Exception uploads cannot take place while a Validation job or another Exception Upload is running. If a user receives a warning that another job is in progress, the user must wait for the job to complete and then retry the upload.