Opened 6 years ago
Closed 6 years ago
#3308 closed defect (fixed)
v.in.ogr GUI generates invalid layer parameter
|Reported by:||marisn||Owned by:||martinl|
When importing a single layer from SQLite database, v.in.ogr GUI generates layer parameter "layer_name|Geometry". Still such value is not a valid layer name for v.in.ogr and thus it is failing with an error: "Layer <layer_name|Geometry> not available". A workaround is to copy actual command and remove the "|Geometry" part and then execute it from a CLI.
The error seems to come from implementing GDAL RFC41 in r63610 thus assigning to the author of the commit.
Change History (7)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
|Version:||svn-trunk → 7.2.0|
comment:3 by , 6 years ago
comment:4 by , 6 years ago
Should be fixed in r70892. (*) Currently geometry column is returned by
gui_core.widget.LayersList.GetLayers() as a part of layer name (which is not ideal). Moreover both GUI wrapper (Import vector data) and G72:v.in.ogr discard this information, what can be problem when OGR layer contains more geometry columns. Moreover G72:v.import lacks
geometry option at all. This should be improved in 7.4.0.
(*) After some testing could backported. Please let me know.
comment:5 by , 6 years ago
|Milestone:||7.4.0 → 7.2.1|
comment:6 by , 6 years ago
|Milestone:||7.2.1 → 7.2.2|
comment:7 by , 6 years ago
|Status:||assigned → closed|
This problem also affects v.import as it shares the same GUI parts with v.in.ogr.
Looking at r63604 hints that v.import (and its wrapper dialog) should have geometry_column option and pass its value to v.in.ogr geometry parameter. This, of course, is already an enhancement.