The EULA version number has been updated to the 4.0 CARIS EULA to reflect the recent company name change back to Teledyne CARIS.

CSR-63249

Existing BDB schemas upgraded to version 5.4.3 or later and using Oracle as the backend could encounter an ORA‑00932: inconsistent datatypes (expected – got CLOB) error when converting certain values in the metadata column of the JOURNAL table. This release resolves that issue.

Running the Server Combine to Raster process with the "Apply dataset metadata rules" option enabled was generating a surface that contained holidays, even when the data overlapped. This has been fixed.

CSR-63160

The Server Combine To Raster process was occasionally causing a BDB Server application failure when the process was resolving metadata equality rules. This has been fixed.

When attachments are added/removed, it is now reported in the journal table that the attachment attribute has been modified.

The Server Combine to Raster and Server Add to Raster Combine processes have been updated to support composite rules and apply them all at the same time.

CSR-62485, CSR-62112

The Server Combine to Raster and Server Add to Raster Combine processes have been updated to no longer apply the Footprint Type option to raster input with a size of 1 pixel.

Validation has been added to the add_attachment and delete_attachment Python API methods to give an error if a transaction is already in progress in the current session. Active transactions must be committed before attachments can be added or removed.

CSR-60063

Attempts to retry the connection between client and server applications will now handle additional error cases.

The Publish function has been updated to support the URIs required since the release of CARIS Cloud 2.5.0.

CSR-61604

When data with unnamed compound Coordinate Reference Systems (CRSs) in Well Known Text (WKT) format (e.g. CSAR, BAG, LAS, Project files) are read by the application, it will currently show the CRS as unnamed. This has been updated to generate the default <horizontal_name> + <vertical_name> for the compound CRS.

The Server Combine to Raster and Server Add to Raster Combine processes were updated to interpret the extents parameter more accurately, fixing certain cases where the output raster dimensions were off by one pixel.

Support was added for using PostgreSQL 17 with PostGIS 3.5 as the RDBMS. No functional changes were required to support this version.

Support for PostgreSQL 15 is expected to be officially dropped in Q2 2025. At that time, testing against PostgreSQL 15 will be officially discontinued, though existing implementations using older versions of PostgreSQL are likely to continue working.

CSR-60063

Attempts to connect client and server applications are now repeated up to three times, if needed.

CSR-60063

Additional information is now logged in error cases, particularly client-server connections.

Changes were made to prevent the application closing unexpectedly when performing geometry intersections. This fixes some cases in Server Combine to Raster when resolving conflicts based on bounding polygons.

The Server Combine to Raster process now stops processing bounding polygons after it reaches an excessive number of polygons. This improves the performance of creating point cloud-like raster surfaces with many isolated nodes. The Server Add to Raster Combine process was similarly affected.

The Server Combine to Raster process was updated to support new contributor value options for enumeration and list attributes. Specifically, by appending "-TEXT" to the attribute name, the textual representation of the attribute value will be written to the contributor string instead of the index number. For example, using the Hydrographic Office profile, using STATUS as a contributor attribute may result in a value of "1" whereas using STATUS-TEXT as a contributor attribute would result in a value of "permanent".

BASE Editor 6.1.16 or later is also required to use the new contributor attribute options.

CSR-60307, CSR-59102

The Manage Active Sessions dialog box now shows locks added when running processes such as Server Combine to Raster. The locks also now show the user who started the process.

When running the Server Setup Utility, if "Upgrade the system folder of the previous installation" is selected and the existing BDB Server 5.4 system folder is selected as the source, the operation now completes successfully using the specified files as is. Note that this option has always been intended to be for selecting the backed up system folder from a previous installation. Backing up the configuration files in a different location before starting the upgrade is critical to avoid losing the previous configuration details.

CSR-60307, CSR-59102

Locks added when running processes such as Server Combine to Raster are now cleared more consistently. Starting BDB Server now clears any pre-existing locks that no longer apply. Closing a connection to the RDBMS now clears associated locks.

