[postgis-users] Intersection errors out with null directed edge

[Martin Davis]

Chris,

As Andreas pointed out, recent (Dec 06) work on GEOS has largely fixed 
this problem (which is likely due to a robustness issue - although it 
could also be due to invalid data!  You should check your data to make 
sure it is fully valid, using isValid() )

Try upgrading and see if the problem goes away.  There's not really any 
other great solution to this problem.

Martin

Chris Hermansen wrote:
> Hi folks;
>
> I had this problem today:
>
> AssertionFailedException: EdgeRing::computePoints: found null Directed
> Edge
>
> I see in the archives that there are others who have suffered this, back
> in 2006 and then in 2005, but there don't seem to be any offerings of
> techniques to either repair the code or the data - and based on the
> error above, I'm not sure which is ultimately at fault.
>
> Does anyone have some more up-to-date thought on this?
>
> I'm running postgis-1.3.1 on Ubuntu with the packaged postgresql-8.2
> installed.
>
> Thanks in advance!
>   

-- 
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022