-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add temporal
attribute to RasterBlock + base Clip logic on it
#117
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems ok, but is NONTEMPORAL_TIMEDELTA still required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice to finally get the temporal attribute on the blocks. I had one comment about a docstring. Otherwise approved.
dask_geomodeling/raster/elemwise.py
Outdated
else: | ||
return timedeltas[0] | ||
|
||
@property | ||
def temporal(self): | ||
"""If any of the sources is temporal, the result is temporal.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is enforced by the init(), but maybe not the most adequate description for this property.
I added the
RasterBlock.temporal
attribute with a default implementation that guesses whether the raster is temporal based on timedelta and period.We can gradually improve this by providing
temporal
from the various sources.I went through the blocks and fixed some low-hanging fruit for propagating
temporal
through the operations.Also: many deprecation warnings that I solved with pinning versions. See issues #118 , #119 , #120