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.

Sign up for GitHub

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

Jump to bottom

Best practice for datetimes #801

Closed
m-mohr opened this issue May 6, 2020 · 0 comments
Closed

Best practice for datetimes #801

m-mohr opened this issue May 6, 2020 · 0 comments
Assignees
@cholmes
Milestone
1.0.0-beta.1

Comments

@m-mohr
Copy link
Collaborator

m-mohr commented May 6, 2020

I think I would like to add a 'best practices' section that discusses datetimes, explaining why it's good to have a nominal date time if possible, and explaining the use cases (zarr, etc) where it doesn't make sense. Plus more encouraging people to define extensions for their data (not just for ones with time ranges), that are more precise with what the datetime means (satellite imagery is acquisition time, mosaics are a representative time for search, and should use start/end, etc) And the implications for servers / clients

Originally posted by @cholmes in #798 (review)
@m-mohr m-mohr added this to the 1.0.0-beta1 milestone May 6, 2020
cholmes added a commit that referenced this issue May 18, 2020
@cholmes
added best practice for datetime - #801
bf8ee8c
@cholmes cholmes mentioned this issue May 18, 2020
Merged
4 tasks
matthewhanson added a commit that referenced this issue May 27, 2020
@matthewhanson
Merge pull request #804 from radiantearth/datetime-best-practice
fcdfa76 
added best practice for datetime - #801
@cholmes cholmes closed this as completed May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cholmes cholmes

Labels
None yet
Projects
None yet
Milestone
1.0.0-beta.1
Development

No branches or pull requests
2 participants
@cholmes @m-mohr