<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Craig,<br>
Comments inline.<br>
<br>
Craig Feuerherdt wrote:<br>
<blockquote
cite="mid:442163630710311602o11fd765encc1af617dc70c8ed@mail.gmail.com"
type="cite">So the original questions remain:
<br>
Are the issues associated with having multiple polygon geometries in
the one table (unlikely in my opinion)?<br>
</blockquote>
Nope. Although perhaps to narrow the scope for testing, try putting a
filter on your evc table perform your query 3 times. Once with a single
polygon that you know that lies completely within your buffered
polygon, once with one that lies on the boundary, and once with one
that lies completely outside. Make sure you get the clipped results
your are expecting to see each time. This way you're only testing two
polygons (one from evc and your buffered polygon) and not your whole
dataset. <br>
<blockquote
cite="mid:442163630710311602o11fd765encc1af617dc70c8ed@mail.gmail.com"
type="cite">Is it something to do with the query?<br>
</blockquote>
Your query looks fine. I assume that your filter of buf_dist=1 returns
a single polygon? But try the filter I suggested, thus breaking your
problem into small pieces.<br>
<blockquote
cite="mid:442163630710311602o11fd765encc1af617dc70c8ed@mail.gmail.com"
type="cite">Are these issues associated with PostGIS or GEOS?<br>
</blockquote>
Unlikely. Having said that, once in a while we do stumble upon a weird
case that reveals a small bug in GEOS. More often than not, however,
the problem lies in the input geometries not being valid.<br>
<blockquote
cite="mid:442163630710311602o11fd765encc1af617dc70c8ed@mail.gmail.com"
type="cite">Is there a work around to solve the issue?<br>
</blockquote>
I noticed in your pictures two small slivers in your evc layer (one
around the middle left, and one around the middle top). Are you sure
your geometries are valid? I don't know if this is how your data is
supposed to look like, or if some geometries may be invalid, or if its
the way QGIS is rendering your data. I haven't used QGIS before, but I
know that JUMP does not render self-intersecting polygons very well
(sometimes it doesn't even try). Maybe something similar is happening
here?<br>
<blockquote
cite="mid:442163630710311602o11fd765encc1af617dc70c8ed@mail.gmail.com"
type="cite"><br>
Thanks in advance,<br>
<br>
Craig<br>
<a moz-do-not-send="true"
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://www.bendigo-orienteers.com.au/study/evc1_under.png"
target="_blank"></a><br>
</blockquote>
I think this may be an input geometry issue. I would verify that your
polygons in your evc and bnd_buff are valid and don't have duplicate
coincident points. Try running them through snaptogrid(the_geom,
<precision>).<br>
<br>
Also, can you verify that your clipped resultset are all polygons?
Maybe QGIS has problems rendering a geometry collection?<br>
<br>
Hope this helps,<br>
Kevin<br>
</body>
</html>