-
Notifications
You must be signed in to change notification settings - Fork 4
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
"to_scl_dilation_mask" does not work as intended with filter_spatial #715
Comments
|
makes things easier to track related to Open-EO/openeo-geopyspark-driver#715
makes things easier to track related to Open-EO/openeo-geopyspark-driver#715
@soxofaan One location, non-merged (cdse-staging j-240311d26137423897c1c73ab3301587) One location, merged (cdse-staging j-240311ad92974f4b828733e8a3717a13) |
FYI, the logs do show that a pixel buffer is applied:
The fact that there's still an edge effect means it's either not applied properly in this case, or not large enough. |
FYI, as discussed in our meeting earlier this week: |
Reassigned in Emile's absence, will look for unit test. |
@GriffinBabe I've been trying to reproduce this. I'm focusing on the case where there are multiple patches, and using sample_by_feature. Can you also try again, to help figure out what part leads to these artifacts? |
@jdries There is still the issue with the border though. You said previously that I'm applying a pixel buffer of a certain size:
Is this related to the size of the polygons? I suppose this is, because that's the only moment in the pipeline where I am choosing a buffer, but the polygon size is 64x64 pixels, so it should be 32.0, not 38.5 What I am getting so far: |
@GriffinBabe can you share the code again that produces this? Because I don't get the border. The buffer is calculated based on the largest kernel size, so that the convolution is applied correctly. This is what normally should prevent border effects. The value of 38.5 is correct for a kernel size of 77. |
This is the code:
|
Thanks, now I spotted it: you do the filter_spatial before to_mask_scl_dilation. Problem is that this process actually needs neighbouring pixels, but filter_spatial will remove them, so output is no longer correct. |
When executing the "to_scl_dilation_mask" process and using the
filter_spatial(geometry)
, undesired results arrive. The array contains NaN, 1.0 and very few 0.0 values.Here is how the extracted scl dilated mask look like, other dates from the datacube yield the same result
The process graph is the following:
I managed to reproduce the issue with this minimal example:
The text was updated successfully, but these errors were encountered: