Is there some trick to enabling this driver with the old non-CMake build
env...? :)
I am building OpenJPEG 2.5.0 (from source) and it's building and installing
fine into the same include/lib tree as everything else, and then GDAL
configure (just adding *--with-openjpeg*, no path, right?) sees it a
This RFC seems to have some things in common with the direct access to
compressed raster blocks. Both by-pass the older raster and vector
data models, yes? And they're quite specific to certain formats. Do
you anticipate that GDAL and OGR will continue to develop more
specialty APIs in addi
Hi Even,
I'm glad you mentioned a shift of concepts. The older Feature API and new
Arrow API are really quite different. I actually don't know how often I
will ever combine them in one program, for example to turn shapefiles into
a huge Parquet file or the reverse. If anybody is doing this kind of
Hi,
I've captured in the RFC text the interesting discussion points. As I
don't see a clear way forward for this RFC that offers a good balance
between usefulness, efficiency, elegance and level of effort to
implement, I'll commit the RFC text with a "on hold" status.
Even
Le 31/01/2023 à 1
Thanks Even!
On 2/12/23 08:36, Even Rouault wrote:
Implemented in https://github.com/OSGeo/gdal/pull/7235
Le 12/02/2023 à 17:16, Scott a écrit :
The hope was to have the gdal_rasterize -sql switch work like it does
in the other gdal utilities, ie, -sql @/path/to/source.sql. That
consistency
Implemented in https://github.com/OSGeo/gdal/pull/7235
Le 12/02/2023 à 17:16, Scott a écrit :
The hope was to have the gdal_rasterize -sql switch work like it does
in the other gdal utilities, ie, -sql @/path/to/source.sql. That
consistency would be really nice.
All my .sql files live in a si
The hope was to have the gdal_rasterize -sql switch work like it does in
the other gdal utilities, ie, -sql @/path/to/source.sql. That
consistency would be really nice.
All my .sql files live in a single directory and things are structured
around the @ syntax. Further, these .sql quieries can
Hi,
Optfile will work if you use it right. Optfile is flexible and it can be used
for anything, not only for saving a SQL query into a file. Therefore optfile
must have the same literal content that user would write by hand to the
command. With optfile
optfile.txt
-sql "select * from
