Support was added for using PostgreSQL 15 with PostGIS 3.3 as the RDBMS.

CSR-56436, CSR-56258, CSR-56201

A remove_coverage method was added to the Feature class in the CARIS Python API BDB Server Module. This removes the reference to the coverage from the feature, but does not delete the coverage in the database. The coverage is purged at the scheduled interval.

This is recorded in the journal as an edit of the feature and as a coverage_modified for the feature.

CSR-55869

The following message was returned by BDB Server to the client in various situations, "The server returned an unrecognized exception". Error handling has been improved to now give a more informative message for many of the cases where this occurs.

Teledyne CARIS is now testing using PostgreSQL 14 with PostGIS 3.3 as the RDBMS. No additional changes were required to support this version.

CSR-55316

BDB Server 5.3 is now tested against Windows Server 2022, and Windows Server 2022 is now an officially supported operating system for this software. No additional changes were required to support this operating system.

An unnecessary warning message is no longer logged when using a PostgreSQL version 14 relational database management system (RDBMS).

CSR-50675

When running the Server Combine to Raster process, if the resolution of the output raster surface is finer than all of the input raster surfaces, a warning message is now displayed that this operation may take a long time. The extents specified for the combine operation also have a significant impact on the time required to create the new raster.

Support was added for querying the journal for a BDB Server database for purged features, OperationType.PURGE. These represent features that have been emptied from the recycle bin.

CSR-53829

Additional error handling was added on startup so that error logs are not written in the Windows system32 directory if there is a problem with the configuration file. Information is now logged in the Windows event system in this case.

CSR-55190

It is now possible to open coverages stored in a BDB Server database when one or more of the band names includes Unicode characters.

BASE Editor version 5.5.30 or later is also required for this fix.

CSR-54744

Support was added for CQL filter files with more than 256 specified values within one rule.

CSR-54252

Marking a coverage as available to be purged - such as by emptying the Recycle Bin in BASE Editor - is now recorded as a PURGE operation in the journal instead of an EDIT operation.

CSR-54149

Support was added for using PostgreSQL 14 with PostGIS 3.2 as the RDBMS.

The Server Combine to Raster process has a new Footprint Type option. This can be used, for example, when the output raster surface is finer than a given coarser input raster surface, and it is desired that any given node in the coarser input raster surface may win in multiple output surface nodes. The default behaviour without using this option is still that a coarser raster surface node would only win for the single output raster surface node containing the cell centre or true position.

Server Add to Raster Combine uses the Footprint Type only if the original Server Combine to Raster used the option.

This new option can be used with BASE Editor 5.5.25 or later or BASE Editor 6.0.3 or later.

The combine processes were updated to ensure they properly consider cases when no data values were different between the source coverages. This was needed to support the new Footprint Type option, and it could in principle impact all combines, but no functional impact is known.

This affects Server Combine to Raster and Server Add to Raster Combine.

CSR-53268

Starting a BDB Server database now checks for a system attribute with acronym CoverageCRS and name "Horizontal coordinate system". If this is found, the name and description are updated to match the current attribute coordinate reference system values, which contain both horizontal and vertical components, when relevant.

CSR-54022, CSR-54021, CSR-53268

When upgrading a BDB Server database from 5.3.24 or before, if any coverages could not be opened, the upgrade could not be completed and the database could not be started in newer versions. Now, an error message is displayed explaining that the coverage could not be opened and the associated coordinate reference system (CRS) information could not be updated. The CRS information of the remaining features is now updated and the database can be started.

CSR-53592

A debug log can now be created through the Administration Tools.

CSR-53592

Additional information is now logged when unable to edit an object. Specifically, information about the user who has locked the object is now logged.

CSR-53848

Searching for coverage data in the RDBMS that is not referenced by anything in the database now has better performance. Also, this is now done in parallel to starting a database, reducing the time it takes to start an upgraded database, particularly for large databases.

CSR-53673, CSR-53247, CSR-51089

Additional information is now logged for the following situations when using the Set Coverage process in a BDB Server database:

- coverage data could not be replaced for a feature in the database

- newer data was added for the feature, but the older data could not be removed

CSR-53262

The maximum number of connections used for each Server Combine to Raster process can now be specified by adding an entry such as <Variable Name="MAX_PROCESS_CONNECTIONS" Value="4"/> to the BDB Server environment.xml file. At least two connections are required; if no value or an invalid value is specified, the default value of NUMBER_OF_PROCESSORS is used, as it was before. Adjusting this number of connections may be desirable if, for example, the 100 connections maximum allowed by PostgreSQL is likely to be reached.

CSR-53848, CSR-53094

Starting a database now looks for any coverage data in the RDBMS that is not referenced by anything in the database and removes it. If the coverage data is large, this may take a while.

CSR-53848, CSR-53094

Setting coverage data in a BDB Server database now prevents a database session from being closed until the operation completes. This is expected to prevent future Bathy Error (11) errors about locked data when later starting a database.

CSR-53268

The first time a database is started with BDB Server 5.3.25 or later, the system now looks for any coverages that have separate vertical and horizontal coordinate reference systems (CRS). In these cases, a new compound CRS is created with both vertical and horizontal CRS information and is set on the coverage. This is effectively a part of migrating data from BDB Server 4.x to 5.x because 4.x had separate vertical and horizontal CRS, and uploading data in 5.x creates a compound CRS.

CSR-53263

When using a PostgreSQL RDBMS, databases can now be successfully migrated from BDB Server 4.x to 5.x when permissions have been manually added to a user in PostgreSQL on the BOID column of the v_bdb_state table.

CSR-52829

Upgrading a database from BDB Server 4.x to 5.x now carries over any attachments associated with survey objects.

Databases upgraded from BDB Server 4.x to 5.x prior to BDB Server 5.3.24 could have orphaned attachment folders for survey objects; starting the database with BDB Server 5.3.24 or later re-adds the link in these cases.

The schema update 050305 is no longer run every time databases are started. Running it multiple times had no impact, but it was unnecessary.

CSR-53171

An informative error message is now shown when attempting to make a username like "dba" or "bdbdba". These usernames are used internally and cannot be used as a new user-level username.

CSR-52635, CSR-51998

The coverage_loader python script was updated to automatically read attributes from an associated .object.xml file and apply them to the feature representing the coverage. The previously available --metadatafile option is still available to set attribute values based on a CSV file and any values set through a metadata file supersede any values applied from an .object.xml file.

Version 1.2 catalogues produced, for example, in BASE Editor 5.5.6 or later, can now be uploaded as the catalogue for a BDB Server database.

BDB Server 5.3.x internally uses version 1.0 catalogues to ensure that older clients can still connect to BDB Server databases.

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. This can be used to create a polygon that is the same as what would be created automatically as a bounding polygon for a coverage when the coverage was created.

Together, these can be used to replace existing bounding polygons in rasters, point clouds, and variable resolution surfaces without the need to manually specify points for the polygon.

CSR-52182

Changes were made to prevent the application becoming non-responsive when many operations are processing at the same time.

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

Upgrading a BDB Server database now updates BOID references in journal entries to the current UUID value.

CSR-49224

When retrieving the type of a list-type attribute value, it is returned as a list consistently now, even when only one attribute is returned.

The Server Combine to Raster process now excludes any deleted string table values. Changes were also made to how the process adds entries to string tables, such as the Contributor band, to ensure all available indices are used.

A new BASE Editor, version 5.5.6 or later, is also required to have this new behaviour.

CSR-51131, CSR-46719

Support was added for PostgreSQL RDBMS hosted on an Azure platform.

Template databases (i.e. template_bdb_53) are no longer used internally. Use of templates is not critical and the required permissions are not allowed by Azure.

CSR-48753

The Map Band option in the Server Combine to Raster process has been updated to have an optional destination. This allows mapping a band to CARIS:NONE and excluding it from the output raster surface. Certain bands, including the primary band and Contributor band, cannot be mapped to CARIS:NONE. Also, if any band referenced by a deconfliction rule is mapped to CARIS:NONE, the combine process will give an informative error message about the sources not containing the referenced band.

BASE Editor 5.5.5 or later is required to get the updated behaviour, in addition to BDB Server 5.3.18 or later.

It is now possible to manage BDB Server databases when the RDBMS is a PostgreSQL and PostgreSQL is setup to require secure SSL connections.

