id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
695	Add ability to read Sentinel-6 / JASON-CS data	Ian Culverwell	Ian Culverwell	"Axel von Engeln (EUM) writes:
{{{
Hi Kent, Ian, Sean, Stig, 


a bit later than envisioned, but here are some example Sentinel-6 L1B 
netCDF files and also one example of a tar package. 

We generated the L1Bs using COSMIC-2 input data, but otherwise 
pretending we do the S6A mission. The data is from 11th Jan 2020, file 
name; variables and attributes should be as in the final product. The 
data processing is fine, though not perfect, so we are not primarily 
looking for a data validation here, but a format one. Some format 
changes have happened in the mean time (and you'll see similar format 
changes for the reprocessing L1Bs we are just setting up). E.g. the 
navbit information is now only provided once, not internal and 
external, there is no closed loop data available for S6, etc. On 
navbits, a flag let's you know which one we used. Hopefully this is 
all rather self-explanatory. I haven't updated the Product Format 
Specification yet, but will do this once we have a final format 
version. 

I ran the data through eum2ropp and eum2bufr of ROPP v10, and that 
flagged no issues (S6A is though currently unknown). This is however 
only on the L1B level, the L1A will need some ROPP updates. Eg the 
eum2ropp -l .. command will not work as implemented now, since there 
is only open loop data available, and no closed loop flags are thus 
set. I suggest you evaluate what is missing / needs to be updated for 
ROPP, or is missing on our side, and we discuss this once you have a 
complete list. The data should though allow to assess whether the 
non-equidistant time stamps are an issue for ROPP L1A to L1B 
processing. 

I also added a tar file, this is how we provide data to the EUM 
archive, as well as to the internal ""Data Lake"", all data is 
""wrapped"" in a tar package, along with an xml manifest. I assume 
you'll get the data in this format or in the corresponding Windows 
zip format. We so far have only a tar file with the latest, real data, 
so you can get acquainted with this tar wrapper. I also did add a zip 
file, but that has a L1B product from earlier testing, so this is just 
a format example of zip files. Do you have any info on what data 
wrapping you'll get, zip or tar or none? And are you interested in 
the xml content? If yes, I could provide a document that describes 
it. But we only wrap / populate the xml for the archive, so all 
relevant info is of course in the netCDF.


The data download link is available to anybody, so you can forward 
this to others. 


Kind regards,


            Axel
}}}"	enhancement	closed	normal	11.1	ropp_io	10.0	fixed	Sentinel-6, JASON-CS	Kent Bækgaard Lauritsen Stig Syndergaard sti