Exporting, publishing, and packaging your ENC product

You can export your changes to the S-57 format once you have compiled your new ENC product or have made the necessary modifications to your existing ENC product and verified your data. Exporting to S-57 is performed on your product database only. The NIS is product neutral and is not designed to support exporting to S-57. You need to perform the following steps for exporting, publishing, and packaging your product for display in an Electronic Chart Display and Information System (ECDIS).

  1. Reconciling and posting changes to DEFAULT
  2. Exporting to S-57
  3. Validating S-57 dataset files
  4. Publishing the export version
  5. Creating an exchange set

Reconciling and posting changes to DEFAULT

All your data changes from your child version of DEFAULT need to be posted back to DEFAULT before the edits are exported to S-57. This is performed through reconcile and post operations; however, the Nautical Solution uses its own Nautical Post command. The Nautical Post command will automatically replace the standard Post command located on the Versioning toolbar in ArcMap and also appears on the Nautical S-57 toolbar.

If your data modifications include geometry edits, the Update Primitives process will reconcile them to the parent version. You would then need to use the Nautical Post operation to move your data changes to the DEFAULT version. If your data changes are only attribute modifications, you need to run reconcile manually before you run Nautical Post.

Steps:
  1. Click the Production Start Editing button Production Start Editing on the Production Editing toolbar.
    NoteNote:

    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.

    TipTip:

    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 Show/Hide Attributes on the Manage Features window.

  2. On the main menu, click Customize > Toolbars > Nautical S-57.
  3. Click the Update Primitives button Update Primitives 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.

    NoteNote:

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

    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.

    NoteNote:

    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 Nautical Post on the Nautical toolbar.
    NoteNote:

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

    NoteNote:

    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 to S-57

The Geodatabase to S-57 exporting command is located in the ArcCatalog application. This tool gives you the option to export all S-57 dataset types (New Datasets, New Editions, Updates, Reissues, and Cancel). However, your database connection must reference the DEFAULT version before you can enable the exporting tool.

Steps:
  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
    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
    Geodatabase to S-57 Export tab
  6. Choose the dataset type from the drop-down list.
    TipTip:

    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
    TipTip:

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

Validating S-57 dataset files

Now that you have successfully exported your AML data stored in the product geodatabase to the S-57 format, you need to run the S-57 dataset file through a third-party validation package.

Publishing the export version

Once your S-57 dataset file has been cleared through a third-party validation package, you need to publish the exported record to incrementally export S-57 dataset files. The Nautical Publisher allows you to both publish and unpublish export versions that reference the data you exported to an S-57 dataset file.

Steps:
  1. Start ArcCatalog.
  2. Navigate to and right-click the feature dataset you want to publish from and click Nautical Publisher.

    The Nautical Publisher dialog box appears.

    Nautical Publisher dialog box

  3. Click Refresh.

    The publisher searches for any changes to the PLTS_EXPORTS table that would change the cells listed in the Publish or UnPublish tabs.

  4. If necessary, click the Publish tab.

    This tab displays the alias names for the DSNM, EDTN, UPDN, HISTORICAL_NAME, UADT, and ISDT fields in the PLTS_EXPORTS table.

  5. Check the row representing the export version you want to publish.

    Check box next to Data set name

    NoteNote:

    The Historical Name field uniquely identifies each export version by showing the date and time of when you exported. This means that all changes to the database up to the displayed date and time will be included in the S-57 dataset file. In the example above, when you publish one of these records, both records will be removed from the Publish tab, and all subsequent exports will change from the Edition and Update numbers. For example, if you were to publish the first record listed, then export the second S-57 dataset file record, when you opened the Nautical Publisher, the Edition number field would list 3 and the Update number field would list 0.

    NoteNote:

    Historical information only applies to SDE databases. If you are using personal or file geodatabases, the Historical Name is not populated.

  6. Click Apply.

Creating an exchange set

Once you have exported and published your S-57 data, you need to package the S-57 dataset files into a valid S-57 Exchange Set. This allows you to view the Electronic Navigational Chart (ENC) datasets in an ECDIS for shipboard navigation. You can create a valid S-57 Exchange Set with the Exchange Set tool.

Steps:
  1. Start ArcCatalog.
  2. Add the Exchange Set tool to a toolbar by completing the following steps:
    1. On the main menu, click Customize > Customize Mode.

      The Customize dialog box appears.

    2. Click the Commands tab.
    3. In the Categories list, choose Nautical S-57.
    4. In the Commands list, click and drag the Exchange Set button Exchange Set to a toolbar.
    5. Click Close.
  3. Click the Exchange Set button Exchange Set.

    The Create S57 Exchange Set dialog box appears.

    Create S-57 Exchange Set dialog box

  4. Click the Browse button next to the Output Location text box to set your output location.

    The Browse For Folder dialog box appears.

    Browse For Folder dialog box
    NoteNote:

    Your ENC_ROOT folder is automatically created at this location.

  5. Click OK once you have selected your output location.

    The Output Location text box shows the path of your directory location.

  6. Click Add in the Content area to add S-57 dataset files.

    The Add File to Exchange Set dialog box appears.

  7. Navigate to the directory that contains your dataset files.
  8. Select the dataset file you want in your exchange set.
    Example of a selected dataset file
    Example of a selected dataset file
  9. Once you have selected your dataset files, click Open.
  10. Repeat steps 6–9 for additional dataset files.

    The table view in the Content area contains record rows for your selected datasets.

    Create S57 Exchange Set dialog box

    In the example above, all .txt files have <No Path> listed in the Path or Location field.

  11. Optionally, you can manually set the external file location for files with <No Path> by completing the following steps:
    1. Right-click the <No Path> field value and click Browse for Location.

      The Browse for Location command allows you to set the path to where the file is stored.

      The Browse for Location dialog box appears. The dialog box automatically populates the File name and Files of type fields with the missing file name. You are not able to select any file but the missing one.

    2. Navigate to the file's location, select it, then click Open.

      The dialog box disappears, and the external file's path is listed in the Path or Location field.

  12. Check the check boxes next to all the files you want to include in your exchange set.
  13. Click Create.

    A progress bar appears. A message box informs you when the process is completed.

  14. Click OK to close the message box.
    NoteNote:

    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\Exchange Set.
    • 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\Exchange Set.
    If the location doesn't exist, the tool creates the space for it. The log file is saved in XML format.

  15. Use Windows Explorer to navigate to your selected output location where you can find the required catalog file and at least one dataset file in your exchange set.
    NoteNote:

    You are not able to add additional exchange sets to this location because the catalog file already exists and cannot be overwritten.


4/19/2012