Hi again,
This was obviously not a known problem. What we ended up with was to split the
GRIB files up in smaller pieces using another software and importing bit by bit
using GDAL. During the work we also had memory allocation problems in plain C++
code (myarray = new float[alotofcells]; gives
Sjur Kolberg wrote:
Hi again,
This was obviously not a known problem. What we ended up with was to
split the GRIB files up in smaller pieces using another software and
importing bit by bit using GDAL. During the work we also had memory
allocation problems in plain C++ code (myarray = new fl
pcreso wrote:
>
> Hi Alan,
>
> This doesn't fix you problem specifically, but may help.
>
> We usually use the packages from the OpenSuse Geo repository, which has
> SLES specific builds available. (We are using SLES for most Linux servers
> in our organisation)
>
> See: http://download.op
Alans wrote:
>
>
>
> Alans wrote:
>>
>>
>>
>> Frank Warmerdam wrote:
>>>
>>>
>>> This is very odd - I've never seen something quite like it.
>>>
>>> One work around would likely be to configure GDAL --without-libtool. I
>>> wonder if 1.6.3 got released with an unstable libtool version.
Adam,
I assume that you're testing on the same machine. Such difference is not
expected. Do you see that slowdown with different GDAL drivers or just
for one in particular (which one?)
Windows builds are able to use overviews. But are you speaking about
internal GeoTIFF overviews or about ex
Hello list,
Could someone tell me how to iterate over the points in a multipoint
feature? I have searched through the mailing list and have looked through
the documentation but can't seem to find it. I was expecting there to be a
"nextPart" or iterator or something, but I don't see anything, am
Folks I need help setting up gdal.
I get the following error when I tried to run the following import line:
from osgeo import gdal
error message:
Traceback (most recent call last):
File "C:\GIS_TOOLS\Python\GDAL_Geotiff_conversion.py", line 9, in
from osgeo import gdal
ImportError: No modu
Matthew Denno a écrit :
A multipoint geometry is a geometry collection, so you can use
OGRGeometry::getGeometryRef(iSubGeom).
See
http://gdal.org/ogr/classOGRGeometryCollection.html#d609f2c7886918a766dd3d3a4fa52ec3
Hello list,
Could someone tell me how to iterate over the points in a mult
Even,
Thank you for your quick reply. I will give it a try when I get home.
Matt
On Fri, Dec 11, 2009 at 4:36 PM, Even Rouault
wrote:
> Matthew Denno a écrit :
>
> A multipoint geometry is a geometry collection, so you can use
> OGRGeometry::getGeometryRef(iSubGeom).
>
> See
> http://gdal.org/
Malanding Jaiteh a écrit :
The Python bindings are not contained in the packages avalaible at
http://download.osgeo.org/gdal/win32/1.6/
That explains the error you get.
However, you can find prebuilt packages with GDAL Python bindings in :
- FWTools : http://fwtools.maptools.org/
- OSGeo4W : h
Hallo,
I have a set of very detailed b&w needing an overlay. But when I run
gdaladdo, no matter what option I choose, fillets are spitefully
deleted.
I don't know if there is a better solution, I tried to get a thicker
trace on a copy of the original image, make the pyramids and rename
the resultin
Carlo A. Bertelli (Charta s.r.l.) a écrit :
Well, I think it's not really a problem, but a characteristics of the
processing. I doubt that any general purpose pyramid building can
preserve high frequency details like fillets. It would require special
processing that would know what is a line a
Even,
Yes, this is on the same machine. The driver is GeoTIFF (I haven't
tried other ones) with external overviews.
Adam
On Fri, Dec 11, 2009 at 12:41 PM, Even Rouault
wrote:
> Adam,
>
> I assume that you're testing on the same machine. Such difference is not
> expected. Do you see that slowdo
13 matches
Mail list logo
