Contingency values - and how to add field values that are not in the contingency table while collecting data

[JayHodny]

Good afternoon,  I have been developing an in-house tree inventory field application. I borrowed the tree taxonomy data from the Esri tree management solution.  I have managed to get the contingency choice functioning in Field Maps.  I select a common name from the list and the remaining genus, species, etc. fields auto-populate.  Our city arborist is asking for more flexibility.  He wants to have the option to enter the taxonomy for trees not in the current contingent list, e.g., an imported tree having no common name in the current listing.  He would like to be able to enter the taxonomy information manually whenever he encounters a tree he wants to add to our inventory but is lacking the contingent value taxonomy information.  Is there a way to allow for entering taxonomy data in the taxonomy fields where these values are not listed in the contingency?   Or, is there another option?  If he knows the taxonomy for trees not in the table, I can update the table later, republish the service, etc., but we are looking for a way to enter the data 'real time' in the field.  Thanks in advance, Jay

[Laura]

If the fields are configured with domains, you’ll need to update those settings in ArcGIS Pro and overwrite the service for the changes to take effect.

One option to consider is using a subtype field. You could define Subtype 1 as your standard trees—those that fit within your existing domains—and apply domains to the taxonomy fields for that subtype. Subtype 2 could represent imported or unlisted trees that don’t yet have a defined domain value. For this subtype, the taxonomy fields would have no domains applied, allowing free-text entry.

You shouldn’t need to duplicate fields if you configure the domains by subtype.

Reference:
https://doc.arcgis.com/en/insights/latest/get-started/domains-and-subtypes.htm

and https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-subtypes.htm

[JayHodny]

Hi Laura, thanks for the reply.  I don't have much experience with subtypes.  Would the contingency workflow still be used for the standard trees?  Thanks, Jay

[Laura]

yes!

[JayHodny]

Hi Laura, that is good to know that my contingent work can be included.  I am still in the dark a bit on how to do this.  My colleagues and I do not have much experience in this area of ArcGIS.  If you or someone reading here can supply some higher-level steps, I would greatly appreciate it.  Many thanks, Jay

[Laura]

You can set up subtypes through the attribute table. Open the table in Fields View, then select Subtypes at the top. From there, choose Create/Manage and add whatever you need. In your case, you would create two options: Other and Trees (with the built-in taxonomy). Once the subtypes are set up, you can assign domains to specific fields for each subtype through the table. 

In the image above you can see my 5 subtypes and the ability to choose  domain for each field by subtype. 

[DavidSolari · Accepted solution]

Like Laura mentioned, subtypes, domains and contingent values all have to be prepopulated by data managers and can't be altered by regular editors. The usual escape hatch is to make one choice an "Other" and then have a text field that only appears when that "Other" is picked. You'll have to use that other text value whenever you do any reporting (arcade expressions can help here) and you can also do regular audits to port those Other entries to proper codes if that helps.

[JayHodny]

David, thanks for the reply.