Combination View Flat View Tree View
Threads [ Previous | Next ]
command line subset L1B MERIS images
toggle
I'm trying to batch process MERIS imagery. I have full swath imagery and would like to subset the LIB imagery from command line before processing to L2. Is this possible?
Flag Flag
RE: command line subset L1B MERIS images
11/12/09 9:35 AM as a reply to Colleen B Mouw.
What kind of subsets do you want to make? Which file format?
Flag Flag
RE: command line subset L1B MERIS images
11/12/09 3:56 PM as a reply to Ralf Quast.
I'd like to make a spatial subset from MERIS L1B Envisat N1 files. I'd like to specify lat/lon limits and extract only the data within this box.
Flag Flag
RE: command line subset L1B MERIS images
11/13/09 9:05 AM as a reply to Colleen B Mouw.
If it is acceptable for you to reproject the product, you can use the mapproj tool from the command line.
Specify an easting and northing, the pixel size in X and Y direction and the width an hight of the target product, so that it covers you region.

best wishes
Marco
Flag Flag
RE: command line subset L1B MERIS images
12/1/09 12:07 AM as a reply to Marco Peters.
I've used the command line version of mapproj to subset a larger MERIS L1B image. I'm able to view the output of command line mapproj in BEAM however this output is unable to be processed to L2 with the Case 2 regional processor. It seems that there is a problem at some level with the sub-setted and projected file. If I subset and project within the BEAM GUI and then process to L2 via command line, the output is fine.

I've placed my files on the brockmann ftp server under users-support/cmouw. Would it be possible to take a look and help me find where I'm going wrong?

Here are the commands I'm calling... I've also supplied an example L1B files I'm trying to subset, project and process to L2

mapproj.command mapproj_2_points_Mendota.xml
meris-case2_batch.sh -v request_file_GeoTIFF.xml

Thanks,
Colleen
Flag Flag
RE: command line subset L1B MERIS images
12/1/09 8:56 AM as a reply to Colleen B Mouw.
Colleen,

without testing your use case, I assume that the problem is related to the product type.
The mapproj tool changes the product type to 'BEAM_MOSAIC'.
The Case-2-regional processor expects product types of 'MER_*_L1B'.

It might help if you open the '*.dim' file in an editor and change the product type
1<PRODUCT_TYPE>BEAM_MOSAIC</PRODUCT_TYPE>

to
1<PRODUCT_TYPE>MER_FRS_1P</PRODUCT_TYPE>

It is located at the beginning of the xml file.

best wishes
Marco
Flag Flag

 

Welcome to the BEAM Forum!

We encourage you to sign in our forum and participate in the BEAM community. The forum is maintained by the BEAM project team who will most likely answer your questions within 24 hours (except during common holidays) - if not done by other community members. Collaborate, share your knowledge and learn from other users!

If you don't find what you are looking for, please also consider the following external forums: