[GRASS5] some BUGS/missing features

[Andreas Lange]

Markus Neteler wrote:
> >
> > This doesn't work. I think now that if r.poly uses the region settings,
> > r.line should too.
> Here r.line works perfectly now on Linux with any region setting.
> I guess you missed to run "make install" or so?
> 
It works now. I think the problem was that i missed the update, couldn't
compile because of the other error. Thanks a lot.

..
> > > > v.what/d.what.vect:
> > > > v.what -i and d.what.vect are very similar and could be merged to one
> > > > module? Not quite sure here.
> > > Yes! Same thing with r.what/d.what.rast.
> > > Or we decide that [rv].what are for script programming and
> > > d.what.[vect|rast] are for interactive usage. Should get comparable module
> > > behaviour.
> > >
> > > > r.what/d.what.rast:
> > > > r.what and d.what.rast are (not really) similar and could be merged to
> > > > one module?
> > > see above.
> >
> > I think now that r.what/v.what should be shell-style and d.* interactive
> > modules. No need to have the interactive part in the r./v. modules.
> > Then the d.* modules could check for display availability. It is
> > important IMHO that the output of both d and r/v modules is identical.
> Definitly! Your proposal sounds good to me.
> > Reported to the request tracker.

If i find time, i will try to fix it the way described, as i already
worked on d.what.(vect|rast).
 
> > > > v.cutregion:
> > > > A module v.cutregion would be very handy to cut a vector map to the
> > > > actual region. When i import from ascii vector files all vectors get
> > > > imported, irrespectable if they fall into the current region or the
> > > > whole GRASS region. This stems from the handling of the ascii header i
> > > > think. With the new vector lib this could be handled correctly, but as a
> > > > intermediate fix a module v.cutregion would be very useful.
> > > I think this is on the way for 5.1 (David, Radim?).
> >
> > I am aware that there are many improvements on the way. But i have to do
> > my work right now.
> > So i need a solution that works.
> > I wrote a shell script for creating a vector bounding box for the
> > current region settings and a second script for cutting the actual
> > region from this.
> > If there is general need for both scripts please tell me.
> At least I would like to have such a script. Intersecting and cutting is not
> at it's best at time...

There are still problems with v.cutter to resolve, this was discussed on
grasslist recently. Sometimes it doesn't work properly. Don't know if i
can check the script in.

cu,

Andreas

-- 
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange at Rhein-Main.de - A.C.Lange at GMX.net


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'