[GRASS-dev] Recent changes in v.out.ogr grass7 trunk

[Benjamin Ducke]

Yes, that would be a problem.
I think here the semantics of the GRASS --overwrite flag
collide with the separate OGR concepts of "datasource"
and "layer". In the case of GRASS maps, the meaning is
always clear: overwrite existing map. But OGR output
formats can be more complex. E.g. the user might want
to overwrite one of many spatial tables (OGR layers)
in an existing Spatialite DBMS (OGR datasource). For this to 
work, the datasource must of course exist.
So I think we may need two different "overwrite" operations
in the special case of v.out.ogr: 
one for OGR layers and one for OGR datasources?

Ben

On 12/18/2010 07:52 PM, Soeren Gebbert wrote:
> Hi,
> i am facing a problem with v.out.ogr which was introduced in revision
> r44484 implementing the
> ability of v.out.ogr to update existing files.
>
> I have a python script which sets the overwrite flag as default to
> True for all modules it calls (in
> gisrc), to avoid overwrite errors when working in temporally created
> grass locations. This works fine for all grass modules.
> Unfortunately the last changes in v.out.ogr switches from overwrite
> mode to update mode (main.c line 285) and expects an existing file.
> Therefor v.out.ogr dies with the error message: ERROR: Unable to open
> OGR data source '/tmp/voronoi_diagram.kml'  in case there is no file.
>
> IMHO using the overwrite flag should not fail in case there is no file
> to overwrite. Updating files should be managed with a special flag and
> should not depend on the overwrite flag.
>
> I am open for suggestions and discussion. :)
>
> Best regards
> Soeren
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
>



------
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.