Understood, and good reason to start using the new gdalinfo convenience option 
"-sd" for selecting sub-datasets by their index.

gdalinfo 
"STACIT:\https://paituli.csc.fi/geoserver/ogc/stac/v1/search?collections=corine_land_cover_at_geocubes\<https://paituli.csc.fi/geoserver/ogc/stac/v1/search?collections=corine_land_cover_at_geocubes%5C>"
 -sd 2

-Jukka-

Lähettäjä: Even Rouault <[email protected]>
Lähetetty: torstai 21. marraskuuta 2024 18.36
Vastaanottaja: Rahkonen Jukka <[email protected]>; Daniel 
Evans <[email protected]>
Kopio: '[email protected]' ([email protected]) 
<[email protected]>
Aihe: Re: [gdal-dev] Issue with the STACIT usage examples




However, the subdataset names on the list are not accepted as-is without small 
edits.
Does not work:
gdalinfo 
STACIT:"https://paituli.csc.fi/geoserver/ogc/stac/v1/search?collections=corine_land_cover_at_geocubes";<https://paituli.csc.fi/geoserver/ogc/stac/v1/search?collections=corine_land_cover_at_geocubes>:asset=1000m

That's "expected". Subdataset names are designed to be used verbatim by 
GDALOpen(). The STACIT driver isn't aware it has been invoked from a shell and 
which quoting rules would apply.



--

http://www.spatialys.com<http://www.spatialys.com/>

My software is free, but my time generally not.

Butcher of all kinds of standards, open or closed formats. At the end, this is 
just about bytes.
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to