[GRASS-dev] [GRASS-SVN] r71093 - grass/trunk/vector/v.in.ogr

Markus Metz markus.metz.giswork at gmail.com
Wed May 17 06:18:31 PDT 2017

On Wed, May 17, 2017 at 3:09 PM, Martin Landa <landa.martin at gmail.com>
> Hi,
> 2017-05-17 15:00 GMT+02:00  <svn_grass at osgeo.org>:
> > +    /* TODO: remove below code, or use it in e.g. a new v.in.pg */
> -1
> v.in.ogr should work for all datasources. Special care should be done
> for database sources. Connection string can be provided as fully
> qualified. But also stored connections (via db.login) should be also
> taken into account. Martin

db.login is used for database access where GRASS reads/writes attribute
tables, right?

Why should these settings be used for OGR input? With v.in.ogr, OGR input
can be anything, and OGR input has nothing to do with where GRASS creates a
new attribute table. It is not clear why OGR should take into account GRASS
db settings. Obviously this only causes confusion.

Markus M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20170517/e19bcbe5/attachment.html>

More information about the grass-dev mailing list