Opened 16 years ago

Last modified 13 years ago

#836 reopened enhancement

QGIS/GRASS import via v.in.ogr.qgis should only import pre selected layer features

Reported by: horst.duester Owned by: nobody
Priority: major: does not work as expected Milestone: Version 1.7.0
Component: GRASS Version: Trunk
Keywords: Cc:
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

When I load a Layer from p.e. PostGIS I can preselect a subset of features of this layer before I load this layer or I redefine this selection after loading with the preferences. QGIS/GRASS v.in.ogr doesn't respect this selection. It always load all features to GRASS although GRASS v.in.ogr supports a preselection of features.

Change History (12)

comment:1 by jef, 16 years ago

Resolution: fixed
Status: newclosed

fixed in r7705

comment:2 by horst.duester, 16 years ago

Resolution: fixed
Status: closedreopened

mmm ...

When I load a layer from Postgres Connection GUI and with double click created query, v.in.ogr starts to load *all* my PostGIS tables from DB.

comment:3 by jef, 16 years ago

hm, just rechecked. I have a postgis database that carries a bunch of tables with geometry. I loaded 2 into qgis and v.in.ogr on with a where clause to grass. Seems to work for me. Which commands get executed for you?

comment:4 by jef, 16 years ago

Resolution: fixed
Status: reopenedclosed

r7712 fixes the problem with all layers being imported without any where clauses.

in reply to:  4 comment:5 by horst.duester, 16 years ago

Replying to jef:

r7712 fixes the problem with all layers being imported without any where clauses.

Great!! Now it works fine. Thank you very very much for this fast fix!!!!

comment:6 by hdus, 15 years ago

Milestone: Version 0.9.1Version 1.2.0
Platform: DebianAll
Resolution: fixed
Status: closedreopened
Summary: QGIS/GRASS import via v.in.ogr should import pre selected layer featuresQGIS/GRASS import via v.in.ogr.qgis should only import pre selected layer features

Now v.in.ogr.qgis shows the same behaviour mentioned above. It seems, that the new v.in.ogr.qgis module doesn't take respect for any subselections. As the result I reopen this ticket.

comment:7 by rugginoso, 15 years ago

Type: bugenhancement

Suggestion: new module v.in.ogr.where.

comment:8 by pcav, 15 years ago

Milestone: Version 1.2.0Version 1.3.0

comment:9 by lutra, 14 years ago

I submitted to Paolo a new module v.in.ogr.qgis.where to workaround partially this problem, but I still think that v.in.ogr.qgis should respect the subsets created in qgis, especially that now that subsets are available also for shapes.

comment:10 by lutra, 14 years ago

sorry

"especially that now subsets are available also for shapes"

comment:11 by pcav, 14 years ago

Milestone: Version 1.5.0Version 1.6.0

comment:12 by pcav, 13 years ago

Must Fix for Release: YesNo
Note: See TracTickets for help on using tickets.