Yep, it is easier to build your process with a listing step that you'll
feed to gdalbuildvrt. For example, on our win10 env it works with
tamas' gisinternal build with cmd but not with the conda build and cmd
:)
Le vendredi 05 février 2021 à 08:58 -0700, Richard Greenwood a écrit :
> I think that
I think that wildcard expansion has been an on and off problem with some of
the GDAL utilities on Windows. If you Google "gdalbuildvrt wildcard
expansion" you'll find at least three tickets, the most recent of which is:
https://github.com/OSGeo/gdal/issues/1749
I think the safest and easiest is to
On Thu, 4 Feb 2021 at 23:22, Simon Shak wrote:
>
> However, your suggestion to check the filelist.txt file has found the error.
> Somehow a trailing space was before the CRLF and caused it to not recognize
> the file.
There also could be an issue if there are spaces in file names.
I don't know
if I try to use wildcard:
gdalbuildvrt output.vrt input/*.ecw
I get the error:
ERROR 4: `input/*.ecw' does not exist in the file system, and is not
recognized as a supported dataset name.
it doesn't matter if I use / or \ or * or *.ecw or *.*.
My expectation based on the documentation and previous
On Thu, 4 Feb 2021, 23:02 Simon Shak, wrote:
>
> If I do it straight via commandline as:
> for %f in (input\*.ecw) do (gdalbuildvrt output.vrt %f)
> I wind up with a VRT with only one of the several hundred files in it.
>
Yes, that's expected, isn't it.
if I try it using a file list by first:
I'm working on using the gdal2tiles to convert a mosaic of ECW files into
TMS format.
Since the gdal2tiles command needs a single input file, I'm building VRT's
to use as the input.
I have gotten this to work on ons set of files. When I do the same
commands for the second set of files, gdalbuildvr
