Hello, I am encountering an error in the Level 1&2 Browser. When I try to narrow the time selection by clicking above the map and entering start and end date, as soon as I click "continue" or "finish" a screen appears. The error screen reads "404 Not Found nginx." Once, I somehow magically got past the time selection step, but after entering coordinates and sensors, when I clicked "find swaths" the exact same error message appeared. Any advice on how to proceed would be much appreciated!
Thanks,
Jessie
jturner@uconn.edu
Error in Level 1&2 Browser
-
OB.DAAC - amscott
- User Services
- Posts: 324
- Joined: Mon Jun 22, 2020 5:24 pm America/New_York
- Has thanked: 7 times
- Been thanked: 3 times
Re: Error in Level 1&2 Browser
Hi,
Thanks for sharing your issue, but we will need specifics so we can try to duplicate your error. It sounds like you entered dates from clicking the link above the map vs using the calendar below the map. Is that true? What mission(s) and dates did you combine/try?
Thanks for sharing your issue, but we will need specifics so we can try to duplicate your error. It sounds like you entered dates from clicking the link above the map vs using the calendar below the map. Is that true? What mission(s) and dates did you combine/try?
-
OB.DAAC - SeanBailey
- User Services
- Posts: 1428
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 1 time
Re: Error in Level 1&2 Browser
Jessie,
It is likely an intermittent issue with the webserver communicating with the script. We'll look to see if there is something we can identify as the root cause, but as it is not a persistent problem, you should just try again.
If you don't need to visualize the browse files for your query, you could also try the https://search.earthdata.nasa.gov tool.
Or even dive deep into command-line searches with the CMR API (https://cmr.earthdata.nasa.gov/search)
Admittedly, that one - while nifty - does have a bit more of a learning curve.
Sean
It is likely an intermittent issue with the webserver communicating with the script. We'll look to see if there is something we can identify as the root cause, but as it is not a persistent problem, you should just try again.
If you don't need to visualize the browse files for your query, you could also try the https://search.earthdata.nasa.gov tool.
Or even dive deep into command-line searches with the CMR API (https://cmr.earthdata.nasa.gov/search)
Admittedly, that one - while nifty - does have a bit more of a learning curve.Sean