[GRASS5] i.points and i.rectify question

GRASS GIS GRASS GIS developer
1

In versions 5.0.x and 5.3 are the 2 modules i.points and i.points3. The documentation for both versions of GRASS discuss the associated programs i.rectify and i.rectify3. However, there does not seem to be a module i.rectify3 anywhere. Some months back, before I realized that i.rectify3 was missing, I tried both i.points and i.points3 and found i.points3 to be a better program in several respects. However, the output file it creates (image xy and georeferenced coordinate pairs) seems to be ONLY in lat long and does not work with i.rectify. This was a major headache.

Has anyone else run into this? Is there any way to "rectify" this problem? :wink:
____________________
C. Michael Barton, Professor
Department of Anthropology
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671

2

Hello,

On Sun, Nov 16, 2003 at 12:54:15PM +0100, Michael Barton wrote:

In versions 5.0.x and 5.3 are the 2 modules i.points and i.points3. The
documentation for both versions of GRASS discuss the associated
programs i.rectify and i.rectify3. However, there does not seem to be a
module i.rectify3 anywhere. Some months back, before I realized that
i.rectify3 was missing, I tried both i.points and i.points3 and found
i.points3 to be a better program in several respects. However, the
output file it creates (image xy and georeferenced coordinate pairs)
seems to be ONLY in lat long and does not work with i.rectify. This was
a major headache.

Has anyone else run into this? Is there any way to "rectify" this
problem? :wink:

Since I'm wandering in the historical 4.1.5 release, I gave a look at
these.

Indeed, there were (back to 4.1.5) i.rectify in src and i.rectify2 in
src.alpha. In 5.[03] there were a merge between i.rectify and i.rectify2
but it seems that there were some clash: i.rectify2 was due to be
renamed i.rectify, but remained i.rectify2 and there is another
i.rectify3 (with some fixes).

So i.rectify2 and i.rectify3 are in the sources but only a i.rectify is
present in the binaries, which seems to be i.rectify2 since i.rectify3
is not compiled by default.

For i.points, there were in src: i.points, in src.alpha: i.vpoints and
the resulting i.points3 seem to be a merge between i.points and
i.vpoints. And there is no i.points2

Yes, my head spins too...:wink:
--
Thierry Laronde (Alceste) <tlaronde@polynum.org>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C

3

Hello,

There is a difference between i.rectify (& i.points) and i.rectify3. Unfortunately, I have never figured out which one is "more" correct. I think that i.rectify3 post dates i.rectify and was intended to replace it??

The i.rectify3 and i.points3 programs both use the image3 library in src/libes. This library utilizes the proj library and converts coordinates on the fly between lat. long. and the users coordinate system. Unfortunately, i.rectify3 is not built by default, but the source is still there.

We probably need to decide which set of programs is more up to date (and accurate). My preference has been i.points3 and i.rectify3 but I may be way off on this.

--
Bob Covill

Michael Barton wrote:

In versions 5.0.x and 5.3 are the 2 modules i.points and i.points3. The documentation for both versions of GRASS discuss the associated programs i.rectify and i.rectify3. However, there does not seem to be a module i.rectify3 anywhere. Some months back, before I realized that i.rectify3 was missing, I tried both i.points and i.points3 and found i.points3 to be a better program in several respects. However, the output file it creates (image xy and georeferenced coordinate pairs) seems to be ONLY in lat long and does not work with i.rectify. This was a major headache.

Has anyone else run into this? Is there any way to "rectify" this problem? :wink:
____________________
C. Michael Barton, Professor
Department of Anthropology
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

4

On Sun, Nov 16, 2003 at 08:31:42PM -0400, Bob Covill wrote:

Hello,

There is a difference between i.rectify (& i.points) and i.rectify3.
Unfortunately, I have never figured out which one is "more" correct. I
think that i.rectify3 post dates i.rectify and was intended to replace it??

The i.rectify3 and i.points3 programs both use the image3 library in
src/libes. This library utilizes the proj library and converts
coordinates on the fly between lat. long. and the users coordinate
system. Unfortunately, i.rectify3 is not built by default, but the
source is still there.

Some clarification (as far as I understood it):

#######################

Family "old" in 4.x:
- i.points (raster target map), i.vpoints (vector target map)
- i.rectify, i.rectify2
- imagery lib

Family "new-but-incomplete" in 4.x:
- i.points3 (aims at merging i.points and i.vpoints, introducing
             DEM support for LANDSAT ortho imagery)
