CARIS HPD : HPD® User Guide : Loading Data
 

Loading Data

 
HPD Data Loader
Batch Script
Log Files
External Files

The following formats can be loaded to HPD:

• S-57/ENC (.000) files, along with ENC updates (.001, .002, and so on) that are available in the same folder.

• Stand-Alone HOB (.hob) files. The HOB file is a CARIS S-57 file format supported by many CARIS programs.

• Digital Nautical Chart (DNC) files.

• Vector Product Format (.dht) data.

Before loading data, check that the following conditions are met:

• Database is installed and running with an HPD schema into which data can be loaded.

• HPD user account exists. The loader program requires an HPD schema owner or a user with a Data Loader role.

• HPD project exists. The load task will be associated with the project.

Data is loaded to HPD using either the HPD Data Loader or a batch file.

Loading times vary, depending on following factors:

• Configuration of the computer and network performing the load

• Amount of network traffic

• System usage

• Size and complexity of the data file.

Files must be loaded sequentially (one file after another). Attempts to load files concurrently will cause data to not load properly.

A log file containing warnings and messages is generated. The default file is called HPDloader.log. See Log Files.

The loader checks that the resolution of the file is acceptable, and not too fine. The finest resolution currently accepted is 0.0000001 decimal degrees, or approximately 11 millimetres.

During loading, checks are performed on features. See the table below.

Checks

Description

Invalid Geometries

Features that can not be loaded due to invalid geometries are skipped. Any dangles and bridges are removed.

Disjointed Features

Any disjointed features are split into multiple objects with new FOIDs:

• Sounding clusters are split into multiple sounding features

• Disjoint lines are split into multiple line features.

• Disjoint areas are split into multiple area features.

Spatials

Any spatials in the file that are not used by features will not be loaded, that is, only spatials associated with features are loaded.

Feature Object IDs (FOIDs)

HPD uses the existing FOIDs, these values are not reassigned during the load.

Any objects that can not be loaded due conflicting or invalid FOIDs are skipped.

If there is an object in the database with the same FOID, but having a different acronym or attributes, then the object will be skipped.

If there is an object in the database with the same FOID, and it has the same acronym and attributes, and it is not on the specified usage, then the new object will be loaded as a new representation of the existing feature.