Working with multi scale data (Maritime Charting)

In an enterprise environment, data is stored in a NIS database for editing and maintenance, which is replicated to other databases for publishing. When implementing the NIS, there are many decisions that an organization needs to make. First, the organization needs to choose a relational database management system, such as Oracle or SQL Server. Once it is configured, the database is then ready to load the NIS schema in one of the following environments:

• SQL Server
• Oracle

One of the powerful benefits the enterprise environment offers is that multiple-scale data can be stored in one central location for easy editing access. Each feature class in the NIS schema contains the field PLTS_COMP_SCALE, which identifies the compilation scale of the feature data.

Loading data

When loading data using the S-57 To Geodatabase tool, the PLTS_COMP_SCALE value is populated according to the CSCL or M_CSCL value in the S-57 cell. The S-57 importer takes care of populating this value for you; however, if you choose to load data via an alternative method, this attribute field will need to be populated in an edit session after loading.

Steps:

1. Start ArcCatalog.
2. In the Catalog Tree window, right-click the feature dataset into which you want to import and click Import > S-57 to Geodatabase.

   The S-57 to Geodatabase dialog box appears.

   S-57 to Geodatabase dialog box for importing into an NIS database

   Note:

   If you are importing into a non-NIS production database, the override options will not be available.

3. Click the browse button (...) next to the Input S-57 Cell text box.
4. Navigate to and choose the S-57 cell you want to import.
5. Click Open.
   Note:

   If you are importing S-57 data into a non-NIS production database or do not want to use the override options for your NIS database, skip to step 8; otherwise, continue to the next step to override CSCL and M_CSCL values.

6. Check the Override CSCL and M_CSCL values check box to enable the grid view for editing.

   If you are importing into NIS, the Override CSCL and M_CSCL values grid is populated with rows that show the imported cell's DSPM:CSCL and M_CSCL:CSCALE values.

7. Click the cell in the Override column and type the new value for the DSPM:CSCL and/or M_CSCL:CSCALE value.

   The updated values are populated into the COMP_SCALE property during import.

8. Click OK.

   A status dialog box appears.

   When the process is complete, the S-57 to Geodatabase dialog box appears and asks you if you want to view the log file.

9. Click Yes to open and review the log file.

   The log file shows the following information:

   • Metadata information that was imported, such as dataset ID (DSID), dataset structure information (DSSI), and dataset parameter (DSPM)
   • The new value, if you have imported into an NIS database and replaced the imported cell's CSCL value with one of your own
   • The number of features and primitives that were imported
   • The amount of time it took to import
   • Any errors that occurred (listed at the top of the log file)
   • The import version name that was created and populated, if you imported into an ArcSDE geodatabase
   • The amount of time it took to read the file for the override option (NIS only)
10. Close the log file once you are finished reviewing it.
11. You will need to reconcile and post your data in the import version to the Default version.

Populating the compilation scale when editing

When working in the Maritime Charting's multiple-scaled enterprise production environment, you are required to establish the scale at which you are compiling data so that newly created features can be managed correctly. In the enterprise environment, a production database is composed of features that meet a specific scale range. To ensure features filter correctly to the production database, the value stored in the compilation scale property must populate the PLTS_COMP_SCALE attribute on each feature created during an edit session. This attribute can also be leveraged to control the display of data while editing in the NIS.

You can set the compilation scale property with the Compilation Scale tool. This tool provides an easy means to both review and dynamically alter the compilation scale value of newly created data without the need to stop the edit session.

Steps:

1. Start ArcMap.
2. On the main menu, click Customize > Toolbars > Nautical.
3. Type a value directly in the Compilation Scale text box and press ENTER.

   You cannot use 0 (zero), negative values, or nonnumeric characters.

   Tip:

   You can also press TAB or move the pointer to remove the focus from the text box.

Controlling the display of data to improve the editing experience

Using the Feature Display Settings tool or manually selecting individual feature layers, definition queries can be set on any given feature layer. Sometimes it is beneficial to see all features when editing. However, it often complicates the display if multiple scale bands of data exist in the area of interest. When you only want to see the features at a single scale, definition queries with the PLTS_COMP_SCALE = <your compilation value> will show only those features with the specified value.

Steps:

1. Start ArcMap.
2. Add the Feature Display Settings tool in ArcMap by doing the following:
   1. On the main menu, click Customize > Toolbars > Customize.

      The Customize dialog box appears.

   2. Click the Commands tab. In the Categories list, choose Production Cartography.
   3. In the Commands list, choose Feature Display Settings.
   4. Drag the Feature Display Settings tool onto any toolbar.
3. Click the Feature Display Settings button .

   The Feature Display Settings dialog box appears.
4. If necessary, click the Definition Queries tab.
5. In the Feature Layers list, click the name of the feature layer for which you want to define the definition query.

   For example, AidsToNavigationP.

   Note:

   Checking the check box next to the feature layer will not select it.

6. Click SQL.

   The Define Query Expression dialog box appears.

7. Double-click the field you want to use in the query.

   The field name appears in the Where text box.

   For example, PLTS_COMP_SCALE.

8. Click an operator.

   The operator appears in the Where text box.

   For example, =.

9. Click Get Unique Values.

   The unique values for the field appear.

10. Double-click the value you want to use in the query.

    The unique value appears after the operator in the Where text box.

    For example, 40000.

11. Click Verify.

    The Verifying expression message appears and indicates whether or not the expression is valid.

12. Click OK to close the verification message.
13. Click OK on the Define Query Expression dialog box.

    The Definition Queries tab appears.

14. Copy and paste the definition query to the Multiple definition queries (checked items) text box.
15. In the Feature Layers list, check the check boxes next to the feature layers for which you want to update the definition query.
16. Click Replace.

    A message appears that indicates which feature layers have had their definition queries replaced.

17. Click OK.
18. Click the Close button to close the Feature Display Settings dialog box.