Thanks @bronwyn for elevating my off-the-cuff remark to a feature request.
I had proposed this as a solution for @igranzow 's problem in Taxon Attribute: loading up data. I think having a Taxon geographies subform in the Taxon form would be preferrable to some string tucked away in the Taxon Attributes.
I might have misunderstood the issue, but I would like to have the table anyway. I myself would indeed use it mainly to indicate which areas we’ve got collections from. We started delivering our Taxon Tree to ChecklistBank last year (well, I’ve done it once) and ChecklistBank let’s you include distribution, e.g., https://www.checklistbank.org/dataset/307515/taxon/104681 (I still need to work out how to deliver them in a way ChecklistBank recognises them).
I like @nfshoobs 's idea of having the authoritative distribution of a taxon in Taxon Geographies and using that as a DQ test and issuing a warning when data is entered that places a Taxon outside its know distribution. Even without the DQ test you could use it to manage checklists in Specify (since you already have the infrastructure).
You can do both things, and others, just by adding a pick list to indicate whether the distribution is Authoritative or Inferred. In our Agent geographies subform, I’ve got an Agent role field with possible values Collector and Determiner.
As botanists, we do not really do type localities, but if Geography is granular enough for this purpose that would be a good use too. Just goes to show that there are many possible uses of an Agent Geography table.