span8
span4
span8
span4
Ideabychris·· attribute handlingvalue modifying
It would be good to replace the attribute value mapper with a ‘bulk attribute value mapper' tool that could do the following:
1.Instead of importing data and it being static - it would be good for the tool to reference a db table/file dynamically so as to always pull in the latest data.
2.Instead of only handling one attribute at a time,it would be good to update multiple attributes at once from multiple lookup locations.
Examples
Source Attribute | Database/File | FeatureType | Lookup Code Attribute | Lookup Value Attribute |
MATERIAL | Oracle GIS_DB | LU_MATERIAL | LCODE | LVALUE |
BEDDING | BeddingLookup.xlsx | Sheet 1 | Code | Value |
In this example the Material AC would be value mapped to Asbestos Cement and the bedding type SND would be value mapped Sand
I understand that this can be done at the moment using a series of feature mergers with process duplicates enables,but this is something that comes up quite frequently as we have multiple datasources that only store the codes and regularly need to be updates to have the description field.
lars_de_vriescommented·
I would use a DatabaseJoiner for the use case you describe.Now you would need multiple DatabaseJoiners.
I would suggest BulkAttributeValueJoiner as the transformer name.
Share your great idea,or help out by voting for other people's ideas.
Option to Select Attributes that should not be Exploded in AttributeExploder
Make custom transformer attributes specific to input/output ports
Aggregator: missing option to not accumulate attributes or use only base
Attribute accumulation for LeftRightSpatialCalculator
Set Conflict resolution per attribute (e.g.FeatureMerger)
Support field indexing in GEODATABASE_FILE writer
Transformer that Exposes all Attributes when Working with Dynamic 亚搏在线Workflows
Add AND/OR logic to Matcher "Attributes that must differ"
© 2019 亚搏在线Safe Software Inc |法律