GDAL 3.13.0 release candidate available
Even Rouault via gdal-dev <[email protected]>
| Newsgroups | gmane.comp.gis.gdal.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, I have prepared a GDAL/OGR 3.13.0 "Iowa City" release candidate. I'll call for a vote promoting it later this week if no serious problems are reported before. NEWS at: https://github.com/OSGeo/gdal/blob/v3.13.0RC1/NEWS.md Pick up an archive among the following ones (by ascending size): https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0rc1.tar.xz https://download.osgeo.org/gdal/3.13.0/gdal-3.13.0rc1.tar.gz https://download.osgeo.org/gdal/3.13.0/gdal3130rc1.zip A snapshot of the gdalautotest suite is also available : https://download.osgeo.org/gdal/3.13.0/gdalautotest-3.13.0rc1.zip A snapshot of the documentation is at: https://download.osgeo.org/gdal/3.13.0/gdal3130doc.zip The release/3.13 branch has now been created, and master is now open for 3.14.0dev. The following changes have been done since beta2: - GDALRasterBand::IRasterIO(): avoid potential int overflow (ossfuzz#506741816) - GDALAlgorithm: check Run() is called at most once per instance - gdal: make sure stdout is properly flushed (#14477) - gdal raster contour: rename --src-nodata to --input-nodata - gdal raster edit: add --color-map to set a color table on a band, and --unset-color-table to remove it - gdal raster footprint: rename --dst-crs to --output-crs - gdal raster footprint: rename --src-nodata to --input-nodata - gdal raster index: rename --dst-crs to --output-crs - gdal raster reproject: rename --src-crs and --dst-crs to --input-crs and --output-crs - gdal raster reproject: rename --src-nodata,--dst-nodata to --input-nodata, --output-nodata - gdal raster rgb-to-palette: rename --dst-nodata to --output-nodata - gdal raster scale: rename --[src/dst][min/max] to --[input/output][min/max] - gdal raster stack/mosaic: rename --src-nodata,--dst-nodata to --input-nodata, --output-nodata - gdal raster tile: rename --dst-nodata to --output-nodata - gdal raster viewshed: rename --dst-nodata to --output-nodata - gdal-bash-completion: make it msys2 compatible - AIG driver: avoid potential stack buffer overflow in CCITTRLE code, and a read heap buffer overflow when opening 'hdr.adf' (#14469) - GRIB driver: fix heap-Buffer-Overflow WRITE on corrupted/hostile data (#14455) - GRIB driver: avoid heap-buffer-overflow in specunpack() (#14470) - HDF4-EOS: fix various vulnerabilities (#14428, #14430, #14431, #14440) - ISIS3 driver: correctly deal with PVL keys with '/' character in JSON representation (#14443) - MRF driver: Fix against corrupted/hostile data (#14472) - NITF driver: fix potential stack buffer overflow in NITFLoadAttributeSection() (#14449) - PCIDSK driver: avoid integer overflow (ossfuzz#500171204) - TileDB driver: do not try to identify /vsis3/.../file.tif files - VRT driver: fix heap-buffer-overflow on misconfigured VRTProcessedDataset (#14462) - WMSDriverSubdatasetInfo::parseFileName(): fix crash if LAYERS= is not fully capitalized (ossfuzz#505232394) - gdal vector concat: rename --src-crs and --dst-crs to --input-crs and --output-crs - gdal vector clip: make it preserve aspatial layers in passthroug mode, rather than wiping out their features (#14438) - gdal vector index: rename --dst-crs to --output-crs - gdal vector make-point: rename --dst-crs to --output-crs - gdal vector materialize: fix issues with SQLite format (#14444) - gdal vector rasterize: make --tap depends on --resolution (#14458) - gdal vector reproject: rename --src-crs and --dst-crs to --input-crs and --output-crs - gdal vector reproject/clean-coverage/simplify-coverage: make it passthrough for non-spatial layers (#14446) - gdal vector set-field-type: rename --src-field-type to --input-field-type - OpenFileGDB driver: when exploring layers in GDB_Items, report deleted rows with a warning instead of a failure (#14424) - PG driver: avoid error when setting a NULL geometry field on a result layer without geometry field - Python bindings: Make gdal.alg.xxxx(...) accept aliases and hidden aliases of argument names - Python bindings: Handle numpy types in Feature.SetField Best regards, Even -- http://www.spatialys.com My software is free, but my time generally not. Highly recommend OxiGDAL if you want to live in the 21th century and cure Bixonimania _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev