Editing multiscale data

One of the benefits the Nautical Information System (NIS) database offers is that multiple-scale data can be stored in one central location. Each feature class in the NIS schema contains the field PLTS_COMP_SCALE, which identifies the compilation scale of the feature data. The Checkout Nautical Replica tool allows you to edit a subset of data from the enterprise NIS in a file geodatabase child replica. You can then synchronize these edits with the NIS using the Synchronize Changes wizard.

With the Checkout Nautical Replica tool, you can do the following:

• Select and edit a specific geographic extent, AOI, or product.
• Edit using a local file geodatabase, eliminating the potential for network latency.
• Select a scale band.
• Create a custom query.
• Reduce the need for a network connection to the NIS.

Creating a template geodatabase

Before using the Checkout Nautical Replica tool, you'll need to create a template file geodatabase with a schema, modify the product table value, create a production database, and associate it with a data model version. Then the empty template can be copied, pasted, and reused for future use of the tool. These steps only need to be executed once. If an administrator changes the schema, a new template is created.

Tip:

It is recommended to use an ENC schema with topology when editing data in one scale band.

1. Start ArcMap.
2. If necessary, connect to a folder in the Catalog window.

   Learn more about using folder connections

3. Expand the file connections in the Catalog tree.
4. Right-click the folder where you want to create the file geodatabase and click New > File Geodatabase.

   A file geodatabase is created in the location you selected.

5. Rename the file geodatabase by right-clicking it, choosing Rename, and typing a new name.

   Tip:

   Use a name that remind you that it's a template that you do not want to populate with data, such as ReplicaTemplate.gdb.

6. In the Catalog tree, right-click the geodatabase into which you want to import the data and click Import > XML Workspace Document.
7. Click the Data option to import the data with the schema and close the import wizard.

   Learn more about importing feature datasets, classes, and tables from an XML workspace document

8. Browse to and select the product schema.

   Note:

   It is recommended to use an ENC schema, which contains topology, when editing data in one scale band. If you have a custom ENC schema containing additional fields or Unit Conversion or Rounding Rules (UC/RR), import your custom workspace XML.

   To use the schema provided when you installed ArcGIS Maritime, browse to the following location:

   • For 32-bit Windows operating systems—<Installation location>\Program Files\ArcGIS\MaritimeCharting\Desktop<version>\Enc\Schemas\Workspace
   • For 64-bit Windows operating systems—<Installation location>\Program Files (x86)\ArcGIS\MaritimeCharting\Desktop<version>\Enc\Schemas\Workspace

9. If you have a custom schema or did not use the ENC schema provided in the installation, complete the following substeps:

   If you're using the ENC schema provided in the installation, proceed to step 10.

   1. In the Catalog window, expand the file geodatabase you just created to view its contents.
   2. Click the PLTS_PRODUCT table and drag it to the Table Of Contents window.
   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. In the Manage Features window, click theCreate tab and select the PLTS_PRODUCT table.
   5. In the Create Attributes window, find the PRSP Field Name.
   6. Change the Field Value to 1002 – NIS.
   7. Click Apply.
   8. Click the Save Edits button on the Production Editing toolbar.
   9. Click the Stop Editing button on the Production Editing toolbar.
10. If necessary, open the Product Library window by clicking Customize > Production > Product Library on the main menu.

    A tree view of the product library appears.

    

11. Expand Production Data.
12. Right-click the database and click Create Production Database.

    The Select Extensions dialog box appears if you have at least one of the ArcGIS Mapping and Charting solutions installed.

13. Choose Maritime and click OK.
14. Accept the default setting in the Create Production Database Workspace dialog box and click OK.

    The Creating Production Workspace dialog box appears with the progress.

15. Click OK when the process completes.
16. Right-click the production database and click Choose Data Model Versions.

    The Choose Data Model Versions dialog box appears.

    

17. Check the check boxes next to the data model versions you want to associate with this production database.

Note:

It is recommended that you associate the template replica schema with the NIS data model version.

18. Click OK.

    The data models appear under the production database.

19. Optionally export, save, and distribute the template file geodatabase to editors.

Checking out a replica from the NIS

After creating the template geodatabase with ENC schema, you are now ready to use the Checkout Nautical Replica tool. It allows you to edit the data in the child replica and synchronize these edits with the parent replica.

1. Start ArcMap.
2. Make a local copy of the template geodatabase.
3. Click the Select Features button on the Tools toolbar.
4. Select the polygons you want to use.

   Note:

   You can use an AOI by checking the component in the Product Library window.

5. Click the Checkout Nautical Replica button on the Nautical toolbar.

   The Checkout Nautical Replica dialog box appears.

6. Click the ellipsis button (…) next to SDE Workspace.
7. Browse to and choose the NIS enterprise workspace you want to replicate.
8. Click Add.
9. Click the Select Version drop-down arrow to define the version.

   If a list of versions is not available, close the tool and create a new version. For more information, see Creating versions and setting permissions.

10. In the Extraction box, choose the method you want to use.
    • Scale Band—Uses a scale range, specified in the ScaleBands.xml, to determine which features will be included in the replica. Click the Scale Band drop-down arrow to define the scale.
    • Custom—An SQL statement that allows you to determine which features are included in the replica. You can modify the provided statement of 0 to 1,000,000 scale or click SQL to build your own query.

      Tip:

      Use only the fields listed in the SQL Builder dialog box. For more information, see Building a query expression.

11. Click the ellipsis button (…) next to Replicate To.
12. Browse to and choose the template geodatabase.

    The target file geodatabase should not contain features.

13. Click Add.

    Tip:

    If you would like to change the child replica name when it is replicated, you can do so under the Replica Name text box. Replica names must be unique and not contain special characters.

14. Click OK.

    The Creating Checkout Replica progress dialog box appears.

15. Click OK when the process completes.

Synchronizing edits to the NIS

A synchronization involves the replica sending data changes and the relative replica receiving changes. Data changes include insertions, modifications, and deletions made in the replica version. To perform a synchronization, you must be connected as the same database user that created the replica or the geodatabase administrator.

Once the data has been synchronized, you must create a new checkout replica to perform additional edits.

1. Click the Synchronize Changes button on the Nautical toolbar.

   If the tool is not active, add a feature class from the replica you want to synchronize to the Table Of Contents in ArcMap.

2. Complete the steps in Synchronizing connected replicas.