Feature request #836: QGIS/GRASS import via v.in.ogr.qgis should only import pre selected layer features - QGIS Application - QGIS Issue Tracking

Feature request #836

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

Added by horst-duester - almost 17 years ago. Updated about 11 years ago.

Status:	Closed
Priority:	Low
Assignee:	nobody -
Category:	GRASS
Pull Request or Patch supplied:		Resolution:
Easy fix?:	No	Copied to github as #:	10895

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.

Associated revisions

Revision 7ae8b35d
Added by Jürgen Fischer almost 17 years ago

add support for where option of v.in.ogr, fixes #836

git-svn-id: http://svn.osgeo.org/qgis/trunk/qgis@7705 c8812cc2-4d05-0410-92ff-de0c093fc19c

Revision 569d12db
Added by Jürgen Fischer almost 17 years ago

add support for where option of v.in.ogr, fixes #836

git-svn-id: http://svn.osgeo.org/qgis/trunk@7705 c8812cc2-4d05-0410-92ff-de0c093fc19c

History

#1 Updated by Jürgen Fischer almost 17 years ago

Resolution set to fixed
Status changed from Open to Closed

fixed in 569d12db (SVN r7706)

#2 Updated by horst-duester - almost 17 years ago

Resolution deleted (~~fixed~~)
Status changed from Closed to Feedback

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.

#3 Updated by Jürgen Fischer almost 17 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?

#4 Updated by Jürgen Fischer almost 17 years ago

Resolution set to fixed
Status changed from Feedback to Closed

bf85ce9f (SVN r7713) fixes the problem with all layers being imported without any where clauses.

#5 Updated by horst-duester - almost 17 years ago

Replying to [comment:4 jef]:

bf85ce9f (SVN r7713) 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!!!!

#6 Updated by Horst Düster over 15 years ago

Status changed from Closed to Feedback
Resolution deleted (~~fixed~~)

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.

#7 Updated by Lorenzo Masini over 15 years ago

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

#8 Updated by Giovanni Manghi almost 15 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.