Increasingly, Subset Editor is used not just to validate but to clean, classify and identify features in georeferenced data points from both sonar and lidar surveys. New options are provided to bring efficiencies to this workflow including:
As more datasets are managed in BDB databases, it is critical to quickly locate the data you need for the task at hand. To this end, a new spatial analysis tool is introduced that provides the ability to select features using existing geometry from any vector source. This can be used, for example, to find all the features within an administrative area, to find all charted features that fall within a survey, or (as shown in the image) to find all survey datasets that intersect with an undersea cable.
This spatial query capability is not limited to BDB databases; it can be used when working with any supported sources such as shapefiles, GeoPackages and Web Feature Services.
BASE Editor is the first CARIS software solution to support time-dependent transformations. These coordinate reference system (CRS) transformations have an epoch component that allows for more precise positioning of data.
The License Manager can now be used to check out licenses from a network license server for a defined period of time. These commuted licenses are temporary local licenses that can be used during surveying when the network license server cannot be accessed.
A new workflow well-suited to performing quality control and building a feature set for hydrographic charting from lidar data is available in CARIS BASE Editor. Bring LAS/LAZ data into the BASE Editor environment to assess quality, adjust classification and compare against other data sources. Identify relevant features from point data and imagery and easily model as S-57 features directly in the area-based cleaning tool. Model as a DEM using CUBE or other gridding methods and combine with data from other sensors to generate a full picture of the seabed and shoreline.
Some of the new capabilities to explore:
Building on BASE Editor's industry leading bathymetry compilation toolkit, two new surface preparation techniques have been added along with several workflow improvements.
A new surface smoothing method called Restrained Laplacian was added that is generally less aggressive and results in less smoothing in X,Y and Z planes than our original (Cumulative) Laplacian smoothing. The effect is that the shape of sloped areas such as along a dredged channel remain largely in place with minimal narrowing of the channel.
The surface smoothing processes can now be run on elevation data that has been simplified in advance using a new Rolling Coin technique. This technique was developed by the Finnish Transport Agency as way of achieving an unambiguously safe for navigation contour set by imposing a pixel-based mask that pushes elevations into the shoaler depth ranges. The effect of the Rolling Coin is a double-buffered surface that produces contours that are greatly reduced in number and complexity than from the original dataset.
The Rolling Coin technique produces the best results when used in conjunction with Laplacian Smoothing and/or vector Contour Smoothing processes. These processes work together in a manual or fully-automated workflow to produce topologically sound, ‘chart ready’ and safe for navigation contours. These results hold even for high resolution contours such as on bathymetric ENC (bENC) overlays where there is little tolerance for topology issues or cartographic manipulations requiring manual adjustments.
Further enhancing the bathymetry compilation workflow are the additions of a new option to directly model shoal-biased thinned points as Sounding features in automated workflows, new safe-guards against producing crossing contours with vector Contour Smoothing and enhanced error reporting.
Bathy DataBASE is the first CARIS release to incorporate our new licensing technology. This upgraded licensing is softkey based, so no physical dongles are required; a license Entitlement will be created for software activation.
Key benefits of this new technology include:
For more information about the new licensing technology and how it will affect your organization contact Customer Services, or visit License FAQ.
Maritime limits and boundaries generated with CARIS LOTS can now be managed in Bathy DataBASE Server. New LOTS catalogue and portrayal files are available to use to set up a database, and then data can be imported, moving your data management into a relational database environment.
As part of expanding the scope of activities that can be supported in BDB Server, databases now supports both feature and coverage data management. The object and attribute model is now fully exposed to the user and can be customized to include any point, line or polygon feature types as required by the customer. This allows the role of BDB Server within an organization to expand beyond the management of bathymetric DEMs and into new areas of data management for features (such as for wrecks or administrative boundaries) and coverages (such as backscatter mosaics or Lidar point clouds). New feature portrayal options allow for styling that can be tailored for use of the system in different domains such as charting, oil and gas exploration and port and waterway management.
Interacting with the data that you want to in Subset Editor has never been easier. There are new geometry and attribute-based filters available that limit the data loaded into Subset Editor, allowing very quick isolation of points of interest in a specific area. The filters can be toggled independently, allowing quick access to points for cleaning or classification.
To support the changing needs of the modern hydrographic office, CARIS is pleased to provide a redesigned application interface that gives users new tools for managing and deriving information and products from diverse sources of data. With expanded access to GIS formats such as GeoPackage, services such as Web Feature Services, and direct connections to databases such as PostgreSQL, new possibilities emerge for integrating and expanding the use of CARIS applications within an organization.
The new application interface provides a consistent user experience when connecting to different data sources, filtering, grouping, setting up display properties and portrayal instructions.
BDB is an effective platform for exploring geospatial data. New navigation options have been added to make interacting with data easier and more intuitive including a new Pan navigation mode and the addition of the 3D View Controls Types in the toolbar. The user can set the preferred navigation modes and transition seamlessly between the 2D and 3D Views.
A new Python API module has been added to support interacting with vector data in a wide variety of formats New capability has also been added to the coverage and BDB Server modules, to allow scripting a wider variety of workflows, with goals of simplicity, usability, and versatility.
For example, a Python scripts can now be used to automatically populate vector feature attributes whenever a feature is created, or when a feature is edited, or when an associated coverage is uploaded to the database. A very simple example is to automatically populate the Recording date attribute when a feature is created, which can be accomplished with just a few lines of code
newFeature.attributes['RECDAT'] = datetime.datetime.now().strftime("%Y%m%d")
Process Designer has several usability updates to make it easier to design and validate a processing workflow. These updates include applying a modern design which makes it easier and more intuitive to interact with the application and design a Process Model
It is now possible to include a Process Model inside another Process Model using File > Insert Model. This makes it easier to manage complex Process Designer models by defining common capability once and re-using it multiple times. In the example below, a Process Model for creating a bMIO has been created from the Add Smoothed Band process and three existing models, which are clearly identified by their teal colour.
Validation has been built into the Process Designer, making it clear to a user if they have not defined a required parameter or connection. In the example below, the process is showing that it requires a connection for the "Coverage" input.