Hi Uwe,
Sorry to bother you again. I actually need your help about another GDALWARP
problem I am having. I just thought it might be better to send you an email
directly about this (a shortcut:)) although I did just post a message regarding
this problem on the GDAL DEV forum:
http://osgeo-org.
Hi there,
When I tried to use GDALWARP to do the re-projeciton on some large GeoTiff
data, the output pictures seemed to contain the gaps, which appeared to be a
few horizontal lines when zooming out. The command I was using is something
like this:
gdalwarp --config GDAL_CACHEMAX 250 -wm 250 -co
So you are talking for something like this:
Example VRT file for data (just to show the geolocation metadata reference):
data.lon.vrt
1
data.lat.vrt
1
0
0
1
1
stuff goes here
1500
10
22180
LSB
On Tue, Feb 15, 2011 at 10:34 AM, F
Hi all
I would like to create ERDAS Imagine compliant overview files for a
larger satellite archive (mainly GeoTIFF files) in an automated way. The
"gdaladdo" tool has the possibility of defining this with "--config
USE_RRD YES". But this writes out not the typical ERDAS *.rrd files but
adds
Le lundi 14 février 2011 21:52:05, Brian Claywell a écrit :
> I'm attempting to use CreateMaskBand() on a MrSID dataset with GDAL
> 1.8.0 and receiving the error that "CreateMaskBand() is not supported
> on this dataset." I presume this is because mask band support was
> implemented using the GDALD
On 11-02-14 03:52 PM, Brian Claywell wrote:
I'm attempting to use CreateMaskBand() on a MrSID dataset with GDAL
1.8.0 and receiving the error that "CreateMaskBand() is not supported
on this dataset." I presume this is because mask band support was
implemented using the GDALDefaultOverviews manage
On 11-02-15 2:47 PM, Frank Warmerdam wrote:
Well, either way will work. But *my* recommendation is creating an
nmake.local with GDAL trunk and beyond. This is better than editing
nmake.opt directly particularly in the case where you later want to
do svn update's and rebuilds. If you hand edit th
On 11-02-14 08:54 AM, Jeff McKenna wrote:
I personally have always just modified the nmake.opt. I am not sure what is
recommended now. Can someone verify that the new recommended way is to create a
'nmake.local' file and then execute 'nmake /f makefile.vc' ?
Jeff,
Well, either way will work.
On 11-02-15 01:20 PM, Nikolaos Hatzopoulos wrote:
So we have three tables:
one matrix for latitude values
one matrix for longitude values
one matrix for our data values
all the matrix have the same dimensions
how we can convert these three tables to geotif using gdal??
Mikos,
This is a geore
So we have three tables:
one matrix for latitude values
one matrix for longitude values
one matrix for our data values
all the matrix have the same dimensions
how we can convert these three tables to geotif using gdal??
--Nikos Hatzopoulos
___
gdal-de
On 11-02-15 07:50 AM, Emilio de Torres Fernández wrote:
If I use the equations of the azimuthal equidistant projection to
transform long=6d32'32.13"W and lat=36d42'16.93"N) I get x = -0.65688 and y =
0.78961, not (-4195457.112, 5006607.739). Why??? I guess I misunderstood some
concept of the "Co
Hello,
I'm trying to understand the corner coordinates info of the following
gdalinfo output:
Driver: GTiff/GeoTIFF
Files: mosaicoRe.tif
Size is 2674, 2649
Coordinate System is:
PROJCS["unnamed",
GEOGCS["WGS 84",
DATUM["WGS_1984",
SPHEROID["WGS 84",6378137,298.257223563,
Selon cobalto :
> These NITFs contain RPCs, so I mostly am unconcerned with the geotransform,
> exact or approximated. However, proper interpretation of the RPCs requires
> knowledge of the projection reference. In these cases, it seems somewhat
> circuitous to look for a projection reference amo
13 matches
Mail list logo
