Uptream NEWS:
* RFC 77 (https://gdal.org/development/rfc/rfc77_drop_python2_support.html): Drop Python 2 support in favor of Python 3.6 (#3142)
* RFC 78 (https://gdal.org/development/rfc/rfc78_gdal_utils_package.html): Add a gdal-utils Python package
* New driver:
- STACTA: raster driver to read Spatio-Temporal Asset Catalog Tiled Assets
* Add /vsiadls/ virtual file system for Azure Data Lake Storage Gen2
* Improved drivers: DIMAP, NITF
* Number of improvements in Python bindings
* Add automatic loading of configuration options from a file
* Add support for enumerated, constraint and glob field domains in MEM, FileGDB/OpenFileGDB and GeoPackage drivers
* Deprecation:
- Disable by default raster drivers DODS, JPEG2000, JPEGLS, MG4LIDAR, FUJIBAS, IDA, INGR, ZMAP and vector driver ARCGEN, ArcObjects, CLOUDANT, COUCHDB, DB2, DODS, FME, GEOMEDIA, GTM, INGRES, MONGODB, REC, WALK at runtime, unless the GDAL_ENABLE_DEPRECATED_DRIVER_{drivername} configuration option is set to YES. Those drivers are planned for removal in GDAL 3.5
- Perl bindings are deprecated. Removal planned for GDAL 3.5. Use Geo::GDAL::FFI instead
* Removal of BNA, AeronavFAA, HTF, OpenAir, SEGUKOOA, SEGY, SUA, XPlane, BPG, E00GRID, EPSILON, IGNFHeightASCIIGrid, NTV1 drivers. Moved to (unsupported) https://github.com/OSGeo/gdal-extra-drivers repository.
* Continued code linting (cppcheck, CoverityScan, etc.)
* Bump of shared lib major version
Following a report of build of gdal linking against ODBC, force off
ODBC support so that even if it the lib leaks through buildlink3 it
will not be used. In theory this could be an option similar to pgsql
and mysql support, and that is left to someone who wants it, if such a
person actually exists. For now, this is unconditionally the half of
the option that enforces not looking for ODBC.
No PKGREVISION, because the build should not be changing.
This is a long overdue update which skips the 3.1 major release.
py-gdal is also udpated.
Besides what is noted in upstream NEWS, gdalserver has been withdrawn.
See NEWS in the source tarball; this pkgsrc update corresponds to 1452
lines.
= GDAL/OGR 3.2.0 Release Notes =
== In a nutshell... ==
* New GDAL drivers:
- ESRIC: ESRI bundle cache read-only driver (#2663)
- HEIF: read-only driver for HEIF/HEIC file. Requires libheif
- OGCAPI: tiles/maps/coverage raster/vector experimental driver
- TGA: read/only driver to read TGA image file format
* New OGR drivers:
- LVBAG: read-only support for Dutch LVBAG/Kadaster 2.0 vector format
* New utilities:
- gdal_create: to create/initialize a new raster file
* Other improvements:
- Multi-threaded overview computation (if GDAL_NUM_THREADS set)
- COG driver: TILING_SCHEME creation option
- OpenFileGDB driver: add support for using spatial indexes
- BAG driver: multiple improvements
- FITS driver: multiple improvements (MEF and binary table support)
- NITF driver: support for SNIP TREs
- OGRFieldDefn: support UNIQUE constraint
- OGRFieldDefn: support a AlternativeName (alias) property (#2729)
- Python bindings: move implementation of scripts (except gdal2tiles) in osgeo.utils package to be reusable
- Faster GTIFF Deflate compression/decompression through libdeflate (if using internal libtiff or libtiff > 4.1.0)
* Removed functionality:
- Python bindings: old-style "import gdal" is no longer available. Use "from osgeo import gdal" instead
- API_PROXY mechanism: likely never used for real usage.
- Removal of GDAL and OGR ArcSDE drivers
== Backward compatibility issues ==
See MIGRATION_GUIDE.txt
= GDAL/OGR 3.1.0 Release Notes =
== In a nutshell... ==
* Implement RFC 75: support for multidimensional arrays in MEM, VRT, netCDF, HDF4, HDF5 and GRIB drivers. Read/write for MEM and netCDF. Read/only for others. Add gdalmdiminfo and gdalmdimtranslate utilities.
* Implement RFC76: add capability of writing vector drivers in Python
* New GDAL drivers:
- COG: write-only, for Cloud Optimized GeoTIFF
- EXR: read/write driver, relying on OpenEXR library
- ISG: read-only, for geoid models of the International Service for the Geoid
- RDB: read-only, for RIEGL Database .mpx RDB 2 files (#1538) (needs proprietary SDK)
* New OGR drivers:
- FlatGeoBuf: read-support and creation (#1742)
- MapML: read/write driver for experimental web spec
* Improved drivers:
- OAPIF driver (renamed from WFS3): updated to OGC API - Features 1.0 core spec
- GTiff: improve performance of internal overview creation
- GTiff: GeoTIFF 1.1 support
- Shapefile driver: add read/creation/update support for .shz and .shp.zip
- netCDF vector: read/write support for CF-1.8 Encoded Geometries (#1287)
- VICAR: multiple improvements and write support (#1855)
- DDS: add read support
* Other improvements:
- gdalwarp: accept output drivers with only CreateCopy() capabilities
- gdal_viewshed: new utility for viewshed algorithm
* Remove GFT driver now that the online service no longer exists (#2050)
* New Sphinx-based documentation
* Multiple security related fixes (ossfuzz)
* Continued code linting (cppcheck, CoverityScan, etc.)
* Compatibility with GDAL 3.0:
- C and C++ API: backward compatible changes
- C ABI: backward compatible changes
- C++ ABI: modified
- Functional changes: see MIGRATION_GUIDE.TXT
gdal-lib does not make stability guarantees and this was a major
release, with a shlib bump. In the absence of an argument that older
versions are ok, move depends up to 3.0.0.
Summary of upstream NEWS:
* many bug fixes
== Major changes in 3.x
* Implement RFC 73: Integration of PROJ6 for WKT2, late binding
capabilities, time-support and unified CRS database. PROJ >= 6 is
now a build requirement
https://trac.osgeo.org/gdal/wiki/rfc73_proj6_wkt2_srsbarn
* New GDAL drivers:
- DAAS: read driver for Airbus DS Intelligence Data As A Service
- TileDB: read/write driver for https://www.tiledb.io (#1402)
* New OGR drivers:
- MongoDBv3: read/write driver using libmongocxx v3.4.0 client (for MongoDB >= 4.0)
* Improved drivers:
- FITS: read/write support for scale, offset and CRS
- netCDF: read support for groups
- PDF: add a COMPOSITION_FILE creation option to generate a complex document
- PDS4: subdataset creation support, read/write table/vector support
* Support for minimal builds on Unix (#1250)
* Add a docker/ directory with Dockerfile for different configurations
* Continued code linting
== New installed files ==
* Resource file: pdfcomposition.xsd
== Removed installed files ==
* Removal of resource files related to EPSG and ESRI CRS databases:
compdcs.csv, coordinate_axis.csv, datum_shift.csv, ellipsoid.csv,
esri_epsg.wkt, esri_extra.wkt, esri_Wisconsin_extra.wkt, gcs.csv,
gcs.override.csv, gdal_datum.csv, geoccs.csv, pcs.csv,
pcs.override.csv, prime_meridian.csv, projop_wparm.csv,
unit_of_measure.csv, vertcs.csv, vertcs.override.csv
== Backward compatibility issues ==
MIGRATION GUIDE FROM GDAL 2.4 to GDAL 3.0
-----------------------------------------
- Substantial changes, sometimes backward incompatible, in coordinate reference
system and coordinate transformations have been introduced per
https://trac.osgeo.org/gdal/wiki/rfc73_proj6_wkt2_srsbarn
* OSRImportFromEPSG() takes into account official axis order.
Traditional GIS-friendly axis order can be restored with
OGRSpatialReference::SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER);
* Same for SetWellKnownGeogCS("WGS84") / SetFromUserInput("WGS84")
* removal of OPTGetProjectionMethods(), OPTGetParameterList() and OPTGetParameterInfo()
No equivalent.
* removal of OSRFixup() and OSRFixupOrdering(): no longer needed since objects
constructed are always valid
* removal of OSRStripCTParms(). Use OSRExportToWktEx() instead with the
FORMAT=SQSQL option
* exportToWkt() outputs AXIS nodes
* OSRIsSame(): now takes into account data axis to CRS axis mapping, unless
IGNORE_DATA_AXIS_TO_SRS_AXIS_MAPPING=YES is set as an option to OSRIsSameEx()
* ogr_srs_api.h: SRS_WKT_WGS84 macro is no longer declared by default since
WKT without AXIS is too ambiguous. Preferred remediation: use SRS_WKT_WGS84_LAT_LONG.
Or #define USE_DEPRECATED_SRS_WKT_WGS84 before including ogr_srs_api.h
== GDAL/OGR 3.0.0 - General Changes ==
* PROJ >= 6.0 is a required external dependency
* libgeotiff >= 1.5 should be used for builds with external libgeotiff
Rather than adding a definition of _NETBSD_SOURCE, avoiding defining
_XOPEN_SOURCE in the first place. What used to be extra is now
normal, and these defines hide rather than expose symbols.
Because gdal-lib depends unconditionally on geograpy/proj, which depends
unconditionally on sqlite3, it doesn't make sense dependency-wise to
conditionally omit sqlite3 support here.
(Also update py-gdal as it shares the distfile.)
Note that the upgrade to 3.0.x is pending evaluation of impact on
depending packages.
Upstream changes: basically bugfixes.
= GDAL/OGR 2.4.0 Release Notes =
== In a nutshell... ==
* New GDAL drivers:
- BYN: read/write support for Natural Resources Canada's Geoid binary format
- EEDAI: read-only driver for Google Earth Engine Data API
- IGNFHeightASCIIGrid: read-only driver to read IGN-France height correction ASCII grids
- NGW: NextGIS Web read-only driver
- NTv1: read-only driver for NTv1 datum shift grids
* New OGR drivers:
- EEDA: read-only driver for Google Earth Engine Data API
- GeoJSONSeq: read/creation support of new-line or record-separator separated GeoJSON features (#378)
- NGW: NextGIS Web read-write driver
* Improved drivers:
- BAG: add read support for variable-resolution grids, and write support for single-resolution grids
- GTiff driver: add Lerc and WebP codecs
- PostgisRaster: add support for out-db rasters
- RMF
- MSSQLSpatial
* RFC 72: Make GDAL Python autotest suite use pytest framework
* Add /vsihdfs/ virtual file system handler for Hadoop File System (via libhdfs)
* Add /vsiwebhdfs/ read-write virtual file system for Web Hadoop File System REST API
* gdal_contour rewriting: speed optimizations and capability to compute polygon isosurfaces.
* Remove PHP and Ruby bindings.
* Continued code linting in C++, Python scripts, Shell scripts and autotest
== Backward compatibility issues ==
* The value of COMPRESSION_ZSTD used for ZStd-in-TIFF compression has been changed. ZStd-compressed TIFF files produced by GDAL 2.3.0 will not be readable
2.3.3: bug fixes and minor improvements
2.3.2: bug fixes and minor improvements
2.3.1: bug fixes and minor improvements
= GDAL/OGR 2.3.0 Release Notes =
Note: due to the change of SCM during the development, #XXXX still refers to
Trac tickets. GitHub tickets are explicitly indicated with github #XXXX
== In a nutshell... ==
* New GDAL drivers:
- PDS4: read/write
- RDA: DigitalGlobe Raster Data Access (read-only)
* New OGR drivers:
- MVT: add read/write driver for Mapbox Vector Tile standalone files or tilesets
- ESRIJson and TopoJSON: read-only, splitted from existing code of the GeoJSON driver
- WFS3: *experimental* read-only driver
* RFC 68: Make C++11 a build requirement
https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11
* RFC 70: Guess output format from extension of output filename, if no explicit format passed to C++ or Python utilities
https://trac.osgeo.org/gdal/wiki/rfc70_output_format_guess
* RFC 71: Move to GitHub for source code repository and issue tracker.
https://trac.osgeo.org/gdal/wiki/rfc71_github_migration
* Significantly improved drivers:
- MBTiles (vector tiles support)
- DXF
- GRIB (GRIB2 write support)
- WCS (support WCS 2.0)
* Improvements in network-based /vsi handlers: /vsicurl, /vsis3, /vsigs. Add:
- /vsiaz for Microsoft Azure Blobs
- /vsioss for Alibaba Cloud Object Storage Service
- /vsiswift/ for OpenStack Swift object storage
* Command line utilities: use Unicode main on Windows to avoid issues with non-ASCII characters (#7065)
* Update to EPSG v9.2 (#7125)
* Update data/esri_extra.wkt and add data/esri_epsg.wkt, taken from https://github.com/Esri/projection-engine-db-doc (Apache v2 license) (#2163)
* Add support for PROJ.5 new API (requires proj 5.0.1 or later). PROJ 4.X is still supported.
* More than 1000 fixes for issues/vulnerabilities found by OSS-Fuzz
* Remove raster OGDI driver (vector OGDI driver still there) (#7087)
== New installed files ==
* data/pds4_template.xml
* data/esri_epsg.wkt
== Backward compatibility issues ==
See MIGRATION_GUIDE.TXT
Note that changes are extensive; see NEWS in the distfile.
Without an explicit request, configure says that proj is "dynamic" and
I can't tell if it is used. With the request, configure says that
proj is "static" and then the build proceeds to dynamically link proj
in the normal manner.
It is possible that gdal operations will behave differently now, if
reference system transformations were skipped before.
(This revbump should not be necessary, because goes's public ABI did
not change. Due to a misfeature/bug in libtool, linking against the
stable geos C API results in a directed NEEDED entry on the unstable
C++ library.)
together with libtool causing gdal's installed library to directly
depend on the C++ ABI.
CVS: ----------------------------------------------------------------------
CVS: CVSROOT cvs.NetBSD.org:/cvsroot
CVS: please use "PR category/123" to have the commitmsg appended to PR 123
