AppearanceStyler uses RGB values ranging from 0 to 1.
For this reason White ffffff 255,255,255 has to be converted to 1,1,1 or Blue-ish 00aaff 0,170,255 to 0,0.666667,1.
When you set the color manually, AppearanceStyler auto-converts it to the right value after you click OK but if you set it via attribute you have to normalize the RGB values.
AppearanceStyler uses RGB values ranging from 0 to 1.
For this reason White ffffff 255,255,255 has to be converted to 1,1,1 or Blue-ish 00aaff 0,170,255 to 0,0.666667,1.
When you set the color manually, AppearanceStyler auto-converts it to the right value after you click OK but if you set it via attribute you have to normalize the RGB values.
Hi @caracadrian
Thank you for the quick response!
I have since converted my hex values to RGB values and normalised these so that they are between 0 & 1 - however all features are still being rejected by the AppearanceSetter with the fme_rejection_code: EXTRA_APPEARANCE_FEATURE.
Do you know what this menas and how I can fix it?
Thanks!
Hi @caracadrian
Thank you for the quick response!
I have since converted my hex values to RGB values and normalised these so that they are between 0 & 1 - however all features are still being rejected by the AppearanceSetter with the fme_rejection_code: EXTRA_APPEARANCE_FEATURE.
Do you know what this menas and how I can fix it?
Thanks!
As in the screenshot of your workspace, AppearenceStyler is not fully configured (note the red cog on the transformer).
Can you supply a sample of your data and/or your workspace?
Hi @caracadrian
Thank you for the quick response!
I have since converted my hex values to RGB values and normalised these so that they are between 0 & 1 - however all features are still being rejected by the AppearanceSetter with the fme_rejection_code: EXTRA_APPEARANCE_FEATURE.
Do you know what this menas and how I can fix it?
Thanks!
Hi @caracadrian
I have attached a sample of my data and workbench.
Thanks for your help!
Hi @caracadrian
Thank you for the quick response!
I have since converted my hex values to RGB values and normalised these so that they are between 0 & 1 - however all features are still being rejected by the AppearanceSetter with the fme_rejection_code: EXTRA_APPEARANCE_FEATURE.
Do you know what this menas and how I can fix it?
Thanks!
I can't read your gdb sample with the GDB OPEN API.
FileGDB Reader: Feature class 'Beams' has shape type 'esriGeometryMultiPatch' which is unknown to FME. Skipping feature class
Try setting Appearance Name in AppearanceStyler to ObjectType attribute, then do the same in AppearanceSetter.
Also, Appearance Join Attribute and Geometry Join Trait are important in most cases.