Forum

Hi, thanks for letting me know of the missing L0 data. I'll try and keep an eye on the STD processing as you suggest. Just wanted to clarify however, that the time is UTC and specifically the time between 14:20-14:30 is local afternoon (not night) for western Europe. So the gap in data is not fully ...

Hello,
I was wondering whether there was an outage on AQUA because there is a large chunk of time missing from AQUA on Lance from Sept 18 - from 1305 to 1525 (see figure). Part of this overpass covers the current wildfires in Portugal so I'm wondering where I can get them.
Thanks,
Conrad

Thanks FIRMS Support Team, if you happen to get more details that would be helpful. Any reference documents (either ATBDs or articles) would also be helpful. I will try and find an SSEC forum and bring up the same issue there to see if they have any more comments on the topic. Any updates I'll share...

Good morning Diane, for the VIIRS processing we use the CSPP Active Fires version: 2.1, ProcessVersionNumber = "2.5.4". I would have thought that the results should be pretty 'stable'. Most of the time, we have a few differences here and there (which I could account to differences in versi...

Hi, I'd like to better understand differences that we are seeing between the VIIRS thermal anomalies (TA) produced through our direct readout over Europe compared to the FIRMS NRT products which we use for daily validation of the TAs. Our team produces RT (to use the current definition from the FIRM...

Hi, thanks for the information. I have joined the list now. A follow up question though regarding the current files. I'm getting 404 errors when trying to access them. One example is the following: https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/61/MOD00F/Recent/MOD00F.A2023056.0...

Hi, thanks for the update. Is there a place where we can get ongoing updates with this situation? Or should we follow this post? Also, has the naming convention been updated on purpose? E.g. https://nrt3.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/61/MOD00F/Recent/MOD00F.A2023056.0700.202...

Hello, I'm wondering whether this issue is being dealt with. Today I'm experiencing 404 errors because the download link and the actual file are different. An excerpt from the JSON output below: { "archiveSets": 61, "cksum": "1830997788", "dataDay": "2022...