Kevin, > I've found that such errors in the past are usually related to the > precision of the coordinates. Try putting your geometries through > ST_SnapToGrid(), snapping them to some reasonable grid. Ensure they are > still valid and try ST_Union again.
I already put them data through FME Workbench's CoordinateRounder and Snapper functions (and validate via FME's GeometryValidator function). So, the data goes in to PostGIS snapped and clean (isvalid etc all report everything OK in PostGIS). > In any case, TopologyExceptions are getting fewer and farther between as > the JTS and GEOS codebases are continually enhanced and improved upon. > Can you provide a concrete example? I'll see what I can do to isolate the offending polygons. regards Simon -- SpatialDB Advice and Design, Solutions Architecture and Programming, Oracle Database 10g Administrator Certified Associate; Oracle Database 10g SQL Certified Professional Oracle Spatial, SQL Server, PostGIS, MySQL, ArcSDE, Manifold GIS, FME, Radius Topology and Studio Specialist. 39 Cliff View Drive, Allens Rivulet, 7150, Tasmania, Australia. Website: www.spatialdbadvisor.com Email: si...@spatialdbadvisor.com Voice: +61 362 396397 Mobile: +61 418 396391 Skype: sggreener Longitude: 147.20515 (147° 12' 18" E) Latitude: -43.01530 (43° 00' 55" S) NAC:W80CK 7SWP3 _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
