I am writing a routine to check an incoming dataset before loading. The first step is to make sure the dataset has all the required attributes, the second step is to make sure the values in the attributes are valid. I am using the AttributeValidator for this second step. Unfortunately, when I am validating a value, I have to hardcode all the values in the Rule Configuration box. I would like to be able to read a table and get these values and populate it in the Rule Configuration box. How can I do this?
Solved
populate the values for the "in" validation rule from a list
+16- Enthusiast
Best answer by takashi
Hi @tnarladni, the Rule Configuration field in the AttributeValidator doesn't have any function that allows you to import the rule from an external table, but you can use an attribute value as a rule configuration here. For the In operator, if you add an attribute that stores comma-separated valid values to every input feature, you can then select it as the Rule Configuration.
For example, if the valid values are stored in a text file (a value per a row), read it with the Text File reader, concatenate the values with comma-separated format (Aggregator), merge it to all the features unconditionally (FeatureMerger), and set the concatenated values to the Rule Configuration in the AttributeValidator.
+19- Safer
Hi @tnarladni, at this time there is currently no way to import a list of rules into the AttributeValidator. I recommend up-voting on the Idea to have it added: Add import attributes button on AttributeValidator .
- Best Answer
Hi @tnarladni, the Rule Configuration field in the AttributeValidator doesn't have any function that allows you to import the rule from an external table, but you can use an attribute value as a rule configuration here. For the In operator, if you add an attribute that stores comma-separated valid values to every input feature, you can then select it as the Rule Configuration.
For example, if the valid values are stored in a text file (a value per a row), read it with the Text File reader, concatenate the values with comma-separated format (Aggregator), merge it to all the features unconditionally (FeatureMerger), and set the concatenated values to the Rule Configuration in the AttributeValidator.
+16- Enthusiast
takashi wrote:
Hi @tnarladni, the Rule Configuration field in the AttributeValidator doesn't have any function that allows you to import the rule from an external table, but you can use an attribute value as a rule configuration here. For the In operator, if you add an attribute that stores comma-separated valid values to every input feature, you can then select it as the Rule Configuration.
For example, if the valid values are stored in a text file (a value per a row), read it with the Text File reader, concatenate the values with comma-separated format (Aggregator), merge it to all the features unconditionally (FeatureMerger), and set the concatenated values to the Rule Configuration in the AttributeValidator.
+16- Enthusiast
fmelizard wrote:
Hi @tnarladni, at this time there is currently no way to import a list of rules into the AttributeValidator. I recommend up-voting on the Idea to have it added: Add import attributes button on AttributeValidator .
+18- Contributor
Why not use the list (from a CSV file or any other format) and validate being in the list by merging on the list values (FeatureMerger): Merged: value is in the list, Not Merged: invalid value.
+16- Enthusiast
erik_jan wrote:
Why not use the list (from a CSV file or any other format) and validate being in the list by merging on the list values (FeatureMerger): Merged: value is in the list, Not Merged: invalid value.
+18- Contributor
tnarladni wrote:
Thanks for the suggestion @erik_jan. The reason why FeatureMerger would not work well in this case is because there are multiple fields that need to be validated, including whether or not there are nulls in the fields. It is cleaner to put all the validation rules into one transformer versus multiple featureMerger and testers.
+16- Enthusiast
takashi wrote:
Hi @tnarladni, the Rule Configuration field in the AttributeValidator doesn't have any function that allows you to import the rule from an external table, but you can use an attribute value as a rule configuration here. For the In operator, if you add an attribute that stores comma-separated valid values to every input feature, you can then select it as the Rule Configuration.
For example, if the valid values are stored in a text file (a value per a row), read it with the Text File reader, concatenate the values with comma-separated format (Aggregator), merge it to all the features unconditionally (FeatureMerger), and set the concatenated values to the Rule Configuration in the AttributeValidator.
accessroad.fmw
takashi wrote:
Hi @tnarladni, the Rule Configuration field in the AttributeValidator doesn't have any function that allows you to import the rule from an external table, but you can use an attribute value as a rule configuration here. For the In operator, if you add an attribute that stores comma-separated valid values to every input feature, you can then select it as the Rule Configuration.
For example, if the valid values are stored in a text file (a value per a row), read it with the Text File reader, concatenate the values with comma-separated format (Aggregator), merge it to all the features unconditionally (FeatureMerger), and set the concatenated values to the Rule Configuration in the AttributeValidator.
And, you have to merge the code list(s) to the features which you need to validate with the AttributeValidator. Looks like the attribute "Code" has been created with the Aggregator and it would be merged to the 11 features, but it won't be merged to the 180 features output from the FeatureReader_2. Is it your intention?
+16- Enthusiast
takashi wrote:
As far as I see your screenshot, not clear why you cannot create code lists with different names for each rule.
And, you have to merge the code list(s) to the features which you need to validate with the AttributeValidator. Looks like the attribute "Code" has been created with the Aggregator and it would be merged to the 11 features, but it won't be merged to the 180 features output from the FeatureReader_2. Is it your intention?
So the 11 that is used in the FeatureMerger is the field names. and the 180 FeatureReader is the actual features
The domain table was something I created so if you think it should be done a different way, I am open to that as well.
takashi wrote:
Hi @tnarladni, the Rule Configuration field in the AttributeValidator doesn't have any function that allows you to import the rule from an external table, but you can use an attribute value as a rule configuration here. For the In operator, if you add an attribute that stores comma-separated valid values to every input feature, you can then select it as the Rule Configuration.
For example, if the valid values are stored in a text file (a value per a row), read it with the Text File reader, concatenate the values with comma-separated format (Aggregator), merge it to all the features unconditionally (FeatureMerger), and set the concatenated values to the Rule Configuration in the AttributeValidator.
Field,Code
PermTemp,PT1
PermTemp,PT2
PermTemp,PT3
PublicPriv,PP1
PublicPriv,PP2
PublicPriv,PP3
NewExist,NE1
NewExist,NE2
NewExist,NE3
SurfaceMat,SM1
SurfaceMat,SM2
SurfaceMat,SM3
tnarladni wrote:
I am at another crossroad. @takashi, I would appreciate your thoughts/solution. First, I am using a featureReader and schema reader to compare the schemas. Then I read in an SDE table which has a list of fields, and all the codes associated with those fields. I use the aggregator to form a comma delimited list for each of the "field". Then using the FeatureMerger, I get just those lists that needs to be validated against. So here's the problem, the lists are all called Code. The only way to know which Code list to use is another field called "Field". Help!
accessroad.fmw
Field,Code
PermTemp,PT1
PermTemp,PT2
PermTemp,PT3
PublicPriv,PP1
PublicPriv,PP2
PublicPriv,PP3
NewExist,NE1
NewExist,NE2
NewExist,NE3
SurfaceMat,SM1
SurfaceMat,SM2
SurfaceMat,SM3
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.