Skip to content

New implementation of affine transformations of SFE objectsΒ #54

@lambdamoses

Description

@lambdamoses

So it's more like BioFormatsImage, storing the transformation info in metadata, only evaluating it last ditch say when plotting. I'm thinking about this because the user may add more geometries say from QuPath annotations to the SFE object. If the SFE object is already transformed, then the new geometries have to be transformed separately, which would be difficult if the transformation info for the SFE object isn't save somewhere. So at least the transformation info should be saved. The disadvantage of being like BioFormatsImage is that the transformation has to be applied every time spatial data from the SFE object is plotted and I know that users can make a lot of plots. That can be slow when there're hundreds of thousands of polygons but I wouldn't plot that many polygons since we can't see them anyway so I'd rather use scattermore to plot the centroids. Furthermore, while spatial methods that use the spatial neighborhood graph are not affected by the transformation, distance view methods like the variogram may be affected, say by rotation (for anisotropic variograms), scaling, shearing, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions