Simplify coordinate/displacement metadata#134
Closed
clbarnes wants to merge 1 commit into
Closed
Conversation
Automated Review URLs |
Contributor
|
Superseded by #145? |
Contributor
Author
|
Yes. For posterity: we decided to turn vector field transforms into multiscale arrays and make use of existing multiscale metadata to handle index transformations. |
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
2 participants
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.
Currently, locating the vector fields associated with coordinates and displacements transforms in the input coordinate system required an extra coordinate system and coordinate transformation metadata on the vector field Zarr array. This proposal moves it to within the existing transformation metadata, erasing the need for a number of metadata features which were only used for this purpose.
Resolves ome/ngff#520 . Notes about the general issue should go there; preferably keep discussion here to the proposed text/ supporting information changes.
Also changes a few examples to use the conventional
coordinateTransformations/location for coordinate transformation Zarr nodes.