Gdal

* fix ResetReading() implementation, when using the ParquetDataset API and
when there's a single batch
* fix opening single file Parquet datasets with the ParquetDataset API when
using PARQUET:filename.parquet

PGDUMP driver:
* add a LAUNDER_ASCII=YES/NO (default NO) layer creation option

PMTiles driver:
* handle decompressing data with a compression ratio > 16 (9646)

PostgreSQL driver:
* serialize GDAL multidomain metadata of layer as XML in a
ogr_system_tables.metadata table
* be robust to inexact case for schema when creating a layer
'schema_name.layer_name' (9125)
* remove support for PostgreSQL < 9 and PostGIS < 2 (8937)
* add a LAUNDER_ASCII=YES/NO (default NO) layer creation option

Shapefile driver:
* Shapelib: resync with upstream
* GetNextArrowArray(): add specialized implementation restricted to situations
where only retrieving of FID values is asked
* make it recognize /vsizip/foo.shp.zip directories
* add read/write support for DBF Logical field type mapped to OGR OFSTBoolean

VFK driver:
* Fix solving circle parcel geometry (8993)

SWIG Language Bindings

All bindings:
* add osr.SpatialReference.ImportFromCF1(), ExportToCF1(), ExportToCF1Units()
* expose Geometry.UnaryUnion()
* expose OLCFastWriteArrowBatch
* add gdal.IsLineOfSightVisible()

CSharp bindings:
* Exposes additional Dataset methods (918, 9398)

Java bindings:
* bump minimum version to Java 8

Python bindings:
* lots of improvements to documentation
* add a pyproject.toml with numpy as a build requirement (8926, 8069)
* pyproject.toml: use numpy>=2.0.0rc1 for python >=3.9 (9751)
* bump setuptools requirement to >= 67.0
* define entry_points.console_scripts (8811)
* add RasterAttributeTable::ReadValuesIOAsString, ReadValuesIOAsInteger,
ReadValuesIOAsDouble, RemoveStatistics()
* implement ``__arrow_c_stream__()`` interface for ogr.Layer
* add a ogr.Layer.GetArrowArrayStreamInterface() method
* add a ogr.Layer.WriteArrow() method consuming ``__arrow_c_stream__`` or
``__arrow_c_array__`` interfaces (9132)
* Invalidate layer ref when Dataset closes
* Accept str arg in FeatureDefn.GetFieldDefn
* Add Band.ReadAsMaskedArray
* Make gdal/ogr.GeneralCmdLineProcessor accept int, os.PathLike
* Avoid crash when accessing closed file

GDAL/OGR 3.8.0 Releases Notes

GDAL/OGR 3.8.0 is a feature release.
Those notes include changes since GDAL 3.7.0, but not already included in a
GDAL 3.7.x bugfix release.

In a nutshell...

