Watershed Areas and Watershed Lines transform templates automatically create a unique index on stream ID and a non-unique index on target ID, for further analysis.
Computing directions on plateaus for watersheds performs significantly faster.
Tables returned by TileWatershedDownstreamLines, TileWatershedDownstreamLinesPar, TileWatershedUpstreamAreas, TileWatershedUpstreamAreasPar, TileWatershedUpstreamLines, TileWatershedUpstreamLinesPar query functions include starting / ending coordinates used to extract downstream / upstream geometry.
TileWatershedAreasUpstream, TileWatershedAreasUpstreamPar, TileWatershedLinesDownstream, TileWatershedLinesDownstreamPar, TileWatershedLinesUpstream, TileWatershedLinesUpstreamPar query functions take an additional parameter for keeping or removing overlaps.
(Fix) TileFillSinks, TileFillSinksPar functions no longer fail to convert produced tiles to the original tile type (altered tiles were being returned as FLOAT64).
Reading a CSV file allows date fields to use multiple different languages (one field US English, another field German, etc).
(Fix) Reading coordinate system from a SID file no longer shifts the origin half-pixel by X and Y.
(Fix) Template parameter pickers indicate current choice in the dropdown menu using radio icon instead of check icon.
Number keys on the numeric keypad are treated as number keys on the number row for shortcuts.
Double-clicking an expand or toggle icon in the Layers pane no longer starts editing layer alpha / field size.
The note on image shading requiring a style based on a single channel is moved from the shading checkbox to a separate readout below shading controls.
Field headers and record handles in grids are made slightly flatter.
Table fields, layout frames, map layers with invalid or missing Z order info are put last rather than first (to the bottom of the display stack rather than the top).
Layer groups in tables, layouts, maps are reworked to use folders instead of leading layers. Group and Ungroup commands are removed. The new New Folder command that creates a new folder asking for its name. The new folder is created in the same place in the folder hierarchy as the current layer. The new Move to Folder command allows moving selected layers to one of the unselected folders, the target folder is specified using a dropdown menu. Moved layers are placed after all existing layers in the target folder. Folder names can be edited. (Groups with leading layers created by prior builds are automatically dissolved. We are going to allow drag-and-drop of layers between folders using the cursor in the next builds.)
The Move to Folder dropdown menu in the Layers pane allows moving selected layers out of all folders, into the root folder, using the Move to Root command.
Moving layers into a folder in the Layers pane automatically expands the folder if it is collapsed.
Pressing Insert in the layer list in the Layers pane invokes the New Folder command.
The map window no longer allows multiple layers to reference the same component. When multiple layers reference the same component, all but the first one are rendered invalid and do nothing. Invalid layers will still show up in the Layers pane and in the layer tabs so that they can be deleted.
The map window better distinguishes between changes to the underlying data and no longer repaints after changes that cannot modify the screen: changes to data in hidden layers no longer force a repaint, changes in Z order of a mix of hidden and visible layers that do not change the Z order of visible layers no longer force a repaint, changes to alpha of hidden layers no longer force a repaint, etc.
The map window better tracks changes to metadata of layer components and automatically reloads layers after changes to referenced components (eg, table) or fields (eg, geom). (Previously the window was only tracking the reference from layer component to its table, and was not doing so in all cases.)
Dropping new components into a map window creates new layers in the same folder as the active layer.
Moving layers using layer tabs in a map window changes the folder of the moved layer to that of the target layer.
(We are going to have layer tabs use folders more, we tried multiple variants on paper and a couple in code, the results are coming in the next builds. We are also likely going to take the Layers pane out of the Contents pane set and allow using it simultaneously with any other pane under Contents.)
The LAS / LAZ dataport creates a specialized spatial index for points, which allows quick display of big point sets as drawings. The specialized index is only created for a linked file. Importing a file will create a standard RTREE index, which will perform worse than the specialized one. The specialized index creates a hierarchical data structure, stored as a .MAPINDEXP file, that is then used to service spatial queries. During a spatial query performed for display, the data structure thins the points in the query area and returns a limited number of the best representatives with the limit depending on the display window size.
The size of .MAPINDEXP file is significantly smaller than the size of uncompressed LAS, but usually bigger than the size of compressed LAZ. The file is versioned so that future builds can choose to reuse files created by this build or overwrite them with new versions.
(We are going to add this specialized index for point sets into the MAP file as well, as soon as it stabilizes. We already did a number of iterations on the structure and it evolved quite a bit.)
The LAS / LAZ dataport reports the time to create the index (could be long, but this is only done once per file).
End of list.