-
Notifications
You must be signed in to change notification settings - Fork 41
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
Re-sampling strategy #21
Comments
Just a note that in #27, we've went with resampling to a pixel resolution of 10m for Sentinel-2 and the DEM (Sentinel-1 RTC already has a pixel resolution of 10m, though see #19 (comment)). The resampling is using For Sentinel-2 optical imagery, nearest neighbor resampling is fine, but for the Copernicus DEM, we might want to consider bilinear resampling which compromises between pixel value preservation (nearest neighbor) and smoothing (cubic resampling), see e.g. answers like https://gis.stackexchange.com/questions/102868/best-resampling-method-for-dem-reprojection-in-qgis. |
Originally posted by @MaxLenormand in #200
@yellowcap, can you make sure for the v1 data pipeline (#178) that we use bilinear interpolation for Copernicus DEM? We'll need to override stackstac's default Nearest Neighbour interpolation. Thanks! |
Thanks for the hint! Definitively something to integrate - and wish we had caught that for v0.2 😄 V1 might not get the DEM anymore at first, but this is good to keep the resampling method at top of mind in the future. |
Closing as out of date, feel free to reopen if appropriate. |
Our 3 data products scoped for v0 training (#19, #18, #20) have a median spatial resolution of 20 meters. We'll assume a single resolution model for v0, using 20m resolution to standardize inputs. We'll need to select an appropriate interpolation method for specifically the DEM and S1 inputs.
The text was updated successfully, but these errors were encountered: