Importing and baselining existing AML data

If you have existing AML data that needs to be imported into the geodatabase for further modifications, you need to first baseline your data within the geodatabase. The baselining process consists of the following steps:

1. Importing your AML cell into the product geodatabase (Desktop only)
2. Verifying features
3. Reconciling and posting to DEFAULT
4. Creating an edit version from DEFAULT
5. Preparing data for export to S-57 format
6. Exporting a New Edition dataset file

The following sections cover these steps in detail.

Importing your AML cell into the product geodatabase

The first step of the baseline process is importing your AML cell into the product geodatabase, which is performed via the S-57 To Geodatabase tool.

Hinweis:

Import should only be done after Setting up the AML production environment.

Schritte:

1. Start ArcCatalog.
2. In the Catalog tree, 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

   Hinweis:

   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.
   Hinweis:

   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.
    Tipp:

    If importing into an ArcSDE database, you will need to reconcile and post your data in the import version to the Default version.

Verifying features

Every feature within the product database holds a VERIFIED field. Whenever a feature is modified, both spatially or at the attribute level, the VERIFIED field will automatically get 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 VERIFIED field to True, follow the steps below.

Schritte:

1. In ArcMap, click the Production Start Editing button on the Production Editing toolbar.
2. Select the unverified feature.
3. Click the Update tab on the Manage Features window and highlight the feature.
4. Click the Update Attributes window.
5. Change the VERIFIED field to True.
6. Click Apply.
7. Save edits.
8. Stop editing.

If you have multiple features that need to have their VERIFIED field set to True, it is highly recommended that you use the Production Advanced Query. The Production Advanced Query 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.

Hinweis:

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

Reconciling and posting to DEFAULT

After successfully importing your AML data into the applicable product database, you need to

Schritte:

1. Connect to the import version in ArcMap.
2. Click the Production Start Editing button .
3. Click the Reconcile button .
4. Click the Nautical Post tool .

   The data stored in your product database is moved into the DEFAULT parent version.

Creating an edit version from DEFAULT

After posting to the DEFAULT version, you need to stop the edit session, connect to the DEFAULT version, and create an edit version from DEFAULT. Make sure you connect to your edit version before moving to the next step.

Schritte:

1. Öffnen Sie das Dialogfeld Versions-Manager mit einer der folgenden Methoden:
   • Klicken Sie im Kataloginhaltsverzeichnis mit der rechten Maustaste auf eine Verbindung zur Geodatabase, und klicken Sie dann auf Versionen.
   • In ArcMap klicken Sie auf der Versionierungswerkzeugleiste auf die Schaltfläche Versions-Manager.

   Das Dialogfeld Versions-Manager wird geöffnet.

2. Zum Erstellen einer neuen Version klicken Sie mit der rechten Maustaste auf die Version, von der Sie die neue Version ableiten möchten, und klicken Sie auf Neu.

   Hierdurch wird das Dialogfeld "Neue Version" geöffnet.

3. Geben Sie einen Namen für die neue Version ein.
   Tipp:

   Der Versionsname ist auf eine Höchstlänge von 62 Zeichen beschränkt.

4. Geben Sie eine Beschreibung der Version ein (optional).
   Tipp:

   Sie können in der Beschreibung zusätzliche Informationen über den Zweck der Version eingeben. Die Beschreibung ist ebenfalls auf eine Höchstlänge von 62 Zeichen beschränkt.

5. Wählen Sie die gewünschte Berechtigungsstufe für die Version aus: Privat, Öffentlich oder Geschützt.
6. Klicken Sie auf OK, um die neue Version zu erstellen.

Performing quality control on S-57 data

After the data has been edited, and prior to export to S-57 format, quality control procedures must be performed. This ensures that invalid or missing features are found and corrected prior to exporting. The following steps outline using the Data Reviewer functionality to perform batch validation.

Schritte:

1. Start ArcMap.
   Tipp:

   If the ArcMap - Getting Started dialog box appears, you can open a new or existing map document. You can also check the Do not show this dialog box in the future check box and click Open.

2. If necessary, load data in the map.
3. On the main menu, click Customize > Toolbars > Data Reviewer.
4. Click the Reviewer Session Manager button on the Data Reviewer toolbar.

   The Reviewer Session Manager dialog box appears.
5. Click Browse in the Reviewer Workspace area.

   The Reviewer Workspace dialog box appears.

6. Navigate to the geodatabase in which the Reviewer dataset is going to be stored.
7. Click Add.
8. Click New to start a new Reviewer session.

   The Reviewer Workspace Properties dialog box appears.
9. Choose an option for the spatial reference.
   • Use Default Spatial Reference (WGS-84)—Sets the Reviewer dataset's spatial reference to GCS_WGS_1984. This is the default spatial reference for ArcMap.
   • Use Active Data Frame Spatial Reference—The Reviewer dataset's spatial reference matches that of the active data frame.
   • Browse To Spatial Reference—Sets the Reviewer dataset's spatial reference to one you choose.
     Hinweis:

     If you choose Browse To Spatial Reference, the New Spatial Reference wizard appears so you can choose the spatial reference you want to use with the Reviewer dataset.

10. Click OK.

    The ID and Name text boxes are automatically populated in the Session area.

11. If necessary, type a custom name for the current Reviewer session in the Name text box.

    By default, the name matches the ID.

12. If you are working with an ArcSDE geodatabase for Microsoft SQL Server Express licensed for ArcGIS Desktop, click the Reviewer Dataset Version drop-down arrow and choose the version to be used.
13. Click Start Session.

    The button name changes to End Session.

14. Click Close.
15. Click the Reviewer Batch Validate button on the Data Reviewer toolbar.

    The Batch Validate dialog box appears.

16. Click Add from Product Library.

    The Choose Batch Job(s) dialog box appears.
17. In the Production Database area, click the Version drop-down arrow and choose the edit version created in the Creating an edit version from DEFAULT section (previous section).
18. Click the Choose Product Class drop-down arrow and choose the appropriate AML product class.

    The ESRI Nautical Solution includes a batch job for each AML product to check that all mandatory attributes are populated based on the V2.1 specification.

    The Choose Batch Job(s) list populates with the associated batch job for the AML product.

19. In the Choose Batch Job(s) list, select the batch job listed.
20. Click OK.

    The Batch Validate dialog box appears.

    The checks in the batch job appear in the Batch Jobs area.

    Hinweis:

    If there are multiple workspaces referenced in the batch job, the Update to Single Workspace dialog box appears so you can choose the workspace you want to validate with the batch jobs.

    Hinweis:

    When there is only one workspace in ArcMap, the batch job's workspace is automatically updated to the current workspace.

    Hinweis:

    To remove a batch job group from the Batch Jobs area of the Batch Validate dialog box, click the batch job group and click Remove. If only one batch job group is listed in the Batch Jobs area, the default checks are also deleted.

    Hinweis:

    To quickly select and deselect checks, you can also use Select All Groups and Unselect All Groups by right-clicking in the Batch Jobs area.

21. Optionally, click Validate All to ensure all the feature classes that correspond with the checks are loaded in the map and to add any default checks.
    Tipp:

    The default checks are selected on the Reviewer Session Manager dialog box on the Default Checks tab.

22. Choose the Full Database option located in the Feature to Validate area.
23. In the Batch Jobs tree view, ensure that all items are checked on.
24. Click Run.
    Tipp:

    Once a batch job is added on the Batch Validate dialog box, you can minimize and maximize the groups in the batch job. This also minimizes and maximizes the default checks that are included.

    The default checks and the checks included with the batch job are run against the extent you have chosen. When the batch job has finished running, a message appears to notify you of the number of records that have been written to the Reviewer table.

25. If there are no errors, click OK. Otherwise, continue with the rest of the steps.
26. If any errors are found, click Yes on the Batch Validate result dialog box to write them to the Reviewer table.
27. If errors are found, open the Reviewer table to see the mandatory attribute errors.

Preparing data for export to S-57 format

Prior to exporting from the geodatabase to S-57 format, the ENC data must be quality controlled by running the S58 quality control checks against it with the Data Reviewer Batch Validate tool to ensure proper attribute encoding. Once the quality control process is complete, the data is prepared for export from the geodatabase to S-57 format by running the Update primitives tool and executing Nautical Post.

Schritte:

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

   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.

   Tipp:

   If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Link Feature Manager To Attributes Window button on the Manage Features window.

2. On the main menu, click Customize > Toolbars > Nautical S-57.
3. Click the Update Primitives button on the Nautical S-57 toolbar.

   A message appears asking if you want to clean unnecessary nodes. If the check box is checked, the Update Primitives tool removes any unnecessary VC nodes and merges the remaining vector edges together.

   Hinweis:

   It is recommended that you check the Clean unnecessary nodes check box if it's the first time you are using this tool after importing a cell.

4. Click OK to update the cell.

   The tool begins to run, and you see a progress bar. When the process is complete, you are prompted to view the log file.

5. Choose an option:
   • Yes—If you want to view the log file.
   • No—If you don't want to view the log files.
   Hinweis:

   The location of the log files generated by the tool is different depending on your operating system:

   • On Windows XP, log files are written to <Installation location>\Documents and Settings\<User Login>\Application Data\ESRI\Production10.0\Nautical\LogFiles\UpdatePrimitives.
   • On Windows Vista, Windows 7, and Windows Server 2008, log files are written to <Installation location>\Users\<UserLogin>\AppData\Roaming\ESRI\Production10.0\NAUTICAL\LogFiles\UpdatePrimitives.

   If the location doesn't exist, the tool creates the space for it. The log file is saved in XML format.

6. If you choose to view the log file, close it when you are finished reviewing it to complete the process.
7. Click the Nautical Post button on the Nautical toolbar.
   Hinweis:

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

   Hinweis:

   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.

Exporting a New Edition dataset file

The final step of the baseline process is exporting a New Edition file that contains all your geometry upgrades from the Update Primitives process. You will need to open ArcCatalog and use the Geodatabase To S-57 tool to generate the New Edition file.

If you need to perform general editing tasks on your existing AML product, see Editing AML features and continue with the rest of the steps in those procedures before exporting.

Schritte:

1. Start ArcCatalog.
2. Navigate to and right-click the feature dataset from which you want to export and click Export > Geodatabase to S-57.

   The Geodatabase to S-57 dialog box appears.

   Geodatabase to S-57 dialog box

3. On the Main tab, check the check box next to the cell that you want to export.
4. Click the Export tab.
5. Click the box showing <Unknown> in the Data Set Record Type column to define the dataset type.

   Geodatabase to S-57 Export tab

6. Choose the dataset type from the drop-down list.
   Tipp:

   Temp New Edition allows you to export a new edition dataset type. You can change the dataset name of the file and other metadata about the temporary new edition.

   The S57 Metadata dialog box appears.

7. Define the cell metadata.

   Once you define metadata, the check box in the Ready column for that cell is checked.

8. Click Output Location.

   Navigate to the location for the export file.

9. Click Export.

   A status dialog box appears showing you which feature is being exported.

10. Click Yes to open the log file.

    The log file shows the following information:

    • Metadata information that was exported such as DSID, DSSI, and DSPM
    • The number of features and primitives that were exported
    • The amount of time it took for the export to process
    • Any errors that occurred, listed at the top of the log file

    Tipp:

    Temporary New Editions do not get stored in the database. The system does not record that a temporary new edition gets exported.