@naglepuff If you are interested in tackling this issue, it would be an introduction to geojs and more of the Girder 3 UI.
I would only add the options to macro and label images, not other associated images. Once the main viewer is loaded, we know that geojs is available. Then, when the label or macro image is loaded, we could replace the image element with a geojs.map which has been initialized with a url to the label or macro image and use https://opengeoscience.github.io/geojs/apidocs/geo.util.html#.pixelCoordinateParams where the tile size is the same as the image size. This also would add an annotation layer. Once the geojs viewer is initialized, then drawing and editing the annotation would follow what we do on the WSI.
If a user is redacting a polygon on the label or macro image, this would be instead of redacting it fully or redacting the top/left square of the macro. It would still get a PHI reason if collecting that is enabled.
@naglepuff If you are interested in tackling this issue, it would be an introduction to geojs and more of the Girder 3 UI.
I would only add the options to macro and label images, not other associated images. Once the main viewer is loaded, we know that geojs is available. Then, when the label or macro image is loaded, we could replace the image element with a geojs.map which has been initialized with a url to the label or macro image and use https://opengeoscience.github.io/geojs/apidocs/geo.util.html#.pixelCoordinateParams where the tile size is the same as the image size. This also would add an annotation layer. Once the geojs viewer is initialized, then drawing and editing the annotation would follow what we do on the WSI.
If a user is redacting a polygon on the label or macro image, this would be instead of redacting it fully or redacting the top/left square of the macro. It would still get a PHI reason if collecting that is enabled.