Sorry, I was writing to .gdalalg.json trying to replicate the example
athttps://gdal.org/en/latest/programs/gdal_raster_pipeline.html#programs/gdal_raster_pipeline-2.
I was expecting it would write the file, and that in API use the
"output" dataset arg would also be opened on the GDALG, but that
p
Thanks Even.
>That could be an option. Another already existing one is to use
>GDALAlgorithmGetUsageAsJSON() on the pipeline algorithm. You'll get the step
>algorithms and their arguments under the "pipeline_algorithms" key. Please
>file a ticket if you prefer the C API.
I'll work with the JSO
Chris,
I don't see a way in the C API to obtain the pipeline algorithm step
registry or access the step algorithms to obtain their argument
properties and values. Would GetStepAlg() and related methods
potentially be exposed in the C API at some point, along with a
"GetStepRegistry"?
That could
Hi,
With the C API, pipeline algorithm can be instantiated, arguments
parsed, and the actual algorithm obtained and run. File output is
successfully generated.
I don't see a way in the C API to obtain the pipeline algorithm step
registry or access the step algorithms to obtain their argument
prope
