Hi All,
I am attempting to read JPEG 2000 compressed data inside NITF files
using the python bindings.
My test python script is as follows
import os
os.environ['CPL_DEBUG'] = r'on'
os.environ['GDAL_DRIVER_PATH'] = r'c:\gdal\bin\gdalplugins'
print os.environ['GDAL_DRIVER_PATH']
from osgeo import
This doesn't address the issue, but:
x = numpy.array( [p[0] for p in polygon] )
y = numpy.array( [p[1] for p in polygon] )
z = numpy.array( [p[2] for p in polygon] )
these list comprehensions are unnecessary -- numpy understands nested lists:
poly_array = numpy.array(polygon)
x =
On Tue, 20 Jan 2009, Howard Butler wrote:
I think the way forward is if you could document this misery on the wiki
http://trac.osgeo.org/gdal It's a hard sell for us to complicate our already
messy configure logic to work around their bug that they stubbornly won't
fix.
It looks like someo
On Jan 20, 2009, at 10:49 AM, Russell McOrmond wrote:
As many of you likely already know (and I just found out), there
are incompatabilities between ESRI's libsde and the zlib library
that many tools we use need. I can stop the various core dumps by
compiling and making available the
As many of you likely already know (and I just found out), there are
incompatabilities between ESRI's libsde and the zlib library that many
tools we use need. I can stop the various core dumps by compiling and
making available the same version of zlib that is inside libsde (which for
ArcS
Chris Padwick wrote:
Howdy,
I’m using gdal 1.5.2. Every time I call GDALRasterBand::GetHistogram()
gdal generates a file with the same name as the image and the extension
.aux.xml. This file appears to contain a band by band image histogram
along with some other information. On subseque
Howdy,
I'm using gdal 1.5.2. Every time I call GDALRasterBand::GetHistogram()
gdal generates a file with the same name as the image and the extension
.aux.xml. This file appears to contain a band by band image histogram
along with some other information. On subsequent calls, using the same
i
On Fri, 19 Dec 2008 09:29:42 -0500
"Gong, Shawn (Contractor)" wrote:
> Thanks Klokan,
>
> I added --with-python
> ./configure --prefix=/home/sgong/dev181/dist --with-png=internal
--with-libtiff=internal --with-gif=internal --with-geotiff=internal
--with-libz=/home/sgong/dev181/dist --wi
Hi,
This should work better. I'm not greatly familiar with the lower-level R
functions for GDAL, but the following should be closer to what you wanted.
This assumes that "bm" is defined in the top level workspace, and the
function can access it via R's scoping rules. You could use a similar
Hei Rasmus,
This is simple:
>gdalinfo datasetfile.grb > textfile.txt
Sjur :-)
> -Original Message-
> From: gdal-dev-boun...@lists.osgeo.org
> [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of rasmus
> borgstrøm
> Sent: 20 januar 2009 10:55
> To: gdal-dev@lists.osgeo.org
> Su
Hi Pål
Im very interested to know if you succeded with the mentioned method and
with the creation of a python script.
regards
Rasmus Borgstrøm
Hi!
Thanks for helping! I will use the method you described them. Maybe I'll try
to make a small python script that calculates the values for each ras
Hi All
Maybe a simple question:
I would like to export the information from GDALINFO to a textfile, is that
possible within the FWTools Shell?
regards
Rasmus
--
View this message in context:
http://n2.nabble.com/Gdalinfo-to-textfile-tp2185759p2185759.html
Sent from the GDAL - Dev mailing list
12 matches
Mail list logo
