Domains have the fields 'Code' and 'Description'.
We experience that different users have different perceptions of the different entries in domains. Therefore we think a more detailed explanation, than the one suitable for the 'Description' field, could assist users in selecting the appropriate values.
This kind of detailed explanation would be suitable for metadata.
Therefore my idea is to enable metadata for domains in ArcGIS similar to the way metadata works for featureclasses.
The kind of geodatabase domains discussed here are the ones accessible via Data » Domains in ArcGIS Pro.
It would be handy if we could store additional information/columns in GDB domains. So that we could use that additional data in SQL queries, reports, labels etc.
Thanks for submitting the idea @Bud We're going to need some additional details to understand what you're looking for here. Can you describe the problem you're trying to solve along with any examples you might have?
Thank you for providing additional details, Bud.
So that we could use that additional data in SQL queries, reports, labels etc.
- CODE [domain coded value]
- NAME [domain description]
- Additional field: DETAILS
So for your additional queries, reports, labels, etc. you want to run those directly against a domain table?
In Oracle, we can select the domain data from the XML system tables as follows:
select substr(extractvalue(codedvalues.column_value,'CodedValue/Code'),1,255) as code, substr(extractvalue(codedvalues.column_value,'CodedValue/Name'),1,255) as description from sde.gdb_items_vw i join sde.gdb_itemtypes it on i.type = it.uuid, table(xmlsequence(xmltype(definition).extract('/GPCodedValueDomain2/CodedValues/CodedValue'))) codedvalues where i.name = 'PIPE_MATERIALS'
So we can already use the domain data in queries, reports, labels etc.
But what we can't do is store additional information/columns in the domain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.