I guess it allows per-map WHERE clauses for those modules that take
multiple input maps (such as v.patch). The global "where=" option
does not and assumes that all input maps have the same attribute
table structure and data ranges?
Ben
Moritz Lennert wrote:
On 22/01/09 21:50, Hamish wrote:
slightly-related, but before I forget, I had an idea about the "adding
where= SQL queries to all vector modules in gr7" wish. hijack the parser
with a semi-colon.
for example:
v.module input="roads; WHERE surface IS 'gravel'"
In what ways do you feel this is superior to input= where= ?
Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Benjamin Ducke
Senior Applications Support and Development Officer
Oxford Archaeology Ltd
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.
Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.du...@oxfordarch.co.uk
------
Files attached to this email may be in ISO 26300 format (OASIS Open Document
Format). If you have difficulty opening them, please visit http://iso26300.info
for more information.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
