Bug #2585
closedAllow ambiguous records only in states where taxon occurs
0%
Description
In some cases records are treated as ambiguous for no apparent reason. For example, a search on Adiantum pedatum shows records from NCU, USDA, RAB and CVS. The NCU records are mapped as ambiguous, while none of those for the other sources are treated this way, even though all are for the same taxon.
RKP:
This is NOT an error. The source of the confusion is that Weakley recognizes A. aleuticum as a segregate of the nominal A. pedatum, so all specimens of A. pedatum are ambiguous as to whether they are really A. pedatum or A. aleuticum. Other data layers are not ambiguous as they map to specific and unambiguous concepts.
RKP:
Note that A. aleuticum occurs in our area only in MD. We have discussed having an improvement in the map generation algorithm such that a check is made on differences in ambiguity by state based on a list of which Weakley taxa are known for each state. If we were to implement this (which would take some time), then A. pedatum specimens would be ambiguous only in MD.