[GRASS-dev] [GRASS GIS] #3349: v.import: add 'where' parameter
GRASS GIS
trac at osgeo.org
Sun May 21 21:22:52 PDT 2017
#3349: v.import: add 'where' parameter
--------------------------+----------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.4.0
Component: Vector | Version: unspecified
Resolution: | Keywords: v.import where
CPU: Unspecified | Platform: Unspecified
--------------------------+----------------------------
Comment (by mlennert):
Replying to [comment:1 mmetz]:
> Replying to [ticket:3349 mlennert]:
> > Was there choice of not adding a 'where' parameter to v.import a
deliberate one ? I would find this parameter quite useful, but do not want
to implement it if there was an explicit decision against it.
>
> The reason to not add a 'where' option to v.import, as well as various
other options and flags present in v.in.ogr but not in v.import, was to
provide a module with a simplified user-interface that combines v.in.ogr +
v.proj. It was not meant to be a replacement for using v.in.ogr and v.proj
separately.
Well, the fact that AFAICT the GUI now exclusively uses v.import for
imports (even when you chose "Common import formats" and **not** "Import
of common formats with reprojection") and automatically proposes to
reproject data at import if it is not in the location's projection,
creates a situation where most people will use v.import, without knowing
it.
Actually, the where option is thus not available at all in the GUI import
wizard... :-(
Once again a case where I think that dumbing down the GUI is not always a
good idea.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3349#comment:2>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list