v.in.ogr GUI generates invalid layer parameter

[marisn]

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.

[marisn]

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.

[marisn]

See also #3333. Changed affected version to 7.2.0 as per #3333

[martinl]

In 70892:

v.in.ogr GUI generates invalid layer parameter (see #3308)

[martinl]

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.

[martinl]

In 71280:

v.in.ogr GUI generates invalid layer parameter (merge r70892 from trunk; fix #3308)