With GDAL 3.11 the command-line interface has been significantly redesigned around a single, unified command structure, inspired by tools like Git and Docker.
Instead of multiple standalone utilities (gdalinfo, gdal_translate, gdalwarp, etc.), GDAL now exposes a single entry point (gdal) with well-structured subcommands, for example:
Old way
gdalinfo my.tif
gdal_translate -of COG in.nc out.tif
New way (GDAL >= 3.11)
gdal raster info --format=text my.tif
gdal raster convert --of=COG in.nc out.tif
This change reflects a deeper reorganization of how GDAL commands are exposed and composed, and it is closely tied to new internal APIs that power the modern CLI.
Does gdal-async currently support (or plan to support this new unified command model introduced in GDAL 3.11?
With GDAL 3.11 the command-line interface has been significantly redesigned around a single, unified command structure, inspired by tools like Git and Docker.
Instead of multiple standalone utilities (gdalinfo, gdal_translate, gdalwarp, etc.), GDAL now exposes a single entry point (gdal) with well-structured subcommands, for example:
Old way
New way (GDAL >= 3.11)
This change reflects a deeper reorganization of how GDAL commands are exposed and composed, and it is closely tied to new internal APIs that power the modern CLI.
Does gdal-async currently support (or plan to support this new unified command model introduced in GDAL 3.11?