CARIS BASE Editor 5 Changes List - 東陽テクニカ · CARIS BASE Editor 5.1.0: Highlights CARIS...

CARIS BASE Editor 5

Changes List

Teledyne CARIS, Inc.(Global Headquarters)115 Waggoners LaneFredericton, NBCanadaE3B 2L4

Phone: 1 506 458-8533 (English/French/Spanish)Fax: 1 506 459-3849Email: [email protected]: [email protected] site: www.teledynecaris.com

Teledyne CARIS USA415 N. Alfred StreetAlexandria, VAUSA22314

Phone: 1 703 299-9712Fax: 1 703 299-9715 Email: [email protected]

Teledyne CARIS EMEA(Europe, Middle East, Africa)Bremvallei 15237 LV 's-HertogenboschThe Netherlands

Phone: +31 (0)73 648 8888Fax: +31 (0)73 648 8889 Email: [email protected]: [email protected]

Teledyne CARIS Asia PacificPO Box 1580Milton QLD 4064Australia

Phone: +61 (0) 7 3719 5132Email: [email protected]

May 2018

http://www.caris.com

Trademarks owned by Teledyne CARIS, Inc.This is a listing of USPTO-registered trademarks and trademarks owned by Teledyne CARIS, Inc. andmight also be trademarks or registered trademarks in other countries. Please note that laws concerninguse and marking of trademarks or product names vary by country. Consult a local attorney foradditional guidance. Teledyne CARIS, Inc. permits the use of its trademarks and registered trademarksonly where they are used in reference to Teledyne CARIS, Inc. and its products, the markings used areappropriate to the country or countries of publication, and Teledyne CARIS, Inc. is explicitlyacknowledged as the owner of the mark. Teledyne CARIS, Inc. reserves the right to withdraw thispermission at its sole discretion for any use it feels is inappropriate or adverse to its interests. TeledyneCARIS, Inc. otherwise prohibits the use of any of its registered symbols, insignia, or other identifyingmarks without express written approval. Violations are subject to liability for damages, injunctive relief,attorney's fees and other penalties.

Not all trademarks used by Teledyne CARIS, Inc. are listed in this document. Failure of a mark toappear on this page does not mean that Teledyne CARIS, Inc. does not use the mark nor does it meanthat the product is not actively marketed or is not significant within its relevant market. The absence ofa product or service name or logo from this list or the absence of a TM or TM Reg. USPTO notation againsta product or phrase listed below does not constitute a waiver by Teledyne CARIS, Inc. of its trademarkor other intellectual property rights concerning that name or logo.

The following are trademarks or USPTO-registered trademarks of Teledyne CARIS, Inc.:

• Article 76 Module• Bathy DataBASE• Bathy DataBASE Server• BASE Editor• BASE Manager• BDB• CARIS• CARIS GIS• CARIS Notebook• CARIS Onboard• ChartServer• CPD• Core Production Database• Easy View

• EAM• Engineering Analysis Module• HIPS• HIPS and SIPS• HPD• HPD Server• Hydrographic Production

Database• Limits and Boundaries

Module• LIN• LOTS• LOTS Browser• LOTS Limits and Boundaries

• LOTS Article 76• One Feature, One Time• Paper Chart Composer• Paper Chart Editor• Ping-to-Chart• Product Editor• Publications Module• S-57 Composer• SIPS• Source Editor• Spatial Fusion• Spatial Fusion Enterprise• Teledyne CARIS

Those trademarks followed by or footnoted as TM Reg. USPTO later in this document are registeredtrademarks of Teledyne CARIS, Inc. in the United States; those followed by or footnoted as TM Reg.CIPO are registered trademarks of Teledyne CARIS, Inc. in Canada; those followed by or footnoted aseither TM Reg. USPTO and CIPO or TM Reg. USPTO, CIPO are registered trademarks of Teledyne CARIS, Inc.in both the United States and Canada; those followed by or footnoted as TM are trademarks or commonlaw marks of Teledyne CARIS, Inc. in Canada and the United States, and in other countries.

The trademarks and names of other companies and products mentioned herein are the property oftheir respective owners.

Copyright owned by Teledyne CARIS, Inc.All written and image content in this document not protected by the copyrights of others is © Copyright2005, Teledyne CARIS, Inc. All rights reserved. All reproduction and redistribution is strictly prohibitedwithout the express prior written consent of Teledyne CARIS, Inc.

Copyright © 2018 Teledyne CARIS, Inc. All rights reserved.

Acknowledgements

Data used in some images was supplied to Shallow Survey 2012 by Kongsberg and is used withpermission from Shallow Survey 2012.

Data used in some images was provided to CARIS for use in training and demonstration material bythe Maritime and Coastguard Agency (MCA), specifically the Shallow Survey 2005 dataset. Theincorporation of data sourced from MCA in this product shall not be construed as constituting anendorsement by MCA of this product.

The Brooklyn Bridge image was created from data provided by NOAA and collected with the OptechMaverick and Optech Polaris systems.

All other registered trademarks or trademarks are property of their respective owners.

BASE Editor 5.1

In this chapter...CARIS BASE EDITOR 5.1.0................................. 6

CARIS BASE Editor 5.1.0: Highlights

6 CARIS BASE Editor 5 Changes List

CARIS BASE Editor 5.1.0

Highlights New scope for Bathy DataBASE1 ServerTM

As part of expanding the scope of activities that can be supported in BDBTM 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.

1. This term is a trademark of Teledyne CARIS,Inc. Reg. USPTO.


CARIS BASE Editor 5 Changes List 7

Subset Editor data filteringInteracting 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.



Flexible interface for organizing and interacting with dataTo support the changing needs of the modern hydrographic office, CARIS1 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.

1. This term is a trademark of Teledyne CARIS,Inc. Reg. USPTO and CIPO.



Navigation controlsBDBTM 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.

Expanded Python APIA new Python 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 script 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.

import datetime

def feature_created(newFeature):

newFeature.attributes['RECDAT'] = datetime.datetime.now().strftime("%Y%m%d")



Process DesignerProcess 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 ModelIt is now possible to include a Process Model inside another Process Model using File > Insert Model. This makes it easier to manage complex process 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.

CARIS BASE Editor 5.1.0: General Notices


General Notices• A new license string is required for BASE EditorTM 5.x. Contact CARIS Customer Services for more

information.• Minor versions of BASE Editor will now upgrade previous versions. For example, installing BASE

Editor 5.1.0 will remove 5.0.0.• BASE Editor 5.x cannot connect to BDB Server 4.3.x or earlier. BE 5.0.0 and later (BE 5.x) is

expected to have compatibility with BDB Server 5.x.

• The HIPS files produced by HIPSTM 11.0 are supported in BE 5.1 and later, but not in older versions.• If you have previously installed a version of the MrSID ECW plugin, it is highly recommended to

install the 1.0.4 version or later. This re-enables these formats in newer applications and ensures the application finds the correct version of binary files in all cases. Note that MrSID ECW plugins are always backwards compatible, so installing 1.0.4 will allow you to continue to use these formats in older applications as well. The plugin is available through the CARIS OCS website, and you can contact CARIS Support for any additional information.

• AddToRasterCombine will only work on raster surfaces created by the CombineToRaster process in BE 5.0.0 or later. ServerAddToRasterCombine raster surfaces will also need to be recreated by the ServerCombineToRaster process in 5.0.0 or later.

• As part of the Layers window changes, additional layers are now shown for S-57/S-100 products. • The bathydbserverloader application has been removed. It is possible to load coverages to the

database through the Python API. A sample coverage_loader.py script is now shipped with the application.

CARIS BASE Editor 5.1.0: Enhancements


EnhancementsBASE EditorReference Description

2D View

A Quick Draw property was added for coverages when displaying nodes as digits in the 2D view. By default, it is turned on, and drawing a digit will suppress drawing others within a certain distance, where the distance is controlled by the scale of the Display window. Note that there is no guaranteed bias in the selection of which digits will be selected for display.

Drawing designated soundings now always suppresses others within a radius around, where the distance is controlled by the scale of the Display window. Note that there is no guaranteed bias in the selection of which digits will be selected for display.

Batch Tools

01701948, 01701807, 01700431

The Extract Coverage process now supports geometries being specified through a WKT file. This allows using larger and more complicated geometries in Extract Coverage. This also allows easier scripting of processes because the Export to WKT process can be used to convert other vector files to a format that can be used directly with the Extract Coverage process.

Like other processes, values entered directly will be given priority if a file of values is also specified. In this case, any specified files will be ignored.

Coordinate Reference Systems

Coordinate reference system (CRS) properties now default to the current CRS of the Display window. This affects, for example, running process models when one of the parameters is a CRS.

Coverage Tools

01800413 A Display Filter property was added for coverage layers that limits the 2D visualization and interaction (e.g. selection) of data for the coverage. This does not change the coverage in any way, and any processes that are run on the coverage will still consider all the data in the source. To use a subset of the data in a process, use the Tools > Coverage > Filter option to create a new coverage with an appropriate subset of the data first.

The Display Filter property works with raster surfaces, point clouds, and variable resolution surfaces (VR). The filter works for VR regardless of the active Surface Rendering property.

This property is currently only available for a single coverage, and not for groups of coverages, and only in 2D views.

The properties for a TIN now include entries for the source of the TIN and the attribute the TIN was created from.

Coverages

When no elevation data is available for an opened raster surface or SIPS coverage, if a colour band is available, this colour data is now mapped automatically to red, blue and green channels in the Colour By > Channels property. This improves the initial display of multi-spectral SIPS mosaics, produced by HIPS & SIPS since version 10.3.



Features

In addition to the previously available Douglas-Peucker line filtering, more line filtering algorithms are now available, including the Reumann-Witkam, Lang, Radius, and Opheim algorithms. This allows a wider variety of standard filtering methods to be used, depending on the specific data, use case, and relevant standard practices. All of these line filtering algorithms are available for selected lines through Edit > Line > Smooth and Filter Lines.

When filtering and classifying data, the LIKE operator can now be used for comparing enumeration attribute values, such as Vertical Datum.

Layers

01500931, 01102159

The Layers window is now primarily a user-customizable list of layers. This is used to control the draw order of data in the Display window, as well as to interact with only a filtered subset of the data. The layers can be arranged and grouped as needed, with the bottom layer being displayed over upper layers by default. The direction for the order can be switched using the Layer Draw Order setting in Tools > Options. Groups can be created dynamically, from any supported data format, and display properties shared by all layers in the group can be set at the group level.

Coverages with multiple bands are now displayed with a single customizable layer by default. As needed, existing display layers can be duplicated to create a new display layer referencing the same underlying data.

With the changes to the Layers window, it is now possible to remove a layer without actually closing the data source for that layer. Because of this, it may be desired to recover a closed layer. This can be accomplished in the Project window by right-clicking on the data source and choosing an option for the Add Layer command. Some formats have specific commands to add specific types of layers.

As part of the reworked Layers window, Designated and Resolution Map display layers are no longer created by default when coverages are opened. These layers can be added, if desired, through the Project window.

A new context menu command, Go to Source, has been added to the Layers window. This command automatically highlights in the Project window the source of the layer that was selected in the Layers window.

The Filter dialog box has been updated to separate the basic graphical expression editing from the advanced CQL expression string.

Process Designer

It is now simpler to create a process model with multiple processes that share the same input parameters or predefined values.

Specific values can be set in advance, either for a single process, or shared between processes, and saved in the model file. This is set up by right-clicking on an option field in the Properties window or on a tool in the model window and choosing "New value". This creates a new Value object linked to an Input connector on the process tool it relates to. This Value can be shared with other processes.

If a particular process requires specific input when the model file is run, the "New parameter" function will add a Parameter object to that process tool. When the process model file is run, the parameter is displayed as a field in the Run dialog box. This will prompt the user to identify or point to the required input. A single parameter may be shared between processes. Parameters can also be used as output prompts.

Parameters that require files as input will now specify a set of filters to enable users to select the appropriate files when running the model.

Reference Description



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 models by defining common capability once and re-using it multiple times.

It is now possible to copy and paste a tool using Ctrl+C or Edit > Copy. Any populated values are also copied. The copy can then be pasted in the same model or in another open model. Note that the copy is initially placed in the same location as the original tool.

Several usability improvements have been made to the components in the model window to make it easier to design and validate a processing workflow. For example, process tools now have green title bars. Similarly, the new Value components that specify predefined shared values are now shown in purple, the new Parameter components for values to be entered at run time are blue, and process models inserted added within a model have teal title bars.

A tool with incomplete processes or missing parameters now displays a red icon with an exclamation mark, to indicate an issue with the model being created.

Parameter links and ports on tools in the main window are now coloured to show whether they have been set. Red circles indicate where a parameter must be linked. Once connected to a user parameter, these circles are green-filled. Optional parameters are always green.

New connections can now replace existing connections when the number of connections is limited, for example, if the option is not repeatable and can only be defined once. The application prompts for confirmation when replacing connections.

The For Each process has been updated to allow inserting a model into the existing model, instead of referencing another model by filename. It will also now accept multiple input parameters/values, and allows an output parameter. This provides greater flexibility in chaining models together.

The new Branch process has been added to the Tools list for performing conditional logic by splitting an output path based on a Boolean value. For example, the Branch tool can be connected to the Exists process, by selecting the Create a branch option from the right-click menu on the Exists tool.

The logic used to conditionally run a process now requires an explicit Boolean input, such as the output from a Branch process. Identical orange pentagonal icons indicate both a condition on the process tool and for the outputs of a branch. The orange connecting lines linking these distinct type of connections distinguish them from the green lines connecting process to process.

It is now possible to open a process model by dragging it and dropping it anywhere in the Process Designer application, including the main window.




Projects

A Project window has been added to allow managing the data sources open in the application. While each data format has its own definitions as to what information is to be displayed for a given source, the Project window can typically be thought of as the catalogue of the source. This is the main way to interact with the data source itself. Display layers in the Layers window can easily be created from the source, or from part of the definition of the source. For example, the bands of a coverage are displayed in the Project window when the coverage item is expanded, and it is possible to easily create a display layer for these bands, create a new TIN source for a given band, or to otherwise interact with the source to delete specific bands or even the source itself.

Interacting with sources in the Project window replaces interacting with the source in the Layers window. Sources are no longer displayed in the Layers window, only display layers and groups are displayed there now.

Note that the Properties window displays properties for the most recent selection from the Layers window or Project window.

Note also that most coverage processes that run based on the selected layer continue to operate on the selection in the Layers window, as the Layers window allows a single unique selection, whereas the Project window supports multi-selection to facilitate managing sources efficiently.

As part of the addition of the new Project window, capability related to configuring data is now available in the Project window context menu instead of the Layers window context menu. For example, the right-click context menu to Delete a CSAR coverage from disk is available from the Project window. Similarly, adding display layers for data is generally available from the Project window, with the exception of creating filtered layers from existing display layers, which is available from the existing display layers, when appropriate.

The Project window allows multi-selection. This has been hooked up for a few operations, such as closing multiple sources at once, or adding multiple coverage band layers at once.

Multi-selection is expected to be added to more commands over time, where appropriate.

The title bar of the application now shows the name of the currently active project. If the active project has never been saved, the title bar shows that the currently active project is untitled.

Properties

All available display properties are now shown in the Properties window by default for vector layers. Users can hide display properties by using the Visible Properties dialog box which is launched from the gear icon in the upper-right corner of the Properties window.

User Interface

A Welcome dialog box is now displayed when starting the application. It has useful links to a number of commonly used commands to get new users started. This dialog box has different content based on what modules are enabled, and unselecting the “Show when application launches” option can be done to not show the dialog box again.

A search option has been added to the dialog boxes displayed when selecting from the available values for enumeration and list (e.g. Vertical Datum and Colour) attribute values in the Attributes window. This simplifies finding the appropriate entry, especially when there are many values defined in the catalogue.

Miscellaneous

The control for entering expressions has been updated to support boolean (true/false) values. This control is used, for example, in the Filter Coverage dialog box and the Filter layer dialog box.


CARIS BASE Editor 5.1.0: Maintenance


MaintenanceBASE Editor

The control for entering expressions has been updated to support searching for an empty ID.


2D View

Double-clicking on a feature in the Selection window now centres the Display window on the feature and zooms in to the area around the feature.

The z-axis convention of the application no longer affects the display of non-elevation bands in variable resolution surfaces.

3D View

01300763, 01201128

Any active display properties for vector formats such as Shapefiles are now also applied when the data is turned on for display in a 3D view. Note that changing the display properties for these formats while the data is loaded in the 3D view does not currently update the 3D view; it is currently necessary to turn off the dataset in 3D and turn it back on to get the updated display properties.

When switching between 2D and 3D views, if the Pan control was active, it now remains as the active control.

Legends can now be displayed in the 3D view.

The way that Tools > Options settings for the 3D view are handled has been updated. No functional changes are expected.

Batch Tools

01800570 The Combine to Raster process was failing to update nodes with designated soundings from the winning source when applying dataset metadata based on bounding polygons. This has been fixed.

01800570 If a node in a BAG file is determined to be the winner in deconfliction as part of the Combine to Raster process, an error message used to be displayed if that node had an associated designated sounding. Now, the combine completes successfully.

The error message has been changed for the Contour Raster process when the Levels File option points to a file that cannot be opened.

The validate-options CARIS Batch option now checks the Tools > Options environment settings for references to files and folders that are not available.

Batch processes now use the first element in the URI to determine whether it represents a file or other kind of source. No functional changes are expected.


The coordinate reference system (CRS) control found in multiple dialog boxes and properties has been updated to improve how it shows information when no CRS has been selected. No functional difference is expected.




Coverage Tools

01800874, 01800537, 01800236, 01800062

The Compute Band command now considers the Z-axis convention of every band that appears in the expression, regardless of whether it is the first entry or a later entry in the expression. This fixes newly created computed bands with expressions like "1+Depth". Any existing computed bands created in older software will continue to have the same values as shown in past releases.

Note that if you have a coverage created in older software, with a relevant computed band, and create a new coverage from the existing coverage and carry over the computed band, the new coverage will have an updated computed band that properly handles the Z-axis convention of the expression.

01702432 When process options contain multiple complex values (e.g. a range with a start value, end value, and interval), all of those values are now stored in the lineage of the resulting CSAR file.

01800214 Using the Combine Coverages dialog box to join point clouds now correctly populates the contributor attribute. Specifically, this was fixed for the case when performing deconfliction based on dataset metadata rules in areas defined by the bounding polygons of the data.

When using the Combine Coverages dialog box with locally opened coverages, point clouds are now consistently shown with no resolution value.

The Filter Coverage process now creates different internal indexing values for point clouds. No functional differences are expected.

Certain lists of open coverages showed multiple copies of the coverage layers in the Layers window. This affected, for example, the Difference Coverage dialog box. Now, these lists show all the relevant data for each open coverage, once only, regardless how many layers are being used to represent the source.

TIN creation has been updated to handle cases such as a CSAR file containing multiple raster surfaces.

The source URI for an open TIN has been updated to better support multiple rasters in a single CSAR file.

The way TINs store their source has been updated to better handle coverages open from a database. It is now possible to interpolate a raster surface from a TIN created from a coverage open from a database.

A warning message is now displayed in the Output window when a TIN Editor TLS file is created in the temporary folder of the system. This happens, for example, when creating a TIN from an unsaved coverage, or from a coverage open from a database. This warns that changes to the TIN are not saved in the same location as the coverage, and the changes will not be applied the next time the TIN is created.

The boundary TIN command is now only enabled for rasters and variable resolution surfaces that have one or more bands with suitable numeric data.

It is no longer possible to create both a boundary TIN and a full TIN at the same time for the same raster surface band.

It is now possible to save transient point clouds, such as point clouds created by the Filter Coverage dialog box.

A fix was made to variable resolution surface (VR) creation when using the Calder-Rice Density resolution estimation with a Swath Angle population method. No functional differences are expected.

The variable resolution dialog box has been updated to support HIPS track lines; no functional changes are expected in BE.




Lineage can now be displayed for Export Points to CSAR, Finalize Raster, and Generalize Raster processes.

The Finalize Raster process no longer fails if an uncertainty option has been specified but the uncertainty band does not contain any data in areas of the raster surface.

When entering a password when performing a vertical shift based on a SPINE water level service, the password is now hidden as it is typed.

The Extract Coverage process now supports a filter expression with band values specified as the textual string and not the internal numeric identifier. For example, the expression Classification=’Water’ can now be used. The Export Coverage to ASCII process and the new Update Band Values process were similarly updated.

The error messages for certain invalid expressions have been improved to be more specific.

For Export Coverage to ASCII, a band filter using the != operator will now return locations where there is no data in the coverage. For example, Depth != -39.0 will export every location the Depth is not equal to -39.0, including the locations where the Depth is undefined.

Colour bands copied by the Coverages > New > Mosaic tool are now properly updated when the resolution of the data is changed.

The Render Raster process now checks whether the specified Tools > Options Colour Maps folder exists.

Coverages

01702499 Creating a bounding polygon for a raster surface has been updated to be more efficient for sparse data.

The Bounding Polygon Type option has been removed from all processes. All new automatically-generated bounding polygons are created using the Buffered strategy. Any existing bounding polygons created using the Convex strategy can continue to be opened, and it is still possible to manually digitize, edit and remove bounding polygons.

The Bounding Polygon Type option has been removed from the properties for CSAR coverages, and the associated Tools > Options setting has been removed.

It is now possible to digitize a new bounding polygon, or automatically generate a bounding polygon, on coverages such as CSAR raster surfaces even when they do not already have a bounding polygon.

If a bounding polygon cannot be cut to the dateline, the original bounding polygon is now used in processing. This fixes, for example, adding vertical-plane-based raster surfaces to a BDB Server database.

The format of lineage has been changed in newer applications. The lineage dialog box has been updated to support both older and newer lineage information.

It is now possible to shade a colour band based on the values in a numeric band.

When displaying a raster surface and shading the display based on numeric values in a different band, pixelated display artifacts could be displayed at some zoom levels. This has been fixed.

Changes were made to how CSAR coverages are opened to prevent errors about not being able access the files. This could affect, for example, running process models. No functional differences are expected.




Export

01702687 When exporting to a variable resolution BAG file, if the lineage metadata is too large to be stored in the BAG file, the data is exported without any lineage metadata and an informative warning message is now displayed.

Improved error messages are shown if exporting a coverage as a variable resolution BAG and the output cannot be created. This can happen, for example, if the output location is read-only.

01702946, 01601325

When rendering a raster surface as a GeoTIFF image, areas with no data are now set as transparent. Third-party applications typically display this background as white.

The Export Selection dialog box used for multiple formats remembers the last output folder. Now, if the last used output folder is not available when the dialog box is opened, the factory default output location is proposed. This happens, for example, if the previously used folder had been deleted or the network path is no longer accessible.

Features

The Edit > Features > Intersect command no longer causes the application to close when two or more of the features share the same edges.

Intersecting edges now correctly handles cases where an edge is split multiple times as part of the same operation, without requiring the operation to be run multiple times.

The new feature creation buttons now enable only if the currently selected layer can have features of the current button type.

When smoothing contours, a tolerance of 1 is now set as the default value the first time the dialog box is opened. The last tolerance used continues to be remembered and is used as the default the next time the dialog box is displayed.

The application could close unexpectedly if a feature was deleted while it was being edited. Now, the feature is deleted as expected.

Creating features inside a selection/superselection now reports the number of features processed. The message also includes whether some were skipped because they were not closed loops.

The active portrayal is now applied when editing features in a HOB file or other feature layer.

Format Support

The Add Layer command now works for raster images.

Support for reading coverages from the CARIS Onboard service has been updated to support Onboard 2.x, while preserving support for Onboard 1.x.

Processes have been updated to support coverages shared by an Onboard 2.x service.

HCRF files containing multiple images now open as a group of raster images instead of a single raster containing multiple image bands.

HCRF layer properties are now saved in project files.

Import

01800557 Importing a Variable Resolution BAG to CSAR now properly sets up the internal indexing. This fixes how digits are displayed for the CSAR variable resolution surface.

01800852 When importing LAS data to a CSAR point cloud, flags are now properly mapped to Status band values as specified.




The GPS reference week no longer needs to be set when importing from LAS data if Time data is not being imported.

Position attribute information is now properly displayed when using the Import Wizard to import from HTF files.

The Import Selected Objects from Selection command will now enable even when the selection is from data in an unsaved coverage, for example a coverage created by the Filter Coverage command.

Clicking on a layer created by the Object Import Utility now works as expected and does not give error messages.

Installations

Two different minor versions are no longer supported on the same system at the same time. Installing a newer minor version now automatically replaces any older versions currently installed on the computer. For example, installing BE 5.1.x automatically uninstalls BE 5.0.x.

The installation wizard now automatically suggests the location of the last relevant BE installation as the default location for the new installation. For example, if BE 5.1.0 is installed in a custom location, BE 5.1.1 automatically installs to the same custom location.

Layers

Filter display layers are saved when projects are saved; this now includes unique feature acronym filter display layers. However, display properties for HOB and S-57 data is not currently saved in projects.

Names for filter layers can now include Unicode characters, such as å and Ø.

Creating classifications based on the number of values has been fixed for enumeration-type attributes.

The Layers window option of grouping by source has been removed. The new Projects window can be used instead for the relevant use cases.

It is now possible to add a display layer for a TIN surface from the TIN in the Project window. It is not currently possible to add a display layer for a TIN Editor layer, other than by recreating the TIN source.

Options

The Tools > Options setting for whether to see all coverages in the tooltip is now set as “On” by default.

The Tools > Options setting for automatic refreshing of the Display window is now respected.

When drawing coverage data as digits, including when drawing designated soundings, the Tools > Options Sounding Rounding rule is now applied.

When reading folders from Tools > Options environment files, any trailing slashes are now ignored. This fixes, for example, how the location for colour map/range files is interpreted, so the value specified for the Tools > Options setting is now respected.

Changing the z-axis convention in Tools > Options after closing some coverages no longer causes the application to close.




Process Designer

01800911, 01800584

Process models with options that support multiplicity now correctly save and load all specified values. This affected, for example, individual contour Levels in the Contour Raster to HOB process.

01800584 The Levels File option can now be set for the Contour Raster process.

A process model with the Warp Raster process can now be run without a Reprojection Method selected. In this situation, the Fast reprojection method is used by default.

The Filter Features process no longer shows duplicated entries for the inputs and outputs.

The Exists process has been updated to support datasets that are not file-based, such as coverages provided through services.

Process models including the Add Features process can now be run.

The File > Open dialog box now allows selecting and opening multiple process models at the same time.

The Recent Files list in Process Designer now only includes process model files.

As part of the changes to process models, data written to HOB files is now properly cached, allowing features to be passed between processes in the model.

This is known to have fixed how Create Soundings from Coverage can be used in models - it can now be used to create soundings in one HOB file and then Add Features can be used to copy those soundings to a second HOB file.

It is now possible to automatically open process models with the Process Designer application if you choose to use the Windows OS to associate double-clicking on a process model with the Process Designer application.

In the Process Designer Save As dialog box, process model files will be saved using the *.processmodel extension. If no other name is entered, the file will be saved using the name of the View tab (e.g., New 1 ) and *.processmodel. By default the file will be saved to the last accessed folder, as listed in the dialog box.

The sample process models in C:\ProgramData\CARIS\BASE Editor\5.1\SampleData have been updated to include changes to the model file format.

Properties with files now show local file paths, when relevant, instead of encoded URIs with %20 for spaces.

The error message has been improved when attempting to open a file in Process Designer that is not a currently supported model format.

Given the addition of Value and Parameter objects in Process Designer, the Data process is no longer necessary and has been removed.

If a process model does not contain any parameters that need to be set at run time, the Run Process Designer Model dialog box will be empty. A message is now displayed to confirm that it is OK to run the model.

When connecting objects in the Process Designer view, it is no longer required to first show the port. Once the connection is drawn, the compatible ports in the second object are now shown in a dialog box, and the appropriate port can be selected.

Connections can no longer be created between ports in processes that have incompatible types.

The process model tools have been updated to a smoother shape and are partially transparent, in order to improve the visualization and to make it easier to follow the connector lines in complicated models.




Tools in Process Designer can be resized from their minimum width.

Right-click context menus now appear at the cursor location regardless of the zoom level in the main window.

A tool being moved in the Process Designer window now always snaps to the underlying grid, to simplify organizing processes and other objects in complicated models.

Unnecessary information is no longer logged in the Output window when the Exists process is run.

The unique identifier of the unit is now stored, for example in process models. This fixes being able to use cables as units in models. It also ensures that the expected definition of a foot is used (US versus imperial feet).

Error messages displayed as a result of running process models now display the full error messages instead of the internal identifiers.

The name displayed for Process Designer in the Windows Task Manager has been updated.

Help is now only opened once when the F1 key is pressed.

Projects

In the new project files introduced in BASE Editor 5.0.0, default display properties were not being written to the project file. This affected reference models, for example, resulting in error messages when opening a project with a reference model with one or more customized display properties. This has been fixed.

Symbolization scale values in the display properties are now saved in project files.

The way project files store the colour file information for coverages has been changed to allow easier sharing of project files.

Project files no longer save items, like the Subset Editor reference layers, that are not intended to be saveable layers.

When opening a project containing references to BDB Server databases, if the proper credentials are not supplied, the BDB Server database is now skipped and the other data in the project is still loaded.

The Close All command has been renamed to Close Project, to reflect that all work is always being done in a project, whether it is a saved project or an unsaved temporary project. The command still closes all open datasets. Also, it now always spawns a prompt to ask to save the project if there are any unsaved changes.

Properties

Colour channel properties are now available for all applicable images, not just CSAR raster images.

The channels available in the colour channel property drop-down lists are now ordered based on the channel identifier.

Setting the Colour Range property for feature layers no longer causes the application to close.

Editing an entry in a property that allows multiple parameters or values and each entry contains multiple options (i.e. a complex option with multiplicity) has been fixed. For example, this affected certain fields in Process Designer.

The Legend > Interval property for coverage band values has been updated to accept fractional numbers.




The values in a string table can now be accessed through the String Table Definition property for a selected band item in the Project window.

Read-only strings in the Properties window now support scrolling through the contents and/or copying to the system clipboard.

The minimum and maximum values displayed in the Properties window for elevation bands now respect the active z-axis convention.

Changes were made to the Properties window to ensure invalid sets of properties would not be processed. No functional changes are expected.

Selections

Selecting from a group containing one or more coverage band layers and associated designated soundings layers now selects the items individually from each layer, resulting in more nodes being selected.

Selecting from a filtered vector layer, such as a filtered layer based on a HOB or S-57 file, now automatically superselects the first feature listed in the Selection window.

The Extents picker has been fixed and now allows selecting a subset of the current Display window. This had affected dialog boxes such as Combine Coverages and the Import Wizard.

TIN layers that had been turned off in the Display window were being displayed when a selection was made from the TIN. Now, only the selection is shown.

The Add Feature to Selection command now adds the highlighted reference model feature to the selection.

Area values in the Selection window now respect Tools > Options units and precision.

Colour values are now displayed in the Selection window as a set of (red, green, blue) values.

Changing the active selection control, such as Lasso or Circle, now adjusts the cursor that is displayed in the view to make it more obvious which selection control is active.

The Selection window is now cleared properly when a source is closed.

The columns in the Selection window can now be reordered.

Subset Editor

01701572 The current user setting for whether to show rejected soundings is now respected consistently in Subset Editor.

The performance of loading data in Subset Editor has been improved when a geometry filter is applied to limit the data loaded. This applies both to the initial load of data and also to moving the subset slice location.

The primary elevation band data of sources in Subset Editor is now shown in the Selection window as the Z-value of the points.

Sources are now displayed in the Subset Editor properties when colouring by source, with appropriate colouring.

Switching between active controls (pan, selection, zoom) in Subset Editor now works the same as the regular 2D and 3D views.

The Subset Editor 2D and 3D buttons are now enabled when Subset Editor is open.

The application no longer closes when Add to Subset Edit Sources is used after a subset bounding box is defined but before data is loaded into the subset.




TINs

Creating a TIN from a non-elevation band now shows the points in the correct location with the correct sign for the elevation of the data.

Creating a TIN from features with Z-values defined in the elevation lookup table has been updated to always use the Z-values with units of metres.

User Interface

The File > Open and File > Save dialog boxes for process options no longer specify the file extensions multiple times. No functional change is expected.

Convenience filters (e.g. *.csar) in File > Open and File > Save dialog boxes have been updated to remove duplicated entries.

Some dialog boxes were always initially displayed in the main monitor, even when the application was being accessed through a secondary monitor. Now, the dialog boxes initially display in the monitor containing the application.