An error message about ORB initialization now has more information about the most likely cause, which is that no ports are available, with a reference to the relevant Tools > Options setting for BASE Manager Connection Configuration.

The Server Combine to Raster process now gives a warning message, instead of an error message, when the inputs do not intersect with the area of use of the output coordinate reference system. This allows creating combined results in adjacent UTM zones, for example.

BASE Editor 5.5.5 or later is required to get the updated behaviour, in addition to BDB Server 5.3.18 or later.

CSR-50425

Support for PostgreSQL 13 was added.

The recommended PostgreSQL RDBMS version has been updated to 13 with PostGIS 3.0.2 to pick up performance and space-saving improvements and other fixes in PostgreSQL. The minimum PostgreSQL RDBMS version remains 9.6. While Teledyne CARIS primarily tests with the minimum and recommended versions, it is expected that PostgreSQL versions between 9.6 and 13 can be used.

CSR-50768

An unnecessary warning message is no longer logged when using a PostgreSQL version 11 or 12 relational database management system (RDBMS).

CSR-49249

Adding coverage data to a database and using an automatically generated polygon for the feature representation of the coverage no longer fails if the polygon is not created successfully. Instead, a minimum bounding rectangle is used as the geometry for the feature representation of the coverage in this case.

Updates have been made for verifying that a user has access to perform an operation. This is intended to fix intermittent "access denied" errors experienced by some users. Additional information is now stored in the security log when access is denied.

CSR-49249

When replacing coverage data, a new unique identifier (UUID) is now used for the new coverage data. This avoids multiple set of coverage data existing in the database for the same UUID if the replacement does not fully complete. A result is that the coverage UUID is no longer necessarily the same as the UUID of the associated feature.

CSR-50776

Interacting with data in a database, such as adding coverages to a database, no longer gives with an error message when some of the object tables are not in use for the current profile.

Changes lists for BDB Server 5.3.x are now delivered as HTML documents, similar to other CARIS products.

02002484,02002194,02002552

When retrieving attribute values from a BDB Server database using a PostgreSQL RDBMS, you no longer get an error message about the st_estimated_extent function not being implemented. Selections, for example, now complete as expected. This fix is needed if using BASE Editor 5.4.9 or later.

When a login to a node manager service is unsuccessful, the error dialog box is now shown only once.

When a connection from a client session, such as a connection from BASE Manager, is unsuccessful, references to the session are automatically removed.

The internal diagnostic tool now logs connectivity messages to the debug log instead of the error log when these messages are expected if a firewall is present.

Additional logging was added to record when deleting objects is completed.

02001912

In the RDBMS, all users who should be able to query data in the database are now explicitly granted the necessary privileges in the user access control list table.

Some unused capability relating to the bdbevents table was removed to improve overall performance.

02001912

Checks to determine if a user has permission to perform an operation are now done through the user's connection to the database instead of the system's connection to the database. This avoids users being unable to interact with data in the database, for example, being unable to query coverage data, while large system tasks are ongoing, such as purging hundreds of gigabytes of data.

01900889

Starting a BDB Server database with BDB Server 5.3.14 or later automatically upgrades the database to add the capability to specify RestrictedEditRegion and RestrictedReadRegion objects. These can be used to allow system administrators to specify regions where no users can edit and/or access the data. A context where this is useful is if coverage data is actively being replaced in the database and older data is deprecated, but the new data is not yet available.

To make these features available to be created by system administrators through BASE Manager, add the following content to the database catalogue profile:

<Object value="RestrictedEditRegion">

<Primitives value="A"/>

<Attribute value="RestrictedUsers"/>

</Object>

<Object value="RestrictedReadRegion">

<Primitives value="A"/>

<Attribute value="RestrictedUsers"/>

</Object>

If there are specific users that should be allowed to access and/or edit the coverages, the RestrictedUsers attribute value can be set to a comma-separated list of user names. System administrators can always access and edit the restricted data.

If a feature is partially contained in multiple RestrictedEditRegion or RestrictedReadRegion regions, then a user will only be able to access/edit that feature if they are set as a RestrictedUsers of all the regions the feature intersects.

