[GRASS-dev] lib/vask

[Glynn Clements]

Brad Douglas wrote:

> > > i.orpho.photo is one of those "applications" for which the only
> > > sensible solution is a complete rewrite (or complete disposal; how
> > > important is it?)
> > 
> > Very. I don't know of any other FOSS tool than can can orthorectify
> > aerial photographs using an already existing DEM.
> > 
> > The only similar one is e-foto project, but their philosophy is a bit
> > different - DEM is created from stereo aerial photographs, then they
> > are orthorectified using that DEM.
> > 
> > Unique and good thing about i.orpho.photo is that you can orthorectify
> > even a single photo, or a set of photos which don't overlap enough to be
> > used for extracting DEM in e-foto or other photogrammetry software.
> > 
> > Please don't remove i.orpho.photo.
> 
> Agreed.  This module is extremely important to me.  If I can't rectify
> images, GRASS becomes somewhat unusable to me.  Most of the imagery
> commands are quite important to me.

Ok, if disposal is out of the question, it will need to be re-written
if vask is to be eliminated.

> I believe i.ortho.photo will require input from one method or another.
> I don't see it working without interactive input, either.

Could you explain why?

> This is one
> of the other reasons I brought up the subject of lib/vask again.  I'm
> honestly stumped as to how to resolve this without rewriting the module
> as GRASS advances.

You can't resolve it without re-writing the module.

This is probably a good example of why it's important to separate
functionality from interface.

-- 
Glynn Clements <glynn at gclements.plus.com>