Processes for refreshing features on products

The Product Refresher tool can operate within an enterprise (NIS) or a desktop production environment. The Product Refresher tool refreshes the features extracted from and/or synced to a product in the NIS environment or imported to a product in a desktop environment.

Refreshing the product allows nautical processes to run effectively and certifies the creation of valid S-57 export files.

The Product Refresher tool runs the following processes:

1. Clip extraneous features (only applicable to an enterprise production environment)
2. Filter replica features (only applicable to an enterprise production environment)
3. Clean relationships
4. Group soundings
5. Populate DSNM and NAME

The product refresher process is not limited to a button in ArcMap. If in an enterprise production environment, processes such as populate instance and apply changes run the product refresher process behind the scenes. The following tables show which processes apply to the specific product.

Populate Instance

	Clip Extraneous Features	Filter Replica Features	Clean Relationships	Group Soundings	Populate DSNM and NAME
Chart			x	x	x
ENC (S-57)	x		x	x	x

Processes run with the populate instance process

Apply Changes

	Clip Extraneous Features	Filter Replica Features	Clean Relationships	Group Soundings	Populate DSNM and NAME
Chart		x	x	x	x
ENC (S-57)	x	x	x	x	x

Processes run with the apply changes process

Product Refresher

	Clip Extraneous Features	Filter Replica Features	Clean Relationships	Group Soundings	Populate DSNM and NAME
Chart			x	x	x
ENC (S-57)	x		x	x	x
AML				x (CLB only)	x

Processes run with the product refresher process

Clip extraneous features (only applicable to an enterprise production environment)

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 that are unique to the 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, children 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 children features.

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

Filter replica features (only applicable to an enterprise production environment)

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 product class 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 imitates what occurs when a sounding is inserted or modified in a production database. The process applies the existing Nautical Solution 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.