i don’t think there’s a bug here.
clarifying a bit, it’s not that the CV doesn’t recognize and suggest S. carolinensis. it’s that it won’t suggest it if you include only suggestions expected nearby. if you include suggestions no expected nearby, you can see that S. carolinensis is the top suggestion (i.e. the top visual match):
if you look at the geomodel range for S. carolinensis, you can see that the geomodel thinks the taxon could exist in the area (in the unthresholded view), but in your particular location, it falls below the threshold for being expected nearby.
i think part of the issue is threshold, and part of the issue is the granularity (or lack thereof) of the prediction, but the main thing is probably just that no model is going to have perfect predictions for every taxon.
