Can you check for me if your geometry is valid? Usually an invalid geometry is the only way to make jts crash out like that. Once we have your geometry (I assume it is just one that is causing the problem?) we may need to go to the JTS list for help.
Cheers, Jody On Sat, Mar 21, 2009 at 12:37 AM, Paulm <[email protected]> wrote: > > Hi, > I don't now if this is a bug in Geotools. > I'm using Geotools 2.5 for clipping maps into smaller tiles. I've downloaded > a Vmap Level 0 map, eurasia. > > when I shall clip the polygons with the following command: Geometry newGeom > = featureGeometry.intersection(clipFeatureGeometry); > I'm getting the folloing error: > Exception in thread "main" com.vividsolutions.jts.geom.TopologyException: > side location conflict [ (36.7401657104492, 45.4868316650391, NaN) ] > at > com.vividsolutions.jts.geomgraph.EdgeEndStar.propagateSideLabels(EdgeEndStar.java:298) > at > com.vividsolutions.jts.geomgraph.EdgeEndStar.computeLabelling(EdgeEndStar.java:136) > at > com.vividsolutions.jts.geomgraph.DirectedEdgeStar.computeLabelling(DirectedEdgeStar.java:127) > at > com.vividsolutions.jts.operation.overlay.OverlayOp.computeLabelling(OverlayOp.java:373) > at > com.vividsolutions.jts.operation.overlay.OverlayOp.computeOverlay(OverlayOp.java:173) > at > com.vividsolutions.jts.operation.overlay.OverlayOp.getResultGeometry(OverlayOp.java:127) > at > com.vividsolutions.jts.operation.overlay.OverlayOp.overlayOp(OverlayOp.java:66) > at > com.vividsolutions.jts.operation.overlay.snap.SnapOverlayOp.getResultGeometry(SnapOverlayOp.java:68) > at > com.vividsolutions.jts.operation.overlay.snap.SnapOverlayOp.overlayOp(SnapOverlayOp.java:25) > at > com.vividsolutions.jts.operation.overlay.snap.SnapIfNeededOverlayOp.getResultGeometry(SnapIfNeededOverlayOp.java:76) > at > com.vividsolutions.jts.operation.overlay.snap.SnapIfNeededOverlayOp.overlayOp(SnapIfNeededOverlayOp.java:25) > at > com.vividsolutions.jts.geom.Geometry.intersection(Geometry.java:1117) > > When I look at the data in uDig I can see that the ocean area (Black sea) > has a hole that isn't really a hole. E.g the hole starts in p1 goes to p2 > and p3 then back to p2 and ends in p1. I.e the hole has no area. > This kind of holes I have also seen in DNC charts e.g a1316120 and others. I > do not know why NGA creates those kinds of holes but it seems that it is > common in VPF maps/DNC charts. > > I have imported the VPF/DNC maps into a postgis database and clips the > mapfeatures from those geometries and they are also impossible to cut. It is > ok to import the data to the database and view them in uDig and QGIS, but it > is not possible to cut them. > > Does someone have a solution on this problem? This a real show stopper for > me. > > Kind Regards, > Paul > -- > View this message in context: > http://n2.nabble.com/Bug--Geometry-exception-tp2508912p2508912.html > Sent from the geotools-devel mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
