Forum

It seems there is no MYD35_L2 data for nearly the whole April in 2023 (Day 091 - Day 120). Are these MYD35_L2 data being processed or there was a data outage for this product in April? Thanks in advance for your attention.

Truely appreciate all your efforts.

I just tested it. It's awesome that now I can use the the L1&2 browser. Moreover I didn't clean my cache before doing this test.

Hi, I appreciate this update. I did several tests on different browsers and different OS. Here are I list what I got: (cache has been cleaned before the test) OS browser result Windows edge 404 chrome 404 firefox 404 Linux firefox 404 (virtual machine) mac firefox can go through the "order data...

Thanks for this advice. I just tried on another browser whos cache and all history had been cleared. However, when I input my earthdata account information, the 404 not found came out again. I copied the webpage address here. I was testing to find swaths in the area of N30S29W100E101. https://oceanc...

Thank you for pointing me to the right direction. I did find my earthdata account had not been authorized with "OB.DAAC L1/2 Browser", and then I added this authorization following the instruction in the post. But I'm still not able to get through the 'order data' process in the L1/2 Brows...

Oh, sorry for this confusion. I should have mentioned this post is a follow-up for my first post in this thread. Actually, since OB finished the data maintenance, I have been experiencing issues in the L1&2 browser. The first webpage is to let us select ROI, time range, instrument etc. Then we c...

Hello, after waiting for one week, I tested the order_data function again, and the response is still the "404 Not Found".

I was testing this on Google chrome internet browser. All history, cache, etc had been cleaned before this test.

Has this maintenance finished?

I have been trying to use the "Level 1&2 browser" since this Thursday. But until now, the website always responds me with a '404 not found' webpage after I click the 'order data'.

Hi,

I found one Terra L1A granule stored in OB.DAAC might show an incorrect timestamp. The OB's name of this granule is TERRA_MODIS.20010816T173146.GEO.hdf. Maybe the timestamp ought to be 20010816.1730 (YYYYMMDD.HHMM) ?

Cheers
Hanzhi

The server of laads seems to be not accessible now roughly since 9 pm EST. Is there a scheduled server maintenance?