Repository navigation
Conversation
…sion it claims No storage format so far is compliant with a released OME-Zarr version: the coordinate transformations follow the RFC-5 draft. The column now reads "0.x + RFC-5 draft", with a note on the 0.6 aim; the recorded version strings stay in the element versions table. Also rename "`spatialdata` writes" to "Written by `spatialdata`" and shorten the 0.3 cell.
Collaborator
Author
|
Alternative: #76 is a minimal version that only changes the NGFF column (header "NGFF version string", cells = the recorded strings, no note). Pick one. |
Collaborator
Author
|
Superseded by #76 (NGFF column) and a separate PR for the header / 0.3 cell. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to Luca's request on Zulip (#Spatial Innovation Team > spatialdata-spec).
The compatibility matrix's NGFF column read "0.5 (
"0.5-dev-spatialdata")" etc., which reads as a compliance claim and clipped on the site. No storage format so far is compliant with a released OME-Zarr version: the coordinate transformations follow the RFC-5 draft (already stated in the "Divergence from NGFF" boxes, including for the plain"0.4"of raster 0.1).0.5 + RFC-5 draft/0.4 + RFC-5 draft, plus a note under the table: the aim is OME-Zarr 0.6 (links the upcoming-version section); the recorded version strings stay in the element versions table (newelement-versionslabel).`spatialdata` writes→Written by `spatialdata`; the 0.3 cell is shortened to "0.4.0 – 0.5.x; ≥ 0.6.0 on request" (the container detail is in the paragraph below the table).