Hi list,
I was wondering why GDALGetProjectionRef delivers an other result than
gdalinfo from FWTools of course by using the same file.
Here is my code from my qgis plugin:
if( GDALGetProjectionRef( inputDS ) != NULL )
{
OGRSpatialReferenceH inputSRS;
char
Adam Nowacki wrote:
Some rather counterintuitive gdalwarp behavior: the bigger
dfWarpMemoryLimit (-wm setting) the more cpu time will be wasted on
warping not existing pixels. Why? Warping begins with the destination
window size of entire output image size. If this size is larger than
You can test with http://pastebin.com/m45e46f53
Also remember to use -wo SKIP_NOSOURCE=YES
Hermann Peifer wrote:
Adam Nowacki wrote:
Some rather counterintuitive gdalwarp behavior: the bigger
dfWarpMemoryLimit (-wm setting) the more cpu time will be wasted on
warping not existing pixels. Why?
Can anyone help with this? Or point me to a source of information?
Thanks v much.
tozjerimiah wrote:
Hello,
I am wondering if anyone can help with a problem which I have to solve: I
want to take coordinates in meters from an ACAD file, and project them in
lat/long as is compatible with
Hi list,
I've got a tiff file of 28 Mb and it is really slow, so I am assuming the
classification gets applied on the fly or something like that.
If I do a gdalinfo I get a huge list of STATISTICS_HISTOBINVALUES
Metadata:
STATISTICS_MINIMUM=-5838
STATISTICS_MAXIMUM=4225
On Mon, Aug 24, 2009 at 6:17 PM, tozjerimiah tozjerim...@gmail.com wrote:
Can anyone help with this? Or point me to a source of information?
Thanks v much.
tozjerimiah wrote:
Hello,
I am wondering if anyone can help with a problem which I have to solve: I
want to take coordinates
bart...@osgis.nl wrote:
Hi list,
I've got a tiff file of 28 Mb and it is really slow, so I am assuming the
classification gets applied on the fly or something like that.
If I do a gdalinfo I get a huge list of STATISTICS_HISTOBINVALUES
Metadata:
STATISTICS_MINIMUM=-5838
Florian Hillen wrote:
gdalinfo delivers the right projection:
PROJCS[unnamed,
GEOGCS[DHDN,
DATUM[Deutsches_Hauptdreiecksnetz,
SPHEROID[Bessel 1841,6377397.155,299.152812809,
AUTHORITY[EPSG,7004]],
AUTHORITY[EPSG,6314]],
[...]
Hi,
I'm having some troubles creating a Nitf image that spans the International
Date Line (180/-180 degrees longitude). If I have an image that has a
western edge of around 150 degrees and an eastern edge of -150 degrees, I am
getting the following error Attempt to write geographic bound
Roger Bivand wrote:
(reverting to list)
Correction, the user reported that:
Apparently, gdalinfo retrieves the correct min, max, and statistics,
despite the use of GDT_Int16.
on his Windows platform. The different GDAL versions ought to explain
why his gdalinfo says Int16 but gives
Hejhej,
please allow me two short questions:
1) Using the GDAL Python bindings I currently need to extract a single
band from a raster stack and save it in a different format, i.e. ENVI.
To achieve this my processing includes
(a) analysis of the source dataset and desired band (width, height,
Frank (and all):
Thanks for the information. Using this link:
http://svn.osgeo.org/gdal/trunk/gdal/swig/python/samples/tolatlong.py
I was able to figure out how to transform points from one EPSG coordinate
system to another using Python. Here's how:
#transform()
def transform(i_srs, o_srs,
12 matches
Mail list logo
