[GRASS-dev] OGR write access

GRASS GRASS developer
1

On Oct 15, 2009, at 3:40 AM, grass-dev-request@lists.osgeo.org wrote:

Date: Thu, 15 Oct 2009 11:09:11 +0200
From: Martin Landa <landa.martin@gmail.com>
Subject: [GRASS-dev] OGR write access
To: GRASS developers list <grass-dev@lists.osgeo.org>
Message-ID:
       <f8fe65c40910150209v49be8404xe616a7dc9922c323@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am thinking how to implement direct write access to OGR datasources
from the user point of view. One approach would be to implement global
flag '--u' for updating existing vector map (i.e. OGR datasource).
E.g.

v.out.ogr input=test dsn=. type=point -n
v.external dsn=. layer=test output=test
v.random out=test n=1000 --u

this could work also for native format

v.edit map=test tool=create
v.random out=test n=1000 --u

Or to add new parameters 'dns/format' which would be used only for OGR
format, not for the native one.

v.random out=test n=1000 format=ESRI_Shapefile dns=.

Any ideas?

Martin

Might this be worth considering integrating with the data catalog mentioned yesterday?

http://lists.osgeo.org/pipermail/grass-gui/2009-October/000679.html

Michael

2

Hi,

2009/10/15 Michael Barton <michael.barton@asu.edu>:

[...]

Might this be worth considering integrating with the data catalog mentioned
yesterday?

http://lists.osgeo.org/pipermail/grass-gui/2009-October/000679.html

I see this as separate issue. First step to implemented it in the
GRASS libraries and for CLI. Integration into wxGUI can come later.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

3

Fair enough. Better to do this one step at a time.

Michael

On Oct 15, 2009, at 8:58 AM, Martin Landa wrote:

Hi,

2009/10/15 Michael Barton <michael.barton@asu.edu>:

[...]

Might this be worth considering integrating with the data catalog mentioned
yesterday?

[GRASS-GUI] DataCatalog

I see this as separate issue. First step to implemented it in the
GRASS libraries and for CLI. Integration into wxGUI can come later.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

4

Hi,

2009/10/15 Michael Barton <Michael.Barton@asu.edu>:

Fair enough. Better to do this one step at a time.

sorry, I don't understand right now. Without direct OGR write support
in the GRASS libraries and the GRASS modules you can work on the GUI
integration. GRASS libraries and modules need to be updated first.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

5

On Oct 15, 2009, at 11:36 AM, Martin Landa wrote:

Hi,

2009/10/15 Michael Barton <Michael.Barton@asu.edu>:

Fair enough. Better to do this one step at a time.

sorry, I don't understand right now. Without direct OGR write support
in the GRASS libraries and the GRASS modules you can work on the GUI
integration. GRASS libraries and modules need to be updated first.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

??

I was agreeing with you.

Michael

6

2009/10/15 Michael Barton <Michael.Barton@asu.edu>:

Fair enough. Better to do this one step at a time.

sorry, I don't understand right now. Without direct OGR write support
in the GRASS libraries and the GRASS modules you can work on the GUI
integration. GRASS libraries and modules need to be updated first.

??

I was agreeing with you.

sorry, I misunderstood. Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa