Hamish wrote: > > Are you talking about making the module handle the query, or extending > > Vect_open_old() to accept a map+query so that the module doesn't need > > to do anything? > > vaguely thinking about ways to avoid having to custom code into each > individual module. So: extending Vect_open_old() to accept a map+query. > But that is perhaps a bit of an ugly mixing of libraries/serious task > so could well be more trouble than it is worth. > > on the other hand, hand crafting each module ensures that only the modules > where it is useful will get done. ie not complicating modules where where= > is not relevant with unneeded junk in an across the board addition. > > also, you probably want to have layer= before the where= query, which > further complicates the input= usage... yuck.
Maybe we need "views" of a vector map? -- Glynn Clements <[email protected]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