02001730

BDB Server database backups can now store attachments with large filenames.

01900889

When using an Oracle RDBMS, previously, long similar object acronyms could not be used as Oracle has 30-character limits for named objects. Now, a UUID is used internally in this case, so any set of unique acronyms can be used.

The Database Properties were not being updated to show the currently selected database after an "access denied" message was displayed in Administration Tools. This has been fixed to be more consistently clear which database is being updated with Manage Active Sessions. This is particularly relevant when a user has system administration rights on some but not all databases managed by a given Node Manager.

Changes were made to prevent the Administration Tools from closing unexpectedly when sessions are terminated.

02001444, 02001398

A new command Manage Active Sessions is available to list information about the sessions currently connected to a BDB Server database. This is available through the right-click context menu on the Database Properties page. In the resulting dialog box, you can save information about active sessions by selecting them, right-clicking, and selecting to Copy session details; this information can then be pasted into a text editor. Also, a button is available to abruptly terminate one or more specified sessions. Terminating a session also cancels any unsaved edits made during the session and releases any lock files. The new command is only available to users who have database administration privileges.

02001233

When uploading an updated BDB Server catalogue, the validation code now checks object acronyms and attribute acronyms separately for uniqueness. As a result, it is now possible to have an object and an attribute that have the same acronym.

A new option is available for the Server Combine to Raster process. The Map Band option allows bands of a given name in the input coverages to be considered as another band for the purpose of the combine process. For example, if you have imported some data using shoal-bias gridding with a Mean band and the primary band Depth with Shoal data, and you imported other data using average-based gridding with a Shoal band and the primary band Depth with Mean data, you might want to map Shoal to Depth so you get the Depth band consistently with the shoalest data no matter the source.

BASE Editor 5.4.4 or later is required to use the new process.

The PostgreSQL RDBMS version has been updated to 12.2 with PostGIS 3.0.1. The minimum PostgreSQL RDBMS version remains 9.6. While Teledyne CARIS primarily tests with the minimum and newest versions, it is expected that PostgreSQL versions between 9.6 and 12.2 can be used.

The Server Combine to Raster and Server Join Points processes no longer create unexpectedly large output coverages that extend significantly beyond the specified extents. The extents are no longer transformed to WGS 84 and back to the output coordinate reference system (CRS), but are used directly in the specified CRS.

BASE Editor 5.4.4 or later is also required for this fix.

Certain SQL queries in Oracle are limited to a maximum of 1,000 items in the query, which resulted in a limit of 1,000 BOIDs in a filter, limiting the number of coverages that could be combined through a CQL file for Server Combine to Raster when using an Oracle RDBMS backend. A separate issue with thousand separators was also limiting SQL queries with a PostgreSQL RDBMS to a maximum of 999 items. The SQL query used when filtering has been updated to support up to 10,000 listed BOIDs on either Oracle or PostgreSQL RDBMS, allowing larger Server Combine to Raster operations.

02000209, 02000079, 01802665

Since BDB Server 5.0.0, users have been given the same permissions for all databases managed by a given Node Manager in order to support LDAP or Active Directory user management. It is now possible to override permissions on a per-database basis to set up a custom permission scheme. This is controlled through a new tab in the User Management tool when editing a user account.

Due to how RBDMS handle permissions, the permissions on individual databases can only be a subset of the ones granted on the main user page.

Note that you can only change user permissions for individual databases for databases that are currently running, i.e. that show as Started in the Administration Tools.

The comparisons used by License Manager have been updated when checking that the system checking in a commuted license is the same system that was used to check out the license. This fixes issues experienced by some clients when, for example, different capitalization was used for the hostname in different contexts.

The performance of the combine processes has been improved. This affects Server Combine and Server Add to Raster Combine.

Error handling has been changed for the Server Combine to Raster and Server Join Points processes to ensure an informative error message is shown if none of the provided input coverages intersect with the extents specified.

GRAVSOFT (gri) and KMS (01) geoid format files can now be added to a BDB Server database as raster surfaces.

01902234, 01902239

Default transformations have been added to the boundcrs.dat support file for GDA 94 and GDA 2020 coordinate reference systems (EPSG:4283, 4939, 4955, 7843, 7844). These transformations take into account tectonic plate changes since the CRS were defined.

BDB Server database backups are now created in a new TAR format that supports files larger than 8GB. Older backup files are still supported, but newer TAR files cannot be used in older software.

01902730

When transforming between coordinate reference systems (CRS), if the input and output have the same datum, the epoch is now only considered if an epoch transformation (velocity grid) is available and the epochs are substantially different.

When creating a new point cloud, rejected points are now excluded from the pyramid levels if any non-rejected points are available in the area. This results in more non-rejected points in higher pyramid levels (zoomed out views). As bounding polygons cover all non-rejected points at a higher pyramid level, and there are more non-rejected points at higher pyramid levels now, the resulting bounding polygons can now be larger.

Existing CSAR point clouds are unaffected. Only new CSAR point clouds are affected.

If a Status band value is changed after the point cloud is created - either by rejecting a point or accepting a previously rejected point - this has no impact on the pyramid levels. Pyramid levels are determined when point clouds are first created, and are not affected by later changes to Status band values.

Windows Server 2019 is now an officially supported operating system (OS). Windows Server 2016 is still an officially supported OS as well. Windows Server 2012 R2 is no longer tested by Teledyne CARIS, but it is expected that it can continue to be used.

Note that if you change the Windows Server OS on the system running an existing BDB Server installation, you may need to reinstall BDB Server or use the installation repair option for BDB Server to ensure all necessary components are installed for the new OS.

Individual product license activations for a system using local licensing can now be revoked. This is useful when it has been decided that software will not be used on a system after licenses had been activated on that system. If an online connection is available, the license server can be contacted directly and all the information can be efficiently confirmed to completely revoke the license activation. Otherwise, a multi-step process is required to transmit encoded license information to and from the license administrator to ensure the system and license server have synchronized information about what licenses are active on the system.

When using an Oracle RDBMS, a script is now available to ensure SDO metadata is populated. This new script, populate_user_sdo_geom_metadata.sql, should be run by a database administrator after any use of the Oracle data pump (impdp/expdp), including as part of an RMAN backup.

01902326, 01602572, 01501677, 01501657, 01401239, 01302047

Natural Resources Canada’s BYN geoid format files can now be added to a BDB Server database as raster surfaces.

International Service for the Geoid (ISG) geoid format files can now be added to a BDB Server database as raster surfaces.

The recommended PostgreSQL RDBMS version has been updated to 12.0 with PostGIS 3.0 to pick up performance and other fixes in PostgreSQL. The minimum PostgreSQL RDBMS version remains 9.6. While Teledyne CARIS primarily tests with the minimum and recommended versions, it is expected that PostgreSQL versions between 9.6 and 12.0 can be used.

An issue that could cause the application to close unexpectedly when making a connection to Oracle has been fixed.

The EPSG database support files used by default as the source for coordinate reference systems (CRS) in the application have been updated from version 9.6.3 to version 9.8.3, specifically epsg.db and spatialref.db. The changes include the addition of Camacupa and IGN CRS; see the EPSG changes list for complete details.

Scale and offset values for units are now respected when adding third-party raster surfaces such as Natural Resources Canada’s BYN geoid format files.

The handling for coordinate reference system transformations that cannot be run, due to missing grid shift files for example, has been fixed to give warning messages.

Error messages about invalid extents now include information about the coordinates of the extents that could not be used.

Error messages about invalid extents are now more explicit when no values were set for the extents.

01902036, 01901172

When replacing coverage data in a BDB Server database, the original coverage data is now backed up with an internal BOID name until the new coverage data has been completely uploaded, at which time the internal BOID is replaced with a user-visible BOID and the old data is removed. This prevents corrupted coverage data from replacing valid data stored in the BDB Server database if the transfer is interrupted. The original data is kept in the case of a transfer interruption.

When adding coverage data to a BDB Server database, the coverage data is now stored with an internal BOID name until it has been completely uploaded, at which time it is renamed to a user-visible BOID. This prevents corrupted coverage data from being stored in the BDB Server database if the transfer is interrupted.

01901592, 01901366

Additional error handling was added to the upgrade script “upgrade_050201.sql” to handle unexpected situations. No functional changes are expected for successful upgrades.

01902156

For BDB Server databases using an Oracle RDBMS, when upgrading from BDB Server 4.3.x to 5.3.x, existing one-way master-slave relationships for survey and surfac objects defined in the catalogue are now updated to be two-way relationships.

It is no longer necessary to specify the transformation for all coordinate reference systems (CRS) in the boundcrs.dat support file. If a given projected CRS does not have a specified transformation, but the base geodetic CRS of the projected CRS does have a specified transformation, the transformation of the geodetic CRS is now applied for the projected CRS. This reduces the number of entries that need to be maintained in the boundcrs.dat support file.

The boundcrs.dat support file now supports a new DEFAULT tag for the transformation. If a geographic CRS is specified with a DEFAULT transformation, no transformation is performed to convert to WGS 84. If a projected CRS is specified with a DEFAULT transformation, the transformation of the base geodetic CRS is used. If a CRS is not listed, a DEFAULT transformation is performed.

01901856

Default transformations have been added to the boundcrs.dat support file for NAD83 coordinate reference systems (EPSG:4617, 8235, 8237, 8239, 8240, 8244, 8246, 8248, 8249, 8251, 8252, 8254, 8255) and ITRF CRS (EPSG:7907-7912) as well as EPSG:8995-9000. These transformations take into account tectonic plate changes since the CRS were defined.

01802048

The boundcrs.dat support file now has a default transformation of EPSG:15894 for SIRCAS 2000 (EPSG:4674). This is also applied to any projected CRS based on this geodetic CRS.

The default boundcrs.dat support file now has EPSG:1193 as the transformation to be used for NTF coordinate systems EPSG:4275 and EPSG:4807 used for France.

The Australia 1966 base geodetic CRS is now used for relevant coordinate reference systems (CRS). Previously, the boundcrs.dat support file had mistakenly specified the Australia 1984 base geodetic CRS for all Australia EPSG codes listed in the boundcrs.dat support file.

The scale factor is now applied when transforming coordinates to/from Lambert Conformal Conic projections.

Gradians and arc-seconds have been added to the units table support file as units for angles. Scale values of parts per million and parts per billion have been added.

General file URI code was fixed to improve support for UNC paths such as \\filepath\to\network\location.db. This fixes, for example, the ability to use UNC paths for the coordinate reference system support file epsg.db.

Drivers for USB license keys are now deployed with the application. This ensures the drivers are available to be installed if needed. The preferred solution remains to use licensing soft keys instead of USB keys.

The expiration date shown in the License Manager for trial licenses now shows the date of the last day that the trial license can be used. This date is based on the number of days granted for the license and the time period during which the license can be used. If the license is activated after part of the available time period has already passed, the date will now reflect the number of days still available in the allotted period of time. If the current license is not a trial license, the field now shows N/A.

Support has been added for Oracle 18c and 19c. Note that Oracle 19c is the terminal patch set for Oracle 12.2. As such, Teledyne CARIS is changing our primary Oracle testing to be on Oracle 19c. Older Oracle versions are expected to continue to work, but will not be tested as extensively and will be removed from the list of officially supported RDBMS versions in the next major or minor release of BDB Server.

01901728

UNC paths, such as \\path\to\file\on\network.txt, are now supported for environment variables in the BDB Server Administration Tools.

add_band and remove_band methods have been added for variable resolution surfaces (VRS objects) in the Python API.

01901412, 01901394

Switching between USB license dongles now works when the new USB key was a previously used USB key. The new key is applied the next time the application is started.

The Offline Activation step of the License Setup wizard has been updated to improve the use of USB license keys (dongles). There are now separate fields to allow the locking code to be taken from the USB license key instead of the local machine. The Dongle locking code field also provides a button to launch the installer for the Sentinel System Dongle Drivers if the drivers have not been previously installed. More informative error messages have also been added for the USB license key not being detected or the drivers not being installed.

01901728

Validation of file and folder locations specified for environment variables in the Administration Tools is now done more consistently. If the file or folder specified does not exist, a message is now displayed in the node manager debug log, which can be found in the following location by default: C:\Program Files\CARIS\BDB Server\5.3\logs\BathyNodeManagerLogs.

Certain meta projections, used as the coordinate reference system (CRS) for BSB and HCRF charts, are now handled more similarly to other CRS. In addition to other changes, if a meta projection identifies that the associated polynomial CRS parameters represent a supported CRS, the known supported CRS is used instead. No functional changes are expected in BDB Server.

Support has been added for Mercator variant C, which has been the typical Mercator used internally. Previously, the internal variant C was converted on export to either Mercator variant A if the scaling latitude is zero, or variant B otherwise. This had been done for interoperability for formats that did not support variant C.

Mercator variant B is now written out in WKT as variant B, unless it is being used for a GeoTIFF. Mercator variant B is still written out as variant A for GeoTIFF as GeoTIFF does not support variant B.

01901987

Data in pyramid levels is now stored and drawn successfully when a new raster band is added through the Python API. Raster bands added in older versions of the Python API may not display when zoomed out - these bands may need to be deleted and recreated.

The level policy used to create a new band through the Python API is now stored as metadata in the BandInfo for raster bands.

BICUBIC level policies can now be used; previously MAX had been used instead. Creating a band with a BICUBIC level policy will result in the coverage not being able to be opened in older software.

Changes were made to only retrieve versioning information from Oracle when needed, which improves performance in some cases.

Internal changes were made for rolling back to savepoints. No functional changes are expected.

The recommended PostgreSQL RDBMS version has been updated to 11.4 with PostGIS 2.5 to pick up security and other fixes in PostgreSQL. The minimum PostgreSQL RDBMS version remains 9.6. While CARIS primarily tests with the minimum and recommended versions, it is expected that PostgreSQL versions between 9.6 and 11.4 work equally well.

Support has been added for new CSAR raster surfaces and SIPS mosaics with expanding extents. These can be created in HIPS 11.2 and Onboard 2.2, and are particularly useful when starting a survey project with uncertain final extents and having the extents of the CSAR automatically update as new areas are surveyed.

When these rasters are added to a database, they are automatically converted to having fixed extents. No functional changes are expected for the existing CSAR support.

A message is sometimes logged stating that the diagnostic tool has timed out when pinging the client. This is an expected message that is displayed when the diagnostic tool is run with a firewall present; the diagnostic tool is a system tool that runs automatically in the background of the application. This message has been changed to be more clear that it is not an error case.

The BDB Server journal has been storing time information with millisecond-level precision, but journal queries were only returning second-level precision. Now, the time values returned by querying the journal through the Python API have millisecond-level precision.

Attempting to add a file to a database when that file has a coordinate reference system that requires a grid shift file, such as a time-dependent transformation, now does not add the file if the grid shift file is not available. An error message is displayed identifying the missing file.

If you get this error message, ensure the uslXsystemgridshifts setting in the Environment Setting tab of the Administration Tools is setup correctly, and then restart the database.

The algorithm for creating new bounding polygons for CSAR point clouds has been updated to create smoother polygons that contain all points in the point cloud, resulting in coarser bounding polygons.

New bounding polygons for CSAR point clouds no longer consider rejected points.

The resolution used when comparing geometries is now based on the definition of the coordinate reference system of the geometries. This affects Python API geometry queries, and fixes "inconsistent location label" errors.

Only files that have been successfully uploaded as attachments to a BDB Server database are now shown as attachments.

The spelling of "license" is now used more consistently. This affects some messages displayed, but has no functional effect.

Minidump reports are now created in more cases when the application closes unexpectedly.

01802738

Support has been added to allow clearing coverage data from a BDB Server database feature. BASE Editor 5.3.5 or later can use this capability.

Support for the set_string_table function has been added to the Python API for CSAR clouds and raster surfaces.

Attribute type information can now be displayed using the __str__ function.

The unused presentationcontrol.xml file is no longer shipped with the application. No functional changes are expected.

The EPSG database used as the default source of coordinate reference systems in the application has been updated from version 9.5.5 to version 9.6.3. The changes include the addition of EPSG:8900, EPSG:9000, EPSG:9003, EPSG:9006 and EPSG:9009; see the EPSG changes list for complete details.

01802491

Position bands with Z-values for 3D CSAR point clouds now have accurate minimum and maximum values computed from the range of data in the point cloud.

