Yes, it does! Thank you very much for the quick fix!
On Wed, 21 Aug 2019 at 15:37, Even Rouault
wrote:
> > So I think, the (already hefty) `if` clause could just be expanded to
> also
> > allow spaces in the separators and we would be fine.
>
> Good catch. Does the following commit fixes the iss
> So I think, the (already hefty) `if` clause could just be expanded to also
> allow spaces in the separators and we would be fine.
Good catch. Does the following commit fixes the issue ?
https://github.com/rouault/gdal/commit/89cbc8f59e39f15b523a912984be8cb265c61953
Even
--
Spatialys - Geospa
Hi Even,
Thanks for your quick response!
The issue is not that we are dealing with POSIX TAR files (which actually
seems to be handled fine with GDAL 3.1, when we created them using `tar
--format=pax`).
The issue seems to be the handling of the file user/group separator.
Looking at the code, the
Fabian,
/vsitar/ has indeed no dedicated support for POSIX.1-2001 (pax)
On a very simple test with a tiny file from GDAL autotest,
tar --format=pax --create -f byte_pax.tar byte.tif
then gdalinfo /vsitar/byte_pax.tar/byte.tif works.
But I see that GDAL sees an extra text file "PaxHeaders.25680
Hi list,
We have a large archive of images which are stored in POSIX TAR format
(POSIX.1-2001 (pax)). GDAL seems to be unable to open these files (GDAL
2.4.0). Unfortunately, re-packing these files in GNU format (which GDAL
seems to be happy with) is not an option.
We also tried with the latest D
