I'm performing polygon extractions (filter_spatial + sample_by_feature=True) using a GeoJSON FeatureCollection in the process graph.
I buffered the geometries within the FeatureCollection to have a shape approximatively of 64x64 pixels when extracting S2 collections (640x640m). The output file has slightly larger dimensions (which seems reasonable as the input coordinates are expressed in lat/lon), but there are some borders with a -1.0 value, which seems like it is a corrupted value as it doesn't even correspond to the NoData value of the output netcdf file
On example can be found with the job ID in the CDSE production environment: j-240223d1ff724586be9c05148383dbdc
I'm performing polygon extractions (filter_spatial + sample_by_feature=True) using a GeoJSON FeatureCollection in the process graph.
I buffered the geometries within the FeatureCollection to have a shape approximatively of 64x64 pixels when extracting S2 collections (640x640m). The output file has slightly larger dimensions (which seems reasonable as the input coordinates are expressed in lat/lon), but there are some borders with a -1.0 value, which seems like it is a corrupted value as it doesn't even correspond to the NoData value of the output netcdf file
On example can be found with the job ID in the CDSE production environment: j-240223d1ff724586be9c05148383dbdc