Skip to main content
Archived

New/modified GUI type for nested list parameters

Related products:FME Form
  • rylanatsafe
    rylanatsafe
  • siennaatsafe
    siennaatsafe
  • geosander
    geosander
  • cwarren
    cwarren
  • marcandre

geosander

Probably no one is going to vote for this, but I need the user to be able to select only the deepest nested list in a published parameter. For example, consider these list attributes:

_list{0}.sublist{0}
_list{0}.sublist{0}.attribute1
_list{0}.sublist{0}.attribute2

_list{0}.sublist{1}
_list{0}.sublist{1}.attribute1
_list{0}.sublist{1}.attribute2

_list{1}.sublist{0}
_list{1}.sublist{0}.attribute1
_list{1}.sublist{0}.attribute2

_list{1}.sublist{1}
_list{1}.sublist{1}.attribute1
_list{1}.sublist{1}.attribute2

Currently, in FME, a user can only select the whole nested list above (e.g. _list{}.sublist{}) or a single item in the list by specifying all list keys (e.g. _list{1}.sublist{0}.attribute1).

What I would like, is to return a specific set of "children" as a list, e.g. _list{1}.sublist{} (notice the 1!!).
When I'd call feature.getAttribute('_list{1}.sublist{}') in a PythonCaller, it will fetch the following list attributes:

_list{1}.sublist{0}
_list{1}.sublist{1}

Those are the "root children" of the second "parent".
Specifying _list{0}.sublist{}.attribute1 will fetch:

_list{0}.sublist{0}.attribute1
_list{0}.sublist{1}.attribute1

Those are "named children" of the first "parent".

I already have 2 situations (the ListKeyValuePairExtractor and the ListAppender I'm currently working on) for which a new/modified GUI type for a published parameter would be very helpful.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

rylanatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • August 30, 2017

@sander_s - After chatting with our Development Team, my understanding is that once "List Append" and "List Demotion" are implemented into the product (i.e. natively) that the need for the Python workaround will not be needed. It is not clear if a new GUI type will be addressed at the same time, but it should at least provide a medium step forward to alleviating the pain!

 

FWIW, @DeanAtSafe created a ListDemoter custom transformer. Perhaps not exactly related to this discussion, but perhaps alluring to an XML enthusiast! ;)


geosander
Forum|alt.badge.img+7
  • Author
  • August 31, 2017
Hi @RylanAtSafe,

 

If "list append" is going to be implemented into the product soon, I don't need to finish my ListAppender custom transformer anymore... :\\

 

Either way, I guess that once these new functions are built in, you will have to provide a way for users to select a nested child list somehow, so I'm hoping the GUI types will be improved for that. Might still be useful for future custom transformers and plug-ins!

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings