-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shapes #73
Comments
regarding the discussion about shapes in #33, there is the question of the desired standard to do that, basically either WKT or GeoJSON. It seems to me that GeoJSON would be better suited? But neither provide geometry primitives like rectangles circles or ellipses, and both are 2D. Also it is not clear to me if ROIs specification should be a subclass of shape or the other way around (as you can also specify ROIs with e.g. a list of pixels? See also: #41 with respect to polygons |
cc'ing @BioinfoTongLI from vizarr issue above. |
I prefer GeoJSON over WKT, simply because it's JSON! But I expect we'd have to abuse the GeoJSON standard a bit to do all the things we want. "GeoJSON supports the following geometry types: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection". So we're missing Ellipse and possibly Rectangle. https://datatracker.ietf.org/doc/html/rfc7946#section-3.1.1 But otherwise, I guess we can use a lot of what's there without having to re-invent a new format. 👍 |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/interchange-formats-for-rois-a-k-a-graphical-annotations/65798/2 |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/roi-annotations-and-tracking-information-in-ome-zarr/65975/7 |
Add support for Polygons, Polylines, Lines, Ellipses etc.
See https://napari.org/tutorials/fundamentals/shapes.html for ways of representing nD shapes.
Prompted by request for viewing Shapes in vizarr: hms-dbmi/vizarr#127
Related to #33 (Mesh specification).
The text was updated successfully, but these errors were encountered: