-
Notifications
You must be signed in to change notification settings - Fork 3
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
Handle nodata or other ignore values in raster data sets #58
Comments
bdubayah
added a commit
that referenced
this issue
Oct 14, 2021
bdubayah
added a commit
that referenced
this issue
Oct 17, 2021
…alue extractor to scale based on min max #58
@bdubayah Have you made this change for the raster pixel loader too? Are you planning to PR/merge or are you still making changes? |
Still need to do it for raster pixels. I think we also need to decide the merge strategy for overlapping patches - whether to stick with mean or do max instead. I'm going to try with max for the vtfs experiment and see how it works out. |
bdubayah
added a commit
that referenced
this issue
Nov 2, 2021
bdubayah
added a commit
that referenced
this issue
Nov 2, 2021
…alue extractor to scale based on min max #58
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rasters often have nodata values that should be ignored in analysis (e.g., edges missing data due to registration). These pixels should be given a specific sentinel value (e.g., -9999) instead of being scored.
The text was updated successfully, but these errors were encountered: