petebankhead
commented
7 years ago This is certainly possible. The easiest way to start would be to write a Groovy script for the import, although you could also create a Java extension if needed. The latter would require more code, but could incorporate extra user-friendliness (e.g. a menu item, drag-and-drop support).
For each boundary, the process would be something like this:
- Create a region of interest from the exported coordinates
- Create an annotation for the ROI
- Add the annotation to the object hierarchy
Most code for specific ROIs is here - so you could create rectangles, ellipses or lines if required, or just stick with PolygonROI for polygons. The most useful constructor is:
public PolygonROI(float[] x, float[] y, int c, int z, int t)For c, z and t (channel, z-slide & time point) you can probably use -1, 0, 0 by default.
After creating your polygon ROI, then create a PathAnnotationObject with the ROI:
public PathAnnotationObject(ROI pathROI)and finally you can add this annotation to the hierarchy simply with
addObject(annotation)I have some memory of Aperio ImageScope having a concept of layers, and also 'negative' regions; I don't know if this would also be in your XML. If so, these may not have exact matches inside QuPath, but there are various tricks you could use if you find they are needed (e.g. combining or subtracting ROIs, adding them to the hierarchy in different ways, setting names, classifications or colors etc.).
If you haven't already, I suggest checking out the Wiki for Writing custom scripts and Advanced scripting with IntelliJ, which can help with writing the code and accessing the QuPath source.
Finally, it may also be useful to know that, if you want to use any other Java libraries to help, then you can drag the required Jar file onto QuPath to copy it into QuPath's extensions directory. Even if the Jar isn't a 'real' QuPath extension, this means that it will still be available on QuPath's classpath when running the script. This could be useful if your XML parsing code is already contained in a Jar, or if you want to add another library (e.g. groovy-xml.jar) to help with scripting the parsing.
Hopefully that helps to get started.
DanaCase
Monk5088
We have a lot of annotations previously done using Aperio ScanScope which generate the XML files. We already have code that can parse those files and get out the boundaries for the various objects/layers....
We'd like to be able to compare analysis results done using QuPath with those we previously did in ScanScope, without having to redraw the annotations ...
If we had the boundaries of the shapes (lets just assume polygons for general use case), would it be possible to somehow import them and create an annotation layer we could use for analysis?