Bathy DataBASE Server 5.2
This section describes all changes made to the application in the 5.2 series of releases.
5.2.4
February 2019
Enhancements
BASE Manager
Reference | Description |
|---|---|
Batch Tools | |
The Server Combine to Raster process now supports the Anchor option for the centre of a cell. This can be used to align the output raster surface with an existing grid. The anchor can be outside the extent of the data as it is simply used to anchor the grid. Any x and y coordinates can be used for the anchor, and the default is to create grids with the cell centres at multiples of the resolution. A special keyword, HALF_RES, can be used to create grids that are aligned with their lower-left corners at multiples of the resolution. A newer BASE Editor version - 5.2.6 or later - is also required to use this new option. | |
Maintenance
Relational Database Management System (RDBMS)
Reference | Description |
|---|---|
Database Settings | |
When using a PostgreSQL RDBMS, previously, object acronyms had to be unique in the first ten characters as only the first ten characters were stored internally. Now, the full object acronym is used internally, so any set of unique acronyms can be used. | |
BASE Manager
Reference | Description |
|---|---|
Coordinate Reference Systems | |
The EPSG database used by default as a source of coordinate reference systems in the application has been updated from version 9.4.2 to version 9.5.5. The changes include the addition of EPSG:8860 and EPSG:8685; see the EPSG changes list for complete details. | |
5.2.3
February 2019
Enhancements
Server Setup Utility
Reference | Description |
|---|---|
Licensing | |
License Manager can now be used to check out licenses from a network license server for a defined period of time. This can be used to create a commuted license, which is a temporary local license, used for example during surveying when the network license server cannot be accessed. | |
Maintenance
Server Setup Utility
Reference | Description |
|---|---|
Licensing | |
A licensing utility has been added to the BDB Server installation to setup local licensing. | |
When only a subset of available licenses are being used, the currently used licenses are shown in bold font in License Manager to make it more clear which licenses are being used by the system. | |
Refreshing the list of detected license servers when selecting a network license source now clears the list before adding the currently detected possibilities, eliminating duplicate entries. | |
When choosing a local / commuted license, the last button in the wizard (Next) was renamed to Activate to make it more clear that the selected license will be applied when the button is clicked. | |
When browsing to an offline license file, the dialog box now starts in the last used folder. If this is the first run of the License Manager, the dialog box now starts in My Documents. | |
When browsing for the license file of a local or commuted license, all files in the current directory are now shown in the filter by default. | |
When selecting a local license in License Manager, the final page has been updated to more clearly state whether any previously activated licenses were found. | |
BASE Manager
Reference | Description |
|---|---|
Python API | |
The overlaps feature_query now only returns the features that overlap with the specified geometry. | |
5.2.2
January 2019
Enhancements
BASE Manager
Reference | Description |
|---|---|
Data Connections | |
BDB Server now respects the Windows setting for how often to notify a client connection that a process is ongoing. This resolves issues experienced on certain network connections that cancelled all operations that ran for more than a specified time limit. To setup the Windows setting, you need to use the Registry Editor (regedit) on the system hosting the BDB Server instance. In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, add a new DWORD (32-bit value) setting with the name KeepAliveTime. The Decimal value must be entered as a number of milliseconds. After the setting change is applied, the system should be rebooted to ensure the new setting is applied. | |
Maintenance
BASE Manager
Reference | Description |
|---|---|
Coordinate Reference Systems | |
The EPSG:4909 coordinate reference system (CRS) can now be specified, which uses the EPSG:4747 horizontal CRS and the EPSG:15879 transformation from GR96 to WGS 84. | |
5.2.1
December 2018
Maintenance
Server Setup Utility
Reference | Description |
|---|---|
Documentation | |
The F1 key can now be used to access the various Help topics available for the new License Manager and the License Setup wizard. | |
BASE Manager
Reference | Description |
|---|---|
Coordinate Reference Systems | |
01800627 | CSAR files created in older software that used either the CARISRectifiedSkewProj or the CARISCylindricalEquidistantProjection projection in the CSAR coordinate reference system can now be used in current applications. |
In BDB Server 5.2.0, additional entries were added to the map definition (mapdef) support files for US coordinate reference systems (CRS) data that are defined with feet units based on a NAD 83 ellipsoid. The mapdef entries are defined in metres, as all mapdef entries are always defined in metres, however, feet can be selected as the overriding unit when selecting the units of the data in the file in the CRS selection dialog box. The specific entries that were added were for Alabama (East & West), Arizona (East, Central & West), Michigan (North, Central & South), Missouri (East, Central & West), North Dakota (North & South), and Oregon (North & South). | |
Coverage Tools | |
Performance improvements were added for copying sparse coverages to/from the BDB Server. Both BDB Server 5.2.1 and BASE Editor 5.2.2 or later are required to see the performance improvements for copying data from the database. | |
Internal changes were made to the Server Add to Raster Combine process. No functional changes are expected. | |
Python API | |
User-specified no data values are now respected in the Python API. | |
Issues with setting band values after creating or deleting a band in the raster have been fixed. | |
5.2.0
August 2018
General Notices
• New licensing software is being used to manage the Bathy DataBASE Server license. A new License Setup wizard is provided in the BDB Server Setup Utility to set up licensing based on entitlement IDs. This wizard can be accessed by clicking the gear button in the License Manager, which is launched from the gear button in theLicense Host field in the Server Setup Utility. Information on this wizard can be found in both the CARIS Bathy DataBASE Server Installation Guide and in Help Topics.
Enhancements
Administration Tools
Reference | Description |
|---|---|
Catalogues | |
01801656, 01701100 | It is now possible to upload a catalogue for an existing BDB Server database that changes the descriptions of enumeration attribute values. This can be useful to correct typos in an existing catalogue. When such a catalogue is uploaded, warning messages are written to the log file to describe the changes to the attribute values. |
A sample catalogue is now shipped in the Limits and Boundaries module that can be used to create a suitable BDB Server database where LBM vector features can be uploaded. A sample portrayal file is also provided. By default, these files are deployed in C:\Program Files\CARIS\BDB Server\5.2\system\SampleCatalogues. | |
Licensing | |
A new licensing system is now in place based on entitlement strings that are individualized for each system. There is still the ability to use network or local licensing, but local licensing is no longer dependent on physical USB keys. A new wizard is provided though the Server Setup Utility to set up licensing and is also available as a standalone installation. As part of these changes, a new license string is required to use this version of the application - contact CARIS Customer Support for more information. Note that older software still uses HASP licensing, and the new license strings cannot be used for older software. The new license strings are also tied to specific modules and versions, and it is expected that future major and minor versions of the software will require new license strings. | |
Portrayals | |
Database portrayal files can now have a file extension of either .styles or .xml. When uploading a portrayal file, the default file filter now displays both .styles and .xml files. The format filters list has been updated to also provide quick filters for just .styles files, just .xml files, and all files. Similarly, when downloading a portrayal file from a database, the file can now be created with either .styles or .xml as the file extension. | |
BASE Manager
Reference | Description |
|---|---|
Batch Tools | |
The Server Combine to Raster process can now be used with a single input. | |
Python API
Reference | Description |
|---|---|
Coverage Tools | |
The Python API now provides read-only access to the bounding polygon of a coverage through the bounding_polygon attribute, which contains the bounding polygon geometries in WKT format. | |
Maintenance
Administration Tools
Reference | Description |
|---|---|
Installation | |
The installation no longer manages HASP drivers, so it is quicker to install and uninstall the software. | |
Licensing | |
The End User License Agreement (EULA) has been updated to include database schemas and XML file schemas. While this is the only change since version 1.4 of the EULA, it is recommended to review the entire agreement. | |
The Server Setup Utility was updated substantially in support of adding the new licensing wizard. No other functional changes are expected. | |
Node Manager | |
01801396 | An issue that could cause the Node Manager to close unexpectedly has been resolved. The issue had happened when cleaning up memory; no functional change is expected. |
BASE Manager
Reference | Description |
|---|---|
Coordinate Systems | |
The EPSG database used by default as a source of coordinate reference systems in the application has been updated from version 9.2 to version 9.4.2. The changes include the addition of EPSG::8395 (ETRS89 / Gauss-Kruger CM 9E); see the EPSG changes list for complete details. | |
01801629 | The comment in the header of the boundcrs.dat support file was updated for clarity. No functional changes were made. |
Coverage Tools | |
01802190, 01802101 | While coverage data is being modified in the RDBMS, it is flagged as being checked out. Data is checked out when running the Set Coverage operation. Previously, data could not be viewed or edited by any user when it was checked out. Now, BDB Server allows the current user or an administrator for the database to replace the data in a coverage that is checked out by the current user. This should only be used if the first operation failed and left the coverage in an invalid state. |
01802190 | The error message displayed when coverage data is checked out for modification, and is therefore not accessible to other users, now includes the CoverageName of the coverage as well as the name of the user who has it checked out. |
01602833 | When combining multiple coverages, string table band values for all winning nodes from all of the source coverages are now copied to the newly created coverage. |
CSAR raster surfaces with flag set bands (e.g. Status) are now created with a new internal marker to indicate that older software cannot open this data. | |
Python API
Reference | Description |
|---|---|
Coordinate Systems | |
When using the Python API, the coordinate reference system well-known text descriptions for coverages now have datum names that are compatible with third-party systems using the GDAL third-party library. | |
Coverage Tools | |
The caris.coverage module now supports creating a raster with a non-zero origin. Previously, an error message was displayed if the origin values were greater than the dimensions of the raster. | |