ArcGIS for Maritime: Charting provides data models for the transfer, conversion, and production of hydrographic data to be used in ArcGIS for Desktop. A data model is a database schema that allows the organization of all data types in the geodatabase.
Features
A feature is a representation of a real-world object on a chart, such as a point, line, and polygon. Nautical features are based on S-57 spatial and feature objects.
S-57 spatial objects are commonly referred to as vectors or primitives in the geodatabase. S-57 feature objects are commonly referred to as features and are divided into four types:
- Meta—Contains information about other objects (M_COVR, M_NSYS, M_NPUB, and so on). The S-57 meta feature objects are within the MetaDataA, MetaDataL, and MetaDataP feature classes.
- Geo—Carries the descriptive characteristics/attributes of a real-world entity (DEPARE, LNDARE, BCNCAR, SOUNDG, and so on).
- Collection—Feature objects that describe the relationship between other objects (C_AGGR, C_ASSO).
- Cartographic—Contains information about the cartographic representation of real-world entities.
Subtypes
S-57 feature objects are expressed as subtypes that are grouped into feature classes or tables based on shared S-57 attributes. For example, the S-57 feature object representing a cable area (CBLARE) is stored in the geodatabase as a subtype named CBLARE within the OffshoreInstallationsA feature class in the Nautical feature dataset. You can find which feature class an S-57 object is related to by searching the S-57 Object Finder.
Feature classes
Feature classes are a collection of geographic features with the same geometry type (such as point, line, or polygon), the same attributes, and the same spatial reference. Feature classes in Maritime Charting are organized by grouping S-57 objects that share similar attribution.
PLTS_VectorConnectedNodes, PLTS_VectorEdges, and PLTS_VectorIsolatedNodes are three primitive feature classes (within the Nautical feature dataset) that store S-57 spatial objects (vectors or primitives). The Nautical_Topology feature class is also included in the Nautical feature dataset and is configured with topology rules related to S-57 data, which are defined from some of the spatial S-58 validation rules.
Maritime Charting also includes other feature classes organized in other feature datasets and stand-alone support feature classes. The stand-alone feature classes are:
- ClosingLinesL—Contains features that are used to close off certain areas (between LNDARE and DEPCNT lines).
- PLTS_NAUTICAL_DELETES_A—Stores area features that have been deleted with the Track Deletes tool, with the reason for deletion, editor name, and the date the feature was marked for deletion.
- PLTS_NAUTICAL_DELETES_L—Stores line features deleted with the Track Deletes tool, with the reason for deletion, editor name, and the date the feature was marked for deletion.
- PLTS_NAUTICAL_DELETES_P—Stores point features deleted with the Track Deletes tool, with the reason for deletion, editor name, and the date the feature was marked for deletion.
Feature datasets
A feature dataset is a collection of related feature classes that share a coordinate system. The feature datasets provided with Maritime Charting are:
- Nautical feature dataset—Stores all the S-57 feature and spatial objects, and uses a geographic coordinate system based on the WGS 1984 datum.
- CartographicFeatures feature dataset—Stores light sector lines and is used to store data related to source diagrams.
- GRD_Grids feature dataset—Stores all grid components (annotation, points, endpoints, ticks, segments, clipping polygons, and neatlines).
Tables
Nautical support tables are used for a variety of functions, and support the production of S-57 datasets:
- PLTS_COLLECTIONS—Stores a record for all existing collection objects.
- PLTS_FREL—Stores S-57 feature relationships (master, slave, and collections).
- PLTS_MASTER_SLAVES—Sets a list of potential master and slave features derived from ENC product specification.
- PLTS_NAME—Stores long name (LNAM) and NAME parameters to use for new feature creations.
- PLTS_PRODUCT—Product identification (ENC and Charting).
- PLTS_SREL—Records spatial relationships between features and their related primitives.
Data models
The nautical models included in Maritime Charting are for hydrographic data storage of the following:
- Nautical Information System (NIS)
- Electronic Navigational Chart (ENC)
- Nautical Chart (Hard-copy Chart Specifications of the IHO S-4 and INT1)
- Inland Nautical Information System (INIS)
- Inland Electronic Navigational Chart (IENC)
- Digital Nautical Chart (DNC)
NIS
The NIS geodatabase model stores large hydrographic datasets of overlapping scale bands. S-57 products of all types can be stored in the NIS data model. The NIS geodatabase model uses the Nautical feature dataset (without the Nautical_Topology feature class), stand-alone support feature classes, and the support tables. The image below shows how the NIS data model is organized.
ENC
The ENC data model supports six scales: Berthing, Harbor, Approach, Coastal, General, and Overview. All S-57 objects are available in all six scales; therefore, there is only one ENC data model. The ENC data model contains the Nautical feature dataset, stand-alone support feature classes, and support tables. The image below shows how the ENC data model is organized.
Nautical chart
The Charting data model supports hard-copy and raster nautical chart production at any scale. It stores S-57 feature objects as well as cartographic information. The Charting data model contains the CartographicFeatures, GRD_Grids, and Nautical feature datasets, as well as the stand-alone support feature classes and support tables. The image below shows how the Chart data model is organized.
INIS
The INIS geodatabase model stores inland hydrographic datasets. Inland Electronic Navigational Chart (IENC) features can be stored in the INIS data model. The INIS geodatabase model uses the Nautical feature dataset (without the Nautical_Topology feature class), stand-alone support feature classes, and the support tables. The image below shows how the INIS data model is organized.
IENC
The IENC data model supports six scales: Berthing, Harbor, Approach, Coastal, General, and Overview. All inland S-57 objects are available in all six scales; therefore, there is only one IENC data model. The IENC data model contains the Nautical feature dataset, stand-alone support feature classes, and support tables. The image below shows how the IENC data model is organized.
DNC
There are four DNC data models that support each of the four DNC scales: Harbor, Approach, Coastal, and General, and a fifth one that supports an enterprise geodatabase, where all scales can be stored in a single database. DNC data models contain the DNC feature dataset for each scale (for example, DNCH for Harbor scale, DNCA for Approach scale, and so forth). In the four scaled geodatabases, the DNC feature datasets consist of feature classes and subtypes specific to each DNC scale, as well as a geodatabase topology. In the enterprise geodatabase, there is no topology and the feature classes and subtypes support all scales. Support tables found in all five of the DNC models include DBS_FC_VVT and notes tables. The following image shows how the DNC data model is organized.
