The Style pane supports formatting images. The pane displays a single style item for color which can be set to either of the following:
- (no field) - all pixels are using the same color, selected using the drop-down menu;
- (use RGBA channels) - the color for an image pixel is going to be combined from BGRA channels edited separately, each channel can be set to use either a tile channel with min/max range mapped to the 0..255 range or a specific value from the 0..255 range;
- Channel X - the color for an image pixel is going to be determined using a palette, the palette is edited in the list, editing options are similar to those for thematic formatting in drawings and labels.
(A few UI tools that we had before are currently missing, we will re-add them very soon.)
Formatting images in the Style pane computes precise statistics for 8-bit and 16-bit pixel values regardless of the image size. Computing statistics tracks progress and can be canceled. Statistics computed for an image are cached in the component window that displays the image to avoid repeat computations.
The Style pane avoids computing statistics for images stored on web servers that are too large. This is useful to avoid computing statistics for Bing Maps or similar base maps.
Items in the list of image channels in the Style pane can be selected. Editing a value for a selected channel applies the edit to all selected channels.
Right-clicking a selected item in the list of image channels in the Style pane allows setting the min/max range of values to the full range of values occurring in the image.
The 'Per-Record Style' button in the Style pane is renamed to 'Overrides'. Same for the 'Per-Record Style' dialog it invokes.
There is a dataport for GEOJSON files. The GEOJSON file has to contain a FeatureCollection object at the top. We might support more subformats in the future.
There is a dataport for GEOJSON web servers. The requirements for GEOJSON data returned by the server are the same as for GEOJSON files.
GEOJSON dataport supports exporting drawings.
Parsing big GEOJSON data performs significantly faster.
GDB dataport supports exporting tables, drawings and maps (exporting a map exports all drawing layers). Exported components are renamed according to GDB rules. WARNING: attempting to export a component to an existing geodatabase will overwrite the geodatabase, similarly how exporting to a SHP file will overwrite that SHP file. To add a component to an existing geodatabase, link the geodatabase and transfer the component using copy/paste.
Export to GDB tracks progress and can be canceled.
Export to GDB optimizes bulk writes to perform faster.
GPKG dataport exports coordinate system data for drawings (converts the definition of the coordinate system to WKT, creates a new SRID value for the WKT, and assigns the created SRID value to the table field).
GPKG dataport supports exporting a single table.
(Fix) Web dataports that are using per-session cache disable writes to MFD_META table. (Before the change it was possible to, say, format components on a web dataport only to lose all formatting after closing the MAP file because changes made to formatting were stored in per-session storage that has been discarded.)
The WFS dataport uses a faster request strategy.
End of list.