|
Changes LAS / LAS library dataports include scaled XYZ values in addition to unscaled ones in tables. Opening an MDB or XLS file collapses log messages generated by attempting to use different versions of Microsoft Jet and reports only the finally used version on success or the list of attempted versions on failure. Direct sub-pixel re-projection clamps and rounds produced pixel values if they are integer, for smoother results. (Fix) Projecting an image with automatic local offsets no longer sometimes generates tiles with X or Y = -1 due to rounding errors in computing the dimensions of the resulting image. (The error was not affecting the values of the projected pixels.) (Fix) Reading a DEM file no longer sometimes shifts the coordinate system of the produced image one pixel down. The map window can now show a map layer if some of the screen locations fail to project to the coordinate system of the layer (eg, a Bing Maps image in a lat/lon map will no longer disappear when zooming out). Connecting to a SQLite database / GPKG file now uses the internal implementation of SQLite if an external version of SQLITE3.DLL is not available. The internal implementation of SQLite includes support for RTREE indexes, JSON, GeoPoly. The internal implementation of SQLite only supports SQLite databases with GPKG-style spatial data, SQLite databases with ESRI ST_GEOMETRY data or with SpatiaLite registry tables require using external SQLITE3.DLL plus the required extension DLL, as before. End of list.
|