[gdal-dev] gdallocationinfo issues, after 3.9.2
Even Rouault
even.rouault at spatialys.com
Tue Jul 8 12:18:24 PDT 2025
Please file a ticket, ideally with a dataset to reproduce
Le 08/07/2025 à 20:55, Scott via gdal-dev a écrit :
> Say you have a file called raster.vrt. In that file are 15 tif's. 9 of
> those rasters don't have data (nodata) at the specified lon/lat:
>
> gdallocationinfo -geoloc -valonly -field_sep "," rasters.vrt
> -88.730767 32.649060
>
> The above may return 6 values, with or without -field_sep:
> 26,2,2,0,3.10467481613159,32.7341842651367,1433
>
> You have no idea which tif those values belong to. In versions 3.9.2
> or earlier, it returns the 'nodata' value for each tif. Not only is
> nodata a valid value, it acts as a place holder. 15 rasters, 15 values
> returned.
>
> Yes, you can remove the -valonly switch and use -xml, but then it
> becomes a parsing debacle. Unnecessary code and overhead.
>
> Apologies for being a pain. I just rolled 3.11.1 and now 3.11.2 into
> production, up from 3.9.2 and it's breaking stuff I did not
> anticipate. :)
>
> Thank you!
> Scott
>
--
http://www.spatialys.com
My software is free, but my time generally not.
More information about the gdal-dev
mailing list