Hello all,
In the course of writing up a first draft of the chapter on image
processing for the GRASS tutorial, I stumbled upon a few questions:
- Do people still use the i.tape.* commands ?
- Is there any reason to use i.points and i.rectify instead of i.points3
and i.rectify3 ?
- Is there any significant difference between i.composite and r.composite ?
Any help is appreciated.
Moritz
Moritz Lennert wrote:
- Is there any significant difference between i.composite and r.composite ?
i.composite operates upon imagery groups; r.composite works on rasters.
i.composite has to be run interactively, r.composite can be scripted.
i.composite takes the intensity range (black/white values) from the
imagery files, r.composite uses the rasters' colour tables.
Other than that, both perform basically the same purpose.
--
Glynn Clements <glynn.clements@virgin.net>
On Mon, Aug 25, 2003 at 04:39:10PM +0200, Moritz Lennert wrote:
Hello all,
In the course of writing up a first draft of the chapter on image
processing for the GRASS tutorial, I stumbled upon a few questions:- Do people still use the i.tape.* commands ?
Maybe not. r.in.gdal does a good job on image data.
- Is there any reason to use i.points and i.rectify instead of i.points3
and i.rectify3 ?
Yes, i.points3 and i.rectify3 fail sometimes. These modules were never
finished and wait for a volunteer.
You may want to mention also i.vpoints.
- Is there any significant difference between i.composite and r.composite ?
Already answered by Glynn.
Markus