[GRASS-dev] [GRASS GIS] #1798: all relevant vector modules should have cats and where parameters
GRASS GIS
trac at osgeo.org
Thu Nov 15 00:12:30 PST 2012
#1798: all relevant vector modules should have cats and where parameters
----------------------------------+-----------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: where cats parameter | Platform: Unspecified
Cpu: Unspecified |
----------------------------------+-----------------------------------------
Comment(by mlennert):
Replying to [comment:1 glynn]:
> Replying to [ticket:1798 mlennert]:
> > A series of vector modules should have cats and where parameters
allowing the user to apply the operation only on selected features. Having
this options avoids having to create many intermediate maps. And for a
more homogeneous user experience it would be nice to have them in all
modules, unless irrelevant.
>
> Would it be feasible (and desirable) to allow the creation of "views"
(virtual maps which obtain their data from an underlying map), similar to
v.external or raster "reclass" maps?
I don't know enough about the "feasible" question, but I agree that it
might be worth looking at this option. At the same time, I really
appreciate the flexibility of doing the "on-the-fly" selection that the
cats and where parameters allow.
Imagine the case where you have 100 points and want to create individual
buffers around each, i.e. you can't call v.buffer on all at once as this
will fusion the buffers. With views you have the extra step of having to
create a view for each cat before calling v.buffer, with the cats/where
options you can just call v.buffer. But I'm aware that we're talking
luxury problems here, and that views that can be called like normal maps
would allow us not to have to worry about this for each new module (and
especially addons).
Moritz
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1798#comment:3>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list