Jason, Moira Many thanks for your replies - the ListExploder did the trick. Of course, now I have a couple of follow-on questions: 1. Jason - you recommended using AttributeRemover to trim down the set of feature attributes to only those that I was going to use. In general, is it advisable to always use this approach, rather than carry the full set of attributes across (on the off chance that you might want to use them later on in the transformation)? Are there performance gains to be had, or is it just considered to be good practice generally (e.g. for the sake of clarity)? 2. I'd like to do a similar kind of list processing with the set of coordinates that come with one of my feature types (a Link feature whose spatial representation is a line drawn through a number of X-Y coordinates). However, this feature type doesn't have an explicit attribute which holds the coordinate data, therefore I need a different approach. I can get hold of individual pairs of coordinates via CoordinateFetcher, or I can concatenate the whole set via CoordinateConcatenator, but I can't seem to extract the coordinates such that they could be translated into a database table with one row per coordinate pair, regardless of how many pairs each Link has. Hope this makes sense. Over to you. Thanks Simon
--- In [email protected], "moirasiebert" <[EMAIL PROTECTED]> wrote: > > Hi Simon, > > I was also having a look at your question. Another alternative way > to do this is to run your NetworkMember list through the > ListExploder Transformer, this will create a separate table. You can > then do a one to many join with the other table based on Road_ID. > > Best Regards, > Moira > > Moira Siebert > Inside Sales - Safe Software Inc. > T: (604) 501-9985 x 261 > [EMAIL PROTECTED] > > > --- In [email protected], "Jason Birch" <jason.birch@> wrote: > > > > Hi Simon, > > > > When you're using attributes that end in braces {} these are known > as > > lists in FME, and are a very powerful construct. There are many > > transformers that can generate lists after grouping operations, and > > there are many other transformers (with List in their name) that > are > > specifically for list manipulation. Individual elements in lists > can be > > exposed one element at a time by right-clicking on the list > attribute > > name under a transformer and choosing "Expose Element". > > > > In your specific case, I would run the Roads data through an > > AttributeRemover, only keeping ROAD_ID and NETWORKMEMBER{}. Then I > > would use a ListExploder to generate individual rows for each list > item. > > > > Jason > > Join us at the FME Worldwide User Conference Sept. 21-22, 2006 Vancouver BC Canada. For more information, visit www.safe.com/2006uc. 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/
