You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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
The text was updated successfully, but these errors were encountered: