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

Best practices for unit values? #47

Closed
tylere opened this issue Apr 26, 2024 · 2 comments
Closed

Best practices for unit values? #47

tylere opened this issue Apr 26, 2024 · 2 comments
Assignees
Milestone

Comments

@tylere
Copy link
Contributor

tylere commented Apr 26, 2024

The current raster spec does not give much guidance about the unit field, and inconsistency in the field may make datasets less interoperable.

As a concrete example, should a unit be meter or metre or meters or m or cm or km?

It would be good to describe a best practice for this field. For example:

@emmanuelmathot emmanuelmathot added this to the 2.0 milestone Apr 29, 2024
@m-mohr
Copy link
Contributor

m-mohr commented Jun 16, 2024

The datacube extension (and others, too, I think) use:

The unit of measurement for the data, preferably compliant to UDUNITS-2 units (singular).

Is this good enough? It's difficult to standardize here as people have so diverging needs.
This field will be migrated to STAC core metadata in 1.1 (raster 2.0) so is not that relevant for the raster extension, but for core.

@m-mohr m-mohr self-assigned this Jul 11, 2024
@m-mohr
Copy link
Contributor

m-mohr commented Jul 11, 2024

Implemented in radiantearth/stac-spec#1254 through commit radiantearth/stac-spec@f35f5d8

@m-mohr m-mohr closed this as completed Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants