Subtypes and domains are fairly useful geodatabase features to know about especially when it comes to data validation and design of editing templates.
Knowing what they are and when to use them can mean the difference between a consistent semi-automatic field data collection experience and database anarchy. We recently looked a little closer at these two features when reviewing a template for collecting weed and other pest observations for a local council or recording tree records for an arborist. Faced with hundreds of different species of weeds, we needed some way to minimize the list of possible values. Continue reading