When creating CSAR point clouds, the internal storage is now compressed. This saves on file size, and also improves transfer speed when uploading to BDB Server databases.

Internal changes were made to improve performance when creating new CSAR point clouds, particularly on a network drive.

The algorithm used to create the bounding polygon for CSAR point clouds has been updated to not be limited by an arbitrary maximum number of points. This change can avoid artifacts in the bounding polygons created for large CSAR point clouds.

The creation of bounding polygons for larger CSAR point clouds was updated to be more efficient.

The previous file size limitations for CSAR files have been removed. It is now possible to create CSAR files bigger than 1 TB and open CSAR files bigger than 2 TB.

01802491

The band_info property of a 3D CSAR point cloud now has accurate minimum and maximum values for the Z-values in a <position_band_name> band.

The maxOccurs property can now be used to determine whether an attribute type supports only one value or multiple values.

Functions that return a FeatureList, like get_related_features, now returns the derived types. For example, if the related features are BDB Server database features, they are now returned as caris.bathy.db.Feature objects, allowing access to the specialized database attributes and functions.

01900940

The environment.xml file updated by the Server Setup Utility and Administration Tools is now also used by the Python API. The separate environment_python.xml file is no longer shipped with the application. This simplifies correctly configuring licensing for the Python API.

When upgrading from a previous version of BDB Server, the Server Setup Utility now correctly parses the path to the existing configuration files regardless if they use a mixture of / and \ characters. Also, the attributemappings.lookup is no longer copied over as this file is no longer used in the application.

The Location field in the Bathy Node Location Editor dialog box is now updated correctly when a new location is selected for a database node.

01900772

Support was added for flag set bands such as Status. The Status band is now listed as a band for point clouds, and when applicable, the band values can be modified.

The query() function for point clouds now has an optional parameter named flags that can be used to limit which values of flag set bands pass the filter. flags=(('Status', ('Rejected'),())) or flags=('Status','Rejected') can be used to exclude all rejected points, whereas flags=(('Status',(),('Designated'))) can be used to only include designated points.

01900772

Entries in a string table are no longer escaped for use in a regular expression. They will now be escaped according to the rules for python strings.

The Python API has been updated to better support multiple values in a single attribute.

An index for the catalogue revision number is now stored in an internal table in the RBDMS. This index tracks the number of times the catalogue changes and the version number of the current iteration of the catalogue.

The licensing software now supports initializing a new license labelled with a major.minor version (5.2). It continues to support major-only versions (5) and previously initialized major.minor versions (5.2).

01900626, 01802752

Copying coverage data from a BDB Server database with an Oracle RDBMS would result in the database closing if any internal chunks of the coverage were empty, which could happen if the extents of the coverage included large areas with no data. This affected, for example, using Extract Coverage, or copying the data from one database to another. This has been an issue since BDB Server 5.2.1.

Attempting to copy the data no longer causes the database to close. Copying the data successfully requires a new version of BASE Editor, 5.3.1 or later.

Filter expressions in the Python API can now use the IS and CONTAINS operators.

It is now possible to iterate over the points in a point cloud stored with 2D positions (X, Y) using the Python API.

Iterating over the points in a point cloud no longer causes the application to close if an empty chunk is found. This could happen if the extents of the point cloud included large areas with no data.

The End User License Agreement (EULA) has been updated to include more information about direct, indirect, and consequential damages. The URL for trademark information has also been updated. While these are the only changes since version 1.5 of the EULA, it is recommended to review the entire agreement.

New licenses for BDB Server now identify the version number as 5, whereas older licenses specified 5.2. Both sets of licenses work for BDB Server 5.3 as it is the major version that is considered when license checking is performed.

The About CARIS Bathy DataBASE Administration Tools dialog box was updated to show the current website URL and trademark information.

The In Use column in License Manager is now correctly reporting the number of licenses in use based on the number of computers accessing a license on the license server.

Coverages defined with supported coordinate reference systems with time-dependent transformations, created in BASE Editor 5.3.0 and later, can now be added to BDB Server databases.

Support was added to show additional general messages - ones that are not explicitly flagged as errors, warnings, or information. No functional changes are expected.