[GRASS5] GRASS + Oracle

[Stephan Holl]

Hello Radim, 

On Tue, 11 Oct 2005 10:28:32 +0200 Radim Blazek
<radim.blazek at gmail.com> wrote:

> It is feature, once g.copy was making copy reading and
> writing lines, now it just copy files/tables.

Thanks for commenting on this. Since I would like to work with several
read-only v.external ogr-files/dbs which occasionally need some
digitizing inside the geometry. Therefor I thought just copying the
dataset into the native GRASS-FOrmat and edit then with
QGIS-GRASS-Digitize-tool.

I would like to see a switch inside g.copy which forces copying writing
lines in the native format. Would that be a possibility to extent the
current behavoiur with the former behaviour?

This would be usefull for copying ogr-datasets without using v.in.ogr
inside GRASS.

Thanks for commenting on this.

Best
	Stephan


> On 10/10/05, Stephan Holl <holl at gdf-hannover.de> wrote:
> > Dear Developers,
> >
> > I have successfully used GRASS and oracle-spatial with v.external.
> > Usually I thought that copying a layer included by v.extrenal with
> > g.copy copies the whole layer as a grass-vector-layer, which can be
> > editied by v.digit.
> >
> > This is not the case when trying to copy a OCI-layer. The resultant
> > layer cannot be edited with v.digit:
> > v.digit roads_oci_copy
> > WARNING: OGR format cannot be updated.
> > ERROR: Cannot open old vector roads_oci_copy at PERMANENT on level 2
> >
> > This is the same error when trying v.digit on the v.external-layer.
> >
> > Is this a bug or a feature?
> >
> > Thanks
> >
> >         Stephan



-- 
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office      -     Mengendamm 16d      -     D-30177 Hannover
Internet: www.gdf-hannover.de      -      Email: holl at gdf-hannover.de
Phone : ++49-(0)511.39088507       -        Fax: ++49-(0)511.39088508