Hi Even,
> I have run this command with gdal 3.4.3 and gdal 3.5.1 and get different
> output files.
Can you compare the output of the two versions of gdalinfo ?
This should determine whether the difference is when reading or writing.
Good idea, I did that and there is no difference in the output
Moises,
I've not reviewed in depth the MITAB driver, but reading from a .tab
file may require random access, and it is thus not surprising that
reading from a compressed file may exhibit poor performance. You might
try to set the VSI_CACHE config option / env variable to YES, but no
guarantee
Le 27/07/2022 à 17:03, Matthew Savoie a écrit :
Hi Andrew,
> I have run this command with gdal 3.4.3 and gdal 3.5.1 and get
different output files.
Can you compare the output of the two versions of gdalinfo ?
This should determine whether the difference is when reading or writing.
Good ide
Hi Andrew,
> I have run this command with gdal 3.4.3 and gdal 3.5.1 and get different
> output files.
Can you compare the output of the two versions of gdalinfo ?
This should determine whether the difference is when reading or writing.
Good idea, I did that and there is no difference in the outp
Hi,
I have compiled GDAL to enable PGeo, and now I have it in --formats.
But if I run "ogrinfo PGeo:input.mdb", I have
ERROR 1: PGeo: MDB Tools driver not found!
Warning 1: Unable to install MDB driver for ODBC, MDB access may not
supported.
ERROR 1: Unable to initialize ODBC connection to DSN fo
Hi,
I have solved it, adding "--with-pgeo=yes"
Thank you to Richard Greenwood for the private email about it.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi everyone!
We're using ogr2ogr to convert MapInfo TAB files into CSV format using the
following command:
ogr2ogr -f CSV -skipfailures -makevalid /vsistdout/ /vsizip/onLDU.zip -oo
> AUTODETECT_TYPE=YES -lco CREATE_CSVT=YES > test_2.csv
The file weights ≈200 MB and the process is taking too mu
