Hi Mark, I think you're better off doing this kind of operation with the TopologyBuilder. With the NeighborFinder, you risk selecting a polygon that does not share an edge with the sliver and it gives you finer control over the rules you select for doing the merge.
For instance, you can choose to use the largest adjoining polygon, or you can choose to merge with the polygon that shares the longest boundary with the sliver, or you can use a composite rule of segment length and polygon attribute, or... It's more robust doing it the hard way, and it's not really all that hard. I spent six years of my life working with ArcInfo/PC ArcInfo/Oracle/Foxpro routines that did this kind of validation. FME is so much nicer to work with... :) Jason -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of mark2atsafe Sent: Wednesday, June 08, 2005 10:30 To: [email protected] Subject: [fme] Re: Data Cleansing Hi Larry, Check out... ftp.safe.com/outgoing/overlap-sliver removal.zip Does a similar thing but with overlaps. I think the NeighbourFinder would be the way to go. Assuming each feature has an ID each 'gap' polygon can grab an ID from its neighbour. Then use Dissolve with a group-by on the ID attribute. The above workspace does the same thing but gets the ID from an areaonarea overlay of the overlapping polygons. Regards, Mark Mark Ireland, Product Support Engineer Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
