Near Real-Time Data Outages and Issues
AIRS NRT data outages and known issues
No known issues.
AMSR2 NRT data outages and known issues
Please be aware that the LANCE AMSR2 NRT products are generated using modified versions of the AMSR-E standard product algorithms, which have not been updated to reflect the differences between AMSR-E and AMSR2 calibrations. All LANCE AMSR2 data should be used with the understanding that these are preliminary data products.
Known issue: NRT AMSR2 L2B Global Swath GSFC Profiling Algorithm 2010: Surface Precipitation, Wind Speed over Ocean, Water Vapor over Ocean and Cloud Liquid Water over Ocean
There are some “square holes” in the lower center of many of the RainOcean images. This is caused by erroneous sea ice values in the Reynolds Sea Ice product that is used to process the data. This problem will be resolved when the RainOcean algorithm is updated to GPROF2014, which uses the NOAA Autosnow product for land snow cover as well as sea ice.
Known Issue: NRT AMSR2 Daily L3 Global Snow Water Equivalent EASE-Grids
JAXA's NRT L1R brightness temperature data are supplied to us in "nearly-orbit" files. Unlike the standard products, the data in these files usually doesn't start or end exactly at the north pole. We process these data in the form in which we receive them by splitting them into descending and ascending "half-orbit" files at the south pole inflection point. Therefore, there may be extra or missing data at the beginning of the descending a half-orbit and at the end of the ascending half-orbit.
Improved latency for the near real time L1R data means that AMSR2 LANCE products are consistently available within the target time period of three hours from observation. However, because the AMSR2 snow product is generated only from the descending passes, when data are missing at the beginning of the descending half-orbit, that data will be missing from the resulting snow product and corresponding imagery as well.
MLS NRT data outages and known issues
No known issues.
MODIS NRT data outages and known issues
OMI NRT data outages and known issues
Several row anomalies have occurred in the recent past. These anomalies affect the quality of the Level 1B and Level 2 data products.
- Anomaly 1: Since June 25th, 2007, cross-track scenes 53-54 (0-based).
- Anomaly 2: Since May 11th, 2008, cross-track scenes 37-44 (0-based).
- Anomaly 3: Since January 24th, 2009, cross-track scenes 27-44 (0-based).
- Anomaly 4: Since July 5th, 2011, cross-track scenes 42-45 (0-based).
- Anomaly 5: Since Aug, 2011, cross-track scenes 41-45 (0-based).
Please be aware that for all other rows the data are of optimal quality and not affected. Also all OMI data before these anomalies are of optimal quality. More information on row anomalies is available here.
Row Anomaly Behavior
Since “anomaly 3” the row anomaly exhibits a more dynamic behavior than before. Which rows are affected and to what extent varies with time. Please visit the “Overview” section of our detailed technical information page for the most up to date information and details.
Row Anomaly Corrections
The anomalies are known to the OMI team and are currently under investigation to examine whether corrections for the effects can be implemented in the Level 1b data. Please visit this information page regularly for updates on the status of corrections implemented and visit our detailed technical information page.
Row Anomaly Flagging
The Level 1B data are partially flagged for the anomalies listed above. We expect to provide appropriate flagging for the anomalies in the near future. Please visit our detailed technical information page for details on the current flagging status of the Level 1B and Level 2 products.
Recommendations To Users
At the moment no corrections have been implemented in the operational Level 1B and Level 2 data. It is recommended not to use the affected cross-track scenes. Please respect the dates mentioned above. All other OMI data, meaning other cross track scenes and earlier observations, is of optimal quality. Level-3 products are being produced after filtering for the cross track scenes mentioned per anomaly.
Page Last Updated: Sep 16, 2015 at 3:23 PM EDT