- i.rectify3
- image3 lib (implements new methods, aims at integrating the
  orthophoto stuff)

#######################

Family "old" in 5.x:
- i.points (raster target map), i.vpoints (vector target map)
- i.rectify (which is the code of i.rectify2 with fixes, old
             i.rectify deleted)
- imagery lib

Family "new-but-incomplete" in 5.x:
- see 'Family "new-but-incomplete" in 4.x'
  with some fixes from Bob Covill

#######################

Summary 5.x: i.points works, i.vpoints works (a few bugs inside),
             i.rectify works

             image3 lib, i.points3, i.rectify3 may work, highly untested
             promising, contains tons of debug code, was left in a stage
             of uncompleteness.

We probably need to decide which set of programs is more up to date (and
accurate). My preference has been i.points3 and i.rectify3 but I may be
way off on this.

I agree. But it will require some work, to get the promising image3 lib
functional. Efforts are welcome :slight_smile:

Markus

5

(cc grass5 list)

On Mon, Nov 17, 2003 at 01:30:13PM +0100, Michael Barton wrote:

Markus,

This is helpful. Thanks much.

The odd thing is that i.points3 is automatically built from source and
shows up in the binaries too. However, AFAICT it only works correctly
with i.rectify3 (i.e., creates a slightly different text file output
from i.points using latlong coordinates regardless of the
$GISBASE/location projection). But i.rectify3 is NOT automatically
built and does not show up in the binaries. It seems like there should
be both or neither.

Cheers

Michael Barton

OK, I have commented both image3 lib and i.points3 in the list
of default modules.

BTW: The image3 lib looks like crying for

indent -nbad -bap -bbb -nbbo -nbc -br -bli1 -bls -cbi0 -ncdb -nce \
-ci4 -cli0 -ncs -d0 -di0 -fc1 -nfca -hnl -i4 -ip4 -l80 -lc80 -lp -npcs \
-pi4 -nprs -npsl -sbi0 -sc -nsob -ss -ts8

to polish the code.
Maybe there should be additionally added 'polishing comments' which
are pretty odd in the image3 lib.

Markus

On Monday, November 17, 2003, at 12:13 PM, Markus Neteler wrote:

> On Sun, Nov 16, 2003 at 08:31:42PM -0400, Bob Covill wrote:
>> Hello,
>>
>> There is a difference between i.rectify (& i.points) and i.rectify3.
>> Unfortunately, I have never figured out which one is "more" correct. I
>> think that i.rectify3 post dates i.rectify and was intended to
>> replace it??
>>
>> The i.rectify3 and i.points3 programs both use the image3 library in
>> src/libes. This library utilizes the proj library and converts
>> coordinates on the fly between lat. long. and the users coordinate
>> system. Unfortunately, i.rectify3 is not built by default, but the
>> source is still there.
>
> Some clarification (as far as I understood it):
>
> #######################
>
> Family "old" in 4.x:
> - i.points (raster target map), i.vpoints (vector target map)
> - i.rectify, i.rectify2
> - imagery lib
>
> Family "new-but-incomplete" in 4.x:
> - i.points3 (aims at merging i.points and i.vpoints, introducing
> DEM support for LANDSAT ortho imagery)
> - i.rectify3
> - image3 lib (implements new methods, aims at integrating the
> orthophoto stuff)
>
> #######################
>
> Family "old" in 5.x:
> - i.points (raster target map), i.vpoints (vector target map)
> - i.rectify (which is the code of i.rectify2 with fixes, old
> i.rectify deleted)
> - imagery lib
>
> Family "new-but-incomplete" in 5.x:
> - see 'Family "new-but-incomplete" in 4.x'
> with some fixes from Bob Covill
>
> #######################
>
> Summary 5.x: i.points works, i.vpoints works (a few bugs inside),
> i.rectify works
>
> image3 lib, i.points3, i.rectify3 may work, highly
> untested
> promising, contains tons of debug code, was left in a
> stage
> of uncompleteness.
>
>> We probably need to decide which set of programs is more up to date
>> (and
>> accurate). My preference has been i.points3 and i.rectify3 but I may
>> be
>> way off on this.
>
> I agree. But it will require some work, to get the promising image3 lib
> functional. Efforts are welcome :slight_smile:
>
> Markus
>
>
____________________
C. Michael Barton, Professor
Department of Anthropology
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671

--
Markus Neteler <neteler@itc.it> http://mpa.itc.it
ITC-irst, Istituto per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy