Added function for setting the annotation target of a table that is outside a SpatialData object. This function has a slightly different name from its counterpart. This because this is specific to setting the annotation target.
I did think about a single dispatch method, but in that case the counterpart wouldn't be specific to a spatialdata object.
The function for dealing with tables outside a spatialdata object is useful when performing a SQL like join operation that results in a table changing the annotation targets from 2 to 1 target. I did not allow for directly just specifying regions as anyways we have to do a validation which would require checking the unique elements in the column.
Instance_id is not included as this is typically not changing. If it does change the user should just parse the table again and specify all the metadata.
Added function for setting the annotation target of a table that is outside a SpatialData object. This function has a slightly different name from its counterpart. This because this is specific to setting the annotation target.
I did think about a single dispatch method, but in that case the counterpart wouldn't be specific to a spatialdata object.
The function for dealing with tables outside a spatialdata object is useful when performing a SQL like join operation that results in a table changing the annotation targets from 2 to 1 target. I did not allow for directly just specifying regions as anyways we have to do a validation which would require checking the unique elements in the column.
Instance_id is not included as this is typically not changing. If it does change the user should just parse the table again and specify all the metadata.