Issue: L3m files not working with Time series GUI tool

Use this Forum to find information on, or ask a question about, NASA Earth Science data.
Post Reply
jrusin
Posts: 2
Joined: Mon Apr 29, 2019 9:59 am America/New_York
Answers: 0

Issue: L3m files not working with Time series GUI tool

by jrusin » Wed May 29, 2019 5:18 pm America/New_York

I have been attempting to use the "New Time Series" GUI tool in SeaDAS 7.5.3.

However, when adding my mapped 3d composites L3m MODIS files, that I created using command line tools, the product(s) are scanned but I have no option of selecting any products for the Time Series creation?

I have assumed this could be due to my seadas.vmoptions (attached) , so I have increased this to "-Xmx8192m" with no apparent issues or warnings, but this does not resolve the issue. I have tested this with a L2 file and this worked correctly. Is the issue likely my file, java, or is the tool not meant for L3m files?

Apologies if I am missing something obvious (very likely) since I am new to LINUX and Seadas!

Seadas 7.5.3
Ubuntu 18.04.2 on VirtualBox 6.0 (This also didn't work on Windows 10)
Java 1.8.0_211

Thanks,

Jozef
attachment 1

attachment 2

attachment 3

Tags:

OB SeaDAS - knowles
Subject Matter Expert
Subject Matter Expert
Posts: 277
Joined: Mon Apr 07, 2008 4:40 pm America/New_York
Answers: 0

Issue: L3m files not working with Time series GUI tool

by OB SeaDAS - knowles » Thu May 30, 2019 9:09 am America/New_York

You posted dim files which require an associated data folder so they are not readable to forum users.

How exactly are you creating the level3 composite file?  Does the resultant level 3 file contain time information?   Within SeaDAS load the file and within the FileManager select the file, open the Metadata folder and select Global_Attributes.  What is in the temporal_range, and time_coverage_start field?  Or you can check whether SeaDAS recognizes the time info by looking at "Pixel Info" with the clock turned on.

Danny

gnwiii
Posts: 713
Joined: Fri Jan 29, 2021 5:51 pm America/New_York
Answers: 2
Has thanked: 1 time

Issue: L3m files not working with Time series GUI tool

by gnwiii » Thu May 30, 2019 10:55 am America/New_York

The .dim files are ASCII metadata, so you can use an editor to search entries with "time_coverage":

                <MDATTR name="time_coverage_start" type="ascii">2016-06-17T04:20:01.000Z</MDATTR>
                <MDATTR name="time_coverage_end" type="ascii">2016-06-20T01:39:59.000Z</MDATTR>

for A2016170.3d.dim and

               <MDATTR name="time_coverage_start" type="ascii">2016-06-18T11:50:00.533Z</MDATTR>
                <MDATTR name="time_coverage_end" type="ascii">2016-06-18T11:55:00.387Z</MDATTR>

for A2016170115000.L2_LAC_OC.dim.

jrusin
Posts: 2
Joined: Mon Apr 29, 2019 9:59 am America/New_York
Answers: 0

Issue: L3m files not working with Time series GUI tool

by jrusin » Thu May 30, 2019 12:50 pm America/New_York

Ah apologies, I didn't think of that..

My L3m 3d composites are created using the command line tools:

- Firstly all my A2016*.L2_LAC_OC.nc daily images are binned using l2bin (qual_max=3, resolution=4 and prodtype=regional)
- Then these L3b files are subset into 3 days into a .txt files and then used as input for l3bin (latnorth=+89, latsout=+52, loneast=+67 and lonwest=+10)
- Finally l3mapgen (resolution=4km, projection=lambert, latnorth=+89, latsouth=+52, loneast=+67 and lonwest=+10)

Loading the file in Seadas and looking at the metadata = "temporal_range" has a value of "3-day" and "time_coverage_start" has a value of "2016-06-17T04:20:01.000Z"

Cheers,
Jozef
attachment 1

OB SeaDAS - knowles
Subject Matter Expert
Subject Matter Expert
Posts: 277
Joined: Mon Apr 07, 2008 4:40 pm America/New_York
Answers: 0

Issue: L3m files not working with Time series GUI tool

by OB SeaDAS - knowles » Thu May 30, 2019 1:15 pm America/New_York

The Time Series Tool is a very limited tool which geographically collocates multiple files using a Geographic Lat/Lon (platecarree) projection.  Unmapped files such as level2 files work as inputs.  But for level3 input files the mapping needs to be Geographic Lat/Lon.

this should work:
l3mapgen (resolution=4km, latnorth=+89, latsouth=+52, loneast=+67 and lonwest=+10)

Danny

Post Reply