On 24/08/2010 21:33, Even Rouault wrote:
Try reducing under 2000 and it should work better. A too big value for the -wm
parameter can even sometimes affect speed negatively, and that'd probably the
case for your example where you are merging a lot of individual files into a
big one.
Just to
Hi,
I want to use GDAL library with Delphi application. I search for any
existing Delphi unit
and find only few topics in list archieves (e.g.
http://www.osgeo.org/pipermail/gdal-dev/2007-April/012565.html)
and ticket in trac (http://trac.osgeo.org/gdal/ticket/1580) that
closed as wontfix.
So I s
Dear list,
I got some data to deal with which use a projection called
"Kertau RSO Malaya Meters". From some earlier posts to proj.4
list I got the information that this is a kind of oblique
mercator projection. But I can't find anything around gdal
about how to deal with this projection.
Do I have
mail2vajram wrote:
Thanks for ur help
I followed the complete procedure,in the PDF provided by JAY.L but after
installing all the appropriate bindings also i got an error..Here i attached
screen shot of the error message
Please give the suggestion to rectify this error...
sorry, no tim
Doug,
No, the spirce image is probably just fine. This error basically means that an
internal buffer of the warper code would need to be larger than 2 GB ( 29400 *
19377 * 4 = 2.2 GB), which cannot be satisified on 32 bit systems. The root
cause is likely to be the huge value of the -wm paramet
Hi folks,
I'm working with someone trying to merge and reproject 1108 4 band tiff
images into 1 BIGTIFF image. The command line options are as follows:
gdalwarp -s_srs EPSG:26918 -t_srs EPSG:32119 -wo 'SOURCE_EXTRA=3' -wo
'SKIP_NOSOURCE=YES' -wm 4000 --config 'GDAL_CACHEMAX=2000' -tps -rcs
-
Tim,
yes you could likely move the OGRFeature::CreateFeature /
OGRFeature::DestroyFeature out of the loop. If you do this, depending on the
underlying OGR driver, you'll probably need doing a poFeature-
>SetFID(OGRNullFID) before poLayer->CreateFeature(), since the previous call
to CreateFeatur
Tim Keitt wrote:
I made my first foray into OGR today and want to be sure I understand
the following code from the tutorial.
In particular, I am wondering why the feature is created and destroyed
in each loop. Could one instead create a single feature object and
simply update its x and y values
I made my first foray into OGR today and want to be sure I understand
the following code from the tutorial.
In particular, I am wondering why the feature is created and destroyed
in each loop. Could one instead create a single feature object and
simply update its x and y values repeatedly? Clearly
ahmet temiz wrote:
hello
I can create spatial column. But I don't know how I can create
nonspatial column with ogr in gdal-java.
something like column "name" and its value ""
Ahmet,
I believe you are looking for the CreateField() method on the OGR Layer
class. Note that it does not pro
That is a very interesting question you are raising. Thank you :-)
Two solutions come to mind:
1: Change the parameters of gdaladdo to something that will produce an
integer division with the input data size. In this case, with 100k by 100k
px, that means it will no longer be multiples of two.
A
hello
I can create spatial column. But I don't know how I can create
nonspatial column with ogr in gdal-java.
something like column "name" and its value ""
how can I do that ?
regards
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists
jonas nielsen gmail.com> writes:
>
>
> The original images that the overviews are built on are 1 by
1 pixels.
>
> And yes, the artifacts appear without reprojection.
>
> -Jonas
Hi,
I do also see such artifacts with Mapserver tileindex layers when
zoomed far away so that the overvi
13 matches
Mail list logo
