Conversation
- for GDAL 3.13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gdalcli 0.7.0 (2026-05-09)
gdal_raster_edit,gdal_vector_edit) viaGDAL_INTENT_MAPPINGS.jsonwith customizable overridesgdal_call()for dynamic/programmatic GDAL command invocation by name or function reference, enabling metaprogramming, serialization, and boilerplate reduction for repetitive command patterns. Includesgdal_list_callable_commands()for command discovery with type filteringgdal_compose()convenience function (deprecated since 0.4.x). Use pipe operator (|>) instead:job1 |> job2 |> job3 |> gdal_job_run()"auto"mode. Specify explicit backend withoptions(gdalcli.backend = "processx")or"gdalraster"