Clarification on Dual Fuel Approach in ArcGIS Maritime

AhmedTarekAlhusainy

Dear ArcGIS Community,

After attending several webinars related to adapting and building Nautical Information Systems (NIS), I encountered some confusion regarding the “Dual Fuel Approach.”

As I understand it, the dual fuel approach aims to facilitate both the import (loading) and export of both S-57 and S-100 data from the same database. However, I encountered challenges in implementing this approach.

Here are the steps I followed:

1. Database Creation:

   • I created a database based on the ENC (Electronic Navigational Chart) Product Schema, which was installed from the product file.

2. Importing S-57 Data:

   • I successfully imported S-57 data into the database.

3. Conversion to S-101 Cells:

   • I converted the S-57 data to S-101 cells.

4. Creating a New Database with S-100 Schema:

   • I created a new database using the S-100 schema, also installed from the product file.

5. Importing S-100 Feature Catalog:

   • I imported the S-100 feature catalog into the new database.

Despite these steps, I faced an issue: I couldn’t export both S-57 and S-100 data. I understand that the schemas of both databases are now different, but my main question is how to adapt the dual nature of data within the same database.

Additionally, I came across a file named “DualFuelS57ProductDefinitions.xml” in the S-101 folder of the installation product files. Could you please clarify its purpose and usage?

 

Tobias-Venable

The file "DualFuelS57ProductDefinitions.xml" you mentioned can be imported into your S-101 geodatabase to provide the S-57 product management alongside the existing S-101 products. Once you've defined your S-57 product using these new tables (following a similar process as defining products in the S-57 data model), you can launch the Export Geodatabase to S-57 geoprocessing tool and point it to your S-101 geodatabase.

Note that this dual fuel capability was introduced at Pro 3.3 and is still evolving as the S-101 standard continues to evolve. Much of the mapping from the S-101 schema back to S-57 is configurable and that configuration is not fully complete at Pro 3.3.