Importing and baselining existing AML data (Maritime Charting)

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 production database (Desktop only)
2. Checking out the AML production database
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 production database

The first step of the baseline process is creating your production database and importing your AML cell into the production database, which is performed using the New Nautical Product wizard. Both creating the production database and importing the AML cell are done by the wizard.

Before you can access the New Nautical Product wizard, you must have a product library set up and configured for the desktop production workflow. This means that a product class should be configured for the AML product you want to create and a series created.

Remarque :

You need to set the required Nautical properties before launching the New Nautical Product wizard.

Etapes :

1. Start ArcMap.
2. 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.
3. If necessary, expand Product Library and Products.
4. Right-click the series for which you want to create a product and click New Nautical Product.

   The Overview area of the New Nautical Product wizard appears.

5. Review the content in the Overview area.
6. Cliquez sur Suivant.
7. Click Import Existing Cell.
8. Click the ellipsis (...) button and browse to the location where your AML S-57 cell is stored.
9. Cliquez sur OK.
10. Cliquez sur Suivant.
The summary shows the AML S-57 cell's header information stored within the metadata table.
11. Review the summary.
12. If necessary, click Back to go back to the creation method and make any corrections.
13. Click Finish.

    A progress dialog box appears with the status of the creation process.

The progress dialog box provides detailed updates of the overall process, which includes:
• Creating the product and instance tree nodes
• Creating the production database
• Importing the applicable AML schema into the production database
• Enabling versioning and archiving for the applicable production database items
• Importing the AML S-57 cell into the production database
• Checking the production database into the product library
14. Click OK when the process completes.

Once your S-57 product is created, it is checked in to the product library, and you need to check it out to begin working on it.

Checking out the AML production database

After the New Nautical Product wizard has successfully created the AML production database and imported the AML S-57 cell, you need to check out the production database from the product library. This process attaches the AML production database, which is either an ArcSDE geodatabase for SQL Server Express licensed for ArcGIS for Desktop or ArcSDE geodatabase for SQL Server Express licensed for ArcGIS for Server Workgroup, to your local SQL Express server.

Etapes :

1. Start ArcMap.
2. In the Product Library tree view, right-click the AML product and click Check Out Product.
   Remarque :

   You need to define a temporary file location to store the production database as it gets created.

   A progress dialog box appears with the status of the checkout product process.

3. Click OK when the process is complete.
4. In ArcMap, expand the Catalog window and expand your Database Servers.
5. If necessary, double-click the SQL Express instance name to connect to it.
6. Expand the SQL Express instance.

   Remarque :

   You should see your AML production database listed.

7. Expand your AML production database and drag the Nautical feature dataset into the map document data view.

   Remarque :

   If the Check Out process failed and you do not see your AML production database under the SQL Express instance, look within the temporary file location for the .mdf file. If the file is there, you can manually attach the .mdf to your SQL Express instance.

Reconciling and posting to DEFAULT

After successfully importing your AML data into the applicable production database, checking out your AML production database, and loading it into the map document data view, you need to reconcile and post the data into the DEFAULT version.

Etapes :

1. Connect to the import version in ArcMap.
2. Click the Production Start Editing button on the Production Editing toolbar.
   Remarque :

   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.

   Astuce:

   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.

3. Click the Reconcile button on the Nautical toolbar.
4. Click the Nautical Post button on the Nautical toolbar.

   The data stored in your production 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.

Etapes :

1. Ouvrez la boîte de dialogue Gestionnaire de versions à l'aide de l'une des méthodes suivantes :
   • Dans l'arborescence du catalogue, cliquez avec le bouton droit sur une connexion à la géodatabase, pointez sur Administration, cliquez sur Administrer la géodatabase, puis sur l'onglet Versions.
   • Dans ArcMap, cliquez sur le bouton Gestionnaire de versions dans la barre d'outils Versionnement.
2. Pour créer une version, cliquez avec le bouton droit sur la version à partir de laquelle vous souhaitez créer la nouvelle version, puis sélectionnez Nouvelle.

   La boîte de dialogue Nouvelle version apparaît.

3. Entrez un nom pour la nouvelle version.

   La longueur du nom de version est limitée à 62 caractères.

4. (Facultatif) Entrez une description de la version.

   Vous pouvez utiliser la description de version pour fournir des informations supplémentaires concernant l'objectif de la version. La taille de la description est limitée à 62 caractères.

5. Choisissez le niveau d'accès souhaité pour la version : Privée, Publique ou Protégée.
6. Cliquez sur OK pour créer la nouvelle version.

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.

ArcGIS for Maritime : Création de diagrammes includes a batch job for each AML product to check that all mandatory attributes are populated based on the V2.1 specification.

The following steps outline using ArcGIS Data Reviewer for Desktop functionality to perform batch validation.

Etapes :

1. Start ArcMap.
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. Cliquez sur Ajouter.
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.
     Remarque :

     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 SQL Server Express licensed for ArcGIS for 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. Cliquez sur Fermer.
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 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 jobs listed.
20. Click OK.

    The Batch Validate dialog box appears. The checks in the batch job appear in the Batch Jobs area.

    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.

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

    Astuce:

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

    Remarque :

    To view the parameter values for a batch job, click the check name in the Batch Jobs area, then click the plus sign (+) that appears.

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

    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.
24. Click Run.
    Astuce:

    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 notifying you of the number of records that have been written to the Reviewer table.

25. Click OK.

    Any errors that are found are written to the Reviewer table automatically.

26. 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 AML data must be quality controlled by running the S58 quality control checks against it with the 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.

