A better way would be to encapsulate the Tester and AttributeSetter inside a custom transformer. It'll help tidy the workspace and you may be able to publish and share some of the parameters so you aren't having to set them in so many places.
Alternatively the StringReplacer might be of use. If you set the output attribute name to be the same as the source you wouldn't need an AttributeXxxx transformer and I don't think there would be any problems. Again you could publish the regular expression or replacement text settings to avoid having to set them multiple times. 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 --- In [email protected], "Jason Birch" <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm looking for a transformer or procedure that mimics the behaviour of > the NullAttributeReplacer, but with a different value than NULL. For > instance, I want to replace the value of a list of attributes with the > word "UNKNOWN" if their current value is "0". Currently, I'm using a > huge string of Testers and AttributeSetters, but there has to be a > better way... > > Thanks, > Jason > 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/
