On Oct 22, 2008, at 8:45 AM, Moritz Lennert wrote:
On 22/10/08 17:25, Michael Barton wrote:
However, interactive control point creation/management works better
if you start in a projected location/mapset and rectify from the xy
location/mapset. This is the way that r.proj and v.proj work to
On 22/10/08 17:25, Michael Barton wrote:
However, interactive control point
creation/management works better if you start in a projected
location/mapset and rectify from the xy location/mapset. This is the way
that r.proj and v.proj work too. If there is to be work on i.rectify,
I'd like to su
On Oct 22, 2008, at 1:03 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]
> wrote:
Date: Wed, 22 Oct 2008 09:03:35 +0200
From: "Markus Neteler" <[EMAIL PROTECTED]>
Subject: Re: [GRASS-dev] Re: i.ortho.photo
To: [EMAIL PROTECTED]
Cc: GRASS developers list
Message-I
Hamish wrote:
> > r33944 | hamish | 2008-10-21 03:35:40 +0100 (Tue, 21 Oct 2008) | 1 line
> > remove code based on Vask_lib+Xmons; porting will happen in
> > develbranch6 then when operational be merged back into grass7 SVN
> >
> > Isn't this backwards?
> >
> > There's no need for i
On Wed, Oct 22, 2008 at 8:05 AM, Hamish <[EMAIL PROTECTED]> wrote:
> I had thought about leaving i.ortho.photo/libes/ in trunk, as that has
> some hope of being reused (ie all but ask_camera.c to be merged into
> lib/imagery/).
>From grass64/TODO:
A)
- lib/imagery/: standard lib, in use (i.
Glynn wrote:
> Re:
>
> r33944 | hamish | 2008-10-21 03:35:40 +0100 (Tue, 21 Oct 2008) | 1 line
> remove code based on Vask_lib+Xmons; porting will happen in
> develbranch6 then when operational be merged back into grass7 SVN
>
> Isn't this backwards?
>
> There's no need for i.o
