Best answer by david_r
View original
Can I export source and destination values from the AttributeValueMapper?
I have a very long list of attributes that I have typed into an AttributeValueMapper transformer. I now want to share this mapping with someone (not an FME user), so I would like to export the source and destination values to excel. I see that there is a button to import to this transformer, but not one to export. Is there a way around this, or doing I have a lot of typing to do?
Page 1 / 2
Userlevel 1
+21
- Contributor
- 3079 replies
-
5 March 2015
Can you not just write out the source and desitination attributes to a csv after passing through a duplicate remover?
+3
If all the source values are present prior to going into the Valuemapper, you can, as Grommm suggested, write them out to txt\\csv using the FileWriter.
Sameway you can use filewriter to write destination vlaues after the Valuemapper.
Of course it is somewhat more handy to create the ValueMap in a txt-file int he first place..
I dont think I was using all of the values so I ended up opening up the FMW in a text editor and did some find a replaces.
+4
I have this same problem, except I don't have a source dataset with all the values in it.
Just inherited an AttributeValueMapper with a long list of Source and Destination values (about 300), and now have no way of getting them out of there. Any suggestions? Maybe @takashi knows?
Userlevel 2
+16
- Contributor
- 2180 replies
-
16 February 2017
And this is exactly why you should use a Joiner, joining for example to CSV or Excel, instead of an AttributeValueMapper if you have a large number of values you want to map.
Userlevel 3
+17
- Contributor
- 7538 replies
-
16 February 2017
I have this same problem, except I don't have a source dataset with all the values in it.
Just inherited an AttributeValueMapper with a long list of Source and Destination values (about 300), and now have no way of getting them out of there. Any suggestions? Maybe @takashi knows?
+4
And this is exactly why you should use a Joiner, joining for example to CSV or Excel, instead of an AttributeValueMapper if you have a large number of values you want to map.
Userlevel 3
+17
- Contributor
- 7538 replies
-
16 February 2017
Joiner no longer exists. There is now a DatabaseJoiner, but that cannot be used for joining to Excel or a CSV. What would you suggest using instead? FeatureMerger?
Userlevel 2
+16
- Contributor
- 2180 replies
-
16 February 2017
Joiner no longer exists. There is now a DatabaseJoiner, but that cannot be used for joining to Excel or a CSV. What would you suggest using instead? FeatureMerger?
Userlevel 2
+16
- Contributor
- 2180 replies
-
17 February 2017
I do have a quick (and dirty) workaround for this:
Copy the AttributeValueMapper in the workspace to the clipboard.
The open a text editor (notepad or similar) and paste from the clipboard.
This will give you the definition of the transformer (including a list of all values) in text format.
This can be read (after a little editing) using the CSV reader.
Userlevel 3
+17
- Contributor
- 7538 replies
-
17 February 2017
I do have a quick (and dirty) workaround for this:
Copy the AttributeValueMapper in the workspace to the clipboard.
The open a text editor (notepad or similar) and paste from the clipboard.
This will give you the definition of the transformer (including a list of all values) in text format.
This can be read (after a little editing) using the CSV reader.
The attachment is an experimental workspace, which demonstrates a possible way to parse a workspace (*.fmw) with the FMW reader, extract source/destination values from AttributeValueMapper parameters setting, and decode them.
extract-mapping-table-from-attributevaluemapper.fmw (FME 2016.1.3.1)
+16
- Contributor
- 1425 replies
-
17 February 2017
Next to the joiner another possibility to use the external mapping file is the SchemaMapper.
I usually try to avoid the AttributeValueMapper as much as possible and just use it in 'throw away' workspaces.
+6
I do have a quick (and dirty) workaround for this:
Copy the AttributeValueMapper in the workspace to the clipboard.
The open a text editor (notepad or similar) and paste from the clipboard.
This will give you the definition of the transformer (including a list of all values) in text format.
This can be read (after a little editing) using the CSV reader.
@takashi
The workspace you provided is excellent, thanks.
But I also found another simple way to avoid the problem of coding,
That is, first create the Summary Annotation for AttributeValueMapper, and then copy the Annotion paste into the text editor.
Userlevel 5
- 8179 replies
-
20 February 2017
@takashi
The workspace you provided is excellent, thanks.
But I also found another simple way to avoid the problem of coding,
That is, first create the Summary Annotation for AttributeValueMapper, and then copy the Annotion paste into the text editor.
Userlevel 3
+17
- Contributor
- 7538 replies
-
20 February 2017
@takashi
The workspace you provided is excellent, thanks.
But I also found another simple way to avoid the problem of coding,
That is, first create the Summary Annotation for AttributeValueMapper, and then copy the Annotion paste into the text editor.
+6
@takashi
The workspace you provided is excellent, thanks.
But I also found another simple way to avoid the problem of coding,
That is, first create the Summary Annotation for AttributeValueMapper, and then copy the Annotion paste into the text editor.
The advantage of this method is not only can be applied to Transformer, can also be applied to user parameters, For example, get the values of choice type parameters etc.
Userlevel 3
+17
- Contributor
- 7538 replies
-
20 February 2017
I
found that there is another way, directly open the workspace(*.fmv) with a
text editor, Find the desired row by searching for a list value, and then copy the required content.
can also be applied to user parameters, For example, get the values of choice type parameters etc.
found that there is another way, directly open the workspace(*.fmv) with a
text editor, Find the desired row by searching for a list value, and then copy the required content.
The advantage of this method is not only can be applied to Transformer,
can also be applied to user parameters, For example, get the values of choice type parameters etc.
#! <XFORM_PARM PARM_NAME="LUT" PARM_VALUE="<u65e5><u672c><u8a9e>,<u6bcd><u56fd><u8a9e>,<u82f1><u8a9e>,<u5916><u56fd><u8a9e>"/>
Userlevel 5
- 8179 replies
-
20 February 2017
The disadvantage of the method is that unicode characters and some special characters within the AttributeValueMapper parameters have been encoded. e.g.
#! <XFORM_PARM PARM_NAME="LUT" PARM_VALUE="<u65e5><u672c><u8a9e>,<u6bcd><u56fd><u8a9e>,<u82f1><u8a9e>,<u5916><u56fd><u8a9e>"/>
from fmeobjects import FMESession
def DecodeText(feature):
text = feature.getAttribute('text')
decoded_text = FMESession().decodeFromFMEParsableText(text)
feature.setAttribute('text', decoded_text)
`text' has value `="???,???,??,???'The disadvantage of the method is that unicode characters and some special characters within the AttributeValueMapper parameters have been encoded. e.g.
#! <XFORM_PARM PARM_NAME="LUT" PARM_VALUE="<u65e5><u672c><u8a9e>,<u6bcd><u56fd><u8a9e>,<u82f1><u8a9e>,<u5916><u56fd><u8a9e>"/>
However,
you can use the first method to get the list value of transformer, and
use second methods to get values of user parameters.
In
addition, I query some information, as well as after testing, found
that Python can be relatively simple to restore these characters.
def processFeature(feature): s= u'\u65e5\u672c\u8a9e' feature.setAttribute("attr",s)
Userlevel 3
+17
- Contributor
- 7538 replies
-
20 February 2017
The disadvantage of the method is that unicode characters and some special characters within the AttributeValueMapper parameters have been encoded. e.g.
#! <XFORM_PARM PARM_NAME="LUT" PARM_VALUE="<u65e5><u672c><u8a9e>,<u6bcd><u56fd><u8a9e>,<u82f1><u8a9e>,<u5916><u56fd><u8a9e>"/>
Userlevel 5
- 8179 replies
-
20 February 2017
- Best Answer
Attached is a workspace (FME 2016.1.3+ required) that uses the workspace reader to export all the AttributeValueMapper settings of a specified workspace to a CSV file. The resulting CSV file has a column for the transformer name and the source and destination values. It should be handling international characters just fine (but do let me know if it doesn't).
Sample input:
Output generated by exportattributevaluemapper.fmw, as imported into Excel:
It should be fairly simple to extend so as to include the default values as well as the source and destination attribute names.
Main workspace: exportattributevaluemapper.fmw
Test workspace: avm.fmw
Output from test workspace: attributevaluemappersettings.csv
Userlevel 3
+17
- Contributor
- 7538 replies
-
20 February 2017
Attached is a workspace (FME 2016.1.3+ required) that uses the workspace reader to export all the AttributeValueMapper settings of a specified workspace to a CSV file. The resulting CSV file has a column for the transformer name and the source and destination values. It should be handling international characters just fine (but do let me know if it doesn't).
Sample input:
Output generated by exportattributevaluemapper.fmw, as imported into Excel:
It should be fairly simple to extend so as to include the default values as well as the source and destination attribute names.
Main workspace: exportattributevaluemapper.fmw
Test workspace: avm.fmw
Output from test workspace: attributevaluemappersettings.csv
Userlevel 5
- 8179 replies
-
20 February 2017
@david_r, thanks for sharing the elegant Python script. To make it robuster, I would suggest modifying the script so that decoding will be performed after splitting the parameter by commas. Because, if a source or destination string value had a comma, it has been encoded as "<comma>" here and it can not be decoded before splitting.
Userlevel 3
+17
- Contributor
- 7538 replies
-
20 February 2017
The disadvantage of the method is that unicode characters and some special characters within the AttributeValueMapper parameters have been encoded. e.g.
#! <XFORM_PARM PARM_NAME="LUT" PARM_VALUE="<u65e5><u672c><u8a9e>,<u6bcd><u56fd><u8a9e>,<u82f1><u8a9e>,<u5916><u56fd><u8a9e>"/>
+4
- Contributor
- 13 replies
-
13 March 2020
Attached is a workspace (FME 2016.1.3+ required) that uses the workspace reader to export all the AttributeValueMapper settings of a specified workspace to a CSV file. The resulting CSV file has a column for the transformer name and the source and destination values. It should be handling international characters just fine (but do let me know if it doesn't).
Sample input:
Output generated by exportattributevaluemapper.fmw, as imported into Excel:
It should be fairly simple to extend so as to include the default values as well as the source and destination attribute names.
Main workspace: exportattributevaluemapper.fmw
Test workspace: avm.fmw
Output from test workspace: attributevaluemappersettings.csv
David, This is awesome. Thank you so much for sharing.
Page 1 / 2
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.