Validating SOE features

The metadata M_COVR feature contains a category of coverage attribute that can have two values: CATCOV = 1 for coverage and CATCOV = 2 for no coverage. If you are working in a desktop production environment, the SOE Validation Check ensures there are no skin of earth (SOE) features outside CATCOV = 1 or any overlaps and gaps between SOE features.

The enterprise production environment, the NIS, does not have the M_COVR feature, so the SOE validation check only reports the overlaps and gaps among the SOE features. Since the NIS is a multiscaled database, only one scale band must be selected for the validation check to run correctly.

Note:

A definition query can be used to select features from one scale band in the NIS, for example, PLTS_COMP_SCALE = 20000.

You can use the SOE Validation check to make sure that, for example, a land area feature doesn't overlap with a depth area feature. If you are working in a desktop production environment, you can also check that there are no SOE features outside CATCOV = 1. This ensures your SOE features are validated.

Skin of earth features are nonoverlapping, contiguous area features and must completely contain the area covered by the M_COVR with CATCOV = 1. These features represent group 1 per the S-57 specifications. The SOE feature classes are as follows:

• Depth Area (DEPARE)
• Dredged Area (DRGARE)
• Unsurveyed Area (UNSARE)
• Floating Dock (FLODOC)
• Hulk (HULKES)
• Pontoon (PONTON)
• Land Area (LNDARE)

Steps:

1. Start ArcMap.
2. On the main menu, click Customize > Toolbars > Data Reviewer.
3. Click the Select Data Check drop-down arrow on the Data Reviewer toolbar, click the plus sign (+) next to Nautical Checks, then click SOE Validation Check.

   The SOE Validation Check Properties dialog box appears.

4. Click the Workspace drop-down arrow and choose the workspace on which you want to run the check.

The SOE feature classes are populated in the dialog box from the chosen workspace. The layers must be visible in the map.

5. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
6. If necessary, click the Severity drop-down arrow and choose a value that indicates the priority of the check's results in the Reviewer Remarks area.

   The severity indicates the importance of the check result. The values range from 1 to 5, with 1 being the highest priority and 5 being the lowest.

Example of SOE Validation Check Properties dialog box populated

The MetadataA features class is only populated for a product in the desktop production environment.

7. Click OK.
8. Click the Run Data Check button on the Data Reviewer toolbar.

   The Features to Validate dialog box appears.

9. Choose an option in the Features to Validate area.
   • Current Extent—The check is run on the current map extent, which is controlled by the map scale.
   • Definition Query—The check is run on the features that are displayed based on definition queries that have been created for the feature class.
   • Full Database—The check is run on all the features in the feature class.
   Tip:

   If you are running the check in the NIS, choose Current Extent. If a definition query was set in the layer properties, it will be used for the scale band.

10. Click OK.

    The check is run on the extent specified on the Features to Validate dialog box.

    When the check finishes, a check results dialog box appears.

11. Do one of the following:
    • If you want to browse the results in the Browse Features window, choose the Browse Results option.
    • If you have started a Reviewer session and want to record the results in the Reviewer table, choose the Write to Reviewer Table option.
12. Click OK.

Depending on what you chose in the check results dialog box, the Browse Features window appears with the check results selected in the map, or a message appears that states the results have been written to the Reviewer table. In the Reviewer table the reason for error is found in the RevStatus column.