CSR-60307, CSR-59102

More information is stored for locks added by the system in the lock table in the RDBMS.

CSR-60295

The column for CoverageCRS in Oracle RDBMS was updated from having a 2,000 character limit to 4,000 characters.

When setting up publishing to CARIS Cloud, user credentials are now validated before being saved.

CSR-58505

When geometry intersections cannot be processed, the system now automatically performs a more precise intersection using floating-point precision. This fixes some cases in Server Combine to Raster when resolving conflicts based on bounding polygons.

CSR-58956

Changes were made to prevent the Manage Active Sessions tool from causing the server to become unresponsive. The issue had occurred when a user had a connection to the RDBMS within the same session before starting this tool.

CSR-59494

Support was added for using PostgreSQL 16 with PostGIS 3.4 as the RDBMS. No functional changes were required to support this version.

Support for PostgreSQL 14 is officially dropped. Testing against PostgreSQL 14 and older versions of PostgreSQL has been officially discontinued, though existing implementations using older versions of PostgreSQL are likely to continue working.

The Server Combine to Raster process now supports contributor attributes for the parent feature of a feature with an associated coverage, with the format parent_feature_acronym.parent_attribute_acronym. For example, a winning surfac feature with a survey parent would include the OBJNAM of the survey in the contributor if "survey.OBJNAM" is used as one of the contributor attributes.

A future version of BASE Editor 6.1 will allow selecting these specific items in the Combine to Raster dialog box.

Some performance improvements were made for processing many geometries. This affects the Server Combine to Raster process when using bounding polygons for deconfliction.

CSR-59181

When upgrading from a previous installation, the previous installation directory is now considered when it is not the default location of BDB Server 5.3.

CSR-58505

A precision issue was fixed for the Server Combine to Raster process when creating combined rasters with geodetic coordinate reference systems and using the bounding polygon conflict resolution option.

Unnecessary escape characters are no longer added to journal entries before apostrophes and backslash characters when storing the previous value for attributes.

The features automatically created for coverages uploaded to a BDB Server database are now correctly split at the international dateline so they can be valid polygons in the WGS 84 coordinate reference system.

Upgrading a database now adds more information to legacy journal entries to improve how the information is displayed in the history viewer available in BASE Editor 6.1.5 and later.

The error message displayed for invalid passwords now lists all supported special characters.

A new feature ID option was added to the query_journal method. This can be used to limit the journal entries returned to only be those for a specific feature instead of for all features in the database.

The Operation Type for Journal Entry objects can now be EDIT_ATTRIBUTE and EDIT_GEOMETRY, which are more specific than the previously supported EDIT type. The new types also store additional metadata about the previous value of the attribute or the previous geometry, respectively.

Editing features now stores additional information about the edit, including the previous value of an attribute or the previous geometry of the feature.

This information can be retrieved later through the journal in the Python API.

Support was added to the BDB Server backend for an optional feature ID when querying the journal.

The EULA has been updated to version 2.2. The changes between 2.1 and 2.2 are the removal of the previous section 8, renumbering the remaining sections, and changing the company name from Teledyne CARIS to Teledyne Geospatial. While these are the only notable changes, it is recommended to review the entirety of the EULA, which is included in C:\Program Files\CARIS\<application>\<version>\caris_eula.rtf , as well as on https://www.teledynecaris.com/en/company/terms-and-conditions, specifically the link for CARIS Software End User License Agreement (version 2.2).

CSR-56956

Additional information is now logged if a service cannot be started because a required port is not available.

CSR-58078

The Display Format of an attribute as defined in the catalogue is now considered for deconfliction rules in processes like Server Combine to Raster, like it had been in versions up to and including BDB Server 5.3.34. For example, for numeric comparisons, only the number of decimal places in the Display Format is considered.

CSR-58078

Display format information is now included in catalogues downloaded from BDB Server.

CSR-58078

Uploading a catalogue no longer duplicates apostrophes in textual descriptions.

CSR-58078

Duplicate apostrophes in textual descriptions are removed when first starting a database in BDB Server 5.4.1.

Support has been added to regularly publish data to CARIS Cloud via Bathy Data Service (BDS). This capability allows specifying the following settings for when new data is published:

- the CARIS Cloud tenant that is to be updated,

- the frequency it is updated,

- the features that have associated coverages that are to be considered,

- the deconfliction rules to be used, and

- the specifications, including IHO S-102, of the coverage products to be created in CARIS Cloud using BDS.

This can be used to distribute up-to-date tiled coverages to clients through a web portal.

CSR-53183, CSR-50247, CSR-49868, CSR-49808

The mapdef.dat support file for user-defined coordinate reference systems (CRS) now supports specifying a reference to a geodetic base CRS in the boundcrs.dat support file with an identifier of up to ten characters. A four-character ellipsoid key can still be used with a reference to a geographic CRS in the datum.dat support file.

The new capability allows adding user-defined projected CRS to the list of available CRS while using well-known geodetic CRS and transformations from EPSG.

CSR-53543

Support for the IN operator has been added for feature layers. In addition to the previously supported ATTRIBUTE=1 OR ATTRIBUTE=3 OR ATTRIBUTE=6, it is now possible to use an equivalent expression ATTRIBUTE IN {1,3,6}.

ERDAS IMAGINE (IMG) format files can now be added to a BDB Server database as rasters.

CSR-41842, CSR-37253, CSR-24535

Geospatial PDF (*.pdf) files can now be uploaded to BDB Server databases.

CSR-48667

The bounding_polygon property can now be set for coverages through the Python API.

Also, a generate_polygon function has been added to the Python API that can be used to create a polygon that is the same as what would be created automatically as a bounding polygon for a coverage.

Together, these can be used to replace existing bounding polygons in rasters, point clouds, and variable resolution surfaces with an automatically generated default bounding polygon.

CARIS Hydrographic Production Database (HPD) functionality has been added to the Python API.

Multi-character short keys have been removed for BDB Server command line tools, such as bathydbclone. They have been replaced by long keys. For example, -log is no longer supported, but --log is now supported.

An internal change was made for handling BDB Server database catalogues to improve performance. No other functional changes are expected.

Support was improved for third-party coordinate reference systems (CRS) for coverages such as GeoTIFFs from other GIS systems. In order to match the currently used CRS to an existing interoperable EPSG CRS, the coord_ref_id column is now considered, and small differences that are typically caused by rounding errors are ignored when matching existing ellipsoids to standard EPSG ellipsoids.

When transforming the coordinate reference system (CRS) for extents, the north and/or south pole are skipped if they are not part of the area of use of the output CRS.

CSR-51058

Changes were made to support GeoTIFF files that use a Mercator 2SP projection. If both Mercator 1SP and 2SP projection information is set, the 1SP projection information is used. Note that other third-party software is known to prefer 2SP over 1SP and these GeoTIFFs will display differently in that software. It is suggested to fix the headers in these GeoTIFF files to only have one set of Mercator parameters, or to update the headers so the 1SP and 2SP parameters are consistent with each other and appropriate for the data.

Initial support was added for vertical coordinate reference systems, resulting in related error messages being updated.

CSR-49508

The no data value (NDV) for third-party rasters is now used explicitly as the expected default value when no NDV is specified for a given third-party raster.

Error handling has been changed for designated soundings. No functional changes are expected.

CSR-57628, CSR-56786

If an invalid geometry is specified for a feature, BDB Server now tries to make a suitable feature. Specifically, if multiple overlapping polygons are specified as the geometry of a single feature, the overlapping polygons are now merged to create a new polygon that covers the same area. Disjoint polygons are not affected by these changes.

Negative integer attribute values are now supported for attributes that are expected to support them.

CSR-50663

The performance of processing variable resolution BAG files has been improved.

