[Bug]: "Geolocate" type georeference import ignores uncertainty about taxonworks HOT 3 CLOSED

The radius is being converted into an error polygon (e.g. a circle that is a polygon) and stored that way.

I have zero recolleciton why we did this. There are 8.5k records or so that exist in this format.

I'm going to defer on changing anything other than adding a column to indicate error polygon present until further discussion.

from taxonworks.

Why isn't it just being converted into an error radius uncertainty? That's what I'd suggest as a fix.

from taxonworks.

Why isn't it just being converted into an error radius uncertainty?

I went back and thought more about this, dug up some history. I think it was because we wanted to compute on shapes in a uniform way, and this would let us do that, i.e. we didn't have to do an "extra" radius-based step in the query.

I think we'll modify it to do both now, clearly we need to include the radius (though technically we can calculate it back from the error shape we have).

from taxonworks.