See http://www.fmepedia.com/index.php/CustomTester on fmepedia for an example of this.
What I did was used the Grepper instead of the Tester, because I wasn't sure if case sensitivity is an issue - ie UNSET or unset? Grepper has the "case sensitive" option to avoid the problem. The downside is that any other string with "unset" in it will be wiped too (eg "Hawaii is known for its beautiful sunsets") It's a simple custom transformer - but a good example of how to publish a parameter and then share it between different settings. BTW - using a Tester is more difficult because of the need to select (ie publish) the one "testee" attribute, but not the other. It can be done: AttributeCreator to create attr1 AttributeSetter to set attr1 = <published attr> Tester attr1=unset AttributeSetter to set <published attr> = null (for Tester passes) ...BUT it isn't very neat and the same published parameter can't be shared so you need to be set one twice. Dale - can I rather cheekily challenge you to allow the Tester testees to be published separately!? Mark --- In [email protected], "Dale Lutz" <[EMAIL PROTECTED]> wrote: > > Hi, > > If the issue is that the attribute in question indeed has the value > "unset" as its real value, then what I'd suggest is to make a custom > transformer that takes as an input an attribute name, and then tests > if this attribute has the value "unset" via a tester transformer, and > then sets said attribute to "" (nothing). > > Mark I -- can I challenge you to create such a custom xformer (I'm > curious if it can be done) and then post it here, showing it used to > do this to a couple of different attributes. > > Thanks. > > Dale > > > > Hi SK, > > Not sure what the difference is between unset and null (or unset and > a > > blank entry). > > > > You could try the NullAttributeReplacer transformer to see if this > > locates the problem features - set them to -999 (for example) then > use > > a Tester to filter them into a different stream to handle them. > > > > Or just try a Tester with a blank value in the test field. > > > > Hope this helps some, > > > > 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], "skhapre" <skhapre@> wrote: > > > > > > Hi All > > > > > > I am using FME to export data from Smallworld 4.0 to ESRI Shape > files. > > > When the attribute values are unset in Smallworld they as passed as > > > unset to ESRI. I want to pass them as null instead of unset. I have > > > around 23 different attributes having similar condition. Is it > > > possible to use filter or similar thing to replace the unset to > null. > > > > > > plz suggets! > 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/