When multiple types of coverages can be used for a command, the name of the function and dialog box has been changed from the more specific "Surface" to the more general "Coverage". For example, Extract Surface is now called Extract Coverage.

When only rasters can be used in a function, the name of the function and dialog box has been changed from the more general "Surface" to the more specific "Raster". For example, Generalize Surface is now called Generalize Raster.

Dialog boxes and properties that allow selecting files no longer allow multiple identical references to the same file to be added.

Properties windows and dialog boxes no longer show horizontal scroll bars when all data is visible.

The paths shown in newer dialog boxes and properties are now more consistently shown with back slashes (\) instead of forward slashes (/).

Menus that list Superselection and Selection options have been updated to list the commands in a consistent order.

A new convenience button for the Open Connection command has been added to the default toolbars.

The Remove Band command, previously known as Remove Layer, has been renamed to Delete Band to make it clear that data is permanently removed from the CSAR file.

The Pan control is now specifically marked as the active control when the application is first started. The last used control, including the specific type of selection (when relevant) is now stored in the application settings and it used the next time the application is started.

Miscellaneous

The SPINE water level service module has been restored.

The application no longer randomly closes unexpectedly when information is added to the Output window.

Closing the application prompts to save when there are unsaved changes. Selecting to Cancel in this instance now cancels the closing of the application.

Editing spatial attributes in the Spatial Attributes window no longer causes the application to become unresponsive.




BASE ManagerTM

Creating a new colour range or colour map file when a group of layers is selected no longer causes the application to close unexpectedly. The displayed histogram shows the data from all relevant sources.

Pressing F1 to read help on an old-style dialog box or window no longer causes the application to close.

UTC time zone corrections are now applied in the correct direction. This affects, for example, setting temporal extent in the Import Points process when the time was specified in the format 2018-03-13T11:16:00+04:00.

When values with units are shown in newer dialog boxes, EPSG-defined units are now displayed as their abbreviation instead of their code. This fixes the use of time units in some contexts; no functional difference is expected.


Catalogues

The new sample BDB Server database catalogues have been updated to all have unique IDs to allow switching between the catalogues.

The new sample BDB Server database catalogues have been updated to define date attributes as dates, instead of generic strings. BDB Server still stores date attributes in the RDBMS as strings.

The sample feature plugin scripts have been updated to only try to set attribute values if the feature has the specified attribute.

The sample feature plugins for the new sample BDB Server database catalogues now populate the identification dates/RECDAT attributes in CCCCMMDD format instead of CCCC-MM-DD.

The SORIND attribute dialog box no longer allows the value to be set to Unknown for data formats that do not support unknown dates, such as BDB Server database objects.

Database Objects

If the provided polygon cannot be used to represent the coverage in a BDB Server database, an informative error message is now provided. This happens, for example, for some automatically generated bounding polygons for vertical-plane-based raster surfaces. An alternate polygon can be specified to upload of the coverage to the database when this error occurs.

When adding a coverage to a database, if there is an associated object.xml file created by BE 5.x, it is used to populate default attribute values. The attribute definitions must match; not all attributes will be mapped over when using a different catalogue or a different feature type in the same catalogue.

The CoverageName BDB Server database system attribute value is now used as the display name for coverages opened from a database.

Layers

When opening a connection to a BDB Server database, the resulting group of layers is now shown as expanded in the Layers window.

BDB Server databases with spaces in their names now show in the Layers window with spaces instead of %20.




Engineering Analysis

Portrayals

Applying a style to BDB Server database objects based on enumeration or list attribute values now results in the objects being displayed based on the specified portrayal.

Miscellaneous

Messages have been updated to more generally refer to coverages and objects instead of surfaces when the item in question was not necessarily a surface.

The Open Connection dialog box now defaults the selection to the first format in the list. If BASE Manager is installed, that is the BDB Server database connection option, which should be used if connecting to a BDB Server database.


Reference Models

Digitizing reference model features on the active reference model no longer causes the application to close when there is no active display layer in the Layers window.

Closing a reference model when a digitizing operation is ongoing no longer causes the application to close.

The Reload Source command has been added to the Project window to allow easily reloading reference models updated outside the current application instance.


BASE Editor 5.0

In this chapter...CARIS BASE EDITOR 5.0.3............................... 28CARIS BASE EDITOR 5.0.2............................... 29CARIS BASE EDITOR 5.0.1............................... 30CARIS BASE EDITOR 5.0.0............................... 31




EnhancementsBASE Editor



Batch Tools

An UpdateVerticalCRS process is now available to change the vertical coordinate reference system metadata of an existing CSAR coverage.


Batch Tools

The UpdateBandValues process now records the sources updated in the lineage.




MaintenanceBASE EditorReference Description

Coverage Tools

The Shift Elevation Bands process could fail with an error message about a band not being found if the shift source did not cover the data being shifted. Now, any data not covered by the shift source is copied with its elevation values unchanged, and the process completes successfully.

CARIS BASE Editor 5.0.1: Enhancement



EnhancementBASE Editor


BASE Manager


CARIS Batch

An UpdateBandValues process has been added to change the values of the Status band for all the nodes that pass a given expression based on the other attribute values.


Import

The Import Points from FAU process now carries over status information from the source FAU data. Specifically, points that are rejected in the source are now imported with a Status of Rejected in a CSAR point cloud.


Python API

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.

CARIS BASE Editor 5.0.0: General Notices



General Notices• A new license string is required for BASE Editor 5.0. Contact CARIS Customer Services for more

information.

• Minor versions of BASE Editor will now upgrade previous versions. For example, installing BASE Editor 5.1.0 will remove 5.0.0.

• BASE Editor 5.x cannot connect to BDB Server 4.3.x or earlier. BE 5.0.0 and later (BE 5.x) is expected to have compatibility with BDB Server 5.x.

• (This notice has been addressed in BE 5.1.0) Changing spatial attributes in the Spatial Attributes window currently causes the application to become unresponsive. Do not use that capability in this version. This will be fixed in BE 5.1.0.

• If you have previously installed a version of the MrSID ECW plugin, it is highly recommended to install the 1.0.4 version or later. This re-enables these formats in newer applications and ensures the application finds the correct version of binary files in all cases. Note that MrSID ECW plugins are always backwards compatible, so installing 1.0.4 will allow you to continue to use these formats in older applications as well. The plugin is available through the CARIS OCS website, and you can contact CARIS Support for any additional information.

• AddToRasterCombine will only work on raster surfaces created by the CombineToRaster process in BE 5.0.0 or later. ServerAddToRasterCombine raster surfaces will also need to be recreated by the ServerCombineToRaster process in 5.0.0 or later.

• As part of the Layers window changes, additional layers are now shown for S-57/S-100 products.

• The bathydbserverloader application has been removed. It is possible to load coverages to the database through the Python API. A sample coverage_loader.py script is now shipped with the application.



EnhancementsBASE EditorReference Description

2D View

A new Pan control is available to shift the view in the Display window in the direction the mouse is dragged.

There are now three possible default controls - Range Selection, Zoom Area, and Pan. Pan is the initial default control, and the last selected default control is used as the initial default control for any new views, and for the next time the application is started.

01702485 It is now possible to draw the points of a point cloud in the 2D view as either circles or squares. This is controlled by the Geometry Type property.

The settings for the active Display window can now be accessed through a single View > Display Window Properties dialog box. This includes the scale, coordinate reference system, measurement reference, and coordinate type settings for the active view.

Note that the coordinate type and measurement reference settings previously were global settings controlled through Tools > Options, but can now be configured independently for each view Display window.

Certain settings for the current Display window can also be configured through the status bar, depending on the active coordinate reference system (CRS). The CRS could be updated by clicking on the status bar in previous releases, but now the coordinate type and measurement reference can also be updated using this method if the active CRS is a projected CRS. Only geographic coordinates and geodetic measurement references are supported for Display windows that have geographic CRS.

Coordinates, measurements and sizes are now always displayed based on the Display Window Properties of the currently active view, including the coordinate reference system, measurement type, and coordinate type. If you have multiple Display windows open, with different display properties, clicking between the Display windows may change • coordinates being displayed in any window (Selection, Coordinates, Registration), • the length and/or area shown in the Selection window,• distances and angles shown in the Coordinates window, • and so on.

3D View

The elevation table lookup file is now used to map feature attribute values to Z-values in the 3D view. With the default support files, this provides Z-values to features such as contour lines and soundings. 2D features without an attribute mapping for the Z-value draw at a height of 0.

A new optional display setting has been added in the 3D view to show a Bounding Polygon layer as a wall, with minimum/maximum heights based on the values in the primary elevation band. This can be used to more clearly show the extents of the coverage.

The new Pan Mode control can be used in the 3D View to change the left mouse button to control navigation rather than select data.

The 3D View Controller Type options are now available through a toolbar button instead of Tools > Options > 3D. This allows quickly switching between the methods of navigating in the 3D View. By default, the middle mouse button affects navigation, and if Pan mode is active the right mouse button can also be used to navigate along different axes.



There is a new Tools > Options setting to switch the behaviour of the middle and right mouse buttons when interacting with the 3D View. This can be particularly useful if your mouse does not have a middle mouse button. Regardless of this setting, any right-click context menus for the Display window will still work with the right mouse button.

The profile lines drawn in the Profiles window can now be drawn in the 3D view by turning on the Profiles layer. The lines display with the same display properties, i.e. colour, in the 3D view as in the Profiles window.

Attributes

01602837, 01600231

The Attributes window can now be used to populate attribute values while creating or editing features.

Batch Tools

Support has been added to the CARIS Batch command line tool to interact with the environment, similar to Tools > Options in the application. Specifically, it is possible to list all settings using --list-options, retrieve the value for a specific option using --get-option, change the value for a specific option using --set-option, and determine if all mandatory options are set using --validate-options. This allows configuring the environment for CARIS Batch without launching the application.

When using the CreateSoundingsFromCoverage process, the bias must now be explicitly set.

An input band can now be specified for ImportPoints from CSAR. This input band must contain elevation information.

This new option can be used to specify which input band is used for gridding a point cloud input, without requiring the primary band name of the output to match the input band. It can also be used to change which band is the primary band of a point cloud.

Catalogue Editor

01700137 Attributes in the profile of a catalogue can now be reordered in Catalogue Editor by clicking on the name and dragging it to a new location.

When a new relationship is added in Catalogue Editor, if there is a corresponding relationship that should logically exist, that relationship is now automatically added. For example, if setting Parent as a "Master" of Child, Child is now automatically also set as a "Slave" of Parent.

When removing an existing relationship in Catalogue Editor, if there is a corresponding relationship that should logically also be removed, that relationship is now automatically removed. For example, if removing Parent from being a "Master" of Child, Catalogue Editor will also remove the "Slave" relationship between Child and Parent.

Catalogue Editor now checks that relationships are defined in both directions, where relevant. For example, Catalogue Editor will report an error if Parent is marked as a "Master" of Child, but Child is not marked as a "Slave" of Parent.

It is now possible to specify 3D line and 3D area feature types in Catalogue Editor, for catalogues that support this type of data, such as BDB Server database catalogues.

Catalogue feature types "Area", "Line", "Point", and "Sounding" have been renamed to better support more general GIS contexts and the addition of the new 3D line and area types, and also to reflect that "Sounding" types are already used more generally as 3D points for drying heights. The new names are "2D Area", "2D Line", "2D Point", and "3D point".




Connections

01501841 It is now possible to connect to Web Feature Services (version 1.0.0 and 1.1.0) to interact with vector features. It is also possible to interact with vector features directly in Oracle Spatial databases, as well as PostgreSQL databases with PostGIS. In addition, connections can be made to ODBC or Oracle databases structured with predefined tables as required by Spatial Fusion Enterprise.

These connections can be established through a single new File > Open Connection command. This shows a dialog box showing customizable names for all previous connections, and allows adding new connection information for any of the above sources that contain features. Information about connections is saved in the folder specified in Tools > Options for the Connections option. The single interface to setup and manage connections to sources that contain features improves consistency.

User credentials (username/password) for these databases and other connections are now stored in the Windows Credentials Manager. By default, the credentials are stored for the single application instance, so closing the application clears any saved usernames and passwords. This can be configured in Tools > Options through the Credential Management option to store passwords longer in the Windows Credentials Manager, such as always remembering the credentials on this computer.

The new database connections now allow adding, editing and deleting features if the user has relevant permissions. Note that some databases should not be edited directly, such as HPD or BDB Server databases, as that would not take advantage of the system management capabilities added at the HPD and BDB Server levels, such as certification, history, and so on.

01701403, 01602600, 01601790, 01503172, 01501841, 00900138

The File > Open URL command now supports connections to HTTP Secure/Secure Socket Layer (HTTPS/SSL) servers. HTTPS/SSL encrypts the connection between server and client to protect both data and Windows credentials from third-party attack.


The EPSG database shipped with the application has been updated from version 8.7 to 9.2; see the EPSG changes list for complete details. Among many other changes and additions, there were changes to the transformation from British National Grid coordinates to ETRS89, and new coordinate reference systems using the Geocentric Datum of Australia 2020.

Support was added for the Lambert azimuthal equal-area (LAEA) (EPSG:3035) projection.

Coordinates

Is it now possible to create 3D lines and areas when digitizing features in formats like GML that support 3D lines and areas. Z-values can be specified in the Coordinates window, and digitizing the next point automatically picks up the Z-value of the previous point, or if the point is snapped to a 3D point, the Z-value of the existing point is used.

When digitizing features on a layer, such as a Profiles layer, it is now possible to manually specify the coordinates in the Coordinates window.

Coverage Tools

A new Smooth TIN command has been added to smooth the temporary in-memory TIN before creating contours. Smoother contours are created from smoothed TINs. The TIN smoothing is not saved and is not restored the next time the TIN is created from the same band. Smoothing cannot be undone without resetting the TIN.




When profiling a single coverage source, and choosing to display fill under the profile line in the Profiles window, it is now possible to configure the colour options to be applied to the fill via a colour map or colour range file. The default colour options are the same as the active display properties of the source being profiled.

When profiling a single source, it is now possible to set the fill under the line to be the same colour as the profile line.

It is now possible to set the Z-axis convention to be considered when applying colours in the Render Raster process. The "down is positive" convention continues to be the default in CARIS Batch, and the active Z-axis convention of the application for BASE Editor and Process Designer.

Data Formats

01401080, 01400869, 01303119, 01302057, 01301736, 01101260

It is now possible to open Google Earth KML files.

It is now possible to open SQLite / SpatiaLite files.

It is now possible to open GeoPackage database files containing vector features.

When opening a Shapefile, the coordinate reference system (CRS) information in an associated PRJ file is now used as the CRS of the data. Note that if an RXL file exists, it is interpreted as an override and its CRS is used instead.

When opening third-party vector format files, the attribution for the features is now better respected. For example, a LAYER attribute in a Shapefile can now be displayed for selected features.

Export

01800345, 01503009, 01300801, 01201518, 01103388, 00701114

To improve interoperability with other applications when exporting features to Shapefile, the application now creates projection (PRJ) files and no longer creates CARIS-specific registration (RXL) files.

01600669 When exporting to Shapefile, enumerated attribute values are now exported with the textual name instead of the numeric ID.

A new filename prefix option has been added when exporting to Shapefile. This prefix is added to all of the created files, allowing easier management of the files that are produced.

When exporting to Shapefile, it is now possible to choose the output coordinate reference system.

It is now possible to export from more vector formats to Shapefile, for example exporting from Shapefile or GML to Shapefile.

It is now possible to export selected vector features to an SQLite / SpatialLite file.

It is now possible to export selected vector features to a new GeoPackage database file.




When exporting a selection of nodes in a coverage to a vector format, the name of the output file is now based on the word "Point" instead of the URI of the coverage. This is consistent with how other components of the coverage are exported, such as the bounding polygon or designated soundings. This affects a number of vector formats, such as GML and Shapefile.

This also affects the acronym for the coverage node data displayed when exporting to formatted ASCII or other custom stylesheet-based exports.

Features

It is now possible to digitize new features or edit existing features in a variety of third-party vector formats, such as Shapefiles, MapInfo files, GML files, SQLite files and GeoPackage files, using many of the same commands that were previously available for HOB files.

It is not yet possible to create new empty files in these formats.

When creating new features on a HOB file, the attribute definition dialog box is now only shown after digitizing the new feature, and only if there are any mandatory attributes that have not been populated and must be populated to create a valid object.

The same applies to the Feature Palette tool - mandatory attributes must now be filled in when features are created.

It is no longer possible to edit the attribute values of a feature object unless the object is in Edit mode.

Files with degenerate geometries, such as zero-length edges or zero-area polygons, can now be opened in the application. This allows using CARIS editing tools to edit and correct, or delete, these features.

Help

Information from the CARIS Geomatics Reference Guide is now included in the application help accessible from the Help Topics command or the F1 key.

The majority of the PDF documentation files have been removed from the installation. The Help > User Guides menu item has also been removed. Help information continues to be available through Help > Help Topics and through the F1 key.

Import

01602202 It is now possible to import FAU files to the CSAR format through both the Import Wizard and the ImportPoints process.

Support has been added to allow using the Object Import Utility (OIU) to import non-English text files. A new option for the character set of the text file has been added to Step 2 of the OIU wizard. The default value is Western (windows-1252), which was the character set used previously in the OIU.

A new UngroupSoundings tag is supported in mapping files to automatically ungroup any grouped soundings and ensure the Z-value for each sounding is properly mapped for it. This applies, for example, when importing features using Import Selected Objects.

INT1 Charts

To support HCRF production, changes have been made to CARIS chart presentation styles - the INT1 catalogue and corresponding PCEConfig portrayal files. These changes were first released in HPD 3.1.6, and are described in detail in the changes list for that product. Contact CARIS customer services for more information.




Comprehensive and extensive improvements have been made to CARIS chart presentation styles - the INT1 catalogue and corresponding PCEConfig portrayal files. These changes were first released in HPD 3.2.0, and are described in detail in the changes list for that product. Contact CARIS customer services for more information. These changes ensure better conformity with the IHO S-4 Ed 4.6.0 Apr 2016 standard.

This includes the addition of Tiled Raster Product portrayal information into the standard portrayal files.

The changes to INT1 charting presentation in this Enhancements section and the Maintenance section that follows are intended to be exhaustive, but the changes are not described as comprehensively as in an HPD changes list. A more comprehensive list of recent changes to INT1 presentation changes, released in BASE Editor 5.0.0 and to be released in HPD 4.0.0, is available upon request from CARIS Customer Services.

01701064, 01700285, 01602550, 01602263, 01503014, 01402667, 01402383, 01400687, 01201714, 01100358, 01100118, 00900746, 00901790, 00802916, 00600233

Spatial attributes for edges can now be used to control the presentation of features. Paper chart presentations support a new conditional symbology procedure (quapos00) specific to the QUAPOS spatial attribute that allows users to specify distinct drawing instructions for QUAPOS in (2,3,4,5,6,7,8,9) and for QUAPOS not in (2,3,4,5,6,7,8,9). For example, edges for COALNE and DEPCNT lines that have QUAPOS spatial attribute values can now be symbolized according to attribute value in the INT1 presentation.

Soundings that have a QUAPOS value are now symbolized accordingly in INT1 presentations.

01402606, 01003576, 00901559

The $size attribute has been added to SOUNDG and $sound objects in the INT1 Charts feature catalogue. When populated, this attribute value is used as a user-override for the size of individual soundings. The $size attribute overrides the default size set by the sounding code and the new size is retained when the dataset is reopened. The $size attribute can include values with decimal places.

01500612, 01301032, 01202659

A new presentation instruction is available to specify how to dynamically fill areas with symbol patterns. This removes the need to annotate areas with a pattern of permanent symbols.

The asymrefs.dic file in the PCEConfig folder includes some examples. AP(pattern_name) refers to patterns saved in the pattern definitions XML file which is referenced from the Presentation ID, e.g. <PatternFile File="%PCEConfig%\annotations\pattern_definitions.xml" />

01602110 Symbols and line styles were added for glaciers and limit lines. The default presentation for ICEARE areas, and COALNE lines were updated in the presentation support files in the PCEConfig folder. PatternFile references were added for INT1 presentations to implement dynamic patterns for these features.

01402314 New symbols were added for INT1 Dumped Individual Mines or Explosives and Prohibited Entry. Presentations were added for MIPARE areas and DMPGRD points for the support files in the PCEConfig folder.

When using a portrayal defined as being of "Paper" type in the portrayal control file, such as INT1, there is a new $ovrid (override) attribute that can be used to hide individual annotated features. The values are 0 - do not hide, or 1 - hide. The attribute is set on annotations and not on the feature itself.




The new $ovrid (override) attribute is added to the source dictionary and profile.

$ovrid is an enumerated attribute that hides individual annotated features on different source usages. The values are 0 - do not hide or 1 - hide. The attribute is set on annotations and not on the feature itself. The $ovrid attribute can be used to hide features on some usages but not on others.

For example, a feature has annotation features associated with it. When $ovrid is set to 1 on an annotation, the feature to which the annotation is related is hidden.

Annotation and raster layer support files have been added for the INT1 presentation.

Layers

01500931, 01102159

This changes list entry has been superseded by additional changes in BE 5.1.0.

The Layers window has been restructured to separate the concepts of sources and display layers. There are now two supported views: Organize layers based on user-customizable layers, and Show layers based on source. The name of the active view is shown in the Layers window tab.

The Organize layers view contains a user-customizable list of layers that controls the draw order of data in the Display window. The layers can be arranged and grouped as needed, with the bottom layer being displayed over upper layers by default. The direction for the order can be switched using the Layer Draw Order setting in Tools > Options. Groups can be created dynamically, from any supported data format, and display properties shared by all layers in the group can be set at the group level.

Coverages with multiple bands are now displayed with a single customizable layer by default, plus a designated sounding layer when appropriate. As needed, existing display layers can be duplicated to create a new display layer referencing the same underlying data.

The Show sources view provides a list of all open data sources and their current display layers. From the source, Add Layer commands can be used to add additional display layers, depending on the type of source. For example, BDB database layers provide options to add recycle bin and offline layers, coverage sources provide a list of the bands present in the coverage as well as the bounding polygon layer, and Shapefiles provide commands to launch the new Filter or Classification tools.


With the introduction of the new modes in the Layers window, it is now possible to remove a layer from the Organize layers mode without actually closing the data source for that layer. Because of this, it may be desired to recover a closed layer. This can be accomplished in the Show sources mode of the Layers window by right-clicking on the data source and choosing an option for the Add Layer command. Some formats have specific commands to add specific types of layers.


A new context menu command, Go to Source, has been added to the Organize mode of the Layers window. This command automatically switches the Layers window to the Source mode and highlights the source of the layer that was selected in Organize mode.

In a future version, it is expected that sources will be organized through projects, and the Source mode of the Layers window will no longer be needed.

01402848 The changes to the Layers window include changes to the default layers we display when opening data. For example, now when opening layers from an AutoCAD DXF file, we preserve the thematic organization of layers as defined in the third-party file.

MicroStation DGN files now always open with a layer for each level defined in the file. This ensures that all levels have a layer even if there is no data in some layers.




01500560 The name of the source is now used in the Layers window as the initial name for the layer for the coverage. This reduces the prevalence of "Band 1" terminology for the first unnamed band in the source.

It is now possible to filter based on attribution for a wide variety of formats, including Shapefiles. This filtering can be done by exact matches or by partial matches, and supports wildcards (underscore _ for a single character and % for any number of characters). The escape character (backslash - \ ) can be entered to use one of the wildcard characters as a regular character in a filter. It also supports searching for attributes that are defined or are not defined, i.e. that are NULL or are not NULL; this is only relevant for non-mandatory attributes. Also, for attributes that support a special UNKNOWN state, it is possible to search for attributes that are UNKNOWN and are NOT UNKNOWN. The NOT operator can be used in queries to find features whose attributes do not match the specified expression.

Filtering is also possible using the unique identifier (ID) of the feature. It is possible to filter based on a single specific ID using "HAS ID" or for any of a list of IDs using "ID IN"

When filtering on attributes that might have multiple definitions (e.g. a buoy colour being red, and green, and blue), it is possible to use "IS" to find attributes that have a specified set of multiple entries, or "CONTAINS" to find attributes that include this entry and may or may not contain other entries as well.

Filters can be saved as .filter files, and existing saved filters can be re-applied. Filters are saved by default in the location specified by the Tools > Options setting for Layer Filters.

01502833 It is now possible to create display layers based on the values of specified attributes in a source vector layer. A new command, Add Layer by Classification, is provided in the right-click context menu of the Layers window to create the display layers and there are a number of controls for how to create the classifications and what the default display settings should be.

The Bounding Polygon layer is now only shown on demand. It can be shown by right-clicking the parent layer of a coverage in Source mode in the Layers window and selecting Add Layer > Bounding Polygon.

The new Remove Layer command found in the pop-up menu of the Layers window removes the currently selected layer. This does not close the data source, but simply removes the layer from the view. A source can only be closed using the Close Source command with the parent layer selected in Source mode in the Layers window.

Note that this is distinct from the Remove Layer command that was previously available for coverages. This was also available in the pop-up menu of the Layers window, but has since been removed and renamed Remove Band in the main menu. In BE 5.1.0, this was further renamed to Delete Band.

The "Create Layers" menu items have been renamed to "Add Layers". This was done to clarify that adding layers does not actually create any new copies of data, but simply creates another way to interact with a subset of the same source data. Similarly, removing layers does not change the data, or close the source - it just removes one way to interact with a subset of an open source.

Options

A Tools > Options setting for Point Cloud Cache size is now available. This can be used to improve visualization of points in the 3D view. Note that care should be taken when adjusting the value; a larger cache requires more RAM, and setting the value too high for your system resources can cause the application to slow.

A new Tools > Options setting for the Memory Cache Size was added to allow control over what portions of coverages are kept in memory.




Portrayals

01001500, 00800187

A new Style property is available in the Properties window for vector formats such as Shapefile, GML and MapInfo to change the portrayal of data in a display layer based on the values of specified attributes.

The display properties and drawing styles for vector formats have been made consistent across the different file formats. This has resulted in a number of changes in each of the previously supported formats, such as AutoCAD DXF, MicroStation DGN, and CARIS DES files. Additional display settings for these vector features can also be set through the Style customization described above. There are known performance implications caused by this consistency improvement.

As well, common properties for vector sources have been added, such as the URI of the source

The display properties for vector data now includes a drop-down list of symbolization styles for point features.

As part of the new, more consistent, vector format handling, the default presentation for polygons in several third-party formats has been adjusted to include 50% fill. This includes formats such as Shapefile and GML. This presentation can still be customized in the Properties window for the selected layer, and can be saved in project files.

It is now possible to specify an attribute to use as the source for symbol angle values. This can be used, for example, to rotate the symbol.

The S-52 Lite and INT1-v2.0 portrayals have been added. These portrayals are most commonly used in chart production and visualizing charts through a website interface. An S-52 Differences portrayal is also added.

Process Designer

The default bias for the CreateSoundingsFromCoverage process has been updated to be shoal-biased, dependent on the z-axis convention. If "up is positive", then a MAX bias is the default in Process Designer, and if "down is positive", then a MIN bias is the default in Process Designer.

Projects

Project files can now be saved to store information about the data and the display settings active in the application. References to data uses relative paths when appropriate, so copying/zipping the project file with its data will produce a usable project with no manual intervention necessary when it is moved to another system.

State information is not currently stored in project files; this includes the active layer, view configuration, and other similar information.

Project file capability replaces session file capability, and session files are no longer supported. Menu items have been changed accordingly. New menu items have been added to only retrieve the data, or only retrieve the Display window extents, from an existing saved project, to allow having multiple project files.

Properties

The Properties window has been updated to a new user interface. A number of new widgets are available as a result, such as sliders for colouring coverages, colour pickers, and shading controls. Also, the properties for the source of the layer are also now available with the layer properties.




When displaying a raster surface band, it is now possible to colour this band based on the data in any of the bands in the coverage. It is also possible to colour based on multiple bands in the coverage, mapping one each to the red, green, and blue colour channels; this is particularly useful for multi-spectral images produced in HIPS. Alpha channels are also supported.

The typical colouring capabilities are still available to:• colour based on a colour map or a colour range file, • reverse the colour map, or • limit the range over which to apply the colour map.

A new capability is to hide the display of any data outside the specified range.

A new tooltip option in the Properties window allows specifying which band values are displayed in the tooltip for the coverage, or group of coverages.

A new gear button in the top-right of the Properties window can be used to customize the properties being shown. Only a subset of the available properties are shown by default.

Python API

Functionality for coverages has been expanded significantly. It is now possible to: • open coverages through the generic caris.open command, in addition to the specific

coverage constructors available before, • determine the type of a coverage using caris.coverage.identify(), • query to retrieve coverage data in specified bands, and/or coverage data in a geographic

area, • add bands to rasters and remove bands from rasters, • modify existing points in a coverage through the write functions, • iterate over the values in a coverage with the caris.coverage.BlockIterator class, • create new coverages based on data in an iterator, • copy coverage data into numpy arrays using read_np_array, and • copy an entire coverage data into a new coverage using create_copy.

Python bindings have been added for general vector maps, such as Shapefiles. These general bindings can also be used for BDB Server database maps. The existing BDB Server Python bindings have been substantially adjusted as a result, and a number of new features were added to the BDB Server bindings, such as being able to specify custom catalogues (pool/profile) for new databases and being able to query online/offline state.

It is now possible to automatically run a Python script when creating or editing features. This can be accomplished by setting the Tools > Options > Feature Plugin value to an appropriate .py file with feature_created and feature_attribute_changed functions.

This could be used to automate the populating of creation-based attributes, which can be as simple or as complicated as required by your business logic. As a simple example, RECDAT attributes could be automatically populated when creating a new feature by the following three-line Python script:

import datetime

def feature_created(newFeature):

newFeature.attributes['RECDAT'] = datetime.datetime.now().strftime("%Y%m%d")

Python (.py) 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.

The Python API has been extended to give access to the application object (caris.ui.Application) to allow using message boxes when using functions in a feature plugin.




The Python API has been extended to give access to a wide variety of vector data formats. A number of classes (e.g. caris.Dataset) and functions have been added.

The Python API can now be used to read from any supported raster format. It can now also be used to write GeoTIFF rasters.

It is now possible to undo changes made to a dataset that have not yet been saved, through the use of a new rollback function.

Selection

It is now possible to create sub-selections of multiple items from part of the existing selection. As needed, processes will be added and/or updated to work on these sub-selections. Existing processes will continue to work as before, operating on the entire selection and/or on the superselection.

The Select > By Filter command now works on more formats, such as Shapefile and GML.

Feature type information is now shown in the Selection grid for all supported vector formats.

Subset Editor

It is now possible to use the Colour By property to colour points in Subset Editor based on data in a specified colour band. If some of the source point clouds do not have a colour band with the same name, they are displayed with a default grey colour.

In Subset Editor, it is now possible to specify an expression to apply to the primary elevation band values in the point clouds through a new property in the Edit Sources layer. This can be used to quickly isolate all points that meet a specified depth threshold and designate or reject them, as appropriate.

When defining a subset area for Subset Editor, it is now possible to choose an existing polygon in the current Snap/Grab target. This will automatically create a subset area around the polygon, and limits the points loaded in Subset Editor to only the points inside the polygon. A property on the Edit Sources layer allows turning off the geometry filter, or switching the filter to exclude all points inside of the polygon. If the automatically created subset box is not appropriate, it is possible to resize, rotate, and/or move the box and still preserve the geometry filter. Explicitly defining a new subset area clears the geometry filter.

This new capability can be used to isolate points within an area to reject, designate, or otherwise flag all points within that area. In conjunction with the filter expression, it can be used to isolate points within an area that pass a depth filter to reject, designate, or otherwise flag a subset of the points within the initial subset within the area.

Subset Editor always shows only the primary elevation band data of point clouds. This display now includes the primary elevation data for all point clouds open and turned on in the Layers window, regardless of which band is set as the active Z attribute.

User Interface

The Escape button no longer has any effect when the Zoom Area control is the active control. There are now three possible default controls - Range Selection, Zoom Area, and Pan, and escape has no impact on any of the three.

Pan is the initial default control, and the last selected default control is used as the initial default control for any new views, and for the next time the application is started.

01702022 Copy Position is now available in the right-click context menu of 2D views, such as the Display window. This can be used to quickly save the position of a feature of interest. It is stored in the clipboard of the system, and can then be pasted into another document, such as a Notepad window.




Context menus in the Layers window have been changed significantly, generally by removing a subset of the previous content, retaining only a subset of the most common commands. This has been done to prioritize the items that are context specific and prepare to support a broader set of workflows in the application.

The Properties and Attributes windows are now docked at the right side of the Display window by default.


As there are now two different modes for the Layers and Properties windows, the title of those windows now changes dynamically to describe the current mode.

As there are now two different modes for the Properties window, the title of this window now changes dynamically to describe the current mode.

Validation

There is a new validation check option for Duplicate Objects to choose whether to test for duplicate sounding depths.

A new validation check is available for Prohibited Objects to check whether coordinates are too close. This check is turned off by default, and can be turned on by selecting Options in the Validation Checks dialog box when the Prohibited Objects item is selected.

Tests 6030 and 6031 have been added to the Invalid Objects validation test. These tests check the POSACC attributes of spatial objects against the POSACC values of M_ACCY or M_QUAL meta objects.

When writing customized QC tests, it is now possible to use CheckExternalFileExists to validate whether an external file exists.

When writing customized QC tests, it is now possible to use CheckExternalFileIsEmpty to check that when attributes point to a file, the file is not empty.

When writing customized QC tests, it is now possible to use GeometryCovers to check whether the test object covers features described by the filter. This is the opposite logic as the GeometryIsCoveredBy test.

When writing customized QC tests, it is now possible to use GeometryIntersects to check whether the test object intersects features described by the filter. This is the equivalent of Not GeometryIsDisjoint.

When writing customized QC tests, it is now possible to use an OppositeDirection tag, in addition to the pre-existing SameDirection tag, to identify line features that are coincident on both sides of an area.

The GeometryCrosses test now allows sounding groups to be specified as either the test object or the filter object.




BASE ManagerReference Description

Catalogue Editor

Catalogue Editor has been updated to do more error checking for BDB Server catalogues.

Catalogues

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.

When adding a coverage to a BDB Server database, it is now possible to create any type of vector feature (2D or 3D points, lines or areas) for the spatial geometry of the coverage. It is possible to have the software automatically generate the vector feature of the specified type, or to manually digitize the vector feature as part of adding the coverage data.

As part of generalizing the BDB Server database catalogue support, the Combine Surfaces dialog box now allows selecting the type of feature to be created in the database when creating a new combined coverage.



The Database > Import Selected Objects command has been updated to work with the more general catalogues supported for BDB Server databases. No mapping capability is provided, so it is necessary for the catalogues of the source to match the catalogue of the database, at least for the feature types being imported.

The sample catalogues and feature plugins shipped with BDB Server are now also shipped with BASE Manager in the install directory, which by default is C:\Program Files\CARIS\BASE Editor\5.0\modules\BASE Manager\support\Catalogues.

The Hydrographic Office catalogues have 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.

An additional version of the BDB Server Hydrographic Office catalogue is also deployed. This version has six letter acronyms so it can be used with HOB files. This catalogue has also been updated to add an "idmstr" (Master ID) attribute which serves the same purpose as the legacy idprnt attribute, but is no longer restricted to just integer data.

To access any of these catalogues, the Tools > Options > Catalogue Control setting can be updated to point to the catalogue control file in the same folder, C:\Program Files\CARIS\BASE Editor\5.0\modules\BASE Manager\support\Catalogues.

A sample HydrographicOffice_to_HOB rule file is now provided to map features in a BDB Server database to a HOB file when using the File > Import Selected Objects command. This allows features using the Hydrographic Office catalogue, with long acronym names, to be mapped to a corresponding catalogue with six letter acronyms, such as the ones used in HOB files.

The existing mapping file BDBServer2S57 was renamed to HydrographicOffice_to_S57 to reflect that BDB Server does not require a specific catalogue any more, and that the Hydrographic Office BDB Server catalogue can be used to maintain existing workflows.

Connections

The single connection dialog box launched from File > Open Connection can also be used to connect to BDB Server databases, which contain features that may or may not be linked to coverages. This replaces the previous BDB Server-specific dialog box and menu item.

Like other connections, when creating the first connection to a BDB Server database, you now configure what layers and groups to show in the Layers window whenever opening the connection. Offline and recycle bin layers are suggested by default and there is an option to automatically add a layer per feature type according to the catalogue in the database to which your connecting. Additionally, individual layers can be added according to a user-specified filter expression. As with other connections, it is possible to rename the layers and otherwise configure how these layers will be displayed each time the connection is opened.

Coverage Tools

The Set Coverage command, formerly known as Replace Bathymetry, now allows either keeping the existing geometry or automatically generating a new geometry for the coverage.

Data Formats

01702630, 01500742

Attachments to a database object are now treated as part of the feature, with the filename of the attachments now shown in the Selection window under the AttachedFiles field when the database object is selected.




Database Features

As part of opening the object data model for BDB Server databases, it is now possible to create arbitrarily complicated survey polygon features. This allows more flexibility when associating coverage data to linked "master" features that contain more general metadata. Of course, with the open object data model, organizations can define the database catalogue to suit any number of other use cases.

The BDB Server catalogue now allows specifying what feature types can be masters of other feature types. This allows continuing to use "survey" objects as masters of "surfac" objects, but also allows any other types to be defined with appropriate relationships.

Because only automatic relationship definition is supported, the object type is used to define the direction of a newly created relationship. This limits the types of relationships that can be used. For example, in a BDB Server database catalogue, it is not possible to have an ObjectA be a slave of another ObjectA.

The typical feature editing commands can now be used to digitize or edit features on a BDB Server database layer. As each layer only contains one feature type, the workflow is simple. There are no longer BASE Manager-specific commands for creating "surfac" or "survey" objects as the generic editing commands are sufficient.

Attachments can now be added to any vector feature added to a BDB Server database. Note that you will be prompted to save if you attempt to add attachments to an unsaved feature.

As OBJNAM is no longer a required system parameter, and is not present in general, it is no longer shown for master features in the Edit Relationship dialog box. The geometry type is now shown, making the display of masters and slaves more consistent.

Export

It is now possible to export selected BDB Server database objects to more vector formats such as KML, Shapefile, Geopackage and SQLite.

Layers

01501530, 01300639

As part of the move to a new filtering mechanism, it is now possible to create filtered layers from existing BDB Server database layers, in addition to creating filters from the database itself.

01601226 It is now possible to create filters based on whether an attribute has a specified value (attribute = value), does not have a specified value (attribute != value), or if the specified attribute is unset (attribute IS NULL). A combination of these expression forms can be used to find all features where the attribute value either does/does not match the specified critieria, or the specified attribute is unset.

01601226 As BDB Server database layers now use the same filtering as other vector types, there is new support for filtering based on an attribute being set (not NULL) or unset (NULL).

01301178 BDB Server filters/queries are now implemented as a set of independently saved .filter files. Because of this, it is now possible to use wildcards when searching for a filter with a given name in the "Open" dialog box.

01301178, 01300856

Like all filters, the BDB Server query/filter information is now readily available, and changeable, in the properties for the layer.

With the updated filter/query system for BDB Server databases, the filter layers can now always be renamed in the Layers window.




The BDB Server-specific queries functionality has been removed. The generic filter capabilities introduced for most vector formats can also be used for BDB Server database filters. The filters can include exact matches based on the IS keyword, and partial matches based on the CONTAINS keyword.

Databases are now opened with the user-defined set of layers that is set up when the database connection is created in the Open Connection command. Additional layers can be added at any time based on a user-specified filter. The new database filter layers support feature creation and editing directly in the database for any feature object type, using the same tools as other vector formats such as Shapefile and GML. Coverage data can be mapped to any of those feature objects on the database and attributes defined as needed. These database features can have 3D coordinates, and when they do they display correctly in the 3D View as well.

Portrayals

It is now possible to store a default portrayal to be used for a BDB Server database in the Administration Tools. 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.

Python API

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.

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 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.

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.

Among the other extensive changes to the BDB Server Python API, it is now possible to specify a custom catalogue (pool/profile) for a BDB Server database through the Python API.

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

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.

Support Files

The dqueries.dbq file is no longer included with the application installation as it is no longer used.




Compose Module



Batch Tools

01301457 Two new processes are now available for modifying S-57 files: • ReassignS57FOIDs assigns new feature object identifiers to an S-57 file. • ModifyS57Header changes header information on an S-57 file.

Validation

New validation QC Tests have been added for S-58 Critical Errors, S-58 Errors, and S-58 Warnings. These have also been added to the Validation toolbar.

New validation QC Tests have been added for S-58 Features and Attributes.

New validation QC Tests have been added for S-58 Geometry.

A set of validation checks has been added for IENC 2.4.

GeneralENCMetadataTests, GeneralS57FeatureTests, and GeneralS57SpatialRelationsTests have been added.


Catalogues

One of the sample catalogues provided with the BASE Manager module and the BDB Server application is an Engineering Analysis catalogue. This, along with an associated rules file also provided with the application, can be used to demonstrate how more data can now be stored in BDB Server databases.

For example, this could be used to import a shoal (SHL) file created by the Shoal Detection command into a feature layer with a BDB Server database catalogue. This can be done using the File > Import > Import Selected Objects command with the Engineering Analysis for BDB Server catalogue and the feature mapping rules file Shoals to BDB Server (Engineering Analysis).

If there was a BDB Server database using the Engineering Analysis for BDB Server catalogue, this vector data could then be imported into the database using the Database > Import Selected Objects command. Set Coverage could then be used to associate the corresponding coverage data with the shoal box and/or shoal area. With Tools > Options set to an appropriate feature plugin, additional attribution from the coverage can be automatically added to the associated shoal box or area vector feature as part of the upload of the coverage to the database.

Model

A new command, Model > Create Template from Selection, can be used to create a new reference model from a selection, where each polygon in the selection is imported as a reference model surface in the template. If the selected polygons have Z-values, those are used to populate the reference model surface depths, using the first three non-collinear points. The specified attribute mapping from the source features is then applied, which overrides any depths if a mapping is provided for the reference model surface Depth attribute.



Maintenance

BASE Editor


2D View

01601440, 01402603

The performance of drawing textual features, such as soundings, has been improved.

01702485 The performance of drawing point clouds in the 2D view has been improved.

01601115 The performance of drawing raster surfaces gridded with respect to other planes in the 2D view has been improved.

01503483 The performance of drawing BSB files has been improved

01502591, 01502204

Geographic grids (set from Tools > Options) are displayed at their correct position in the Display window.

01800082 Geographic grids now display properly aligned, consistent with the display of geographic data.

01502176 The symbols for point features were not displaying at the correct angle if the definition of the feature in the dictionary file included an orientation setting. Symbols now display at the correct angle.

01700625 When drawing complex line patterns in a feature layer, a symbol could randomly appear at the end of the line for some symbolization scales. This has been resolved.

01601828 Features are no longer hidden if the view scale is the same as the SCAMIN value. The viewing scale must be smaller than SCAMIN for features to be no longer displayed.

Changing the size of the Display window while the Swipe command was enabled was causing the data to stop displaying in one half of the view. The size of the Display window can now be changed while Swipe is enabled.

The view was not being updated if a new layer was selected for display while Swipe was enabled. This has been fixed and the view updates correctly.

When creating a new Display window using the Window > New Window menu item, the initial extents of the project, if set, will now be used as the extents for the Display window.

It is no longer possible to specify 0 as the display scale for a Display window. An attempt to do this will automatically change to a scale of 1:1.

When drawing points in a feature layer defined based on an XSLT presentation in the portrayal control file, scaleFactor and rotationCRS are now properly applied.

Arcs are no longer drawn with a dashed segment extending beyond the end of the arc.

Some complex line patterns would not draw over the entire feature at some display scales. This has been resolved.

Using Shift+F5 now refreshes the symbology for all open feature layers, such as HOB and 000. This can be used to quickly apply changes to presentation, symbolization, and system files referenced by Tools > Options.

3D View

01002131 Changing a display property for a vector layer in 3D now only affects the one vector layer and not all layers.

01700993, 01702705

Information about all visible coverages is now shown in the tooltip in the 3D view.



The 3D View now displays features from HOB and 000 based on the Z-values of the attributes specified in the elevation lookup table. Other features with no elevation lookup are displayed at 0. The 3D view display properties used to drape vector data or to specify a Z offset are no longer available.

Turning on certain background images in the 3D View caused the application to close. This has been fixed.

Right-clicking in the 3D View when the Measure Distance and Angle tool is active still shows the Measure Distance control context menu, but the view is now rotated appropriately when the mouse is moved.

A number of fixes have been made to improve how vector data displays in the 3D view.

Attributes

01503509 Loading of features from S-57 datasets now ignores leading and trailing whitespace characters for attribute values of type integer.

Batch Tools

The process API version has been changed. This means that some CARIS Batch command lines created in previous versions may no longer work. These changes are limited, and are also described in this changes list.

Like in BASE Editor, regional settings are now overridden when using CARIS Batch. This allows using the same files (e.g. CRFX files) in both applications, and a consistent way to enter numbers for both.

The performance of the Export Features to Shapefile process has been improved.

The --output-vertical-crs option has been added to the Combine to Raster and Join Points processes.

The Extract Coverage process now respects the specified bounding polygon option.

When using the recurse option to process all files matching a string with wildcards (e.g. *.csar) in a folder structure, a more informative error is now shown if the root folder does not exist.

The order of feature catalogues listed in CARIS Batch has changed due to a change in the ID for the S-101 draft feature catalogue. No functional change is expected.

The legacy DescribeRasterProduct process has been removed.

The rasterproducttemplate.xml file is no longer installed with the application as it is no longer used.

The short key for the input format option in ImportPoints has been changed to a capital "I" (i).

The intersection code used by ClipFeatures has been adjusted to better handle more complex intersections that could fail with error messages and/or create artifacts along the clipping boundary.

Catalogue Editor

When editing an empty catalogue in Catalogue Editor, the first attribute is now assigned an ID of 1 instead of 0.

The Close button icon in Catalogue Editor has been fixed; it is now the same red Close button icon used in other applications.




Catalogues

The Bathy DataBASE catalogue has been updated to remove the legacy BDB Server catalogue objects (e.g. surfac, survey) and attributes as there is now no expectation that any given BDB Server catalogue will have any specific objects or attributes.

It is recommended that you have a Catalogue Control file that lists all of your BDB Server database catalogues and set Catalogue Control in Tools > Options to append these catalogues to the standard catalogues. This will allow using the BDB Server database catalogue for feature layers as well. Alternatively, features can now be digitized directly on BDB Server database layers, so there is no requirement to use feature layers for intermediate steps.

The ENC 3.1 catalogue has been updated for compliance with S-58 edition 6.0. This included explicitly adding all the PermittedValues to the enc31Profile.xml file to appropriately filter the list of available values. It also included removing previously listed inappropriate values such as 3 for CATCBL and 4 for CONDTN, removing the list of PermittedValues for BUISHP, and making MARSYS and ORIENT conditional for M_NSYS.

DEPARE lines were removed from the S-57 ENC 3.1 catalogue (enc31Profile.xml). The supporting DEPARE line symbolization information has been removed from presentation support files.

A few non-functional typos were fixed in S5731Pool.xml and shoalspool.xml.


01502595 The coordinate reference system (CRS) support file boundcrs.dat has been updated to use the OS36 transformation when transforming data with CRS EPSG:4277.

01602522 Changing the coordinate reference system (CRS) of the view was sometimes causing the patterns for line features to display incorrectly. Line patterns now display correctly after changing the CRS of the view.

01600767 Images of type RDNap GeoTIFF that use the CT_Stereographic coordinate transformation now display correctly with the RDNapTrans 2008 datum transformation.

It is now possible to set the coordinate reference system (CRS) for datasets even when they are not local files, such as Oracle databases. The CRS registration file (RXL) is saved in the Tools > Options folder for Connections.

The name for compound coordinate reference systems (CRS) is now shown as "horizontal CRS name + vertical CRS name"

Features are now displayed at the correct scale when the coordinate reference system (CRS) of the view is set to the CRS of an open HCRF.

Filtering vector features based on area now works when the coordinate reference system (CRS) of the Display window is based on an engineering or chart datum, in addition to geographic or projected CRS.

Line masking has been updated to work when the coordinate reference system (CRS) of the display is different than the CRS of the data.

When reading units from EPSG, units such as metres per second are now properly interpreted as speed units.

The units table was updated with new area units, specifically square centimetres and square millimetres are now available.




ED50 has been removed from the list of available datums and the coordinate reference system (CRS) support files have been updated to use the EPSG:1311 transformation when handling the ED50 geographic CRS EPSG:4230 and the UTM - ED50 projected CRS, specifically EPSG:23030 to EPSG:23032.

Data stored in a coordinate reference system (CRS) that spans the dateline is no longer drawn incorrectly when drawn in another CRS. This affected, for example, data stored in World Mercator CM 180 and displayed in WGS 84.

