Hi Luca,
I follow your advice and now I have all my features. I had to do some
union/collect to have the awaited result.
It's just sad that I can't take more advantage of GDAL to do this : do we
know why my first method can't work ? Because of a limitation in
ST_GeomFromText ? Because of a limita
Derek,
Can you provide a screenshot of the displayed image. Especially the
scrambled blocks.
On Tue, Jun 14, 2011 at 4:22 AM, Cole, Derek wrote:
> Hello,
>
> I have the following code:
>
> qDebug("tilePosX: %i ", this->tilePosX);
> qDebug("tilePosY: %i ", this->tilePosY);
>
>
> floa
Hello,
I have the following code:
qDebug("tilePosX: %i ", this->tilePosX);
qDebug("tilePosY: %i ", this->tilePosY);
float * floatData = (float *) CPLMalloc(sizeof(float)*nXSize*nYSize);
poBand->RasterIO( GF_Read, this->tilePosX*nXSize, this->tilePosY*nYSize,
nXSize, nYSize, flo
On 11-06-13 04:53 PM, Alex Mantaut wrote:
Hi all:
I've ran into some troubles while trying to interpret an HDF5's
metadata...
Every field on HDF5 has it's own type(string, uchar, double) But
GetMetadataItem("field_name") converts the data from the dataset into a
C-style zero terminated
Hi all:
I've ran into some troubles while trying to interpret an HDF5's
metadata...
Every field on HDF5 has it's own type(string, uchar, double) But
GetMetadataItem("field_name") converts the data from the dataset into a
C-style zero terminated string.
This gives me a few problems:
a-T
Hi Elijah,
With regards to the CRT dependency I would always recommend to use that
version which corresponds to the CRT dep. of the application. You might use
the Dependency Walker tool to identify which CRT dll the application depends
on. For example the official python (python.org) windows build
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 GDALReg
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
Hi Tamas and GDAL devs,
I recently used Tamas' Win binaries (http://www.gisinternals.com/sdk/)
to install Gdal 1.8 for Python 2.7, and everything is working fine---Tamas,
thanks so much for providing those.
However, I do have a question about selecting the correct release, and
want to confirm
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/tra
Hi Alexandre,
if I well understood your problem, you're already doing half of the job
(the queries)in PostGIS, so why not doing everything using PostGIS
queries?
Moreover, I think you don't need union.
Assuming towns is a polygon layer, try:
select distinct t.* from
towns as t,
(select dist
Hi,
I need to do the following request to find some data:
- I have a bunch of towns (let's call them group A)
- I retrieve the towns touching the group A (let's call them group B)
- I make the union of group A and group B
- I ask the towns covered by the resulting union
For the moment, I use GDA
12 matches
Mail list logo
