Your code below works for me also. It's obviously just my data.
the field is data type bytea:
\x010300000000000000
I ran:
select st_astext(the_geom) from tbl where id = 6052
and it returns: "POLYGON EMPTY"
When I run the st_isvalid on it:
select st_isvalid(the_geom) from tbl where id = 6052
or
select st_isvalid(the_geom::geometry) from tbl where id = 6052
It throws the segmentation error.
I just upgrade to postgis 1.5.5 and this made no difference.
On Wed, Jul 25, 2012 at 2:10 PM, Sandro Santilli <s...@keybit.net> wrote:
> On Wed, Jul 25, 2012 at 01:02:59PM +0100, Rebecca Clarke wrote:
> > I have resolved the issue.
> >
> > It was happening because there was a record with an empty polygon.
> >
> > When I added this code into the query it worked successfully.
> >
> > CASE WHEN ST_IsEmpty(st_astext(the_geom)) THEN false ELSE
> > st_isvalid(the_geom) END
>
> So are you saying that ST_IsValid('POLYGON EMPTY'::geometry) and
> ST_Contains('POLYGON EMPTY'::geometry, 'POLYGON EMPTY'::geometry)
> both crash for you ?
>
> They work fine for me as of PostGIS 1.5.4
>
> --strk;
>
> ,------o-.
> | __/ | Delivering high quality PostGIS 2.1
> | / 2.1 | http://strk.keybit.net - http://vizzuality.com
> `-o------'
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
