The sample HydrographicOffice python feature plugin now maps the identification title from the ISO 19115 metadata to the OBJNAM attribute. This may assist with migrating workflows to BDB 5.0.x. It effectively duplicates the CoverageName content to OBJNAM, for newly uploaded coverages.

The BDB Server 5.0 upgrade script (bathydb50upgrade.exe) now handles spaces in paths.

Uploading a catalogue for a BDB Server database no longer automatically adds survey and surfac objects, or system attributes such as OBJNAM. There is no longer any hardcoded functionality depending on these acronyms. The system attribute changes are described in the BASE Manager enhancements section.

The BDB Server catalogue (pool and profile) provided with previous versions of the application has been renamed to be the Hydrographic Office catalogue, and moved under SampleCatalogues. This is still the catalogue used by default when creating new databases.

This catalogue has been updated to ensure the survey-surfac master‑slave relationship is bidirectional. This is required to ensure the Relationships window displays the relationship consistently. Single direction relationships are now reported as validation errors in Catalogue Editor.

This catalogue has also been updated to remove the old BDB Server system attributes and add several new ones. The new system attributes have more descriptive acronyms that are no longer restricted to six characters.

Additional sample catalogues are now shipped with BDB Server, to illustrate that databases can now be customized to be used for vector and coverage data in any number of contexts. For example, it can now be used for general vector data. Custom catalogues can also now be made to better suit specific domains; a sample Engineering Analysis catalogue is included to show some examples of customizations that could be relevant in the ports and waterways domain.

Sample feature plugins are shipped for each set of catalogues. These can be used in BASE Manager to automatically populate attribute values from CSAR metadata as part of uploading a coverage to a database. This is controlled in BASE Editor by the Tools > Options > Feature Plugin setting.

The system requirements have been updated to require 16 GB of RAM and multiple processor cores to support more efficient processing.

Windows Server 2016 is now a tested and supported operating system for BDB Server. Windows Server 2008 is no longer tested by Teledyne CARIS.

Oracle 12c Release 2 (12.2) is now a a tested and supported RDBMS for BDB Server. Oracle 12c Release 1 (12.1) is no longer tested by Teledyne CARIS.

PostgreSQL 10.0 with PostGIS 2.4 is now as a tested and supported RDBMS for BDB Server. PostgreSQL 9.4 is no longer tested by Teledyne CARIS.

A new command line tool is available that is run as part of the upgrade of databases to BDB Server 5.0.0. This tool adds an enumerated string value for Unknown to the catalogue as a possible attribute value for any attributes that currently have the Unknown system attribute value set for at least one coverage in the database. To allow specifying the exact wording for the Unknown attribute value options, it is required to first run this tool with the desired value prior to upgrading to BDB Server 5.0.0. If the tool has not already been run, any system Unknown values will be converted automatically by the upgrade procedure to a new entry "Value is unknown".

Note that the Database > Import Selected Objects command will not automatically convert any future Unknown special values to the attribute value for Unknown. This Import Selected Objects command does no mapping. It is necessary to create features in a feature layer with a consistent catalogue prior to importing them into a BDB Server database using this command.

When using a PostgreSQL RDBMS, it is now possible to configure user authentication and role management for BDB Server databases based on LDAP or Active Directory user management. Specifically, a user import tool bathydbldapsync is now deployed with BDB Server to facilitate importing the existing user accounts and assigned roles to the PostgreSQL RDBMS.

The administration of user roles has been simplified, and database security is now handled by the RDBMS, i.e. by Oracle/PostreSQL. Each user is now assigned roles, which provides the same set of permissions for all databases managed by a given Node Manager Service. When updating a database from a previous version of BDB Server, user permissions are automatically upgraded so each user now has the maximum permissions they had previously been assigned on any of the updated databases.

The new bathydbclassifyrasterholidays command line tool can be used to add holiday bands to coverages in a BDB Server database.

BDB Server database catalogues now support a much wider variety of feature types and names. All hard-coded references to "surfac" and "survey" features have been removed, and the functionality has been generalized to work with general catalogues. Coverages can now be associated with any type of vector feature defined in the catalogue - points, lines and/or areas, both 2D and 3D. Master/slave relationships can be setup in the catalogue for sets of feature types.

Note that, currently, BDB Server database catalogues only support a single primitive type per object name.

The read-only system attribute "CoverageName" is added to all objects, and is automatically populated with the name of the coverage when it is added to the database.

There is no longer any custom behaviour related to the OBJNAM attribute. OBJNAM is no longer mandatory in the provided sample BDB Server catalogues. The upgrade procedure does not affect how OBJNAM is defined in existing catalogues, as existing user workflows may require this to be mandatory.

The sample HydrographicOffice python feature plugin maps the identification title from the ISO 19115 metadata to the OBJNAM attribute, to facilitate migrating workflows that expect the OBJNAM to be populated.

The system attributes added to all BDB Server database objects have been renamed to be more readable and are no longer limited to six characters. Note that when upgrading databases from a previous version, system attributes will be automatically updated. The default and sample catalogues shipped with the application have been updated.

Changed names are: idprnt became MasterId, modtim became ModificationTime, cretim became CreationTime, uidcre became CreatingUser, srfres became CoverageResolution, srftyp became CoverageType, srcfil became CoverageSource, hcosys became CoverageCRS, and srfdsc became CoverageDescriptor.

The CoverageDescriptor now stores more information about the associated coverage, if relevant, such as type, resolution (if relevant) and band information.

The CoverageCRS now includes both horizontal and vertical coordinate reference system (CRS) information in a single CRS attribute.

The following system attributes are no longer created or populated: srffmt, srfcat, sdruls and vcosys.

The internal objects and attributes have also been renamed: bathdb became BDBServerDatabase, svrver became BDBServerVersion, and dbuuid became BDBServerID.

01701813

As part of generalizing the BDB Server database catalogue support, it is now possible to associate any type of coverage with any type of vector feature in the database. This includes new support for uploading raster images and SIPS mosaics to the database.

It is now possible to store a default portrayal to be used for a BDB Server database. This allows setting up a custom visualization for all users' first experience of objects in the database, which users can then edit to suit their individual needs. Users can save their override portrayal options in a project file.

The Python API for coverages and vector files has been greatly expanded. The general vector API can now be used for creating and editing BDB Server database features. There is still BDB Server-specific content, mostly related to associating coverages with vector features.

01501046

The Python API now allows querying all offline objects, or all offline objects with a given feature type.

It is now possible to specify a custom catalogue (pool/profile) for a BDB Server database through the Python API.

The Python API now supports explicitly adding relationships to features in a BDB Server database when a master/slave relationship is defined in the database catalogue for the two feature types. This can be done using the add_related_feature function call. Similarly, remove_related_feature can be used to remove an existing relationship.

When uploading coverage data to a BDB Server database feature, it is now possible to choose whether to replace the existing vector feature with one based on the bounding polygon of the coverage, or to keep the existing vector feature geometry.

A new feature in the Python API provides the ability to determine if a geometry is valid with floating point precision. This can be used, for example, to determine if the geometry has issues, such as self-crossing, that would prevent it from being used as a representative geometry for a feature in a BDB Server database.

It is now possible to automatically run a python script when uploading coverage data to a BDB Server database. This can be accomplished by setting the Tools > Options > Feature Plugin value in BASE Editor to an appropriate .py file with a coverage_assigned function.

This replaces the previous XSLT and attribute plugin functionality. bdbattributetransfom.xsl is no longer installed with the application as it is no longer used.

Python files are loaded into memory before executing them, so some built-in functions may not work as expected. The __file__ variable is explicitly set, so it can be used to find other python files in the same directory, e.g. by calling sys.path.append(os.path.dirname(os.path.realpath(__file__))) before importing the other files.

Values in the environment_python.xml system file are now overridden by any values defined in a user-created copy of the files in either ProgramData or the user directory for the application, %appdata%\CARIS\Bathy DataBASE Server\5.0.

01700958

Uploading a catalogue to a BDB Server database no longer fails when an attribute is defined in the pool and not used by any object definition in the profile.

Validation when uploading a catalogue for a BDB Server database has been improved to do case insensitive checks to ensure none of the new objects has the same name as an object in the existing catalogue.

Installations are now only provided as full installations. Patch installations with roll-back capability are no longer supported.

Unnecessary log messages about "ERROR: invalid value for parameter "lc_numeric": "English_Canada.1252"" are no longer recorded. It is still the case that if English (Canada) cannot be used, English (US) is used.

Improvements have been made to exceptions reported by BDB Server.

Additional information is now displayed when issues are encountered by the BDB Server Setup Utility. For example, if the user does not have permission to start the newly configured service, the utility will now report the error message reported by the operating system, such as "System error 5 has occurred. Access is denied."

Using the Setup Utility to configure a newer version of BDB Server using the configuration files from an existing previous installation will no longer fail if the system is setup with "My Documents" pointing to an inaccessible location.

GDAL support files are now deployed with the installation to ensure a consistent set of files is available.

The scripts to upgrade from older versions to BDB Server 4.2 have been removed. If using a BDB Server application older than 4.2, it is necessary to first upgrade to 4.2 before upgrading to 5.0.

The Password column has been removed from the table on the User Management page of the Administration Tools.

When creating a new database or an administrator role in Administration Tools, the privileges granted in an underlying Oracle RDBMS are now more limited, while still allowing the necessary capability.

When granting Delete permissions, users are automatically granted Edit permissions as well.

When removing Edit permissions from a user account, Delete and Purge permissions are now removed automatically as well.

CARIS Batch is no longer shipped with BDB Server.

The list of available coverage types under the CoverageType attribute (called StorageType, or srftyp, in previous versions) has been reduced to just the different types of CSAR coverages, as all data is converted to CSAR when imported into the database. Values 0 to 5 with references to third-party formats have been removed. third-party formats have been removed.

Unique identifiers for BDB Server database features are now universally unique strings. As a result, the same BOID identifier will no longer be used to refer to different features on two BDB Server databases on the same node manager. Also, the identifiers no longer have the old structure of having prefixes that describe the type of feature.

FeatureID has been added to the list of reserved attribute names that cannot be used in BDB Server database catalogues. This applies to all capitalization variations.

01702033

The copying of many designated soundings has been made more efficient. This affects the Server Join Points process, for example.

The calculation of the default resolution used in the Combine process has been updated to produce more representative values when some of the sources have geodetic coordinate reference systems.

01501393

The Python API now requires Python version 3.4.x or 3.5.x.

The Python API documentation and tutorial have been improved and fixed, with clarifications, more links, and new content for the new capability.

In the updated Python API, which uses CQL rules, it is now possible to setup arbitrarily complicated nested rules.

As attribute mapping is now done through Python scripts, the ability to upload and download attribute mapping files has been removed.

It is recommended that existing mapping files be downloaded prior to upgrading to BDB Server 5.0 and used as the basis of Python scripts, as appropriate.

Importing data into a BDB Server database has been made more tolerant of multiple different coverages being added to the database at the same time. This prevents random loading failures.

Coverage data with string table bands can now be replaced in BDB Server databases.

CSAR files were being duplicated on disk for BDB Server databases when using Set Coverage to apply or replace a coverage to an existing BDB Server database object. The files are no longer duplicated.

When an object is locked by another user, a more informative error message is now displayed, including the name of the other user when it is available.