Hello Andrew, In this case I would simply use an AttributeCreator to create an attribute for each table. For the first table create an attribute called dataType and give it the value base. For the second create an attribute again called dataType, but this time give it the value bndy
Then in the Matcher, use the "Attributes that must Differ" setting and select the dataType attribute. This will solve the problem of base features matching against themselves. Then I'd be tempted to change the Lenient Geometry Matching setting to Yes. This will ensure a match where the x/y coords are the same, but the direction of the line is different (for example). You might also use the FME Viewer to check the coordinates of two features that you think ought to match to find out what the problem is. The data in the Viewer is how FME Workbench sees it, so you will be able to tell the problem by browsing the coordinates. Make sure you have the view option "view all decimal places" turned on. If the coordinates are slightly different - eg one is to 4 decimal places, the other 3, then use a CoordinateRounder transformer in Workbench to solve the issue. One other thing you could try is the ChangeDetector transformer instead of the Matcher. That way it has separate ports for Original (base) and Revised (bndy). The "unchanged" output port would be what you need. Another matching method is the CRCCalculator transformer. Here's a good example: http://www.fmepedia.com/index.php/CRCCalculator_Example Hope some of this helps, Regards, Mark Mark Ireland, Senior Product Specialist Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access --- In [email protected], "Andrew Newman" <[EMAIL PROTECTED]> wrote: > > Hello > > I have two tables of line features. Both tables are in MapInfo Tab > format and share the same projection. > > One table contains base lines (base) and one boudary lines (bndy), > some of the bndy features are duplicates of features in the base > table and I am trying to identify these! > > There are also duplicate features within the base table but these are > valid. > > I thought this would be fairly simple to do I have created a > workspace with readers for the two tables and feed these into a > matcher the output from the MATCHED port goes to a writer. > > This is giving me a result but not the one I expected: the duplicate > features within the base table are being identified but features that > are duplicates between base and bndy are not! > > I use FME faily infrequently and would welcome any help or advice! > > Thanks > Andrew > For insights into what's up at Safe Software and what's on the development horizon, visit Safe's blog at spatial-etl.blogspot.com. Love FME? Then open your diary to March 6-7, 2008 and write this... "Second Worldwide FME User Conference - Must Attend!" See http://www.safe.com/company/fmeuc2008/index.php for more details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/fme/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
