[gdal-dev] SDE driver: connecting to rasters never returns

[Duarte Carreira]

Howard,

This is the output:

GDAL: Auto register C:\OSGeo4W\bin\gdalplugins\1.8\gdal_MG4Lidar.dll using GDALR
egister_MG4Lidar.
GDAL: Auto register C:\OSGeo4W\bin\gdalplugins\1.8\gdal_MrSID.dll using GDALRegi
ster_MrSID.
GDAL: Auto register C:\OSGeo4W\bin\gdalplugins\1.8\gdal_SDE.dll using GDALRegist
er_SDE.
SDERASTER: Open("SDE:xxx,5151,database,yyyy,zzzz,sig_owner.
MOSAIC_ORTO_10K_IGEOE,RASTER") revealed 7 tokens.
SDERASTER: SDE Column name is 'RASTER'
SDERASTER: 'sig_owner.MOSAIC_ORTO_10K_IGEOE' raster layer specified... using it
directly with 'RASTER' as the raster column name.
SDERASTER: minx: 174950.20000, miny: 99950.20000, maxx: 295049.80000, maxy: 2100
49.80000
SDERASTER: Tile origin: 174914.20000, 210083.40000
GDAL: GDALDeregister_GTiff() called.


So it stops at SDERASTER: Tile origin: ...
Because the last line appears only after pressing Ctrl-C  (GDAL: GDALDeregister GTiff).

I'm really sorry you don't have access to ArcSDE anymore... I can offer my time to test though.

Duarte

-----Mensagem original-----
De: Howard Butler [mailto:hobu.inc at gmail.com]
Enviada: segunda-feira, 13 de Junho de 2011 16:28
Para: Duarte Carreira
Cc: gdal-dev at lists.osgeo.org
Assunto: Re: [gdal-dev] SDE driver: connecting to rasters never returns


On Jun 13, 2011, at 9:38 AM, Duarte Carreira wrote:

> Hello listers.
>
> So now that OGR connecting is solved by specifying the version name (or maybe by making a readonly connection), I'm stumbling on the same effect when connecting to a raster with gdalinfo or gdal_translate. But there is no option to specify  version or readonly...
>
> My gdalinfo/translate commands never end... they keep going with 0 cpu...
>
> This is the same raster that I used when reporting #2063...
>
> One example command:
> gdal_translate -of vrt SDE:server,5151,database,user,pwd,user.MOSAIC_ORTO_10K_IGEOE,RASTER c:\temp\gdalteste.vrt
>
>
> Anyway I can debug this?

set the environment variable CPL_DEBUG=on  This should allow you to watch the connection happen and at the very least, see where it is hanging in either the SDE connection or query process.

Note that I wrote the SDE driver, but I haven't had a running SDE instance for years, and I am in no position to test. sorry.

Howard