Metadata-based rules for combining database surfaces were being ignored by the application if the rules included a comparison to a specified number. For example, a rule for only picking winning surfaces if a metadata value was exactly 17.04 was ignored. Disambiguation would continue based on other rules. Now, the rules are properly applied.

BE 5.4.x or later is also required for this change.

When passing attributes into BDB Server using the create_feature() function in the Python API, there was an issue with lists that caused the resulting feature in BDB Server to be missing attributes. This has been fixed.

Combining two attribute sets together no longer creates duplicate values when both attribute sets have the same value defined for a given attribute and the attribute supports multiple values. This specifically fixes uploading attributes from an object.xml file through the Python API to an existing feature in a BDB Server database that already had the same attribute values defined.

CSR-48667

Error checking was added to the function set_iso19139_xml for Raster objects.

CSR-49224

Clearing mandatory list-type attribute values can now be done through the Python API for BDB Server database objects. As a side-effect, setting mandatory list-type attribute values now behaves the same way as setting optional list-type attribute values, i.e. in both cases, the previous set of values is cleared when a new set of values is defined.

The get_related_features function in the Python API now returns only the features of the specified type.

Adding an elevation band to an existing coverage no longer sets the new band as the default elevation band when the coverage does not already have a default elevation band.

CSR-49109

The coverage_loader.py python script now reports more detailed errors when it cannot import the referenced libraries.

Backend support for catalogues was changed, including a switch to using parent-child terminology for relationships. To ensure backwards compatibility with older versions of client software, BDB Server continues to use the previous terminology, which continue to be read by newer versions of client software.

The sample catalogues HydrographicOfficeProfile.xml and LOTS_BDBServer_Profile.xml were updated to use parent-child terminology.

In the Windows Programs and Features tool used to uninstall or change a program, the "Help link" and "Support link" items displayed when a Teledyne CARIS application is selected have been updated.

The End User License Agreement (EULA) has been updated in the following ways:

- information was added about individuals accepting the EULA on behalf of others,

- section 1 was updated,

- section 2 was replaced,

- clause 4.1 was updated,

- clause 6.2 was added,

- section 7 was added, and

- sections after section 7 were renumbered.

While these are the only changes since version 1.6 of the EULA, it is recommended to review the entire agreement.

Internal changes were made to use the standard boost third-party library for file system and date-time handling. No functional changes are expected.

CSR-53764

The way NULL values are handled with relational databases, such as Oracle and PostgreSQL, has been updated.

Internal changes were made to PostgreSQL bindings. No functional changes are expected.

The internal bdb_system_var table has been updated so the value column is of type TEXT in postgres or CLOB in Oracle. No functional difference is expected.

The agencies.txt file has been updated significantly to add dozens of new entries and replace the names for others.

The boundcrs.dat file has been updated significantly:

- EVRK, EPSG:4015, EPSG:7931, EPSG:8399, EPSG:8403, and EPSG:9067 to EPSG:9069 were added

- The transformations were changed for EPSG:4171, EPSG:4245, EPSG:4283, EPSG:4617, EPSG:4939, EPSG:4955, and EPSG:7843 to EPSG:9000

The epsg.db and spatialref.db files were updated from 9.8.3 to 9.9.1.

Various error messages in errors.txt were updated.

The fontdef.fnt file was renamed to ih_fontdef.fnt.

Entries in the ih_master.txt file were updated for NABNDI and NPLMCS. Entries were also added for NPMLSLHV, NPMLSLLT, DOLPHIN, DLFGGDASH, DLFGGDASHSY, DLFGGASY, CRESTIHO2019, IK47SHELL, IK447_4 and IK447_6. Similar updates and additions were made in the ih_symbol.bin file.

A rule name was changed in the SoundingRounding.xml file.

The unitstable.xml file was updated to support a higher resolution and to add additional units.

BDB Server is now identified as having CARIS_Server_Configuration version 6.0 in the bathynodemanagerconfig.xml