Coordinate reference system support has been expanded for third-party formats to support more datums, with special handling to map Militar_Geographische_Institut as Militar_Geographische_Institute, World_Geodetic_System_1984 as WGS_1984, WGS_72_Transit_Broadcast_Ephemeris as WGS_1972_Transit_Broadcast_Ephemeris, World_Geodetic_System_1972 as WGS_1972 and European_Terrestrial_Reference_System_89 as European_Reference_System_1989.

Coordinates

The z-values for selected features in a Shapefile now show as regular numbers (e.g. 10) instead of scientific notation (e.g. 1.000000000e+001).

Pressing the Tab key when the Coordinates window is active now unselects the previous rows when switching to another populated row.

No-data values used to be displayed the Z value in the Coordinates window when the Holidays band was populated outside the data extent and this data was selected. The Coordinates window no longer shows no-data values for the Z-value.

Coverage Tools

01702009 The Combine to Raster process could fail with geometry-related error messages when using bounding polygons to control deconfliction. The resolution of the geometry operations has been made more precise to resolve these issues.

The Combine to Raster and Join Points processes have been updated. Now, the rule files in combine must define the z-axis convention of the rule, when appropriate. Also, any error messages about not being able to use a rule will specify the name of the rule, not the description.

The state of the "Override ambiguity check" option is now preserved when adding new deconfliction rules in the Combine Surfaces dialog box.

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.

The Filter Coverage dialog box auto-completion functionality no longer prevents typing a band name containing spaces, such as "Depth and Holidays".

The Filter Coverage dialog box auto-completion now works better when brackets - e.g. () - are typed into the expression box.

The auto-completion for expressions used in the Filter Coverage dialog box has been enhanced to support using this functionality in the Filter dialog box used for vector features.

Edits made to a TIN created from a HOB layer were not being reapplied when the file was reopened and the TIN created again from the same layer. A .tls file is now stored, so any user edits to the TIN are now reapplied when the TIN is created again.

Creating a TIN now displays a dialog box to select the band containing the values to be used.




It was not possible to edit the data in a coverage after a TIN had been created for the coverage. This has been corrected.

The default maximum number of points in a TIN has been increased to 10 million vertices. Now that win32 systems are no longer supported and the system specifications have been updated, much larger TINs can be used.

The command to edit the selected profile has been removed. The standard Edit > Feature command can be used to edit profiles.

When creating a variable resolution surface, the horizontal units of the output coordinate reference system (CRS) are now set to the default horizontal units of that CRS. This improves the results and ensures correct extents when the Tools > Options > Ground Units are set to non-standard units.

The extents of variable resolution surfaces (VR) reported in exported metadata now precisely match the extents specified when the VR was created.

When running the Shift Elevation Bands process based on tide values, it is now possible to specify the Time band for both Date and Time information. Some related error messages were updated to be more similar to other existing messages.

The Vertical Shift dialog box now respects the specified z-axis convention.

The New Line command can now be used to digitize a new profile on an existing Profiles layer.

The specific commands to remove a selected bounding polygon, profile, and TIN Editor feature have been removed. The general Edit > Delete commands can now be used to remove these features.

The commands to create and edit bounding polygons have been renamed.

The Render Raster process no longer creates a Designated band when the source has a Designated band.

When applying colour maps to a specific range of elevation values in the Render Raster process, the colour maps were flipped compared to applying the colour maps to the whole range of data. Now, the colour maps are applied consistently whether a range is specified or not.

When using the Extract Coverage process to do an exclusive extraction, there is now an improved error message if the entire coverage is within the polygon.

JPG files with CMYK colouring are no longer supported. These used to be created erroneously in CARIS processes. Using a JPG input file marked as having CMYK colouring in a process like ClipRaster will now result in a file with RGB colouring being produced.

The application no longer closes when creating a raster surface with a very small tile size.

The Warp Points process has been updated to have better performance and to update the progress bar as it is run.

The Warp Points process now preserves designated soundings.

The Create Source Areas command has been removed, as it has been replaced by the Vectorize Raster process. As indicated in the BE 4.3.0 changes list, combined coverages created prior to BE 4.2.0 may not have the band definition information necessary to use the new process.

The old Remove Layer command for coverages, renamed to Remove Band, now displays a dialog box that is used to select the band to be removed from the source.




When relevant, warning messages given by the Finalize Raster process are now more explicit about which source could not be used to apply designated soundings.

The Finalize Raster process now considers all sources for designated soundings to apply, even when some of the sources cannot be used as a source of designated soundings. Warning messages are displayed which clearly indicate each source that could not be applied, and when none of the sources could be applied.

The SPINE module has been removed. An alternate way to perform vertical shifts based on the SPINE water level service is expected to be provided.

An issue that could cause the creation of a CSAR point cloud to hang has been fixed.

The error message displayed when a coverage cannot be edited because it is open in another application has been updated.

The Remove Collinear Points option has been removed from the Contour Raster process. All exactly collinear points, in the coordinate reference system of the data, are always removed.

The Contouring command in the application now automatically removes all exactly collinear points, in the coordinate reference system of the data.

The Coverages > Difference command is now enabled if at least one coverage is open in the application. This allows differencing two attribute bands within a single coverage.

Export

The schema used when writing out GML has been updated. That includes changing the maxOccurs from unbounded to 1. We also now write out the feature ID (fid).

Exporting a raster to USGS DEM did not produce a usable output if the coordinate reference system (CRS) of the raster had a NAD 27 ellipsoid, as there is not a single valid transformation from NAD 27 to WGS 84. CRS with a NAD 27 ellipsoid are no longer supported for USGS DEM export. CRS with NAD 83, WGS 72 and WGS 84 ellipsoids remain supported for USGS DEM export.

Exporting a raster to ESRI ASCII now produces slightly different results when the decimal precision is set to 0. Bands with floating-point values are now written to the ESRI ASCII file with the first value written with a single decimal place (.0) and all other values with no decimal places. This results in the band in the ESRI ASCII file being opened as a floating-point value band instead of an integer band.

Exporting a raster to the GeoTIFF format now supports JPEG compression if the input band is an RGB or RGBA colour band. Otherwise, an informative error message is now displayed that JPEG compression cannot be used.

Export > Points now always includes the primary elevation band in the output point cloud.

When exporting to Shapefile, the application and CARIS Batch now use the same conventions. This includes using the same naming conventions, such as (P) suffixes instead of _Points suffixes.

01700072 Exporting selected features to Shapefile could miss features if multiple acronyms in the source feature catalogue had the same letters but different capitalizations, and the same primitive type. This has been fixed.

01602636 The Export to HOB command now better supports Unicode characters for file and folder names.

The map scale set in the display properties is now used when exporting the view to a new file.




Numeric values in coordinate reference systems in Well-Known Text files are now written with more precision, when relevant.

The order of alignment coordinates for coordinate reference systems (CRS) written to Well-Known Text files has been changed to x1, y1, x2, y2 for each line. This only applies for chart alignment-based CRS.

The Export to WKT process now writes "Point Z" as the type for 3D points.

Features

01700710, 01200240, 00902970

When creating filter layers based on comparisons to fixed values, the precision used is now 1e-7, instead of the precisions specified in Tools > Options for the various types of measurements.

01700592, 01700542, 01601716, 01601444, 01601093, 01600408, 01600371

Parallel lines and corridors would be generated at the wrong offset from the baseline. This has been fixed.

01700515 The Line from Image command, which creates a line based on pixels in a raster image, no longer automatically performs line smoothing. If necessary, smoothing can be applied after the line is created.

01601020 Clipping vector features, such as clipping as part of Import Selected Objects, has been made more reliable, particularly when the clipping area is near the dateline. If clipping fails, more information about the problematic features is now reported.

01500026 The Shift key can now be used more consistently when snapping to divide an existing edge, including when the Display window coordinate reference system (CRS) is different from the data CRS.

01502812, 01502169

An error is no longer displayed after cancelling a new feature (using the ESC key) that was initiated from the Feature Palette.

01502176 Sector light arms drawn in a Display window with a UTM projection now respect the angles as entered in the Coordinates window.

01600691, 01600649, 01600614

Entering and exiting Edit mode multiple times after editing an attribute value no longer slows down the application.

01600808 Adding a new feature via the Feature Palette now cancels any ongoing digitizing operation that is not correctly ended.

01601878 The performance of applying mapping files has been improved significantly. This can affect Import Selected Objects, certain Validation checks, and Change Selection.

01701011 The application no longer closes unexpectedly when saving a new feature that was created via the Use geometry of selection command in the Feature Palette.

01502907 The application no longer closes when CRFX filter files include empty names as part of a rule file.

01600230 Spatial attributes are now retained properly in a feature after its geometry has been modified.

01800053 Area features that include edges of type loxodrome are now better handled by the Invalid geometry test. Valid area features are no longer reported as incorrect and users will see better messages when inconsistencies are detected.




Improved error handling has been added when attempting to edit vector features in a read-only file.

Edit Line > Click Within Edges now works even if the grabbed feature is on a different layer than the feature that is being edited.

The "Grab" functionality now also works when the feature has 3D coordinates.

Using a B-spline line smoothing algorithm on a closed line or polygon now smooths the entire feature, including the area near the start/end points.

The Edit > Features > Cut commands are now disabled if there is no superselection.

Master/slave relationships are no longer set implicitly when creating features. The relationships must be defined explicitly by using a selection to associate features with the Create > Master/Slave Relationships command, or through the Python API.

Any points adjusted by the Smooth Features by Direction Bias process were adjusted based on the bias provided. In some instances, an inappropriate sampling of points was adjusted, producing a result that was less smooth, for example, with ripples along an edge that was fairly straight. The algorithm has been adjusted to initially move all points by a fraction of the tolerance, in accordance with the bias, before applying smoothing. This changes all results by negligible amounts, but generally produces smoother results with fewer ripples, while continuing to ensure that the bias is respected.

The inappropriate sampling could also result in relatively large complicated areas of the contour being simplified to a simple line, and now the form of the contour is better preserved - depending on the parameters selected.

An improved error message is now displayed when creating features from a coverage, but no destination has been specified.

Calculations of intersections between two vector features is now done more accurately. This resolves cases that used to result in error messages describing topological inconsistencies.

The uncommon case of a geometry operation attempting to determine if a point was on a collapsed ring has been fixed.

The Edit > Features > Intersect command used to fail with an error if sticky mode was on and you had lines and areas selected, depending on the order of the features in the selection. This has been fixed.

Copying text from a VPF no longer causes the application to become unresponsive when there are duplicate coordinates defining the position.

The Edit > Edges > Filter command now skips filtering certain features and gives an informative message in the Output window if the resulting geometries would be invalid. This can happen when a large tolerance is specified.

The term "master/slave relationships" is now used more consistently, replacing other wording such as master/slave relations.

When using the Change Selection command to define an attribute that holds associations to other files, such as PICREP or TXTDSC/NTXTDS, it is now possible to access a file from or save a file to the ExternalFiles folder, as defined in Tools > Options.

It is no longer possible to save changes to sources while there is an active digitize or edit operation. The edit must be ended or cancelled before the changes can be saved.

The Create Features from Selection dialog box now remembers the last selected Destination Layer.




Deleted objects in feature layers are now skipped by more processes, but no substantial functional changes are expected.

Edit > Change Selection > Basic > Change Attribute Value has been updated to do the same processing and error reporting as the Change Feature Attribute process. Some messages will be displayed differently, but no functional differences are expected.

The feature palette has been updated; no functional changes are expected.

Help

Pressing the F1 button to see help content when exporting a raster surface to HTF could cause the application to close. This now properly shows the help documentation.

Import

01502547 A new option for encoding non-English language character sets is added to Step 2 of the Object Import Utility (OIU) wizard for importing text files. This addition improves support for non-English text files. A character set is selected from a list and the default is Western (windows-1252) which was the character set used previously in the OIU.

Warning messages are now given by the Object Import Utility when objects collapsed during transformation and could not be included in the output layer.

The Import Selected Objects function now properly imports spatial attributes when the option is selected.

The Import Selected Objects function no longer fails when mapping numeric attribute values that are greater than 999.

Import Selected Objects was updated to ensure messages are displayed as expected when clipping was performed as part of the import process.

The Import Selected Objects command can now be used to import selected 2D or 3D data, such as 3D lines in a Shapefile, to a HOB file as the corresponding 2D data.

The Import Points process with CSAR input format now skips any invalid sources, such as raster images, and continues to process other sources. Appropriate warning messages are now displayed for each source that is skipped, and if no data was found to be imported.

The Import Points process with CSAR as the input format now works with multiple input files even when they have different band names and/or different internal orders of bands. All data in all sources with the same band name is now be properly considered when creating the band in the new CSAR file.

Importing points to CSAR from ASCII now does additional error checking for date-time values. If the format information file specified that there are time values in a given field, but the values are not valid times, an error message is now displayed.

The Import Points process has been updated to use threading to improve the performance of importing points to CSAR.

Improvements have been made to the Import Points from ASCII process that affect values with very high precision. Typical users of the process will see no functional difference.

Error handling when importing to CSAR has been improved when the output primary band name is the same as a specified computed band.




Updates have been made to the feature mapping "IH f2o to ENC 3.1 Conversion" file (ih_f2o.xml), which is used in the Import Selected Objects command to import features from a GIS file and convert them to S-57 objects. Now, unsurveyed coastlines and approximate depth contours are imported with their spatial attributes already assigned. Specifically: • when CLIK objects are imported as COALNE, QUAPOS is set to 2 (unsurveyed), • when COIK objects are imported as DEPCNT, QUAPOS is set to 4 (approximate), and• when COTPIK objects are imported as LNDELV, QUAPOS is set to 4 (approximate).

In addition, DLFGG1 objects are now mapped to OBSTRN as "Foul ground" instead of "Foul area", i.e. with a CATOBS attribute value of 7 instead of 6.

INT1 Charts

01602963 Edges that were set as masked were being displayed when the presentation was set to INT1. The edges are now masked appropriately.

01601483 Default INT1 and INT1 v2.0 presentations have been updated to match IHO S-4 specifications for unsurveyed areas. This includes: • the addition of two new line patterns, black and magenta (DLDAUNS4 and

NPDLDAUNS4) in ih_master.txt, and • the default presentation for UNSARE area has been changed in the asymrefs.dic

support file in the PCEConfig folder. There is also a disabled entry in the same file to display the UNSARE with the horizontal cyan bands pattern instead.

01700507, 01700430

The ih_master.txt and symbol files (ih_symbol.dat and ih_symbol.bin) have been updated to include the new IHO logo for INT charts.

The following feature codes are added to ih_master.txt: • CRESTIHONEW• CRESTIHOFIN• CRESTIHO_1

The following new symbols are added to ih_symbol.dat and ih_symbol.bin: • CRESTIHOFIN• CRESTIHO_1

The feature class $ntare has been added to the INT1 Charts catalogue for borders that include neatline areas.

SymbolOrientation presentation instructions are now defined for INT1 presentations.

The Transparent Colour attributes ($clmsk and $clmst) for paper charts (INT1 Charts catalogue) are now renamed to Filter Colour to be consistent with other changes to image properties.

When drawing a feature layer that has overlapping features of the same type, with the same $prior value, the draw order of the features is now determined by the FOID, with the newest feature drawn on top.

The maximum value for the display priority has been increased from 31 to 8 million (8,388,607) for the INT1 portrayal.

Layers

The default names shown in the Layers window for CARIS DES files open in the application has been changed to Name : Header_Number.

Removing a coverage from a group when the coverage has an associated TIN no longer causes the application to fail.

It is now possible to interact with layers in the Layers window using the arrow keys, and the plus (+) and minus (-) keys on the keyboard.




The names shown for temporary raster surfaces now show with spaces instead of %20.

The term "layer" is being used for display layers available in the Layers window. References to attribute bands in several dialog boxes have been changed to refer to "bands".

The term "attribute band" is now being used more consistently in the application.

Offline data in a BDB Server database is now available through a layer. Online/offline is no longer available as a queryable attribute.

When creating layers or selecting features based on attribute values, the logic to parse complex expressions has been improved to better handle the presence or absence of spaces within the expression.

The tags used when filtering vector features have been made consistent across processes. These tags are used, for example, when creating layers based on rule files. GO_AttributeContains is now always used instead of GO_ContainsAttributeAcronym, GO_AttributeNotContains instead of GO_NotContainsAttributeAcronym, GO_AttributeContainsOrdered instead of GO_ContainsOrderedAttributeAcronym, and GO_AttributeNotContainsOrdered instead of GO_NotContainsOrderedAttributeAcronym.

