We had a resource with original coordinates that were incorrect, they were outside of Colombia and it was a clear mistake, so the thing that we made in those cases is delete the decimal coordinates and kept the original coordinates in the verbatimLatitude and verbatimLongitude.
However, we realized that GBIF still interpreted those two fields and plotted the incorrect coordinates with a flag Country coordinate mismatch, as you can see here Occurrence Detail 2294394411.
So we should like to know how different data providers deals with this kind of problem, maybe keeping the whole coordinates in verbatimCoordinates field (we are not sure if GBIF still interpreted that field), or maybe with a comment in georeferenceRemarks saying that the original coordinates are a mistake.
This is an important issue for us, because when we discover incorrect coordinates, we always put them in verbatimCoordinates and delete the decimal fields, we use the decimal in our analysis and not the verbatim. But if GBIF portal always made the transformation, our job is not as useful as it can be for other end users.
We also like to know if there is a way to stop GBIF portal to interpreted wrong coordinates, maybe if the coordinate has a flag, the best option is do not interpreted them.
Thanks in advance for your time and have a good day,