I have created a geotiff file using the "GTiff" driver, and have
successfully set options for it to be a strips file with no
compression. Also, successfully called the functions
dataset->SetMetadataItem( "AREA_OR_POINT",
"Point",
Norman,
I believe you want to call SetGCPProjection() instead of SetProjection()
when using GCPs instead of an affine transform.
Best regards,
Frank
On Wed, Nov 6, 2013 at 1:23 PM, Norman Goldstein wrote:
> I have created a geotiff file using the "GTiff" driver, and have
> successfully set o
Frank,
I am using GDAL
Version : 1.9.2
so maybe that is why I do not see the method SetGCPProjection().
I think you have convinced me, though, to calculate the 6 coefficients
directly,
and then call SetGeoTransform(). Will let you guys know how this works out
for me.
Thank you,
Norm
O
Norman,
My apologies. The GCP projection is actually supposed to be passed as the
third value in the SetGCPs call - where you have passed the string
"Richmond". Instead pass the whole WKT strings for the coordinate system.
Best regards,
Frank
On Wed, Nov 6, 2013 at 4:00 PM, Norman Goldstein
Frank,
Things are better, now, but not quite there for me.
Still not able to transform pixel/line to PCS space.
(the listgeo dump is, below)
I think the problem is that there is no definition of the
ModelPixelScaleTag
It seems that this tag, together with the ModelTiepointTag,
is how an affine
On Sat, Nov 9, 2013 at 1:07 PM, Norman Goldstein wrote:
> Things are better, now, but not quite there for me.
> Still not able to transform pixel/line to PCS space.
> (the listgeo dump is, below)
>
> I think the problem is that there is no definition of the
>
> ModelPixelScaleTag
>
> It seems that
Le dimanche 10 novembre 2013 00:14:42, Trent Piepho a écrit :
> On Sat, Nov 9, 2013 at 1:07 PM, Norman Goldstein wrote:
> > Things are better, now, but not quite there for me.
> > Still not able to transform pixel/line to PCS space.
> > (the listgeo dump is, below)
> >
> > I think the problem is
Frank and Trent,
I have created a proper GeoTIFF file with the code
listed, below. There is still one oddity:
The code sets the line/sample --> x/y affine transformation
using an array of 6 doubles. The code contains a conditional
compilation that chooses between two different arrays of
6 d
Le lundi 11 novembre 2013 20:46:47, Norman Goldstein a écrit :
> Frank and Trent,
>
> I have created a proper GeoTIFF file with the code
> listed, below. There is still one oddity:
> The code sets the line/sample --> x/y affine transformation
> using an array of 6 doubles. The code contains
On Nov 10, 2013 1:44 AM, "Even Rouault"
wrote:
>
> Le dimanche 10 novembre 2013 00:14:42, Trent Piepho a écrit :
> > I've found that unless you call SetGeoTransform() and give an affine
> > transform, most apps, including listgeo and gdalsrsinfo, aren't
> > entirely happy with the georeferencing.
Le jeudi 14 novembre 2013 21:24:01, Trent Piepho a écrit :
> On Nov 10, 2013 1:44 AM, "Even Rouault"
>
> wrote:
> > Le dimanche 10 novembre 2013 00:14:42, Trent Piepho a écrit :
> > > I've found that unless you call SetGeoTransform() and give an affine
> > > transform, most apps, including listge
11 matches
Mail list logo