Opening Data

01701403, 01601790, 01602600, 01503172, 01501841, 00900138

An informative error message is now displayed if a specified web service has no layers that can be displayed in the application.

01701740 Opening ENC datasets with incorrect updates no longer cause an application failure.

01702395, 01601024

Changes have been made to the way WMTS URL are opened to account for some non-standard server settings.

01702258 The application no longer closes when opening a reference model with a reach that does not have a representable geometry.

VPF support files were updated to improve support for opening VMap1 content.

Errors are no longer reported when trying to open encrypted HCRF charts.

GeoTIFF raster surfaces are now enabled in the Layers window when they are opened, so they now automatically draw in the Display window.

Opening several files at once when the file names and paths are long could result in exceeding the file name buffer size and stop files from opening. The file name buffer size has been increased to help avoid this.

When drawing CARIS files (DES) in the 2D view, any Z-values are now ignored. This resolves some issues when the envelope of the data is defined with dummy elevations and caused incorrect transformation and display of the data.

WMTS are only supported when the tile resolutions in the pyramid level are multiples of two of the root layer. The exactness of this requirement has been relaxed as numerical precision can limit how exactly the resolutions match.

Spatial Agent Files (SAF) are no longer supported.

Connecting to a web service, such as a web coverage service, now correctly shows sources available through a URL redirect.




Some ESRI binary grid files with Mercator coordinate reference systems were displaying as shifted when opened. These files are now displayed as expected.

Specialty support for displaying compass rose features has been removed as CARIS files are now opened using generic vector map handling.

Opening an invalid HOB file no longer causes the application to close. Specifically, if the HOB file has been truncated, or if 2D or 3D points have more than one spatial, an error message is now displayed and the file is not opened.

When opening third-party raster images, an XML file is created to store information such as what channels to associate with the RGB colours. In previous versions, the channels could be mapped to "None"; this is no longer supported. Attempting to open a third-party raster image with an XML file that has the channel set to None will fail. It is recommended that you delete the XML file in the unlikely event that you run into this issue.

WKT files can now be opened whether the coordinate reference system (CRS) is encoded in a human readable form with newlines, or if the CRS is encoded without newlines.

When a HOB file that contains features with invalid attributes is opened – messages in the Output window now inform you what features contain the invalid attributes and what attributes are invalid.

Text in a VPF opened in the application will no longer appear stretched when there are duplicate coordinates defining the position.

More detailed error message are now given when attempting to load an S-57 file with invalid fields.

Opening a file used to fail if any of the features referenced a spatial that did not exist. These features are now reported and skipped, and the remainder of the data is opened.

Forwards compatibility has been improved for CSAR files, so there will be better validation and reporting if a new version of CSAR cannot be opened in the application.

JPEG files are now expected to be baseline JPEGs, unless they are explicitly set as being progressive JPEGs.

BMP files opened in the application no longer use information found in the header of the file for the resolution of the georeferenced raster image.

Support for the CARIS HNS file format has been removed.

Support for an old style of CARIS reference models produced by CARIS BEAMS, with three linked XML files, has been removed. Single-file CARIS reference models and LandXML reference models are still supported.

Any legacy files can be upgraded to the new format by any previous version of EAM, in BASE Editor or HIPS.

Options

01701355 When Tools > Options > General > Selection > Show Distance is turned on, showing the size of the selection area, the distance being displayed is now based on the coordinate type and measurement reference of the view.

01702731 An error message is now reported when starting the application if the system is setup with "My Documents" pointing to an inaccessible location.

01700457 Changing speed units no longer affects sound speed units.

Changing the zoom or pan factor in Tools > Options now has an immediate effect. For example, when using the mouse scroll wheel immediately after changing the option, it now zooms in or out based on the specified percentage.




The Tools > Options setting for automatically zooming in on the superselection has been replaced by new menu items View > Zoom > Superselection and Selection.

Tools > Options settings for display precision no longer limit the precision that can be entered in a number of dialog boxes, and does not limit the precision that is actually applied. If a more precise value is specified, it is used with the user-provided precision more consistently now.

An empty file named "False" is no longer created when starting the application with the Tools > Options setting for Console set to "False".

The Tools > Options setting for the Logs folder is now monitored as a required setting.

Settings for geographic distances parallel to axes, such as raster resolution values, have been moved in Tools > Options to now be under the Coverage category.

The Tools > Options setting for Coordinate Type has been replaced with Initial Coordinate Type for Projected Display. The net effect is that Ground-type coordinates are no longer ever used when a geodetic coordinate reference system is active.

The Tools > Options setting for Measurements Reference has been replaced with Initial Measurement Reference for Projected Display. The net effect is that Planimetric-type measurements are no longer ever used when a geodetic coordinate reference system (CRS) is active, and geodetic-based measurements are no longer ever used for an engineering datum CRS.

Portrayals

01702488, 01700426, 01503210, 01500067

Text colours can now be set in the text lookup table (tsymref.dic) by using the new TC option. For example, the following entry sets the beacon colour text ($bccol): "$bccol","","TC(Nautical_Purple)","29","S","DISPLAYBASE","21010","20Mask_Black_and_BathyContours_Box"

In this example, the "TC(Nautical_Purple)" option sets this text to be always displayed in nautical purple. The colour setting can be changed by selecting an override colour ($coltk) attribute.

01602858 Symbols were added for wave and current farms (OSPARE). The default presentations for OSPARE areas were modified in the asymrefs.dic support file in the PCEConfig folder.

01700787 A new symbol for heliports (AIRARE point with CATAIR=3 and 4) has been added. Presentation for AIRARE points with CATAIR=3 and 4 (heliports) has been added to the psymrefs.dic file in the PCEConfig folder in the installation directory.

01600876, 01200503

Symbols and line styles were added for breakers, and a symbol was added for overfalls. The default presentation for WATTUR areas, lines and points were updated in the presentation support files in the PCEConfig folder.

01701833, 01701738

Symbol P4 was added for beacons. It has a star at the bottom, and does not have a topmark. A new entry with Feature Code = P4STAR was also added to the ih_master.txt file in the CARISConfig folder in the installation directory.

A short "T" symbol has been added to the master and symbol files. It can be used, for example, to represent contacts in a mechanical sweep bar survey.

Extra space was removed from the S-52 IENC point portrayal files for Paraguay and Brazil to allow the following to rotate as expected when ORIENT is none-zero: notmrk with catnmk=104, bnkwtw=1, dirimp=1, and fnctnm=2.

When drawing a feature layer defined based on an XSLT presentation in the portrayal control file, invalid features are now skipped and the remaining features continue to draw.

The default presentation for ISTZNE areas was changed in the PCEConfig asymrefs.dic file. The T line is used in the correct direction now, based on the NPPRRT attribute.




The default thickness of lines for RDOCAL points has been increased, specifically in NPCI and NPCIN symbols and in the psymrefs.dic presentation file in the PCEConfig folder in the installation directory.

The presentation for RDOCAL lines has been improved. Two new line patterns have been added to the master file for dashed lines with the Radio Reporting sign for one-way or two-way, depending on the TRAFIC attribute. The default presentation was also updated in the PCEConfig lsymrefs.dic.

The default presentation for conical starboard red lateral buoy (BOYLAT) from IALA B has been modified in the PCEConfig psymrefs.dic file to be displayed with a transparent conical buoy, instead of black.

A line pattern NPFAIRWAYS4 for fairways has been added to the ih_master.txt support file. The default presentation for FAIRWY areas was changed to use this new line pattern in the asymrefs.dic support file in the PCEConfig folder in the installation directory.

Symbols were added for ice limit areas for glaciers. The presentations for ICEARE areas were modified in the asymrefs.dic support file in the PCEConfig folder. The presentation for COALNE lines with CATCOA=6 (glacier, seaward end) was modified in the lsymrefs.dic support file.

TE and TX drawing instructions were removed for $COMPS and MAGVAR in the point look up file (psymrefs.dic) in the PCEConfig folder.

The S-101 support files and portrayal files have been updated to the DCEG draft from March 2016, and the presentation has been improved.

The mapping files from S-57 3.1 to S-101 were also updated.

Any feature layers created with S-101 Draft (DCEG 201404) in older software, and saved as H2O files, can no longer be opened. These files can be opened if the extension is renamed to 000.

Work has been done to prepare for the future addition of vector dynamic masking. No functional changes are expected.

Process Designer

The format of Process Designer process models has been changed. Old process models need to be recreated. Older software will not be able to read newly created models.

The Include Band options of the Grid Points process have been renamed. Include Band Name is now Band Name, Include Band Output Band Name is now Output Band Name, and Include Band Operation Type is now Operation Type.

When using certain processes in process models in certain orders, Process Designer would fail with a message about "The sources from (process one) to (process two) are not compatible." Changes were made to the following processes to avoid these inaccurate error messages: Import Points, Join Points, Export Points to CSAR, Grid Points, Fill Raster Holidays, Resample Surface to Raster .

The sample process models in C:\ProgramData\CARIS\BASE Editor\5.0\SampleData have been updated to pick up file format changes.

Projects

01500720 Grouping for BSB (KAP) files is now saved correctly in project files.

When saving a project, if any datasets are in memory (e.g. new feature layers, transient coverages), there is now a prompt to optionally save the data. Choosing not to save the data results in it not being included in the saved project file.

Projects cannot be saved if there are any empty unsaved feature layers.




Project files, which are replacing Session files, can now be saved even when the 3D view is active. Note that the active views are not saved in project files; that capability is expected to be added in a later release, in user-specific files that can optionally accompany project files.

In older software, it was not possible to save a session file, now known as project files, if all sources were in groups in the Layers window. Now, it is possible to save a project file regardless of the grouping in the Layers window.

Properties

01701840 It is no longer possible to choose an undefined colour file when setting the display properties for coverage data.

01701344 With the new grouping system in the Layers window, applying properties on the group applies it to all layers in the group. This fixes applying transparency on grouped raster images such as BSB files.

01601799 The name for the time properties in deconfliction rules have been updated to Minimum and Maximum Time. CRFX files that reference the old Data Start Date and Data End Dates names will continue to work.

Right-clicking in the Properties window now only shows the Undefined and Unknown options when they can be set for the selected property.

When changing a colour file property and choosing to create a new colour map or colour range file, the new file is now immediately applied when it is created.

Setting an override transparency on vector formats with text data, such as DWG and DGN, now works, and is respected when exporting the view.

The Colour Map Editor and Colour Range Editor have been updated with a new look and feel; no functional differences expected. In addition to the colour, the numeric RGBA colour values are also now shown in the Editor dialog boxes.

A new display property is available for raster surfaces with true position data. When the primary Z band is the active attribute for a layer, it is now possible to choose whether to interact with the data in that layer based on the cell centres or based on the true position of the data.

When editing a colour range file, the slider now adjusts the minimum/maximum values (clipping the colour range) in a similar fashion as with colour maps.

It is no longer possible to specify an overriding colour map for the display of an 8-bit raster image.

String table definitions are now accessed in the Band Information dialog box launched from the Source ( i ) section of the Properties window.

Filter colours set on a group of raster images are now respected by all image layers in the group.

Changing the display properties of a TIN while it is still drawing now cancels the draw.

Timestamps now more consistently end with the Z character when they indicate UTC times, in accordance with ISO 8601.

The URI of transient rasters in the properties of the source, such as those created by New Mosaic, has been changed to show that it is in memory; to keep a copy of the coverage it is necessary to save it to a new file.

Process creation information (e.g. software name/version, username) is now set more consistently for all processes. No functional difference is expected.




The coverage display properties for digit suppression have been removed. In BASE Editor, the Thin Points process can be used to create appropriate subsets of the data based on controllable options.

Note that visualization is determined by the pyramid level, and does not have a shoal-based guarantee.

Python API

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

01501045 The RasterTransform.convertGridBox function used to fail with an error message; it has been fixed.

When listing the expected (allowed) values for an attribute through the Python API, only the values permitted in the profile of the catalogue for this feature are now shown.

Error checking was added to the coverage API to ensure that provided areas are valid areas.

The return type for RasterTransform::convertGridBox has been changed to a tuple type, to make it easily usable in function calls such as Raster.read.

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

The Python API now uses the same environment files as the application. There is no longer a separate environment_python.xml file to maintain.

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

Selection

01602839, 01601462

Computation of the values for the Length and Area columns in the Selection window now works even when the coordinate reference system of the view is based on a chart alignment (CHMR).

01601071 Selecting a feature containing multiple disjoint components in a Shapefile used to fail with an error message. Multi-part features in a Shapefile are now supported.

01102315 It is no longer possible to try to drag columns out of the Selection window.

Selections are now performed only on the active layer if two sources with identical names are open in the application and a selection is made on one of these sources.

When making a large selection, the application can now be used while the selection is being updated in the view.

Data in raster images can no longer be selected in the Display window. Colour band data as part of raster surfaces can still be selected.

Single clicking in the view to perform a range selection at a point has been updated to be more likely to select a point feature more of the time.

You can now select a symbol (or any part of a symbol such as a top mark) based on where it is drawn on the screen, or by selecting around the true origin of the symbol. This applies specifically to symbols which are displayed offset from their true origin.

Selecting multiple features whose attribute values are entered through custom controls, such as the date format calendar tool, could cause the application to close. This has been fixed.




When a newly created geometry crosses over the the dateline (or 180 degrees away from the central meridian), it is automatically split into multiple geometries, which can result in invalid geometries. This happens, for example, when doing range selection. Now, any of the geometries that are invalid are skipped, instead of reporting an internal error "Number of boundary points passed to constructor is fewer than 3.

There is now a single toolbar button that combines Select by Range, Select by Lasso, and Select by Circle. The active selection mode can be chosen from a drop-down list.

Selection functionality has been reworked significantly. Specific changes are reported in other changes list entries; no other functional changes are expected.

Subset Editor

It is now possible to start Subset Editor when a group is active in the Layers window. The point clouds with active bands in the Layers window are displayed in Subset Editor in this context.

Subset Editor selection has been updated to be more consistent with selection in other 2D and 3D views. No functional changes are expected.

The Colour > Attribute property in Subset Editor is now respected when Source is selected as the attribute, even as the slice or subset area is moved.

Support Files

01500606 The code 'XM' (NATO) has been added to the country codes list for NACPP production.

The list of Producing Agencies has been updated for compliance with the latest IHO S-62 specification. Specifically, FI, DE, KR, M1, N3, 3D, 5W, and 8A were updated, and 0S, 2Q, 6W, 6D, 6V, 5S, 6E, and 2L were added.

A list of the third-party library versions used by the application is now included in the installed files.

The schemas deployed with the application have been updated to allow automatic validation of more types of files.

User Interface

01701574 Windows and dialog boxes that contain grids, such as the Tools > Options dialog box, now support using the <Tab> key to switch between fields. Only modifiable fields and buttons are in the TAB order; drop lists are not.

01701574 Improvements have been made to the display of fields and values in dialog boxes used to view and select coordinate reference systems, providing a better output on high resolution monitors.

01701866 The check boxes for child layers in the Layers window were not displaying correctly if the display settings of the computer were set to Windows High Contrast mode. The check boxes now display correctly regardless of the display settings of the system.

01702617, 01701574

Improvements have been made to the display of fields and values in the New Feature Layer dialog box used when data is open in the application, providing a better output on high resolution monitors.

The Refresh icon in the toolbar is now consistent, regardless of whether data is open in the application or not.




Newer dialog boxes, such as the one for picking coordinate reference systems, remember where they were positioned when they were last used and show in the same location the next time they are launched. If that previous location was on a monitor that is no longer available (e.g. a second screen that has been unplugged), the dialog boxes now default to a visible screen instead.

Dialog boxes that have Yes/No buttons were changed so the X button in the upper-right corner of the dialog box now does the same thing as clicking the No button.

The context menu in the Display window is now only shown for a single active control at a time. This prevents duplicate Edit Line menus being displayed in the context menu.

When browsing for a file or a directory, there is no longer an error message if the system is setup with "My Documents" pointing to an inaccessible location.

Newer dialog boxes now respect the application locale, and the behaviour is consistent with the older dialog boxes. In the current version of the application, this means that dialog boxes expect numeric data to be entered with a standard English formatting, using periods as the decimal separator.

Combo boxes in the menu have been updated to better ensure the contexts are completely visible.

Status indicators have been removed from the right-hand side of numerous dialog boxes in all CARIS applications other than Process Designer, where they are still required to set fields as prompts to specify values when running a process model.

An improved error message is now displayed if a module cannot be loaded when the application starts.

Several dialog boxes, such as Contouring, now set the default band to be the active Z attribute selected in the properties for the layer.

The "Zoom to Map" command has been renamed to "Zoom to Source."

The Output window has been updated to have a new user interface. No functional differences are expected.

Some name changes have been implemented in the Tools menu. For example, the Surfaces sub-menu has been renamed Coverages and the Layers sub-menu has been renamed Bands.

Mnemonics used as short-keys in the Tools menu have been adjusted as a result.

Validation

01700903, 01700742, 01700698, 01700268, 01700246, 01700246, 01602762, 01503364

GeometryIsWithin and GeometryEquals have been improved to better determine whether features overlap the geometry being tested.

01600982 Overlapping M_QUAL could fail to be detected in certain circumstances. This has been corrected.

01602762 The Validation check for Periodic Dates attributes could incorrectly flag values as containing a space character when they did not.

01302653 Custom quality assurance tests now run significantly faster, which is especially noticeable on larger projects and datasets.




01600197 Error messages for S-58 Group 1 Area Coverage or Overlapping Areas validation now provide more detailed information on why tests are skipped when there are problems with data.

01600982 Error messages for S-58 Group 1 Area Coverage and Overlapping Areas validation now provide more detailed information on why tests are skipped when there are problems with data.

Unnecessary newlines have been removed from the Validation window output.

The S-58 Depth Areas and Depth Contours validation tool now returns a warning if no depth contours are found between depth areas. Previously, an error was returned.

The AttributeValueContains test now passes if any of the list values is set to the specified value.

The GeometryTouches test now reports touches for both lines and areas when they touch along an edge, as well as when they touch at a point.

The GeometryIsCoveredBy check now gives a warning message if a feature is covered by areas and those areas overlap and share edges in the same direction.

The Invalid Attributes validation test now also compares SOUACC and M_QUAL CATZOC attribute values.

The GeometryIsDisjoint test failed with messages about features not being disjoint if none of the features overlapped. Now, if none of the features overlap, the test correctly identifies them as being disjoint.

Some custom validation tests displayed in the Validation dialog box had Unicode characters that were not displayed correctly. These characters have been replaced with hyphens and other standard characters.

A warning is now reported if customized validation tests reference checks that do not exist.

The Intersecting Edges validation test now reports self-crossing edges more consistently.

Soundings that have a Z-value that differs from the DRVAL1 by one system epsilon (the smallest numeric difference on the system) are no longer reported as being errors.

The GeometryIsCoveredBy check has been updated to use more precise geometries. No functional difference is expected.

The Output/Validation window hyperlinks have been updated to ensure deleted objects are not included or counted.

The confirmation message when clearing the Validation window was improved.

The Collection Features validation test now correctly reports any collection objects with less than two features when this test is run on HOB files.

Support for the EdgeIntersections tag in validation rules has been removed.

The s58errors support file now includes more detailed comments. This is only available in the file and is not displayed in the application.

QC files are made more readable by applying the following changes: • message attributes are now on separate lines • comments that are exact matches to messages are removed

Error messages when validating geometries have been improved.

It is now possible to resize the Validation Checks dialog box to expand the Customized QC Tests section.

Customized tests can now be run by double-clicking the test in the list.




The GeometryCrosses test has been updated to support multi-point features such as grouped soundings.

The behaviour of GeometryIsCoveredBy has been changed to be consistent with the S-58 edition 6.0 definition. When testing if a line GeometryIsCoveredBy an area, it will now include cases where the line is within the boundary of the area. If the previous behaviour is required, line GeometryIsWithin an area gives the same result that GeometryIsCoveredBy did in the previous releases.

The CompareAttributeValues test now supports comparing spatial attributes.

"General Sounding Tests" was renamed to "General S-57 Sounding Tests" to indicate the context of the checks that exist in the file.

The tag AttributeValueIsDefined can now be used in custom validation rules.

The progress monitor now shows more information as certain validation checks are running.

When running S-58 geometry checks, "Edges to Merge" is now run before "Lines to Merge". When running S-58 Compatibility tests, "Edges to Merge" now shows up for S-58 Warnings.

When the provided QC rules contain stricter checks than the published S-58 6.0 tests, a statement starting with "Extended" has been added to the reference field.

When Validation checks identify edges of interest, or specific soundings, there are often Zoom and Highlight hyperlink options. These options have been improved, such that Zoom shows slightly more than just the area of interest, making the Highlight more obvious. The width of the highlight has also been adjusted to improve visibility.

The validation checks for soundings have been renamed from "S-58 Grouped Soundings" to "S-58 Soundings".

The S-58 Soundings (formerly S-58 Grouped Soundings) Validation test has been optimized to produce faster validation results.

In the s58errors support file, test 6010 was updated to also reference test 513, which is equivalent to test 1530.

S-58 test 557 has been enhanced to allow a precision of 1 or 2 decimal places for SIGSEQ.

Miscellaneous

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

01500529 Errors are now reported when there are invalid parameters in the utilities.xml file specified for Tools > Options > Files and Folders > Utilities.

The Registration Grid window now always displays the "X" column to the left of the "Y" column when displaying ground coordinates. When displaying geographic coordinates, the behavior of the grid is unchanged.

When creating a new publication with a border, the neat line of the border is now transformed, in order to better handle cases where the data spans the dateline.

Changes have been made to how sources are closed when save operations fail, ensuring the application remains operational.

More tools have been updated to use high precision geometries for calculations, which should result in fewer tolerance/precision-related errors.




BASE Manager

High precision geometries are now used internally when interacting with features in all map types. No functional changes are expected.

Very large numbers are no longer rounded when displayed. For example, 2025493936704847874 is no longer converted to "2025493936704850000".

Performance optimizations were added to a number of geometry operations in the high precision geometry library. No functional differences are expected.


Attributes

The Create Date Attribute dialog box, used to define the value for date attributes like "Source date", no longer allows the value to be set to Unknown for data formats that do not support unknown dates, such as BDB Server database objects.

The system level ability to set Unknown for BDB Server database enumeration and list values has been removed. To set a value as Unknown, it must be added as a possible value for the attribute in Catalogue Editor.

Batch Tools

The --output-vertical-crs option has been added to the Server Combine to Raster and Server Join Points processes.

The unimplemented recurse option was removed from the ServerCombineToRaster process.

Catalogue Editor

The order of attributes in a feature catalogue written to a database through Catalogue Editor is now preserved.

Catalogues

01300100 Filenames of the source data are stored in the CoverageName system attribute even when there are periods (.) included as part of the filename.

When editing an empty catalogue in Catalogue Editor, the first attribute is now assigned an ID of 1 instead of 0. Note that any attributes set to have an ID of 0 are skipped when uploading a catalogue to a BDB Server database.

When using Catalogue Editor to update the catalogue of a BDB Server database, it is no longer possible to specify the query layer as that information is not relevant.

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.

Connections

Error messaging has been improved when unable to connect to a BDB Server database.

Coverage Tools

01503294 Coverages open locally from a database are now shown in the Join Points dialog box by their layer name, which is defaulted to the CoverageName system attribute for the associated database feature. The layer name can be changed in the Layers window, if needed.




Using Set Coverage (previously called Replace Bathymetry) to replace raster data with a point cloud or variable resolution surface now clears the CoverageResolution attribute value.

Edits made to a TIN created from a coverage open from a database are now maintained throughout the current application session, even when the TIN is closed and re-created. Resetting the TIN will still clear the TIN edits.

When starting the Combine command with a selection of BDB Server database features with associated coverages, the automatically populated CoverageName system attribute is now used to identify the coverages in the dialog box.

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.

Export

When exporting coverages from a BDB Server database, object.xml files are also created containing the attributes of the associated vector feature. The format of these files has been changed in order support the wider variety of catalogues supported for BDB Server databases, and older files are no longer supported.

There are now improved messages when exporting coverages from a BDB Server database if some of the selected vector features are not associated with coverages.

The ASCII export format has been removed from the Extraction dialog box. It remains possible to write process models to loop over all exported CSAR files in a directory and convert them to other formats, such as ASCII, as desired.

Import

The bathydbserverloader application has been removed. It is possible to load coverages to the database through the Python API. A sample coverage_loader.py script is now shipped with the application.

Support for attribute plugins, like the Simple Attribute Plugin used to populate attributes when uploading coverages to a BDB Server database, has been removed. The Python API can instead be used to accomplish the same goals.

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.

Layers

01501530 Issues related to the listing of BDB Server database queries (e.g. the number shown, the 10th one being duplicate, etc.) are no longer relevant. The new filter capability, with each stored in its own file, does not have these issues.

Opening Data

The way that BDB Server database connections are initialized and closed has been made more consistent for the various executables that connect to databases. This may resolve some issues such as the application crashing when closing in certain circumstances.

Properties

The Database Location property has been removed for BDB Server databases. The node location can be found using the BDB Server Administration Tools when needed.




Compose Module

Python API

Due to the increased capability for general vector datasets, and the removal of assumptions about the specific feature names in use for a BDB Server database, many of the BASE Manager-specific Python API have been removed (e.g. caris.bathy.db.Object).

The Python API documentation and tutorial have been updated for the updated interfaces.

An appropriate error message is now displayed if attempting to create a new object in the database with the same unique identifier as an existing object.

Selection

Emptying a BDB Server database recycle bin now updates the selection as appropriate. Similarly, restoring a selection from the recycle bin also now updates the selection as appropriate.

User Interface

The Set Vertical Reference System command has been removed.

Miscellaneous

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.

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


Batch Tools

The AssignSoundingSCAMINValues process has been updated to match other processes, including how the help is displayed.

Product Creation

01601417 The S-57 Exchange Set Editor now produces reissue exchange sets that pass the S-58 555 validation test, with features exported in following order: meta features, geographic features with slaves before masters, and then collection features in order of increasing level.

01700109 Creating an S-57 AML from an existing dataset could result in an incorrect scale band being used. This has been corrected.

Creating a new product from multiple datasets now reports features that could not be clipped to the specified template.

The PRSP subfield of the DSID field in a S-101 dataset has been corrected to "INT.IHO.S-101.1.0"

The reissue57 executable is now included with the Compose module. This can be used to reissue an exchange set from an S-57 exchange set containing a base cell plus updates. To run this executable, the path must be setup appropriately for the command prompt; this can be done by using the Start Menu item for the BASE Editor 5.0 Command Prompt.

The S-57 Exchange Set Editor was fixed such that: - the Validate button also validates external files referenced by the dataset, - when reissuing a dataset, the Remove button can be used to remove all external files, - removing newly added files happens immediately and no longer requires validating and applying the removal, and - reissuing a dataset with updates now requires the updates to be included in the exchange set.




SCAMIN

The SCAMIN mapping file (assignIHOscamin.xml) now assigns a SCAMIN step value of 3 to WRECKS features with a CONVIS or CONRAD equal to 1.

SCAMIN values have been updated to comply with S-57 Use of the Object Catalogue (UOC) Edition 4.0.

Support files have also been renamed and updated accordingly, specifically sdgparm_S-65.txt was renamed to sdgparm_IHO.txt and S-65_ScaminMapping.xml was renamed to assignIHOscamin.xml.

Sounding Groups

01600265 A correction was made to how a sounding cluster is updated. If the last sounding in a cluster was removed and a new sounding added to the same cluster, the new sounding was getting deleted instead of the intended one.

Validation

01601585 Tests "S-58 1670 EXPSOU", "S-58 1670 QUASOU", "S-58 1670 SOUACC", "S-58 1670 TECSOU" and "S-58 1670 WATLEV" in the S-58 Level 3 QC XML have been updated to report if a WRECKS/OBSTRN point is shallower than the depth of the WRECKS/OBSTRN area containing it, or if the attributes in the area are not equal to the ones in the shallowest point feature.

01500771 The S-58 QC level 3 Test 1565 has been enhanced so that the spatials are reported, leading the user to the location of the problem.

Test "S-58 507 LIGHTS SIGPER SIGGRP" in the Level 1 file now excludes air obstruction and fog detector lights (CATLIT=6 and 7) when LITCHR is undefined.

Certain rule files that searched for list values set to specific values were incorrectly using AttributeValueIsEqualTo. This only worked if that was the only value set for the attribute. Now, the rules check if any of the set values are the given specified value, using AttributeValueContains.

Using "S-58 check 1775" on IENC datasets could result in missing some specific features. This has been corrected.

Using "S-58 check 549" on IENC datasets was erroneously reporting errors for depth features covered by M_QUAL. This has been corrected.

Using "S-58 check 1565" on IENC datasets was incorrectly flagging LNDARE features. This has been corrected.

A check for trailing spaces in SORIND values has been added to the IENC 2.3 Level 1 features QC tests.

Traffic separation S-58 tests were previously reporting features with shared edges, but now properly check for shared edges being used in the opposite direction.

The performance of some custom tests has been improved by removing redundant GeometryIsEqual and/or GeometryIsWithin checks.

S58_Level3_SpatialRelations tests now check each sounding within a sounding group, instead of treating sounding groups as a whole and only checking the first sounding.

QC tests were updated to remove references to tests that no longer exist, to avoid unnecessary warnings.

The LBO_1_0_Level5_Metadata validation file was updated to include checks 5, 7, and 9 inside the list of checks.





The RAL_1_0_Level5_Metadata validation check for M_SDAT objects was updated to correctly reference the RAL 1.0 check 5.

S-58 Test 1765a is now only run if the dataset contains both M_QUAL and M_ACCY features.

A typo has been fixed in the error message for the S-58 50 RECTRC test when the geometry is not a straight line and the CATTRK is set to 1.

Several spatial relations custom tests were unnecessarily limiting themselves to cases where the CATBRG attribute value was set. They now run regardless of the value of CATBRG.

Features located on the Product Boundary could occasionally be omitted when QC checks were run. This has been fixed.

The following changes have been made to the S58_Level3_SpatialRelations.xml QC test file: • Test 550 no longer checks if an UNSARE feature overlaps a SOUNDG feature.• Test 1512a warning level is changed from WARNING to ERROR.

As part of the upgrade to S-58 edition 6.0, certain obsolete tests were removed, including: • S58_Level1_Features check for each TS_TSP attribute value that does not conform to

the correct structure, (i.e. values not separated by commas).• S58_Level3_SpatialRelations check for each WRECKS or OBSTRN feature object of

geometric primitive area which is not WITHIN a DEPARE, LNDARE or UNSARE feature object of geometric primitive area, and the S-58 1662 check from OBSTRN, and the S-58 1662 check from WRECKS.

• S58_Level5_Metadata checks for BOYCAR, BOYINB, BOYISD, BOYLAT, BOYSAW, BOYSPP, M_HDAT objects, and the S-58 1526 check from M_QUAL.

Extensive changes were made to wording and logic of checks in all S-58 customized checks (levels 1-6). Error levels were also changed, including to use the new level of CRITICAL ERROR, as appropriate. Additional tests were also added. The associated errors file was also updated. Contact CARIS customer service for more information if needed.

Existing validation rule files have been simplified, using the new check AttributeValueIsDefined instead of Not AttributeValueIsUndefined.


Batch Tools

Now only true URIs of the format file:///DriveLetter:/DirectoryStructure/ReferenceModelName.xml?template=TemplateName can be used to specify templates in the Contour Raster by Model process.

Model

Reference model reaches that are defined as beginning in an area of an alignment that does not intersect a template, are now drawn starting from the first point where the alignment definition intersects the template. Similarly, reaches defined as ending in an area of the alignment that does not intersect a template, are now drawn ending at the last point where the alignment definition intersects the template.

The Make Features Horizontal command now works for reference model surfaces even when the first three points are collinear.




It is no longer possible to set the name prefixes used when creating new reference model features. The feature type is now available in the Selection grid rather than the feature prefix.

Process Designer

The Contour Raster by Model processes now give a more intuitive way to define the reference model template URI.

Miscellaneous

Combo boxes have been added to the Hyperbolic and Rectangular Volumes, Analyze Conformance, and Detect Shoals dialog boxes to select the band to use with the process.


CARIS BASE Editor 5 Changes List - 東陽テクニカ · CARIS BASE Editor 5.1.0: Highlights CARIS...

Documents

Transcript of CARIS BASE Editor 5 Changes List - 東陽テクニカ · CARIS BASE Editor 5.1.0: Highlights CARIS...