Etapes :

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

   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.

   Astuce:

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

   Remarque :

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

   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.2.2\Nautical\.
   • On Windows Vista, Windows 7, and Windows Server 2008, log files are written to <Installation location>\Users\<UserLogin>\AppData\Roaming\ESRI\Production10.2.2\NAUTICAL\.

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

   Remarque :

   If linear or point feature records hold conflicting P_QUAPOS and/or P_POSACC values during the Update Primitives process, the resulting spatial feature is listed in the log file describing the attribute conflict. For example, if two recently inserted BOYLAT and FOGSIG point features are spatially coincident but hold different values for P_QUAPOS, then the resulting vector isolated spatial feature will be listed in the log file showing the two different QUAPOS values. Since the vector isolated node feature is still created via Update Primitives, you can modify this feature with the correct QUAPOS value.

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

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

   Astuce:

   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. The Select Unverified Features tool can help you find these features and review them.

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.

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.

Etapes :

1. 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.
2. Navigate to and check out the product you want to export with the Open check box checked on the Check Out Product dialog box.
3. Right-click the product and click Export Nautical Product.

   The ENC Export dialog box Export Information area appears.

4. Click the S-57 Export Type drop-down arrow and choose New Edition.
5. Click the ellipsis button (...) in the Export Location area and browse to the location where you want to store your package.
   Astuce:

   If you previously exported from the product library, the output location you chose appears in the Export Location area.

6. Optionally, skip the next section and click Next if you don't want to attach files.

Attaching files

You have the option to attach files to your package, such as a supporting text or image file.

Etapes :

1. Click Add in the Attach Files area.

   The Insert File dialog box appears.

2. Navigate to the location where the files you want to attach are stored.
3. Choose the files you want to add.
   Astuce:

   Use the SHIFT or CTRL keys to select multiple files if necessary.

4. Cliquez sur Ouvrir.
Astuce:

If you previously exported from the product library, the output location you chose appears in the Export Location area.

5. Cliquez sur Suivant.

Adding metadata

You can view and modify your product's metadata values. The metadata is divided into two sections you can modify:

• Product level—Contains the DSID (Dataset Identification) and DSSI (Dataset Structure Information) fields found in an S-57 file. DSID provides information regarding the dataset's source and product description information. DSSI provides information concerning the structure of the dataset.
• Instance level—Contains the DSPM (Data Set Parameters) fields that allow you to define the types of measurement units and data used with the S-57 cell.

Each node in the metadata view represents the DSID, DSSI, and DSPM S-57 field. The left side of the view shows the metadata fields and the right side shows the values. You can input new values in the fields that are not disabled.

The metadata options are different depending on the task you are performing. For example, if you are exporting a New Edition file, you can set the Vertical Datum; however, if you are exporting an Update file, you cannot change this value.

Product metadata (DSID and DSSI)

You can add a comment, edit the Issue Date for new editions, and edit the Update Application date for DSID. You can edit the ATTF and NATF lexical levels for DSSI.

Etapes :

1. If necessary, click the cell next to Comment and type a comment for the Data Set Identification.
2. If necessary, click the ellipsis button (...) next to Update Application Date and select your product's S-57 update application date.
3. If necessary, click the ellipsis button (...) next to Issue Date and select your product's S-57 issue date.
4. Click the cell next to ATTF lexical level and click the ellipsis button (...) that appears.
5. Specify the appropriate information.

   Lexical levels 0 and 1 are supported per the S-57 IHO Transfer Standard Edition 3.1, part 3, section 2.4.

6. Click the cell next to NATF lexical level and click the ellipsis button (...) that appears.
7. Specify the appropriate information.

   Lexical levels 0, 1, and 2 are supported.

8. Click Next if you are finished updating the metadata information or continue to update the instance metadata.

Instance metadata (DSPM)

You can define the types of measurement units and data used with the S-57 cell.

Etapes :

1. If necessary, click the cell next to Comment and type a comment for the Data Set Structure Information.
2. If necessary, click the cell next to Coordinate Multiplication factor and type the multiplication factor.
3. If necessary, click the cell next to Compilation scale of data and add your S-57 product's compilation scale value.
   Remarque :

   The SCAMIN tool references the compilation scale of data value to autopopulate the SCAMIN attribute field on the applicable feature records.

4. If necessary, click the cell next to the Sounding Datum and choose the appropriate sounding datum.
5. If necessary, click the cell next to the Units of depth measurement to choose the appropriate unit for depth fields.
   Remarque :

   The corresponding DEPTH value of the specified units (that is, DEPTH_M field value for meters) is exported instead of the value in the source field in the geodatabase (that is, DEPTH).

6. If necessary, click the cell next to the Units in height measurement field and choose the appropriate unit for height fields.
   Remarque :

   The corresponding DEPTH value of the specified units (that is, DEPTH_M field value for meters) is exported instead of the value in the source field in the geodatabase (that is, DEPTH).

7. If necessary, click the cell next to the Unit in positional accuracy field and choose the appropriate unit for positional accuracy fields.
   Remarque :

   The corresponding DEPTH value of the specified units (that is, DEPTH_M field value for meters) is exported instead of the value in the source field in the geodatabase (that is, DEPTH).

8. If necessary, click the cell next to the Vertical Datum field and choose the appropriate vertical datum.

Viewing the export summary

You can review your export type and metadata entries before exporting your package.

Etapes :

1. Scroll through the export summary and verify that your export type, export location, export version, and any attached files are correct.
2. Review the metadata summary.
3. If any errors are found, click Back to go back and make any necessary changes.
4. Once you have reviewed and made any necessary changes, click Finish.

   A progress dialog box appears showing the export process. When the process completes, a path to your export package is listed.

5. Click OK to close the progress dialog box.
   Remarque :

   You can navigate to the location of the export and open the export package. The package is also stored in the product library at the product level. You can view the export package through the file manager.

You have now baselined your AML product.