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

Add methods that accept Raster as an input type #114

Open
vlandau opened this issue Mar 31, 2022 · 0 comments
Open

Add methods that accept Raster as an input type #114

vlandau opened this issue Mar 31, 2022 · 0 comments
Assignees
Milestone

Comments

@vlandau
Copy link
Member

vlandau commented Mar 31, 2022

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.

@vlandau vlandau added this to the Version 1.0 milestone Mar 31, 2022
@vlandau vlandau self-assigned this Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant