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

STAC harmonization changes #236

Merged
merged 4 commits into from
May 2, 2023
Merged

Conversation

pvretano
Copy link
Contributor

@pvretano pvretano commented Apr 26, 2023

Numerous changes listed in issue #178 to bring OARec and STAC into closer alignment.

Closes #178
Closes #231
Closes #232

@pvretano pvretano self-assigned this Apr 26, 2023
@kalxas kalxas requested a review from tomkralidis April 27, 2023 12:38
@pvretano
Copy link
Contributor Author

27-APR-2023: Discussion about why the time field is a top level field versus the STAC datatime property. The idea with the time member is, like geometry, to provide a fixed key for temporal filter as opposed to looking at stuff in the properties object which can be domain or community-of-interest specific. At the moment, there is no conflict between Records and STAC in this respect but there might be an unfortunately duplication on information if the temporal info exists both in the properties object using STAC properties and the time member in Records. Not ideal but no easy resolution.

@cnreediii
Copy link

cnreediii commented Apr 27, 2023

@tomkralidis what does resolution mean in this context? Thnx

@cnreediii the resolution of the temporality of the data (hourly measurements [P1D], etc.)

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

Successfully merging this pull request may close these issues.

Fix time example Add more guidance about the license field. STAC / Records Harmonization
5 participants