Thanks Mark, worked beautifully although I did use the following syntax: LINE:direction POINT:fme_node_angle . I will see if that causes problems further down the line.
Another more complicated question: I have a "custom" transformer that parses XML that is in one of the attributes on the feature entering the transformer. So basically the one XML attribute creates several new attributes on the feature depending on what is in the XML. As the XML may contain several different elements I can't really add these as defined output in the .fmx file. Is there a way to somehow identify the new attributes added to the feature (in the FME Objects code) and 'expose' them in the output? PS: How should the "custom" transformers be referred to in future to avoid confusion? Thanks Gunter --- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote: > > Hi Gunther, > For everyone's info - I think these are "custom" transformers in that > they've apparently been written from scratch (with the FME Objects > API?). I wouldn't want anyone to think this was related to the custom > transformers you can create within Workbench. > > Anyway, I believe these go in the fmx file. Check out the fmesuite.fmx > for examples. The field appears to be called ATTRIBUTES_ADDED, eg... > > ATTRIBUTES_ADDED: LINE:{}.direction POINT:{}.fme_node_angle > > I think the LINE and POINT parts refer to which port features emerge > from, and so aren't always needed. But the syntax can be tricky, so if > you have problems let me know and I'll query someone in our > development team. > > Hope this helps > > 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], "gunter_nt" <gunter_nt@> wrote: > > > > Hi, > > We have written a few custom transformers which add new attributes > > to the passing features within the c++ code. > > Is there an easy way to add these new attibutes to the > > transformers/*.fmx file so that they are visible as output > > attributes? > > > > Currently I use an attribute creator and define the needed > > attributes (as null) before it gets passed into the custom > > transformer. > > > > Thanks in advance! > > > > Gunter > > > 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. Safe Software has also made slides available that outline enhancements planned for FME 2007. The slides are from the "Road Ahead" presentation given on Day 2 of the FME Worldwide Users Conference. To view these slides, visit www.safe.com/2006uc. 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/
