I didn't try to load this layer in QGIS before I realized the errors when doing analyses in postgis only and corrected the errors. But as this is a) clearly a postgis/data error and b) QGIS forwards the error message properly to the user, I don't think it's an issue to pay any attention to on QGIS side.
Matthias On Fre 28 Jun 2013 16:06:14 CEST, Paolo Cavallini wrote: > ********* *BEGIN ENCRYPTED or SIGNED PART* ********* > > Il 28/06/2013 15:57, Jürgen E. Fischer ha scritto: > >> Using the same version of PostGIS / GEOS ? > > yes, on the same DB > >> I suppose it's the && operator (bounding box intersection) and/or >> (st_)intersects function that causes this (on certain invalid geometries). >> And >> 1.8 would also trigger that. > > I see - unfortunately I do not have a 1.8 at hand now, I'll try to check. > Thanks. > -- > Paolo Cavallini - Faunalia > www.faunalia.eu > Full contact details at www.faunalia.eu/pc > Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario > > > ********** *END ENCRYPTED or SIGNED PART* ********** > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer