Skip to content
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

3.1 Axes metadata #30

Open
dstansby opened this issue Nov 22, 2024 · 1 comment
Open

3.1 Axes metadata #30

dstansby opened this issue Nov 22, 2024 · 1 comment

Comments

@dstansby
Copy link
Contributor

"axes" describes the dimensions of a physical coordinate space. It is a list of dictionaries, where each dictionary describes a dimension (axis) and:

  • MUST contain the field "name" that gives the name for this dimension. The values MUST be unique across all "name" fields.

  • SHOULD contain the field "type". It SHOULD be one of "space", "time" or "channel", but MAY take other string values for custom axis types that are not part of this specification yet.

  • SHOULD contain the field "unit" to specify the physical unit of this dimension. The value SHOULD be one of the following strings, which are valid units according to UDUNITS-2.

      Units for "space" axes: angstrom, attometer, centimeter, decimeter, exameter, femtometer, foot, gigameter, hectometer, inch, kilometer, megameter, meter, micrometer, mile, millimeter, nanometer, parsec, petameter, picometer, terameter, yard, yoctometer, yottameter, zeptometer, zettameter
    
      Units for "time" axes: attosecond, centisecond, day, decisecond, exasecond, femtosecond, gigasecond, hectosecond, hour, kilosecond, megasecond, microsecond, millisecond, minute, nanosecond, petasecond, picosecond, second, terasecond, yoctosecond, yottasecond, zeptosecond, zettasecond
    

If part of § 3.4 "multiscales" metadata, the length of "axes" MUST be equal to the number of dimensions of the arrays that contain the image data.

https://ngff.openmicroscopy.org/0.4/index.html#axes-md

@dstansby
Copy link
Contributor Author

I think a combination of #43 and #42 fixes this 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant