Search found 362 matches
- Wed Jul 10, 2024 6:42 am America/New_York
- Forum: Home
- Question: MOD06_L2 data ranges and missing data
- Replies: 8
Re: MOD06_L2 data ranges and missing data
Here is the description for the 3-dimension “Retrieval_Failure_Metric” in a MOD06_L2 granule: short Retrieval_Failure_Metric(Cell_Along_Swath_1km=2030, Cell_Across_Swath_1km=1354, RFM_nband=3); :long_name = "Retrievals and other information for points that failed to retrieve via standard soluti...
- Mon Jul 08, 2024 2:06 pm America/New_York
- Forum: Home
- Question: v002 delays and incomplete updates VJ113A1 VNP13A1
- Replies: 2
Re: v002 delays and incomplete updates VJ113A1 VNP13A1
We checked and for the VNP13A1 and VJ113A1 for June 17, 2024 the tiles you asked about are all available. Full suite of products were generated on July 3, 2024. The VI (VNP13A1/VJ113A1) is a 16-day product, so the outputs are not created until 16-days (give or take a little) from the start time of t...
- Mon Jul 08, 2024 12:56 pm America/New_York
- Forum: Home
- Question: MOD06_L2 data ranges and missing data
- Replies: 8
Re: MOD06_L2 data ranges and missing data
Our product SME investigated MOD06_L2 data and found how to distinguish Cloud_Optical_Thickness (COT) between no data case and failed retrieval. For example, for 2.1 micron (band 7), the valid range for scaled Cloud_Optical_Thickness (1354, 2030) is [0,150]. The valid range for scaled Retrieval_Fail...
- Fri Jul 05, 2024 1:05 pm America/New_York
- Forum: Home
- Question: download VJ2 products
- Replies: 1
Re: download VJ2 products
Dear Marco Laiolo: The Near Real Time (NRT) products (e.g., VJ202MOD_NRT and VJ203MOD_NRT) and standard products (e.g., VJ202MOD and VJ203MOD) are archived and distributed from different servers. All NRT products are available from https://nrt3.modaps.eosdis.nasa.gov/ (main) or https://nrt4.modaps.e...
- Fri Jul 05, 2024 8:32 am America/New_York
- Forum: Home
- Question: MOD06_L2 data ranges and missing data
- Replies: 8
Re: MOD06_L2 data ranges and missing data
Yes, the scale and the add_offset are fixed for each Scientific Data Set (SDS). The following conversion equation should be used to convert stored integers back to useful floating point values: float_value = scale_factor * (integer_value – add_offset) Information about missing data is provided in th...
- Tue Jul 02, 2024 7:57 am America/New_York
- Forum: Home
- Question: NASA's Black Marble monthly data: Reprojection isn't accurate
- Replies: 3
Re: NASA's Black Marble monthly data: Reprojection isn't accurate
Thanks very much for the information. Yes, we have this tool available from our black marble tools website at:
https://blackmarble.gsfc.nasa.gov/Tools.html
https://blackmarble.gsfc.nasa.gov/Tools.html
- Mon Jun 17, 2024 11:03 am America/New_York
- Forum: Home
- Question: VNP46A2 - VIIRS/NPP Gap-Filled Lunar BRDF-Adjusted Nighttime Lights Daily Extended GAP
- Replies: 1
Re: VNP46A2 - VIIRS/NPP Gap-Filled Lunar BRDF-Adjusted Nighttime Lights Daily Extended GAP
Yes, you are correct, the data gap and delay in processing is because of the impact of the GPS Anomaly posted on the forum and at: https://ladsweb.modaps.eosdis.nasa.gov/alerts-and-issues/143045 We should be able to resume the C1 processing and take it up from that day on wards, but will not get pro...
- Fri Jun 14, 2024 8:22 am America/New_York
- Forum: Home
- Question: CLDPROP_L2_MODIS_Aqua data missing?
- Replies: 1
Re: CLDPROP_L2_MODIS_Aqua data missing?
Is there a specific file that you are referring to because we checked CLDPROP_L2_MODIS_Aqua.A2005001.0000.011.2021144065133.nc file and it seems complete with all SDSs in it (see attached)
- Tue Jun 11, 2024 9:25 am America/New_York
- Forum: Home
- Question: APIv2: TemporalRange across years giving strange results
- Replies: 3
Re: APIv2: TemporalRange across years giving strange results
Yes, there is ticketing system but this is internal for the development team and not open to public. You can check back towards the middle to end of July.
- Mon Jun 10, 2024 3:46 pm America/New_York
- Forum: Home
- Question: APIv2: TemporalRange across years giving strange results
- Replies: 3
Re: APIv2: TemporalRange across years giving strange results
Thanks very much for notifying this issue. Yes, seems to be a bug. We will try to get to it soon, however due to current priorities it might take several weeks before this gets resolved. We are expecting that the earliest we can get to it is around middle of July.