On Tue, Apr 05, 2016 at 06:09:12PM +1000, Nyall Dawson wrote: > What's the topology issue you're hoping to solve with this?
Topology face layers from the TopoViewer (via DBManager plugin) use an expensive (and volatile, thus non-indexable) query to generate the geometry to be used for display. The provider generally applies the spatial filter to the geometry field, which in this case is ineffective. I could fix this by adding the possibility to specify a "spatial-filter-field" which is different from the "spatial-display-field" (similarly could be done for obtaining the $area from the provider, for example). Or there could be a way for a query to include its own scale-and-extent-dependent filter to be applied when fetching geometries. This would be more flexible for the user as it could specify any arbitrary filter that could serve to modify what's fetched depending on the viewport (which could even include calling functions that query different tables based on different viewport scales, for instance). --strk; _______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user