Hallo !
i want to make a white-border of a tif-image transparent for merge in
the next steps.
in photoshop a analyst the color like 255,255,255 = color-index 255.
the image to edit is:
Driver: GTiff/GeoTIFF
Files: C:\temp\Nordfriesland\L1516l0.tif
C:\temp\Nordfriesland\L1516l0.tfw
I am quite new to GDAL.
I want to read a big remote sensing image (tiff file format),do the digital
image process, then write the result to a tiff file. The program language is
C++.
I have finished read in the digital image file and digital image processing.
As the image file has several bands.
Ivan-5 wrote:
You can start by looking at the tutorial:
http://gdal.org/gdal_tutorial.html
The section Using Create() shows how to create new files.
Other examples in C or C++ can be found at the /apps folder.
Regards.
---Original Message---
From: cudars
cudars wrote:
I have read GDAL API Tutorial.
The Tutorial wrote Once the dataset is successfully created, all
appropriate metadata and raster data must be written to the file. What this
is will vary according to usage, but a simple case with a projection,
geotransform and raster data is covered
Hi,
In trying to build GDAL 1.6.3 and 1.7.0 on an RHEL 5 64-bit box, I'm
seeing that libtool in linking is inserting -L/usr/lib
/usr/lib/libexpat.so and provoking:
/usr/lib/libexpat.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[1]: *** [libgdal.la]
Roger Bivand wrote:
Hi,
In trying to build GDAL 1.6.3 and 1.7.0 on an RHEL 5 64-bit box, I'm
seeing that libtool in linking is inserting -L/usr/lib
/usr/lib/libexpat.so and provoking:
/usr/lib/libexpat.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
On Fri, 4 Dec 2009, Frank Warmerdam wrote:
Roger Bivand wrote:
Hi,
In trying to build GDAL 1.6.3 and 1.7.0 on an RHEL 5 64-bit box, I'm seeing
that libtool in linking is inserting -L/usr/lib /usr/lib/libexpat.so and
provoking:
/usr/lib/libexpat.so: could not read symbols: File in wrong
I think the year for GDAL 1.7.0 should be 2009, instead of 2008. Greg
On Dec 4, 2009, at 12:16 PM, Roger Bivand wrote:
$ gdalinfo --version
GDAL 1.7.0dev, released 2008/11/26
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
Patrik,
The code you mentioned did't appear to do correct mashaling with the buffer
passed to gdal.
You might want to use the following readraster signature instead:
public OSGeo.GDAL.CPLErr ReadRaster(int xOff, int yOff, int xSize, int
ySize, short[] buffer, int buf_xSize, int buf_ySize, int
Frank Warmerdam wrote:
cudars wrote:
I have read GDAL API Tutorial.
The Tutorial wrote Once the dataset is successfully created, all
appropriate metadata and raster data must be written to the file. What
this
is will vary according to usage, but a simple case with a projection,
python 3.1.1
gdal 1.6.2
There are no errors during I built the gdal and python. The installtion is
ok.
But when I type import gdal in python, I got the error as follow:
import gdal
Traceback (most recent call last):
File stdin, line 1, in module
File D:\Python31\lib\site-packages\gdal.py,
11 matches
Mail list logo