* Add [JSONFG](https://gdal.org/drivers/vector/jsonfg.html) read/write vector
driver for OGC Features and Geometries JSON.
* Add [PMTiles](https://gdal.org/drivers/vector/pmtiles.html) read/write vector
driver for PMTiles v3 datasets containing MVT PBF tiles
* Add [S102](https://gdal.org/drivers/raster/s102.html) raster read-only driver
for S-102 bathymetric products (depends on libhdf5)
* Add [gdal_footprint](https://gdal.org/programs/gdal_footprint.html) utility:
compute the footprint of a raster file, taking into account nodata/mask band,
and generating polygons/multipolygons corresponding to areas where pixels are
valid (6264)
* Python bindings: various enhancements to reduce the number of "gotchas"
related to inter-object ownership relationships, and a few syntaxic sugar
enhancements
* Arrow interface: improve spatial and attribute filtering on read side;
add write side with OGRLayer::WriteArrowBatch()
* GeoPackage: much faster spatial index creation (~ 3-4 times faster)
* ARG driver deprecated: will be removed in 3.9.0

Backward compatibility issues

See [MIGRATION_GUIDE.TXT](https://github.com/OSGeo/gdal/blob/release/3.8/MIGRATION_GUIDE.TXT)

New optional dependencies

* libaec to enable CCSDS Adaptive Entropy Coding decompression in the GRIB driver

Build

* emit better error message when a raster driver cannot be enabled
because of OGR_BUILD_OPTIONAL_DRIVERS=OFF
* improve static linking for CURL and EXPAT
* Java bindings: change default installation directory of JNI shared
library and control it with GDAL_JAVA_JNI_INSTALL_DIR
* automatically enable SQLite driver if -DOGR_ENABLE_DRIVER_GPKG=ON
* Don't use libjpeg if disabled (and libjpeg-turbo >= 3.0 available) (8336)
* gdal.pc generation: use CMAKE_INSTALL_INCLUDEDIR/CMAKE_INSTALL_LIBDIR for
includedir/libdir (8012)
* gdal-config: add a --plugindir switch (8012)

a) cd $BUILD_DIR/swig/python/gdal-utils

b) python3 setup.py bdist_wheel

c) Check the output:
twine check dist/gdal_utils-*.whl

c) For trial :
twine upload dist/gdal_utils-*.whl -r pypitest

d) For real :
twine upload dist/gdal_utils-*.whl

16) Generate signed maven artifacts with GPG for Java bindings.
This step is required in order to deploy the
maven artifacts to the central Maven repository. Before this step can
proceed you must set up a signing key as described here:

http://central.sonatype.org/pages/working-with-pgp-signatures.html

a) Each developer can use their own signing key although it is usually best to
avoid constantly using a different key for releases as users will need to
import the public key in order to verify the artifacts.

Here are a quick set of steps to generate a signing key key.

gpg --gen-key
gpg --list-keys (and note the key id)
gpg --keyserver hkp://pool.sks-keyservers.net --send-keys <key id>

See the above link for more details.

b) Run CMake with the following variables:

1. GPG_KEY: the identifier for the signing keys
2. GPG_PASS: the passphrase for the signing key (optional)

c) Build the bindings: make java_binding

Upon success you should see a file named "swig/java/build/maven/bundle.jar"
that contains all the maven artifacts with signatures. This file is what
will be uploaded to maven central. See the next step.

17) Deploy maven artifacts to Maven central.

NOTE: Before you can deploy to maven central you must set up an account
in Sonatype JIRA. That can be done here:

https://issues.sonatype.org/secure/Signup!default.jspa

Once you have an account set up you must be associated with the gdal
project. Create a ticket here asking to be associated with the project:

https://issues.sonatype.org/browse/OSSRH

The entire deployment process is described in detail here:

http://central.sonatype.org/pages/manual-staging-bundle-creation-and-deployment.html
http://central.sonatype.org/pages/releasing-the-deployment.html

The following steps summarize the process.

a) Log into the Sonatype repository manager at https://oss.sonatype.org. Use the
same credentials as your Sonatype JIRA account.

b) Once log in select "Staging Upload" on the left hand side.

c) Select "Artifact Bundle" under "Upload Mode" and then choose the "bundle.jar"
created in the previous Step 22. Finally "Upload Bundle" to start the upload.

d) When the upload has been completed you will be notified that a staging
repository has been created. Note the name of the repository. It should look
something like "orggdal-100x".

e) From the left hand menu navigate to "Staging Repositories". In the search
box look for the staging repository name you noted from the previous section.
Or just search for "gdal". It should be obvious which repository is the
current one.

f) Select the staging repository. If all is well You should see the option to
"Release" (Located as a button near the top of the page). If not it means
there was an issue with the bundle. Consult the "Activity" tab at the bottom
of the page to find out why.

e) Click the "Release" button and that is it! The release should be available in
Maven Central shortly. You can verify this by going to search.maven.org and
searching for "gdal".

18) Create a release on GitHub
Go to https://github.com/OSGeo/gdal/releases/new
And create a release for the vX.Y.Z tag
Attach the following files:
- gdal-X.Y.Z.tar.gz
- gdal-X.Y.Z.tar.gz.sig
- gdal-X.Y.Z.tar.gz.md5
- gdalXYZ.zip
- gdalXYZ.zip.sig
- gdalXYZ.zip.md5
- gdalautotest-X.Y.Z.zip

19) Regenerate Docker images

e.g
./docker/build-all.sh --with-multi-arch --release --tag 3.3.1 --gdal v3.3.1 --proj 8.1.0 --platform linux/arm64,linux/amd64 --push

and update docker/README.md with the latest release

20) Announce release to :
- major release: gdal-devlists.osgeo.org, gdal-announcelists.osgeo.org, news_itemosgeo.org.
- bugfix release: gdal-devlists.osgeo.org, gdal-announcelists.osgeo.org

Example:
- bugfix release: https://lists.osgeo.org/pipermail/gdal-dev/2019-July/050543.html
- feature release: https://lists.osgeo.org/pipermail/gdal-dev/2020-May/052117.html

Note: gdal-announce is moderated. Make sure that your email address is approved
('mod' tick disabled in https://lists.osgeo.org/mailman/admin/gdal-announce/members),
or your message manually approved, with an administrator of the list.

21) For a feature release: after it has been done, in the master branch, update
the VERSION to the next one and in gcore/gdal_version.h.in, update
GDAL_VERSION_MAJOR/_MINOR, GDAL_RELEASE_NAME (with a dev suffix, like "3.7.0dev"),
and set GDAL_RELEASE_DATE to a date like {YEAR}9999.
Update swig/python/gdal-utils/osgeo_utils/__init__.py to something like (3, 6, 99, 0)
if master is 3.7.0dev



GDAL/OGR 3.9.0 Releases Notes

GDAL/OGR 3.9.0 is a feature release.
Those notes include changes since GDAL 3.8.0, but not already included in a
GDAL 3.8.x bugfix release.

In a nutshell...

* [RFC 96](https://gdal.org/development/rfc/rfc96_deferred_plugin_loading.html):
Deferred C++ plugin loading
* [RFC 97](https://gdal.org/development/rfc/rfc97_feature_and_fielddefn_sealing.html):
OGRFeatureDefn, OGRFieldDefn and OGRGeomFieldDefn "sealing"
* [RFC 98](https://gdal.org/development/rfc/rfc98_build_requirements_gdal_3_9.html):
Build requirements for GDAL 3.9
* [RFC 99](https://gdal.org/development/rfc/rfc99_geometry_coordinate_precision.html):
Geometry coordinate precision
* Add [S104](https://gdal.org/drivers/raster/s104.html) (Water Level Information
for Surface Navigation Product) and
[S111](https://gdal.org/drivers/raster/s111.html) (Surface Currents Product)
raster read-only drivers (required libhdf5)
* Add raster [GTI](https://gdal.org/drivers/raster/gti.html) (GDAL Raster Tile
Index) driver to support catalogs with huge number of sources.
* Add vector [MiraMonVector](https://gdal.org/drivers/vector/miramon.html)
read/creation driver (9688)
* Deprecated ARG driver has been removed (7920)
* Code linting

Build

* CMake: add ``[GDAL|OGR]_REGISTER_DRIVER_<driver_name>_FOR_LATER_PLUGIN``
variables (RFC 96)
* CMake: Bump max compatible version to 3.28
* CMake: add a way of defining an external deferred driver by setting one or
several ADD_EXTERNAL_DEFERRED_PLUGIN_XXX CMake variables (RFC 96)
* CMake: error out if a driver has been asked as a plugin, but conditions are not met
* CMake: rework PROJ detection
* CMAKE_UNITY_BUILD=YES builds are possible, but not recommended for production
* gdal.cmake: set -DDEBUG for CMAKE_BUILD_TYPE=Debug for Windows builds as well
* CMake: add GDAL_FIND_PACKAGE_OpenJPEG_MODE and GDAL_FIND_PACKAGE_PROJ_MODE
variables
* FindSQLite3.cmake: avoid repeating finding `SQLite3_INCLUDE_DIR`/
`SQLite3_LIBRARY` if existed.
* Add compatibility for Intel Compiler 2024.0.2.29

Backward compatibility issues

See [MIGRATION_GUIDE.TXT](https://github.com/OSGeo/gdal/blob/release/3.8/MIGRATION_GUIDE.TXT)

Changes in installed files

* data/MM_m_idofic.csv: new
* data/gdalvrtti.xsd: new
* data/pci_datum.txt and data/pci_ellips.txt: updated (8034)
* include/cpl_minizip_ioapi.h, cpl_minizip_unzip.h, cpl_minizip_zip.h:
removed. They use since 3.5 an header that is not installed, so were unusable

a) Create a build directory if not already done. Go to it and run cmake

b) cd $BUILD_DIR/swig/python

c) python3 setup.py sdist

d) Check the output (this assumes setuptools >= 65.3.0, otherwise the filename is GDAL-*.gz):
twine check dist/gdal-*.gz

e) For trial :
twine upload dist/gdal-*.gz -r pypitest

f) For real :
twine upload dist/gdal-*.gz

a) Install twine https://pypi.org/project/twine/

b) Create a $HOME/.pypirc file :

[distutils] this tells distutils what package indexes you can push to
index-servers = pypi
pypitest

[pypi] authentication details for live PyPI
repository: https://upload.pypi.org/legacy/
username: yourlogin
password: yourpassword

[pypitest] authentication details for test PyPI
repository: https://test.pypi.org/legacy/
username: yourlogin
password: yourpassword

Remove the RC suffixes for the final RC, like:
mv gdal-3.8.3rc1.tar.xz gdal-3.8.3.tar.xz
mv gdal-3.8.3rc1.tar.xz.md5 gdal-3.8.3.tar.xz.md5
mv gdal-3.8.3rc1.tar.xz.sig gdal-3.8.3.tar.xz.sig
mv gdal-3.8.3rc1.tar.gz gdal-3.8.3.tar.gz
mv gdal-3.8.3rc1.tar.gz.md5 gdal-3.8.3.tar.gz.md5
mv gdal-3.8.3rc1.tar.gz.sig gdal-3.8.3.tar.gz.sig
mv gdal383rc1.zip gdal383.zip
mv gdal383rc1.zip.md5 gdal383.zip.md5
mv gdal383rc1.zip.sig gdal383.zip.sig
mv gdalautotest-3.8.3rc1.tar.gz gdalautotest-3.8.3.tar.gz
mv gdalautotest-3.8.3rc1.zip gdalautotest-3.8.3.zip

And edit the .md5 file to remove the reference to RC in the names they contain
vim gdal-3.8.3.tar.gz.md5
vim gdal-3.8.3.tar.xz.md5
vim gdal383.zip.md5

Check that everything is fine:
md5sum -c *.md5

11.3) In /osgeo/download/gdal, add a symlink from X.Y.Z to CURRENT (except for stable releases in a "old" branch).

% ln -sf X.Y.Z CURRENT

12) (Removed)

13) Update doc/source/about_no_title.rst and doc/source/download.rst to advertise the new release and link to the release notes

14) Update GitHub to close the release milestone.
Then create a new milestone for the next release.

15) Upload the new Python bindings to Pypi (requires upload rights to
the GDAL package by one of the current owners : HowardB/FrankW/EvenR)
( procedure taken from http://peterdowns.com/posts/first-time-with-pypi.html )

git checkout v3.1.0RC1
git tag -a -m "Create tag v3.1.0" v3.1.0
git push origin v3.1.0