You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I can only create collectors in a Groovy function. Especially in conjunction with #185 it would make collectors much more powerful if it was possible to define a collector by piggy-backing it on any other function.
Using this feature, function #185 and enhancement #307 together enables use cases like these:
Collect IDs of all Features of a specific Feature Type and then create local references, e.g. from a Network to its members
Collect Geometries and then assign all of them together without requiring use of a computationally expensive Merge
Collect IDs of Features and group them according to a value in the source data structure so as to create references to other features in a hierarchy, e.g. for lowerLevelUnits in AdministrativeUnits
Workflow:
Select source and target schema element as need for the function, e.g. "Formatted String"
Go through the regular steps of configuring the function
On the "Additional Options" page, add option to collect results (checkbox) in a named collector (text input)
Optionally, add a source mapping anchor (selector for a field in the source data structure) to store Key-Value pairs for the collected value and a key;
Enhancement: Differentiate between the initial function creation and later function editing steps. It might make sense to have a subset of options such as "Define Collector" only available in editing, so as not to make the initial function setup process too long.
The text was updated successfully, but these errors were encountered:
Currently, I can only create collectors in a Groovy function. Especially in conjunction with #185 it would make collectors much more powerful if it was possible to define a collector by piggy-backing it on any other function.
Using this feature, function #185 and enhancement #307 together enables use cases like these:
Network
to itsmembers
lowerLevelUnits
inAdministrativeUnits
Workflow:
Enhancement: Differentiate between the initial function creation and later function editing steps. It might make sense to have a subset of options such as "Define Collector" only available in editing, so as not to make the initial function setup process too long.
The text was updated successfully, but these errors were encountered: