Making an URGENT modification to the compilation scale of a feature

When you run the Update Instance command to capture the changes that have occurred on the NIS that relate to a given product, the geodatabase replication component of ArcGIS determines which of those changes are pertinent by looking at each feature at two points in time: (1) at the start of the time period (the last time Update Instance was run) and (2) at the end of the time period (the present time, when you selected Update Instance again). If the feature meets the filter criteria for the replica at either of those points in time, it is included in the change message. With this approach, the replication system can ensure that a product is notified about features moving into or out of the product definition as well as features that change within the product definition. Product definition is defined by any of the criteria that determine whether or not a feature is part of a product. These feature criteria can include the AOI boundary and nonspatial attribute criteria like the compilation scale value. For example, any feature that has a compilation scale between value x and value y and is geographically located within a defined AOI boundary will be determined as meeting the defined criteria for a given product. If you need to include a feature in a product that has a different compilation scale criteria, then you need to change the feature's compilation scale value in the NIS before running the Update Instance process and applying this change to the production databases replica versions.

This workflow guides you through the process of changing the compilation scale of a feature in the NIS and getting that change into the URGENT version of a product, which involves the following steps:

1. Propagate compilation scale changes to URGENT.
   • Create a copy of the feature in the NIS.
   • Modify the PLTS_COMP_SCALE and URGENT values on the cloned feature in the NIS.
   • Mark the original feature for deletion with the Track Delete tool, indicating that it is an URGENT delete
2. Verify the change.
3. Posting the change to Default.
4. Run the Update Instance command.
5. Apply changes the next time you try to edit the URGENT version.

Modifying the PLTS_COMP_SCALE value on the feature in the NIS

Propagating compilation scale changes to continual maintenance (CM)

If the scale change took the feature out of that product definition, the feature will be deleted from the continual maintenance (CM) version. If the scale change resulted in the feature meeting the product definition for the first time, it will be inserted into the CM version.

Propagating compilation scale changes to URGENT

Changing the compilation scale of a feature in the NIS and propagating that change into the URGENT version of a product takes a little more work. You cannot modify both the PLTS_COMP_SCALE value on the feature on the NIS and its URGENT value to one of the URGENT settings (Internal or External). This will not work because of the way replication decides which changes are relevant to a product. When the replication process looks at that feature to determine whether the URGENT replica should be notified, it will conclude that, at the start, it was not marked URGENT and, at the end, it did not meet the scale criteria. Instead, you must create an URGENT clone of the feature and delete the original.

Steps:

1. Start ArcMap.
2. In the Nautical Properties pane of the Production Properties dialog box, set the PLTS Compilation Scale Value to the appropriate scale.
3. Click the Production Start Editing button on the Production Editing toolbar.
   Note:

   The Manage Features and Create Attributes, Update Attributes, or Metadata Attributes windows automatically appear when you start an edit session using the Production Start Editing tool.

   Tip:

   If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Show/Hide Attributes button on the Manage Features window.

4. Select the feature you want to modify.
5. On the main menu, click Edit > Copy.
6. In the Manage Features window, on the Create tab, choose the same feature class and subtype as the original feature.
7. On the main menu, click Edit > Paste.
8. Select only the original feature.
9. Click the Track Deletes tool and fill out the dialog box.

   Most importantly, make sure the feature is marked as Urgent.

10. Select the new feature.
11. In the Update Attributes window, set the URGENT field to one of the URGENT values and click Apply.
12. Click the Save Edits button .

Verifying the change in the NIS

Every feature within the NIS database holds an NIS_VERIFIED field. Whenever a feature is modified in the NIS, both spatially or at the attribute level, the NIS_VERIFIED field will automatically be set to False. These unverified features need to be reviewed through your quality control process, and the field must be set to True before you can post your data changes to the Default version. To set the NIS_VERIFIED field to True, follow the steps below.

Steps:

1. Click the Production Start Editing button on the Production Editing toolbar.
   Note:

   The Manage Features and Create Attributes, Update Attributes, or Metadata Attributes windows automatically appear when you start an edit session using the Production Start Editing tool.

   Tip:

   If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Show/Hide Attributes button on the Manage Features window.

2. Select the unverified feature.
3. Click the Update tab on theManage Features window and highlight the feature.
4. Click the Update Attributes window.
5. Change the NIS_VERIFIED field to True.
6. Click Apply.
7. Click the Save Edits button .
8. Click the Stop Editing button on the Production Editing toolbar.

   The geodatabase becomes uneditable. If you have made edits, you will be prompted to save the changes if you want.

If you have multiple features that need to have their NIS_VERIFIED field set to True, it is highly recommended that you use the Production Advanced Query Command tool. The Production Advanced Query Command tool can select all the unverified features and allow you to browse through them one by one, or you can perform a batch update and set all the verification fields to True at once.

Note:

When querying for unverified features using the Production Advanced Query Command tool, make sure you use a query expression that finds both false and null values for the applicable verification field, for example, NIS_VERIFIED = 0 OR NIS_VERIFIED Is Null. This expression will ensure that you find both NIS_VERIFIED = 0 (False) and NIS_VERIFIED fields that are null.

Posting the change to Default

The Nautical Post tool acts as the standard ArcGIS Post command for all versioned nautical databases. Nautical Post is used in both the desktop and enterprise production environments after the Reconcile or Update Primitives tools are run.

Reconciling updates the edit version with changes from the target version and checks for conflicts; it doesn't merge changes into the target version. Once you've finished reconciling and have resolved conflicts (if necessary), you complete the merge process by posting your changes to the target version.

The Nautical Post tool merges all the changes made to the nautical databases into the target version once the reconciling and the conflict reviews are completed.

Steps:

1. Click the Production Start Editing button on the Production Editing toolbar.
   Note:

   The Manage Features and Create Attributes, Update Attributes, or Metadata Attributes windows automatically appear when you start an edit session using the Production Start Editing tool.

   Tip:

   If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Show/Hide Attributes button on the Manage Features window.

2. Click the Reconcile button on the Nautical toolbar.
3. Click the Nautical Post button on the Nautical toolbar.
   Note:

   If the Nautical Post button is disabled, you must first reconcile any changes or run Update Primitives.

   Note:

   If you have unverified features in your edit version, a message appears notifying you that there are unverified features found in your version. You must verify all features before clicking the Nautical Post button again.

Updating the instance

After these changes are verified and posted to Default, you can run the Update Instance process on all the relevant products. You can run Update Instance by right-clicking on an instance. The new feature will be added to your product's URGENT version, and the deleted feature will be removed from the products that no longer meet the scale definition.

Edits made on the central database repository (CDR or NIS) are packaged in an update file through the update instance process. Once you have created the update file, you can apply those changes to your product using the Apply Changes tool. Using this workflow, it is possible to create various ENs and ERs based on user requirements.

Steps:

1. Add the NIS feature dataset.
2. Create an edit version.
3. Switch to the edit version you just created.
4. Click the Production Start Editing button on the Production Editing toolbar.
   Note:

   The Manage Features and Create Attributes, Update Attributes, or Metadata Attributes windows automatically appear when you start an edit session using the Production Start Editing tool.

   Tip:

   If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Show/Hide Attributes button on the Manage Features window.

5. Make necessary edits to your NIS edit version in the cell/chart panel you are focused on.

   You can use the AOIs in your instance to locate your cell/chart among all the cells/charts in the NIS.

6. Be sure you or your quality control administrator verifies the changes.

   Perform the substeps if you are the one who needs to verify the changes.

   1. Click the Update tab in the Manage Features window.
   2. Accept the necessary changes by changing the NIS_VERIFIED field to True.
7. Click the Reconcile button on the Nautical toolbar.
8. Click the Nautical Post button on the Nautical toolbar.
   Note:

   If the Nautical Post button is disabled, you must first reconcile any changes or run Update Primitives.

   Note:

   If you have unverified features in your edit version, a message appears notifying you that there are unverified features found in your version. You must verify all features before clicking the Nautical Post button again.

9. Right-click the instance in the product library tree and click Update Instance.

   The update XML files that will be applied to your product database are generated. These are stored in the product library and are automatically referenced when you start editing in your continual maintenance version.

10. Click the Save Edits button .
11. Click the Stop Editing button on the Production Editing toolbar.

    The geodatabase becomes uneditable. If you have made edits, you will be prompted to save the changes if you want.

Applying changes

The Nautical Information System (NIS) environment allows multiple production databases to be updated with edits that were applied to the Central Database Repository (CDR). Each time the instance is updated in the product library, an XML data change message is generated for each of the product's replicas. For example, in a common production workflow, data change messages are generated for typical edit operations performed within the NIS. These data change messages are stored within the product library and applied to the production database through the Apply Changes tool.

Applying all change files at once

Within the NIS to product environment, data changes from the NIS are propagated to the production databases through a two-step process using the Update Instance command and Apply Changes tool.

The Apply Changes tool runs the Product Refresher processes automatically once the apply changes process is complete.

Steps:

1. On the main menu, click Customize > Toolbars > Nautical.
2. Click the Apply Changes button on the Nautical toolbar.

   The Product Updates dialog box appears.

3. Click Apply All.
   Note:

   If you try to start an edit session when there are changes pending for that version, you will receive a warning message that you must first apply the pending changes.

   All existing data change messages will be applied to the replica version from oldest to most recent date.

   When Apply Changes is finished, a message appears saying the updates were applied.

4. Click OK.

Applying change files individually

The Apply Changes tool runs the Product Refresher processes automatically once the apply changes process is complete.

Steps:

1. On the main menu, click Customize > Toolbars > Nautical.
2. Click the Apply Changes button on the Nautical toolbar.

   The Product Updates dialog box appears.

   
3. Click Apply Oldest.

   A message box appears saying the updates were applied. The oldest data change message is applied to the replica version based on the creation date.

4. Repeat steps 2–3 if you want to apply more updates.
5. Click OK.