Processes for refreshing features in a production database (Maritime Charting)

The product refresher processes operate within an enterprise production environment during product creation and updates. Refreshing the product allows tools essential to the nautical workflow to run effectively and ensures that the data content is appropriate for the creation of valid exports.

The product refresher processes are the following:

  1. Clip extraneous features
  2. Filter replica features
  3. Clean relationships
  4. Group soundings
  5. Populate DSNM and NAME
  6. Verify features

The following tables show which commands/tools run the product refresher processes and which processes are run for specific products:

New Nautical Product and the Create Database commands

Clip Extraneous Features

Filter Replica Features

Clean Relationships

Group Soundings

Populate DSNM and NAME

Verify Features

Paper chart

x

x

S-57

x

x

x

x

x

Processes run by the New Nautical Product and the Create Database commands
Apply Changes tool

Clip Extraneous Features

Filter Replica Features

Clean Relationships

Group Soundings

Populate DSNM and NAME

Verify Features

Paper chart

x

x

S-57

x

x

x

x

x

Processes run by the Apply Changes tool

Clip extraneous features

The clip extraneous features process deletes any point, polygon, or polyline feature that falls completely outside the extent of your product. The process splits line and polygon features on the M_COVR (CATCOV = 1) and M_CSCL boundaries. Clip extraneous features supports the horseshoe and donut hole cases unique to an enterprise production environment. These special cases are described below:

Horseshoe

When a feature extends both inside and outside the extent of the cell more than once when clipped, child features of the once-whole feature are created within the database. Each individual child feature is linked with matching IDs in a ParentID field. The ParentID field is used to track the original GlobalID of the once-whole feature prior to the clip process. This allows updates from the NIS to be applied to all child features.

Horseshoe
Horseshoe

Donut hole

An M_CSCL polygon defines an area of the cell that was compiled at a scale different from the main cell (M_COVR, CATCOV=1), creating a donut hole within the main cell. The clip extraneous features process splits line and polygon features on the M_CSCL boundaries. It also deletes any features that are not at the appropriate scale for the area in which they are located, such as 40K features in the 20K M_CSCL area and vice versa.

Donut Hole
Donut Hole

Filter replica features

As a normal part of geodatabase replication, features that met the filter criteria of a replica during the previous synchronization (Apply Changes) cycle may have been edited and no longer meet the filter criteria. The filter replica features functionality identifies and deletes features that do not meet the filter criteria of a replica during the updating of your product. For example, if the NIS editor changes the compilation scale on a coastline feature from 40K to 50K, that feature will still be synced to the 40K product. This process finds and deletes that feature from the 40K product because it no longer belongs there. Likewise, if an NIS editor modifies the NIS_PRODUCTS attribute of a navigational aid from all products to charts only, the filter replica features process finds that feature on the ENC products and deletes it.

Clean relationships

The clean relationships process clears the PLTS_FREL table of nonexisting relationships. Any collection or master/slave relationship that does not have at least one feature relationship (FREL) record is removed.

Group soundings

The group soundings process ensures that sounding features are optimized for export to S-57 data by being placed into groups. The process applies the existing ArcGIS for Maritime:Charting property setting for group soundings and places each sounding into a group accordingly.

Populate DSNM and NAME

The populate DSNM and NAME process populates empty Data Set Name (DSNM) and NAME fields for features and collections.

4/27/2014