-
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
Manage NODATA #30
Comments
Well this is a wide open issue... Most of the resampling tools can deal with no data locally. Indeed, most of the resampling tools are working locally in spatial domain...
When it comes to Sirius and spectral domain it becomes more complicated. If we are to provide only correct output, we cannot try to reproduce what we would do in spatial domain. We are not working locally so we cannot easily avoid the computation of some output pixels for which the computation would have required using no data input values. Moreover, we cannot use an input binary mask to try to figure out to what extent the input no data are spreading away and then tagged to no data all these corrupted pixels in the output data. I mean we can, but because we are using a rather global approach, a no data value will impact much further away from where it originates. And this does not depend on the filter support but on the discontinuity created by the value assigned to no data pixels and the filter use to resample. I'm afraid this method will not leave us with sparse correct outputs but with dense no data values :s The only way I can think of right now would be to divide the block to resample in recursive manner if it contains no data values. Then, up to a minimal block size the resulting blocks are divided again until they posses no no data value. This way we would only resample blocks without a single no data value. The output would be correct but will be composed of no data "tiles" (the ones we did not process). |
No description provided.
The text was updated successfully, but these errors were encountered: