Import Taxonomic coverage does not handle code/definition enumerations very well
In a data package where some columns were annotated to use an enumerated domain (code=definition) the taxonomic import wizard columns (you select from) were offset. In this case it was by two. Still trying to generalize this behavior and replicate it myself.
#1 Updated by ben leinfelder almost 8 years ago
There was a slight bug in how the code/def values were retrieved from attributes that provided them. We were processing a subset of the columns, but mixing up array indexes in the subset with array indexes in the complete set.
The fix is committed to both trunk and the 1.10.0 branch (for potential 1.10.1 release)