geoMetaVIIRS for JPSS2

[marcolaiolo]

Dear Staff,
Ireceive the notification of the VJ2 products released and downloadable from nrt-lance system. Sorry, about a possible futile question; but I'm interested to a "vital" product for my script regarding the downloading and processingof MODIS and VIIRS data that is the geoMeta file (e.g. https://nrt3.modaps.eosdis.nasa.gov/archive/geoMetaVIIRS/5201/NOAA-20/2024). Can you indicating me if this product is already available for the VJ2 and/or if there not yet a specific path for this? May be, simply, I don't find the folder where this product has been inserted. In fact, contrarely, the VJ03 and 02 (MOD and IMG) are available in the same path of VJ1 (https://nrt3.modaps.eosdis.nasa.gov/archive/allData/5200).
Thank you very much for your work and your attention on the data dissemination.
Marco Laiolo, Technician, Department of Earth Sciences - University of Turin (Italy)

[LAADS_UserServices_M]

Dear Marco Laiolo:
Currently, we are working on generating geoMeta for NOAA-21 (JPSS-2). We are hoping to have this available sometimes towards the end of February or early March. Please, check back around that time. These will be available at:
https://nrt3.modaps.eosdis.nasa.gov/archive/geoMetaVIIRS/5200/

[marcolaiolo]

Dear Staff,
I wrote to tell you if there are some news about the proposal to upload the geoMeta files of NOAA-21 in one of these path https://nrt3.modaps.eosdis.nasa.gov/archive/geoMetaVIIRS/5200 ; https://ladsweb.modaps.eosdis.nasa.gov/archive/geoMetaVIIRS/5200 .
Thank you for your attention and for your great work.
Marco Laiolo

[LAADS_UserServices_M]

Dear Marco Laiolo:
Due to other higher priority tasks, the NOAA-21 geoMeta were not completed. At this time we don't have a date of release either.
We are just curious what you will use them for. If just searching for files in an area of interest, you can use LAADS API-V2 – it is much more efficient, and it works for all our products. You can find information about API-V2 at:
https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/#api-v2

[marcolaiolo]

Deat Staff,
thank you for your question! I'm a memeber of the MIROVA team (www.mirovaweb.it) and, currently, our system is based on a list of volcano coordinates and the selection of what 02 and 03 Level1b product to download, rely on the read of geoMeta data (in the LANCE-NRT system) that are inserted the boundary Lat and Lon of each granule. If the coordinates of one (or more) volcanoes is included in these boundary, we search, download and processes, the 02 and 03 product in the specific folder. In fact, we use the following path for MODIS and VIIRS data
https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/5200/
https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/geoMetaVIIRS/5200/

Since now, this system works very well. However, thank for your interesting and, in the case, we will work for changing code in order to adopt new strategies based on API-V2.

Thank you again for your great work,
Marco Laiolo

[marcolaiolo]

Just a little thing. Currently, we already use, succesfully, for download (after verification of useful granule) the wget Command-line proposed in https://nrt3.modaps.eosdis.nasa.gov/archive
wget -e robots=off -m -np -R .html,.tmp -nH --cut-dirs=4 "https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/" --header "Authorization: Bearer INSERT_YOUR_TOKEN_HERE" -P TARGET_DIRECTORY_ON_YOUR_FILE_SYSTEM

sincerely

[LAADS_UserServices_M]

Thanks very much for the details. We will try to generate the geometa for NOAA-21 as soon as possible but cannot provide you a date.

[marcolaiolo]

Dear Staff,
in the latter discussion, you suggest me to adopt the API system to check the file(s) to download in order to bypass the geoMeta files. I'm curious about the possibility to compare and verify, previous download (because time- and storage-consumption), by comparing a list of coordinates (latitude and longitude) target with the 03 or 02 .hdf (or .nc). This is because, currently, every X minutes we download the daily geoMeta data, compare the boundary(ies) of each granules with our list (.csv or other) and then, we check the presence of 03 and 03 Level1b data for download or not the files.
If you can help about this question and, eventually, with an example suggest me a strategies to bypass the use of geoMeta file(s) .
Thank you very much for your work and assistance and don't hesitate to contact me for any other details or others.
Sincerely
Marco Laiolo

[LAADS_UserServices_M]

Hi Marco:

An example HTTP request would look something like
https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/archives?ArchiveSets=61&products=MOD021KM&temporalRanges=2012-015&regions=[BBOX]N21.5 S20.5 E12 W-15
for HTML output, or
https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/details?ArchiveSets=61&products=MOD021KM&temporalRanges=2012-015&regions=[BBOX]N21.5 S20.5 E12 W-15
for JSON output.

If you are interested in Day only, or Night Only, you can specify that by adding the “illuminations” parameter to the query. See the API description (link below) for the full syntax. HTTP query parameters can be submitted in any order.

Be careful with the “[“ and “]” characters around “BBOX” if you are running “system” commands from your script – “[“ and “]” characters might need HTTP encoding so that the shell and some tools, like curl, don’t get confused.

The full API is described at
https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/api-v2/specs/content#archives

Basically, your script would read your list of areas of interest and dates from your file, substitute your geolocation and date/time values into the HTTP request, run the request using a User Agent (curl, wget, or your favorite HTTP library/tool/script language UA), parse the outputs looking for file links (most scripting languages can decode JSON now), and download the files.