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

Time-series assets are missing date/time metadata #4

Open
benscarlson opened this issue May 3, 2016 · 2 comments
Open

Time-series assets are missing date/time metadata #4

benscarlson opened this issue May 3, 2016 · 2 comments
Labels

Comments

@benscarlson
Copy link

In order to be accessible to the annotation library, time-series data should have system:start_time and system:end_time information.

For climatology data, the year should be set to 1800

@adammwilson
Copy link

Why 1800? If you are just picking a year, I would recommend something
within the period of the data at least. Maybe a nice round 2000? Or are
you doing 1800 to allow filtering only climatologies by choosing their date?

__o Adam M. Wilson, Ph.D. [email protected]
[email protected] `<, Department of Geography & Program in Evolution,
Ecology, & Behavior
()/ () University at Buffalo
######## http://www.AdamWilson.us http://www.adamwilson.us/
@AdamWilsonLab https://twitter.com/AdamWilsonLab

On Tue, May 3, 2016 at 4:47 PM, Ben Carlson [email protected]
wrote:

In order to be accessible to the annotation library, time-series data
should have system:start_time and system:end_time information.

For climatology data, the year should be set to 1800


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#4

@benscarlson
Copy link
Author

Good question - the 1800 basically means 'no year'. It's really just a hack to make the join work. I'm envisioning that if you have a bunch of data and you want to, say, join it with the monthly cloud climatology, you don't really care about the year. Really what you want is to annotate all the points from Jan with the January image, all the points from Feb with the Feb image, etc. There are a couple of ways to make this happen, but this approach allows us to always use the same two fields (even with daily data) - system:start_time and system:end_time - to do the joining. A different approach could be - on climatology layers we could have a new metadata field called "month" and then I just match on month. That would not require funky defaults, but means we loose some of the generality.

Here is how it works now:
https://github.com/MapofLife/annotate/blob/master/annotation.py#L219

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

No branches or pull requests

2 participants