The Select and Transform panes include the Preview button which shows the preview of the operation. In the current build, previews are limited to a table window, the next build will allow using previews in a map window.
The preview for a transform operation in a table window shows a virtual preview field on top of the regular fields. The name of the preview field is set to the name of the transform template. The preview values are computed dynamically as you scroll the table. The preview field cannot be scrolled out and is always visible.
The preview for a select operation in a table window shows a virtual preview field on top of the regular fields, but reduces the preview field to its caption. The values in the preview field as not shown directly as 'true' / 'false' and instead change the background color of the records: white = the record is currently unselected and will stay unselected, red = the record is currently selected and will become unselected, blue = the record is currently unselected and will become selected, red-blue = the record is currently selected and will stay selected, gray = the selection value is being computed. The name of the preview field is set to the name of the select template. The preview values are computed dynamically as you scroll the table.
The preview field can be hidden using the Hide Preview command in the context menu.
The preview field for a transform can be temporarily collapsed to its caption or expanded back to caption and values using the Values command in the context menu (works as a toggle), or by clicking on the arrow icon on the right side of the caption.
The preview field can be resized by dragging either of the borders. Dragging the border of a preview field snaps it to a border between regular fields, with some tolerance.
The preview field can be dragged around using either the caption or the body with the values. Dropping the preview field onto a regular field makes the preview field start at the left border of the target field. Dropping the preview field close to the right border of the last shown field makes the preview field start at that border.
The preview for a transform operation that puts the result into an existing field indicates that field in a table window using a bullet icon.
The preview for a transform operation that produces geometry / tile / binary values in a table window reduces the preview field to its caption and shows a tooltip reporting that the preview is unavailable. (Operations that produce geometry or tile values should be previewed in a map window. Operations that produce binary values will not be previewed because checking whether a particular binary value is the one you wanted to produce is impractical without highly specialized UI.)
Previewing the result of a select or transform operation and then changing the parameters for the operation in the relevant pane does not update the preview automatically. To update the preview, click the Preview button again. Previews for select and transform operations override each other. Performing a select or transform operation removes the preview from the active window.
Switching between windows does not remove previews. (It is possible to have multiple previews in multiple different windows shown simultaneously.)
Renamed transform parameters: 'cuts' -> 'parts', 'Cut with:' -> 'Split with:', 'Cut with selection only' -> 'Split with selection only', 'coordinates with step' -> 'line coordinates'.
Renamed query function: GeomToCuts -> GeomToParts.
Renamed query functions: GeomSplitToConvex / Par -> GeomToConvex / Par.
New query function: GeomPartLine - computes part of the line between two specified distances. If the begin distance is larger than the end distance, the returned part goes in the direction opposite to that of the line.
New query function: GeomToPartsLineSequence - splits the line into parts between specified distances. If the begin distance is larger than the end distance, the returned parts go in the direction opposite to that of the line. The result table includes minimum and maximum distance for each part.
The Split transform template for geometry values allows splitting lines into 'line parts'.
The rules for world file extensions are changed to: (a) take the original extension and add W, (b) take the first letter, take the last letter and add W, for compatibility with other products.
The Reshape transform template for geometry values rotates geometry values clockwise. (The GeomRotate query function keeps rotating geometry values counterclockwise, the template merely changes the sign of the parameter value.)
The Copy transform template for geometry values support copying 'rectangle' to an x4 field.
The ArcGIS REST dataport supports ArcGIS servers with vector data. Downloaded vector data can be cached in the parent data source via the 'Save cached data between sessions' option.
(Example server that powers the dashboard for COVID-19 data from JHU: https://services1.arcgis.com/0MSEUqKaxRlEPj5g/arcgis/rest/services/ncov_cases/FeatureServer )
The GDB dataport attaches EPSG codes to coordinate systems with equivalent WKID codes, to allow using grid-based and other EPSG coordinate transforms when re-projecting components with these systems.
The WMS dataport detects server errors that aren't flagged as errors and reports them in the log window.
The WMS dataport performs additional filtering of layer coordinate systems to better work with servers that report unsupported coordinate systems in bounding box data.
Dataports for SQL Server / Oracle / DB2 / MDB wrap batch insert, batch delete and batch update operations into transactions for robustness and performance. (Dataports for other databases were already doing this, the change completes the feature for all dataports for databases.)
Dataports for all databases automatically break big transactions for batch operations into manageable portions. (Without this, most databases just fail with an overflow error after the amount of data about to be committed exceeds a certain limit. The limit is frequently not a terribly big one either, in the range of 15-20,000 records or 50-100 MB of record data, far too low for GIS.)
The SQL Server dataport supports the newest ODBC driver for SQL Server available from Microsoft (v17). (In particular, the dataport recognizes custom types for geometry / geography / XML fields reported by the driver.)
The MDB dataport automatically corrects names of newly inserted tables to fit into the limits imposed by MDB (no leading spaces, no double quotations, no periods, etc).
(Fix) Computing viewsheds for all observers (visible area from all / visible level from all) no longer sometimes fails to handle tiles without observers.
End of list.