On 12-05-30 5:09 PM, steve.tout...@inspq.qc.ca wrote:
>
> Hi!
> I use this command to get the tables from an ODBC connection
> ogrinfo ODBC:User/Pwd@DNS
>
> The connection is succesful but I get this error several times
> ERROR 1: No column definitions found for table '�s���s!.���',
> lay
Note that it is a non-spatial mssql database
Steve Toutant/INSPQ/
2012-05-30 16:09
A
gdal-dev@lists.osgeo.org
cc
Objet
ogr ODBC problem
Hi!
I use this command to get the tables from an ODBC connection
ogrinfo ODBC:User/Pwd@DNS
The connection is succesful but I get this error seve
Even Rouault wrote:
> There will be likely a compatibility problem if we do this, because
> GDAL up to now writes TIFF RGBA images with EXTRASAMPLE_ASSOCALPHA
> (pre-multiplied), but I think in most cases the data that people have
> feed in the GTiff driver was not pre-multiplied. So if we un-pre
Hi!
I use this command to get the tables from an ODBC connection
ogrinfo ODBC:User/Pwd@DNS
The connection is succesful but I get this error several times
ERROR 1: No column definitions found for table '�s���s!.���',
layer not usable.
I used OGR ODBC for several months from a Windows serv
Frank Warmerdam wrote:
> because it is hard to hit all the appropriate code paths safely and
> partly because the result will be lossy.
It depends on what you mean by "lossy". The value returned through the
GDAL interface won't be the literal sample value that is in a TIFF file
with associated
Hi,
I'm working with a fairly straightforward Python script to produce geodesic
buffers. One step I need is to force dateline wrapping so my buffers don't
span the globe. I poked around ogr2ogr.cpp, and found that it sets
'WRAPDATELINE=YES'. Looking into ogr.py, I see that papszOptions exists,
but
