C2RCC-MSI for S2 Not Producing Output Since Jan 14

We’ve been using the C2RCC-MSI processor for Sentinel-2 imagery for a few years now. It seems that since the upgrade to processing baseline 04.00 this produces empty results, and nothing in our processing has changed. I suspect it may be related to needing Sen2Cor2.10 - however the C2RCC-MSI processor invokes Sen2Cor itself for L1C imagery. We’ve updated all plugins - and have obtained the Sen2Core2.10 standalone installers - however they do not “slipstream” into SNAP, and I see no way to instruct the C2RCC-MSI processor to use it (if indeed that resolves the issue).

Guidance on this would be appreciated.

sen2cor is not needed for C2RCC. It does not invoke it.
But if S2TBX, S3TBX and SNAP are all correctly updated it should work.
We use it in operational production, and we get results.

Can you invoke the following command from the bin folder of the SNAP installation?
On Windows: snap64 --list --modules
On Linux: snap --list --modules
This will print the list of installed modules. Can you share the result?

I’ve attached a file contining the output for the modules. I did an update of all plugins on the weekend, so they should be current.

Here’s an example of the output we are (not) getting. C2RCC-MSI is run against the product on the left – which has been resampled to 20m, subsetted to the rough size, and then masked to a specific polygon. This particular image/date is cloud free.

modules.txt (24.3 KB)

The installed modules look up-to-date. So, this is not the issue.
Have you checked the other bands? Are they empty too?
Can you tell the exact name of the source product? Then I can try to reproduce it.

The product link is https://scihub.copernicus.eu/dhus/odata/v1/Products(‘a35046d1-a675-4439-b70f-f6b5a8101345’)/$value for the product S2B_MSIL1C_20220213T075959_N0400_R035_T35JNN_20220213T095938

We first resample to 20m using B5 as the reference band, then subset it with the following geoRegion:

POLYGON((27.38902829853393 -25.36675044861542,27.52514118903696 -25.36675044861542,27.52514118903696 -25.301394657363502,27.38902829853393 -25.301394657363502,27.38902829853393 -25.36675044861542))

, and then use the Land-Sea-Mask with the vector defined in the attached shapefiles.
Archive.zip (1.1 KB)

This is occurring with all AOIs that we are following for Sentinel-2 since mid-January

As a matter of fact, the ONLY band that produces any output (still empty) with the C2RCC-MSI process is the conc_chl - which is the one we’re interested in, however I’ve just found an image from 2022-01-24 for the same location that does produce output, and has all of the other bands in addition to conc_chl

Hi Marco … is there any update on this?

Oh, sorry for not answering. I just forgot to reply.
This is bug.
[SNAP-1507] Subset cannot be created if tie-point grid is sparse - JIRA (atlassian.net)
I haven’t found a suitable workaround.
Only option would be to write the product in NetCDF4-CF format. This would turn the tie-points into bands.
It is already planned to provide a fix or at least a workaround, but I can’t tell you an ETA right now.

What still puzzles me is that you have empty results when I try to subset the product with your polygon I get an error.

@donCarlosOne did you find a cause for your issue? it seems I am facing the same problem

No. We’ve suspended processing S2 for dates beyond January 19, 2022 when the problem began.

1 Like

@donCarlosOne did you get a clear idea of what is the cause?

The best answer we’ve been able to come up with is that there is something different with the data from Sentinel-2 after that date. The issue is consistent across all dates and locations that we process post January 19. We’ve actually abandoned C2RCC in general as it fails to provide us consistent results for our purposes, and have built our own models now - which also do not provide proper results after January 19 - which is why we believe the problem is with the Sentinel-2 data.

Hello @donCarlosOne Charles

Is it linked to the introduction of PB 04.00?



OPT-MPC S2 Technical Manager

1 Like

@Jan thanks for pointing it out. Can you please develop on how this afftects the C2RCC processor and why resutls are empty? Is the manual change suggested in your post a solution for this?

1 Like

Hello @sentinel dg

I can’t comment on the impact on the C2RCC processor, I’m afraid. The intricacies of the processor are unknown to me. All I can say is that the significant changes for L1C in PB04.00 involved changes to the handling of Quality Masks (they are JP2 now, not GML) and the introduction of the Radiometric Offset.

Sorry I can’t be more help.



1 Like

@Jan Thank you for the info. I hope it helps c2rcc developers to fix the bug sooner than later.

For reference, I confirm I have tried the same S2 Tile for two 1C prodcut: August 2021 (baseline N0301) and 2022 (baseline N0400). The first produces and output, the second is empty.

@marpet @abruescas is this a known issue? any work-around known?

Hello dg @sentinel

The details of the changes involved in the PB04.00 evolution are set out here Open Access Hub



1 Like

Thanks for this information @Jan … we’ve focussed on S3 imagery since, but the lower resolution is not welcome. We’ve also developed our own models - which exhibit the same characteristics for S2 imagery since Jan 19, so I’ll have our data scientist look into it.

If there’s any other information that you can provide, which could assist in solving this, that would be useful to us and the community in general. Likewise, I’ll share the results of our investigation if they prove promising.