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
May do this after implementing multi-processing in chunks.
Adding a method that accepts a Rasters.Raster as an input step might make folding Omniscape into larger geospatial workflows more seamless. To do this, I should probably create a base method that just accepts an AbstractArray with no metadata about projection, transform, etc. Then making new methods for additional data types will be pretty seamless and will involve only adding a few extra lines of code around a call to the base method to process inputs and format/construct outputs of the same type.
The text was updated successfully, but these errors were encountered:
May do this after implementing multi-processing in chunks.
Adding a method that accepts a Rasters.Raster as an input step might make folding Omniscape into larger geospatial workflows more seamless. To do this, I should probably create a base method that just accepts an AbstractArray with no metadata about projection, transform, etc. Then making new methods for additional data types will be pretty seamless and will involve only adding a few extra lines of code around a call to the base method to process inputs and format/construct outputs of the same type.
The text was updated successfully, but these errors were encountered: