Finally I made it.
I wrote a simple python program that converts the goes.nav file to a
format that can be used by i.rectify (POINTS file).
The only thing that I'm worried now is that the rms = 0.31 in
i.points. Is that too high? I'm attaching both the i.points screen
dump and the python script, in case someone needs it
Thanks
Daniel
PS - Murphy's law rules everything. After a couple of days to get this
working I found out I downloaded the wrong images 
they don't cover
the area I want... At least it's all done now
On 4/5/06, Glynn Clements <glynn@gclements.plus.com> wrote:
Daniel Victoria wrote:
> > > I'm trying to import GOES tif images that have no georeferencing. The
> > > georef information is in a separate file which I finaly opened. It
> > > contains the lat and lon for every cell in the GOES images. The
> > > problem is, I just can't seem to get the lat/lon information into the
> > > TIF files. Is there any way to do this? gdalwarp? gdal_translate?
> > > i.points?
> >
> > add GCPs with gdal_translate, then gdalwarp?
>
> but my control points are in a huge text list and the switch -gcp in
> gdal_translate does not accept that. So, I have to enter the corner
> points by hand? Or is there a way to make gdal_translate read from a
> text file (all 1200000 points)?I don't think that gdal_translate was designed to handle such large
numbers of control points.You could import your data as a vector point map then use v.surf.rst.
You would probably need to match the coordinates with the cell values
manually (e.g. exporting the raster with r.out.ascii, importing the
coordinates along with the r.out.ascii output into a DBMS, then
joining the two tables).Alternatively, you may be able to get adequate results by using a
small sample of the control points and gdalwarp's -tps switch.--
Glynn Clements <glynn@gclements.plus.com>
(attachments)
goes.py (953 Bytes)