Feature request #836

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

Added by horst-duester - over 9 years ago. Updated over 3 years ago.

Status:Closed Start Date:
Priority:Low Due date:
Assigned to:nobody - % Done:

0%

Category:GRASS
Target version:Future Release - Nice to have
Platform:All Resolution:
Platform version: Pull Request or Patch supplied:
Status info:0 Tag:

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 569d12dba21e1310816a416ff2112067803d8e27
Added by Jürgen Fischer over 9 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

Revision 7ae8b35d9e908bafbaf452b02eafd7c7fafab9a6
Added by Jürgen Fischer over 9 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

History

Updated by Jürgen Fischer over 9 years ago

  • Status changed from Open to Closed
  • Resolution set to fixed

fixed in 569d12db (SVN r7706)

Updated by horst-duester - over 9 years ago

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

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.

Updated by Jürgen Fischer over 9 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?

Updated by Jürgen Fischer over 9 years ago

  • Status changed from Feedback to Closed
  • Resolution set to fixed

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

Updated by horst-duester - over 9 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!!!!

Updated by Horst Düster almost 8 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.

Updated by Lorenzo Masini almost 8 years ago

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

Updated by Giovanni Manghi over 7 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.

Updated by Giovanni Manghi over 7 years ago

sorry

"especially that now subsets are available also for shapes"

Updated by Giovanni Manghi over 5 years ago

  • Target version changed from Version 1.7.0 to Version 1.7.4

Updated by Giovanni Manghi almost 5 years ago

  • Target version changed from Version 1.7.4 to Version 2.0.0

Updated by Pirmin Kalberer over 4 years ago

  • Target version changed from Version 2.0.0 to Future Release - Nice to have

Updated by Jürgen Fischer over 3 years ago

  • Status changed from Feedback to Closed

Also available in: Atom