I am setting up Geodatabase Domains for my Fire Hydrant layer. The Domain restricts the "Type" of Fire Hydrant to a designated list of Brand Names. I'm running into an issue where some of my coded values behave differently than others. 
As seen above, on the left is the "Select By Attribute" window, on the right is the Geodatabase Domain.
Coded Domain Values for "Mueller" display in the Attribute Table only as the description 'Mueller'. This is how I expect them to behave.
However, the Coded Domain Values that have a description containing special characters display as something different.
You'll notice that I have two query options for the brand "M&H".
Are the special characters in the description messing things up, or should I just scrap the "HydrantType" domain and rebuild it?
Answer
As Richard's comment points out, the issue here isn't the special characters. Domains aren't enforced until time of validation (Validate Features on Editor toolbar), so even if a field has a domain on it you can enter whatever you want to the field. In this case, it appears that the description rather than the value code has been entered. This is evidenced by the screenshot of the Select by Attributes dialog on the left of your image, which shows all unique values actually in the data entered in that field. Coded values show up as code - description while cases where the description has been entered directly it's that in single quotes. Also, as Richard further points out, Domains aren't retroactive - they don't change existing data when applied, though they would then fail validation.
No comments:
Post a Comment