Hey, in QGIS you will have slow visualization essentially on faces. If your topogeom are based on node or edge it is faster.
If not, I use materialized view (requiere postgres 9.3), as a "buffer" for qgis. The problem is QGIS 2.0 doesn't support yet materialized view, so you have to create a proxy view onto your materialized view for qgis! It is a bit of useless code but it is a great comfort gain. Also, you can use QGis visualisation settings to make the element appears dynamically, again this is better than just waiting with blank screen Cheers, Rémi-C 2013/10/28 Christophe Vergon <[email protected]> > > OK. >> >> So for now, working with a large topology data set is not practical. >> Some processing should not be a problem, if it operates on the primitives, >> which are indexed. >> >> ----- >> > I'm not sure to understand all of the problem, the way I use to link > Buissnes Object (here "tronfluv" ) and Primitives in a request is as folow > > SELECT st_AsBinary(st_**GetFaceGeometry('topocommune',**face_id)),idtronfluv > FROM topocommune.face,topocommune.**relation, schemaname.tronfluv WHERE > layer_id=:lid AND mbr && st_LineFromText(:rg,srid) AND face_id=element_id > AND (the_topo).id=topogeo_id; > > Nota : :rg parameter who describe a polyline (a rectangle in fact). > > It works well and relatively fast with a large topology dataset (23 518 > Buissnes Object "tronfluv" in my Database) > > Christophe > > > > > > ______________________________**_________________ > postgis-users mailing list > [email protected] > http://lists.osgeo.org/cgi-**bin/mailman/listinfo/postgis-**users<http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users> >
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
