![]() |
Earth Radiation Budget Experiment Regional, Zonal, and Global Averages (S-4) Output Product Langley ASDC Data Set Document |
![]() |
This document describes the Regional, Zonal, and Global Averages (S-4) Output Product and provides the user with the necessary information to use the Earth Radiation Budget Experiment (ERBE) data for scientific research studies.
The S-4 data set consists of scanner and nonscanner data processed for the months in which the scanners were operational. During this processing, the nonscanner data were processed using scene identification information (see Table 21) from the scanners.
ERBE_S4_NAT: Earth Radiation Budget Experiment (ERBE) S-4 (Scanner and Nonscanner) Regional, Global, and Zonal Averages of Radiant Flux and Albedo in Native (NAT) Format (ERBE_S4_NAT)
The S-4 contains averages of flux and albedo on regional, zonal, and global scales for both scanner and nonscanner data.
The objectives of ERBE are:
The S-4 contains averages of flux and albedo on regional, zonal, and global scales for both scanner and nonscanner data. It is available as a single or as a combination of all operational spacecraft (ERBS, NOAA-9, and NOAA-10) for the scanner data and the wide field-of-view (WFOV) data. It is available as a combination of the ERBS and NOAA-9 spacecraft for medium field-of-view (MFOV) data. Single satellite data will soon be available. The S-4 is a multifile product which has seven files of scanner data; scanner data are of 2.5 degree resolution and each region is nested to 5 and 10 degrees. The S-4 contains five files of MFOV numerical filter and five files of WFOV numerical filter. Numerical filter data are of 5 degree resolution and each region is nested to 10 degrees. Also on the S-4 are three files of MFOV shape factor and three files of WFOV shape factor data, which are of 10 degree resolution. Monthly (day), monthly (hour), daily, and monthly hourly averages are determined for each region. The data are represented in 8-, 16-, and 32-bit integers. The values contained are as follows:
The goal of the ERBE is to produce monthly averages of longwave and shortwave radiation parameters on the Earth at regional to global scales. Preflight mission analysis lead to a three-spacecraft system to provide the geographic and temporal sampling required to meet this goal. Three nearly identical sets of instruments were built and launched on three separate spacecraft. These instruments differ principally in the spacecraft interface electronics and in the field-of-view limiters for the nonscanner instruments because of differences in the spacecraft orbit altitudes.
The ERBS spacecraft was launched by Space Shuttle Challenger in October 1984 and was the first spacecraft to carry ERBE instruments into orbit. The ERBS was designed and built by Ball Aerospace Systems under contract to NASA Goddard Space Flight Center (GSFC), and ERBS was the first spacecraft dedicated to NASA science experiments to be launched by the Space Shuttle. The ERBS carries the Stratospheric Aerosol and Gas Experiment (SAGE II) instrument in addition to the ERBE instruments. The Payload Operation and Control Center (POCC) at GSFC directs operations of the ERBS spacecraft and the ERBE and SAGE II instruments, employing both ground stations and the Tracking and Data Relay Satellite System (TDRSS) network. Spacecraft and instrument telemetry data are received at GSFC where the data are processed by the Information Processing Division that provides ERBE and SAGE II experiment data to the NASA Langley Research Center (LaRC).
The second and third spacecraft launched with ERBE instruments are Television Infrared Radiometer Orbiting Satellite (TIROS) N-class spacecraft, which are part of the NOAA operational meteorological satellite series. The NOAA-9 and NOAA-10 spacecraft were launched in December 1984 and September 1986, respectively. The NOAA spacecraft include other instruments, such as the Advanced Very High Resolution Radiometer (AVHRR) and the High-Resolution Infrared Radiometer Sounder (HIRS), which provide NOAA with data for near-real-time weather forecasting. Both spacecraft are in nearly sun-synchronous orbits. The equator-crossing times (at launch) of the orbital nodes for the NOAA-9 and NOAA-10 orbits were 1420 UT (ascending) and 1930 UT (descending), respectively, where UT denotes universal time. The Satellite Operations and Control Center (SOCC) at the National Environmental Satellite and Data Information Service (NESDIS) operates the NOAA spacecraft. NOAA also provides decommutation processing of the telemetry data.
NASA tracks the ERBS spacecraft, and the North American Aerospace Defense Command (NORAD) tracks the NOAA spacecraft. The tracking data are provided to GSFC where orbit ephemeris data are calculated for all three spacecraft and provided to LaRC.
| SRB_Daily | Surface Radiation Budget Daily Averages |
| SRB_Monthly | Surface Radiation Budget Monthly Averages |
Dr. Bruce R. Barkstrom
ERBE Principal Investigator
NASA Langley Research Center
Earth Radiation Budget Experiment (ERBE)
The theory behind the measurements made to collect the ERBE data is non-trivial and well beyond the scope of this document. However, interested readers are referred to the following publications: NASA Reference Publication 1184, Angular radiation models for Earth-atmosphere system, Volume 1: Shortwave radiation, and Volume 2: Longwave radiation; NASA Technical Paper 2670, Calculation and accuracy of ERBE scanner measurement locations; and Smith (Reference 15).
All three sets of ERBE instruments were designed to collect data for one year but had a goal of two years. The nonscanner instruments continue to collect data for ERBS; however, the nonscanner instruments on-board NOAA-9 and NOAA-10 have been deactivated. Table 1 describes the nominal orbit parameters for each satellite at launch.
| Nominal Orbit Parameter | ERBS | NOAA-9 | NOAA-10 |
|---|---|---|---|
| Launch Date | October 5, 1984 | December 12, 1984 | September 17, 1986 |
| Planned Duration | 1 Year | 1 Year | 1 Year |
| Actual Duration Scanner | 5-1/2 years (February 28, 1990) |
3 years (January 20, 1987) |
2-1/2 years (May 22, 1989) |
| Actual Duration Nonscanner | Operating | Over 12 years, deactivated April 3, 1997 | Over 8 years, deactivated December, 1994 |
| Orbit | Precessing | Sun-synchronous | Sun-synchronous |
| Semi-major Axis | 6988 km | 7248 km | 7211 km |
| Mean Altitude | 610 km | 872 km | 833 km |
| Inclination | 57 deg | 98 deg | 98 deg |
| Nodal Period | 98 minutes | 102.08 minutes | 101.2 minutes |
| Equator Crossing Time (at launch) | Variable | 1430 Local Mean Solar Time, ascending | 0730 Local Mean Solar Time, descending |
The ERBE instruments are on the ERBS, NOAA-9, and NOAA-10 satellites.
ERBS was the first spacecraft dedicated to NASA science experiments to be launched by the Space Shuttle. ERBS carries SAGE II instruments in addition to the ERBE instruments. The NOAA spacecraft include other instruments, such as the Advanced Very High Resolution Radiometer (AVHRR) and the High-Resolution Infrared Radiometer Sounder (HIRS), which provide NOAA with data for near-real-time weather forecasting.
A complete list of the measured parameters is found in Table 2.
| CHANNEL | WAVELENGTH LIMITS (microns) |
MEASUREMENT | |
|---|---|---|---|
| Nonscanner Fixed Wide field of view | 1 | 0.2 - 50.0 | Total Radiance |
| 2 | 0.2 - 5.0 | Shortwave Reflected | |
| Nonscanner Fixed Medium field-of-view | 3 | 0.2 - 50.0 | Total Radiance |
| 4 | 0.2 - 5.0 | Shortwave Reflected | |
| Fixed Solar Monitor | 5 | 0.2 - 50.0 | Total Irradiance |
| Scanner Narrow field-of-view | 1 | 0.2 - 50.0 | Total Radiance |
| 2 | 0.2 - 45.0 | Shortwave Reflected | |
| 3 | 5.0 - 50.0 | Longwave Emitted |
The ERBE is a multisatellite system designed to measure the Earth's radiation budget. The ERBE instruments fly on a mid-inclination NASA satellite, (ERBS), and two sun-synchronous NOAA satellites, (NOAA-9 and NOAA-10). Each satellite carries both a scanner and a nonscanner instrument package with characteristics listed in Table 2.
The scanner package contains three radiometric detectors each of which consists of an f/1.84 Cassegrain telescope. All are located within a single, rotating scan-head which, when operating in the cross track azimuth position, scans the Earth perpendicular to the satellite ground track from horizon to horizon. The scan-head can also be rotated in azimuth at a slow rate (0.9 degrees/second NOAA, 0.675 degrees/second ERBS). Each detector samples 74 measurements per scan. The total detector has no filter and so absorbs all wavelengths. The shortwave detector has a Suprasil-W1 filter which transmits only shortwave radiation. The longwave detector has a multilayer filter on a diamond substrate to reject shortwave and accept longwave radiation. To enhance the spectral flatness of the detectors, each thermistor chip is coated with a thin layer of black paint.
The nonscanner instrument package contains four Earth-viewing channels and a solar monitor. The Earth-viewing channels have two spatial resolutions: a horizon-to-horizon view of the Earth, and a field-of-view limited to about 1000 km in diameter. The former are called the wide field-of-view (WFOV) and the latter the medium field-of-view (MFOV) channels. For each of the two fields of view, there is a total spectral channel which is sensitive to all wavelengths and a shortwave channel which uses a high purity, fused silica filter dome to transmit only the shortwave radiation from 0.2 to 5 microns. The solar monitor is a direct descendant of the Solar Maximum Mission's Active Cavity Radiometer Irradiance Monitor detector. Because of the concern for spectral flatness and high accuracy, all five of the channels on the nonscanner package are active cavity radiometers.
The nonscanner elevation beams can be rotated to any of three positions: launch/stow/internal calibration position (180 degrees), solar calibration position (78 degrees), and Earth-viewing (nadir) position (0 degrees). The WFOV detectors view the Earth from limb-to-limb (plus a small ring of space). The MFOV detectors are designed to include approximately an Earth view of 10 geocentric degrees within the unencumbered field of view (FOV).
The scanner can rotate in azimuth between 0 degrees and 180 degrees with an accuracy of 0.075 degrees. The normal scan mode is cross-track. The effective FOV of the scanner is 3 degrees.
The ERBE instruments were developed by TRW, Inc.
Not applicable.
The tolerance is 1 percent for the total channel and 2 percent for the shortwave channel.
For the scanner instruments, in-flight calibrations were accomplished every scan, as well as on a bi-weekly basis. In-flight calibrations of the nonscanners were normally performed on a bi-weekly basis.
The ERBE instruments were developed by TRW, Inc. Laboratory calibrations of the ERBE nonscanner and solar monitor instruments were completed in the TRW calibration facility at Redondo Beach, California in 1984. The fundamental standards used for the ERBE instruments were the International Pressure and Temperature Standard of 1968 (IPTS-68) and the World Radiation Reference (WRR). The TRW master reference blackbody (MRBB) was calibrated using these, and the MRBB was subsequently used to transfer the calibrations to the internal blackbody (IBB) and to the shortwave channels via an integrating sphere. The results of the calibrations were reported in detail in TRW calibration documents.
In-flight calibrations are performed in order to maintain the accuracy of radiometric measurements by accounting for internal instrument component parametric changes brought about by the spacecraft's environmental variables. In-flight calibrations of the nonscanners were normally performed on a bi-weekly basis. These included internal calibrations, space looks, and solar calibrations. Internal calibrations consist of cycling of IBB temperatures (total sensors) and shortwave internal calibration source (SWICS) voltages. Space looks consist of observations of "cold" space, both before and after solar calibrations. Solar calibrations consist of measurements made while the solar disc is within the instrument's field-of-view.
On days when internal calibrations are performed, shortwave offsets are independently determined in four ways:
In cases where the first option is not viable, the second option is used, along with a linearly-fitted delta based upon the historical differences between method 1 and method 2. The offsets determined using options 3 and 4 have never been used in production processing.
The ERBE nonscanner instrument consists of four Earth-viewing detectors and one solar monitor detector located on the head assembly. The four Earth-viewing detectors are unchopped active cavity radiometers (ACR), whereas the solar monitor is an unfiltered chopped ACR designed to measure direct solar radiation for calibrating the Earth-viewing detectors. Two of these detectors have wide field-of-view (WFOV) apertures allowing the detectors to view the entire disk of the Earth; the other two detectors have medium field-of-view (MFOV) apertures allowing the detectors to view an area about 1000 km in diameter. Two of the Earth-viewing detectors, one WFOV and one MFOV, and the solar monitor detector measure total radiation, whereas the other two Earth-viewing detectors measure shortwave radiation. The total radiation detectors are unfiltered, and the shortwave spectral bands are achieved by use of fused silica dome filters placed over the detectors.
The nonscanner instrument microprocessor processes and executes ground-commanded and stored commands to direct and control the instrument operations. The instrument can operate in several modes so that radiation measurements can be made over a wide range of operational conditions. The instrument can operate at azimuth angles between 0 and 180 degrees, and at fixed elevation beam positions of 0(nadir), 78 (solar ports), and 180 (stow or internal calibration position) degrees. Normal Earth-viewing operation is at the nadir elevation position and at an azimuth position of 180 degrees for NOAA-10, 170 degrees for NOAA-9, and 0 degrees for ERBS. The ERBE nonscanner instrument output consists of a complete cycle of radiometric and housekeeping measurements every 16 seconds. There are 20 radiometric measurements every 16 seconds, while the frequency of housekeeping measurements is either 1, 2, or 4 measurements per 16 seconds, depending on the type of measurement.
Telemetry data from the ERBE instruments on the NOAA-9 and NOAA-10 spacecraft are transmitted to Control and Data Acquisition (CDA) ground stations at Gilmore Creek, Alaska, and Wallops Island, Virginia that relay the data through a geostationary communications satellite to the SOCC at NESDIS in Suitland, Maryland. NOAA provides decommutation processing of the telemetry data and provides the data to LaRC. During portions of the ERBE mission, telemetry data from the NOAA spacecraft were transmitted to GSFC for decommutation processing and delivery to LaRC. Telemetry and tracking data from the ERBE instrument on ERBS are transmitted to the NASA ground terminal at White Sands, New Mexico through the Tracking and Data Relay Satellite System (TDRSS). The data are transmitted from the ground terminal to the NASA communications center at GSFC, where the data are processed by the Information Processing Division (IPD) that provides ERBE telemetry data to LaRC.
Not applicable.
Not applicable.
The spatial coverage differs with the channel and the spacecraft, as described below.
WFOV Instruments: these two fixed detectors continuously view the earth disc (plus a small ring of space). The measurements are continuous over the entire globe for NOAA-9 and NOAA-10, and between 57 degrees north and south latitudes for ERBS which precesses approximately 3.95 degrees west per day.
MFOV Instruments: these two fixed detectors continuously view an area about 1000 km in diameter (nominally, a 5 degree earth central angle at the top of the Earth atmosphere, TOA). The measurements are continuous over the entire globe for NOAA-9 and NOAA-10, and between 57 degrees north and south latitude for ERBS.
Scanner Instruments: these three scanning instruments continuously view small areas over the entire Earth. The cross-track scan FOV is approximately 40 km at nadir, and there is a 35FOV overlap at nadir for ERBS between scans.
The ERBE instruments on board the NOAA-9 and NOAA-10 satellites provide global spatial coverage, while the scanner instruments on board the ERBS provides coverage between 67.5 degrees north and south latitude and the nonscanner instruments on board the ERBS provide coverage between 60 degrees north and south latitude.
Though a map is not available, the limits of coverage are discussed in the Spatial Coverage Section.
The spatial resolution differs with the four types of instruments and the two types of spacecraft (ERBS and NOAA). The WFOV instruments have 136 degree FOV on ERBS and 126 degree FOV on the NOAA satellites. The MFOV instruments have footprints of approximately 5 geocentric degree radius or 1000 km at the TOA. The scanner instruments have an instantaneous hexagonal FOV with an angular size of 3 X 4.5 degree, which is equivalent to a 31 X 47 km footprint at nadir for ERBS and 44 X 65 km for NOAA. The solar instrument has an unencumbered FOV which observes the entire solar disk.
Gridded products of the scanner data are available in 2.5 X 2.5 degree resolutions. S-4 and S-4G scanner data are also available as 5 X 5 degree and 10 X 10 degree nested grids. 5 X 5 degree resolution and 10 X 10 degree nested grids are available for numerical filter nonscanner data, and 10 X 10 degree resolution is available for the shape factor nonscanner data on the S-4 output product.
Gridding is an equal-angle projection of 2.5 X 2.5 degree (NFOV, 10368 bins), 5.0 X 5.0 degree (MFOV, 2592 bins), and 10.0 X 10.0 degree (WFOV, 648 bins).
Binning of the data is based on an equal-angle grid of 2.5 X 2.5 degree (NFOV, 10368 bins), 5.0 X 5.0 degree (MFOV, 2592 bins), and 10.0 X 10.0 degree (WFOV, 648 bins). In each resolution, the bin number 1 is found at 90 degree N, 0 degree W with the bin number increasing in an easterly direction.
Instruments on the three satellites (ERBS, NOAA-9, and NOAA-10) began acquiring Earth viewing data in November 1984, February 1985, and October 1986, respectively. All of the scanner instruments outlived their life expectancy of one year. The NOAA-9 scanner ceased operations on January 20, 1987 and the NOAA-10 scanner on May 22, 1989. The ERBS scanner ceased operations on February 28, 1990. All of the Earth-viewing nonscanner instruments collect measurements continuously except during calibrations. The solar instrument collects about 20 minutes of usable data during regularly scheduled bi-weekly solar calibration periods. Additional solar measurement data are sometimes obtained for special projects.
Table 3 shows the archival status of the S-4 product. The various combinations of the satellites reflect the actual duration of the scanners as indicated in Table 3. Note that the MFOV data were not processed.
Please consult the Langley ASDC IMS for available data granules for both single and combination satellites.
| November 1984 - January 1985 | ERBS |
| February 1985 - October 1986 | ERBS/NOAA-9 |
| November 1986 - January 1987 | ERBS/NOAA-9/NOAA-10* |
| February 1987 - May 1989 | ERBS/NOAA-10* |
| June 1989 - February 1990 | ERBS |
| *MFOV data from NOAA-10 are not archived. | |
Data records for the Level 2 products are instantaneous measurements and estimates. Gridded data (the S-9, S-10, S-4, and S-4G products) are daily, monthly hour (hourly averages for a month), monthly day (daily averages for a month), and hourly.
Although the data are stored in two different record formats (scanner and nonscanner), the data item definitions are the same for both. The main difference between the two formats is the presence of clear-sky data in the scanner records. Also, the nonscanner region numbers are calculated on a 5.0 or 10.0 grid versus a 2.5 grid for the scanner region numbers.
The definitions below apply directly to the input data (from Monthly Time/Space Averaging) found in files 4, 11, 16, 21, and 24 as listed in Table 11. These same data items in the remainder of the files are averaged values which have passed through the nesting process (files 5, 6, 12, and 17), the zonal averaging process (files 7, 8, 9, 13, 14, 18, 19, 22, and 25) or the global averaging process (files 10, 15, 20, 23, and 26).
The data items are divided into two groups: descriptive data items and scientific data items. The scientific data item are defined by data type (Monthly (Day), Monthly (Hour), Daily, or Monthly Hourly) rather than according to the order found in Table 16 and Table 17, to preserve the original order among the items. (See the Variable Description/Definition Section directly below).
Region: In those files containing input data or nested data, this number is actually a region number. Note that on the scanner file, Region 1 lies in the range 87.5°<lat<=90° (0°<=colat<2.5°), 0°<=long<2.5°. The regions are numbered consecutively, west to east, 144 per latitude band. The last row of regions includes a latitude of -90 degrees (colat = 180 degrees) (Reference 1).
However, in the zonal files, this number indicates the zone or latitudinal band. In the global files, the number represents the resolution as follows: (See Table 11 for a description of the files.)
| File 10: | 1 = 2.5 2 = 5.0 3 = 10.0 |
| Files 15, 23: | 1 = 5.0 2 = 10.0 |
| Files 20, 26: | 1 = 10.0 |
Deadscanner Flags: Because the scanners on the ERBS, NOAA-9, and NOAA-10 satellites became inoperative at different times, deadscanner flags were defined to inform the user whether the scanners were operating for each satellite for a particular data month. Three 8-bit integers represent the NOAA-9, ERBS, and NOAA-10 deadscanner flags, respectively. The values are:
0 - operative scanner
1 - inoperative scanner
32767 - fill value signifying live scanner data which were processed before the
dead scanner option was implemented, or no data for that satellite
File ID: The file ID is a number from 1 to 23. File 1 on the tape is actually file 4 in Table 11.
Date: YYMM: The date reflects the year and month of the data processed by S-4. The S-4 processing date can be found in the header file (Data Format Section). (Example 9304)
Spacecraft: The spacecraft code will be a number from 1 to 7. Table 4 defines the values of the spacecraft code.
| Code No. | Satellite |
|---|---|
| 1 | NOAA-9 |
| 2 | ERBS |
| 3 | NOAA-10 |
| 4 | NOAA-9/NOAA-10 |
| 5 | ERBS/NOAA-9 |
| 6 | ERBS/NOAA-10 |
| 7 | NOAA-9/ERBS/NOAA-10 |
In the following definitions, numbers in parentheses refer to equations in Reference 2.
The default or fill values for all missing data items are listed below in Table 5. Note that such values are not scaled by S-4 prior to being packed and written to the output tape.
| Number of Bits per Word | Default Value |
|---|---|
| 32 | 2147483647 |
| 16 | 32767 |
| 8 | 137 |
Monthly (Day) Quantities: These are monthly means based on daily calculations of flux. For longwave (LW) quantities, the daily means are obtained from the extrapolation, interpolation, and diurnal modeling algorithms that operate on the existing longwave measurements. The extrapolation and interpolation algorithms will, in general, cross daily boundaries, but the longwave diurnal model applied to land scenes operates on a specific day.
The shortwave (SW) quantities are based on calculations for specific days. The days are defined to be symmetric about solar noon.
The monthly mean shortwave flux (SWF) based on daily SWF values, including
"measurements" from the Inversion Subsystem
(Reference 6) and modeled values, within this region
(Wm-2).
where N = all days of month.
The monthly mean longwave flux (LWF) based on all extrapolated,
interpolated, and modeled LW values for the month in this region.
where N = all days of month.
ALBEDO: The monthly mean albedo from daily values, based on the sum of
all SWFs calculated for days with at least one SW measurement
(Dsw).
where S(d) = integrated solar radiance.
The solar incidence is integrated from sunrise to sunset for each day with
SW data, assuming a sun position for the day that is fixed at its position for
0h0m0s UT. The summed SWF for each day is
multiplied by the ratio of the integrated to summed solar incidence for that
day to provide some corrections to the summation error.
where S'(d) and S(d) are the summed and integrated solar radiances,
respectively.
Other equations used to calculate the albedo values in S-4 may be found in the Calculated Variables Section of this document.
The monthly net flux defined from albedo in Monthly Time/Space Averaging, the
sum of integrated solar incidence over the entire month, and monthly net LWF
(Wm-2).
TSOLRD: The monthly total integrated solar incidence for all days of the month (W-hm-2).
Monthly (day) values for clear-sky: The previous quantities are calculated from all data including clear, partly cloudy, mostly cloudy, and overcast conditions. Clear-sky information (identified with a CS subscript) for longwave (means and statistics defined in Reference 2) is calculated in the Inversion Subsystem and passed through Monthly Time/Space Averaging without modification. The shortwave clear-sky values are calculated by Monthly Time/Space Averaging according to the distribution of cloud conditions as indicated by the scene fraction vector.
Monthly (Hour) Quantities: These items are monthly means based on values averaged over the month at each local hour. In general, they result in different values for the same quantity, compared to the monthly (day) means.
The monthly mean SWF based on summing SWF values over days with at least one
SW measurement, and then over each local hour
(Wm-2).
where N = all days of month.
The monthly mean LWF based on extrapolated, interpolated, and modeled LW values
only for days during the month that had at least one actual LW
measurement (Wm-2).
ALBEDO: The monthly mean albedo from monthly hourly values, based on the
sum of all SWFs calculated. There is no correction for integrated solar
incidence in the monthly hourly albedo calculations. The equations used to
calculate the albedo values in S-4 may be found in the
Calculated Variables Section of this document.
where S(d) = integrated solar radiance, Dsw = days with at least one
SW measurement.
The monthly net flux defined from albedo in Monthly Time/Space Averaging, the
solar incidence summed (not integrated) over the entire month, and monthly net
LWF defined from days with at least one LW measurement
(Wm-2).
where mha = monthly hourly average.
TSOLRH: The monthly total solar incidence for all days of the month (W-hm-2).
Monthly (hour) values for clear-sky: Clear-sky information for longwave (means and statistics defined in Reference 2) is based on values calculated in the Inversion Subsystem. The shortwave clear-sky values are calculated by Monthly Time/Space Averaging according to the distribution of cloud conditions as indicated by the scene fraction vector.
Daily values: These quantities are calculated for each day in the month.
The daily shortwave flux; i.e., the sum of all measured and modeled SWFs for
every day with at least one SW measurement, corrected by the ratio of
integrated to summed solar incidence (Wm-2).
where S(d) and S'(d) are the integrated and summed solar radiances,
respectively.
Daily LWF consisting of measurements and extrapolated, interpolated, and
modeled values (Wm-2).
ALBEDO: The daily albedo is defined as the ratio of daily SWF to the integrated daily solar incidence. The equations used to calculate the albedo values in S-4 may be found in the Calculated Variables Section of this document.
TSOLRD: The integrated solar incidence for a day that includes at least one SW measurement (W-hm-2).
NDSW: The number of hours with SW measurements for a day that includes at least one SW measurement.
NDLW: The number of hours with LW measurements for a day that includes at least one LW measurement.
Daily values for clear-sky: The above values are repeated for clear-sky conditions (except for the SOLARD). The LW clear-sky values are passed from the Inversion Subsystem, but the SW values are calculated within Monthly Time/Space Averaging.
Monthly hourly values: These values are calculated for the month at each local hour.
The monthly average SWF at this hour (Wm-2).
The monthly average LWF at this hour (Wm-2).
ALBEDO: Monthly hourly albedo. The equations used to calculate the albedo values in S-4 may be found in the Calculated Variables Section of this document.
SOLARH: The integrated solar incidence over those days with SW data for a given hour (W-hm-2).
NHSW: The number of days that contain SW measurements for a given hour.
NHLW: The number of days that contain LW measurements for a given hour.
Monthly hourly values for clear-sky: The above values are repeated for clear-sky conditions as defined by the Inversion Subsystem.
Scanner:
An integer from 1-5 denoting the surface type for the region.
The types are:
1 = ocean
2 = land
3 = snow
4 = desert
5 = land/ocean mix (coastal regions)
For the land/ocean mix, the corresponding directional models (clear, partly, or mostly cloudy over this scene) are linear composites of land and ocean models and not independent models.
Nonscanner:
The fraction of cloud-free (as determined by the
Inversion Subsystem) land and desert geotype. If greater than 0.5, the
half-sine model is applied in the calculation of LWF (Reference
2).
Units of measurement for the calculated and measured science variables for the S-4 data product can be found in the Variable Description/Definition Section of this document.
The purpose of the S-4 Output Product is to provide averages of radiant flux values and albedos using data from the Monthly Time/Space Averaging Subsystem (Reference 4) on a regional, zonal, and global basis. The basic structure of the ERBE grid system lends itself to calculating several types of averages. Reference 1 provides a detailed description of the ERBE grid system and gives the necessary background information for the design of this subsystem.
The S-4 product contains data which have been averaged to 2.5,
5.0, and 10.0 degree grid scales. The layout
of a 2.5 degree system is given; the 5.0 and 10.0 degree systems are
designed similarly. In this grid system, L = longitude and
= latitude is replaced with colatitude, where
= 90 -
,
so that
.
The following list shows the number of regions for each resolution:
| Resolution | Total No. Regions |
|---|---|
| 2.5 | 10,368 |
| 5.0 | 2,592 |
| 10.0 | 648 |
To facilitate comparison with nonscanner data, the scanner data are nested with area weighting to 5.0 and 10.0 degree regions, with four scanner 2.5 degree regions producing a 5.0 degree region and sixteen 2.5 degree regions producing a 10.0 degree region. Similarly, four nonscanner numerical filter 5.0 degree regions are nested to produce a 10.0 degree region. This nesting is pictured in Figure 2, and the weighting is described further on in this section.
The S-4 product also contains averages over the latitudinal bands (zones). The following list shows the number of latitudinal bands for each resolution:
| Resolution | Total No. Bands |
Total No. of Regions in Each Band |
|---|---|---|
| 2.5 | 72 | 144 |
| 5.0 | 36 | 72 |
| 10.0 | 18 | 36 |
The equation below gives the formula for calculating averages:
where,
= nested average flux value
N = number of regions included in nested average
Wi = area weighting factor
Mi = individual values
The final type of average is on a global level. Each parameter is averaged over the entire globe with area weighting.
For each of the three ERBE spacecraft, (ERBS, NOAA-9, and NOAA-10), there are three sets of measurements (scanner, nonscanner MFOV, and nonscanner WFOV). For the nonscanner measurements, there are two data reduction techniques (shape factor and numerical filter). For each satellite, the on-line processing proceeds as follows:
Table 6 provides a summary of the type of data available in the S-4 output product.
| Estimate | Scanner | Nonscanner | ||||
|---|---|---|---|---|---|---|
| Area | SCAN | SCAN CS | MFOV NF | MFOV SF | WFOV NF | WFOV SF |
| 2.5 region | X | X | - | - | - | - |
| 5.0 region | X | X | X | - | X | - |
| 10.0 region | X | X | X | X | X | X |
| 2.5 zone | X | X | - | - | - | - |
| 5.0 zone | X | X | X | - | X | - |
| 10.0 zone | X | X | X | X | X | X |
| Global | X | X | X | X | X | X |
Processing is controlled by the lower resolution region numbers. A simple set of calculations can be used to derive the four higher resolution region numbers which will be nested into the lower resolution region (see Figure 2). The formulas for finding the four 2.5 degree region box numbers which are nested into a 5.0 degree region box are:
| B2.5(1) = 288 INT [(B5 - 1)/72] + 2 MOD [(B5 - 1),72] + 1 |
| B2.5(2) = B2.5(1) + 1 |
| B2.5(3) = B2.5(1) + 144 |
| B2.5(4) = B2.5(1) + 145 |
| B2.5(N) | = 2.5° region box number |
| B5 | = 5° region box number |
The formulas for finding the four 5.0 degree region box numbers which are nested into a 10.0 degree region box are:
| B5(1) = 144 INT [(B10 - 1)/36] + 2 MOD [(B10 - 1),36] + 1 |
| B5(2) = B5(1) + 1 |
| B5(3) = B5(1) + 72 |
| B5(4) = B5(1) + 73 |
where,
B10(N) = 10.0° region box number
The colatitude index is used to obtain the correct area weighting value and to distinguish between polar latitudinal bands and nonpolar latitudinal bands. It can be derived from the region number as follows:
COLAT = INT[B6 - 1)/N] + 1
where,
B6 = higher resolution region number
N = number of regions in a latitudinal band
The 2.5 degree product is used to nest the 5.0 degree product which is then used to nest to the 10.0 degree product. This process is done for each satellite and each combination of satellites. For each of these processes, separate zonal and global products are produced for each resolution,
where for any data product,
designates the source and final product resolution. Analogously, there will
also be similar paths for numerical filter data:
and
and for shape factor data:
and
So, for each satellite and combination of satellites, there are potentially nine different global (monthly) averages of each calculated quantity. Why is there a difference between, for example, G(2.5-2.5) and G(2.5-5)? If there were no missing data on the high resolution grid, these numbers should be the same. However, missing data forces nesting procedures which can produce some discrepancies between the two products.
Because the ERBE grid system divides the globe into regions which are defined by equal increments of latitude and longitude rather than equal areas, the nested averages must be normalized by weighting each region based upon its area. Since regions across a latitudinal band have the same area, only one weighting factor is needed for each latitudinal band. It also follows that since the area weighting factors across a latitudinal band are the same, the zonal averages do not have to be normalized. The following equation gives the formula for calculating the area weighting factors.
by
region in km2
= resolution in degrees (2.5, 5.0, 10.0)
= colatitude in degrees of the center of the latitudinal band region
Polar day-night indicators are used to identify those regions within approximately 23.5 degrees of the poles that experience continuous darkness or continuous daylight at certain times of the year. These regions are treated differently from those which always experience day-night cycles.
In general, radiant flux values for regions not observed by the satellite are not accumulated as part of the averaging process. However, since it is known that the shortwave radiant flux is zero when there is no daylight, those unobserved regions which are in complete darkness for the entire month (i.e., near the polar regions at certain times of the year), will have the shortwave set to zero. The reason for doing this is to reduce the error in the zonal and global averaging process.
There is a direct relationship between the daily solar declination and the colatitude of a region. This can be used to determine whether or not that region is experiencing total darkness or has some daylight and which part of the month is affected. Of course, none of this has any effect on regions in latitudinal bands which are not near the north or south poles.
The criteria for setting the polar day-night indicators for latitudes in the northern hemisphere are:
The criteria for setting the polar day-night indicators for latitudes in the southern hemisphere are:
In order to clarify this concept, some tables have been provided to illustrate the results of applying the logic described above. Table 7 shows which colatitudes are considered to be the northern and southern polar latitudes for each resolution.
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Table 8 shows the solar declinations for 1985, which was chosen as the example year.
| DAYS | MONTHS | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JAN | FEB | MAR | APR | MAY | JUN | JUL | AUG | SEP | OCT | NOV | DEC | |
| 1 | -23.02 | -17.17 | -7.68 | 4.44 | 15.00 | 22.02 | 23.13 | 18.09 | 8.38 | -3.08 | -14.34 | -21.76 |
| 2 | -22.94 | -16.89 | -7.30 | 4.82 | 15.30 | 22.15 | 23.06 | 17.83 | 8.02 | -3.47 | -14.66 | -21.92 |
| 3 | -22.85 | -16.60 | -6.92 | 5.21 | 15.60 | 22.28 | 22.98 | 17.58 | 7.65 | -3.86 | -14.98 | -22.06 |
| 4 | -22.75 | -16.30 | -6.54 | 5.59 | 15.89 | 22.40 | 22.90 | 17.31 | 7.28 | -4.24 | -15.29 | -22.20 |
| 5 | -22.64 | -16.00 | -6.15 | 5.97 | 16.18 | 22.52 | 22.81 | 17.05 | 6.91 | -4.63 | -15.60 | -22.33 |
| 6 | -22.53 | -15.70 | -5.77 | 6.35 | 16.46 | 22.63 | 22.72 | 16.77 | 6.54 | -5.01 | -15.90 | -22.46 |
| 7 | -22.40 | -15.39 | -5.38 | 6.73 | 16.74 | 22.73 | 22.62 | 16.50 | 6.17 | -5.40 | -16.20 | -22.58 |
| 8 | -22.28 | -15.07 | -4.99 | 7.10 | 17.02 | 22.82 | 22.51 | 16.22 | 5.79 | -5.78 | -16.49 | -22.69 |
| 9 | -22.14 | -14.75 | -4.60 | 7.48 | 17.29 | 22.91 | 22.39 | 15.93 | 5.42 | -6.16 | -16.78 | -22.79 |
| 10 | -22.00 | -14.43 | -4.21 | 7.85 | 17.55 | 22.99 | 22.27 | 15.64 | 5.04 | -6.54 | -17.07 | -22.89 |
| 11 | -21.84 | -14.11 | -3.82 | 8.22 | 17.81 | 23.07 | 22.14 | 15.35 | 4.66 | -6.92 | -17.35 | -22.98 |
| 12 | -21.69 | -13.78 | -3.42 | 8.59 | 18.07 | 23.13 | 22.01 | 15.05 | 4.28 | -7.30 | -17.62 | -23.06 |
| 13 | -21.52 | -13.44 | -3.03 | 8.95 | 18.32 | 23.20 | 21.87 | 14.75 | 3.90 | -7.67 | -17.89 | -23.13 |
| 14 | -21.35 | -13.11 | -2.64 | 9.31 | 18.56 | 23.25 | 21.72 | 14.45 | 3.52 | -8.05 | -18.16 | -23.20 |
| 15 | -21.17 | -12.77 | -2.24 | 9.67 | 18.80 | 23.30 | 21.57 | 14.14 | 3.13 | -8.42 | -18.42 | -23.25 |
| 16 | -20.98 | -12.42 | -1.85 | 10.03 | 19.04 | 23.34 | 21.41 | 13.82 | 2.75 | -8.79 | -18.67 | -23.30 |
| 17 | -20.79 | -12.07 | -1.45 | 10.38 | 19.27 | 23.37 | 21.24 | 13.51 | 2.36 | -9.15 | -18.92 | -23.35 |
| 18 | -20.59 | -11.72 | -1.05 | 10.73 | 19.49 | 23.40 | 21.07 | 13.19 | 1.97 | -9.52 | -19.16 | -23.38 |
| 19 | -20.39 | -11.37 | -.66 | 11.08 | 19.71 | 23.42 | 20.90 | 12.86 | 1.59 | -9.88 | -19.40 | 23.41 |
| 20 | -20.18 | -11.01 | -.26 | 11.43 | 19.92 | 23.43 | 20.71 | 12.54 | 1.20 | -10.24 | -19.63 | -23.43 |
| 21 | -19.96 | -10.65 | .13 | 11.77 | 20.13 | 23.44 | 20.52 | 12.21 | .81 | -10.60 | -19.86 | -23.44 |
| 22 | -19.73 | -10.29 | .53 | 12.11 | 20.33 | 23.44 | 20.33 | 11.87 | .42 | -10.96 | -20.07 | -23.44 |
| 23 | -19.50 | -9.92 | .92 | 12.44 | 20.53 | 23.43 | 20.13 | 11.54 | .03 | -11.31 | -20.29 | -23.44 |
| 24 | -19.27 | -9.56 | 1.31 | 12.78 | 20.72 | 23.42 | 19.92 | 11.20 | -.36 | -11.66 | -20.49 | -23.42 |
| 25 | -19.03 | -9.19 | 1.71 | 13.10 | 20.90 | 23.40 | 19.71 | 10.85 | -.75 | -12.01 | -20.70 | -23.40 |
| 26 | -18.78 | -8.81 | 2.10 | 13.43 | 21.08 | 23.37 | 19.50 | 10.51 | -1.14 | -12.35 | -20.89 | -23.38 |
| 27 | -18.52 | -8.44 | 2.49 | 13.75 | 21.25 | 23.33 | 19.27 | 10.16 | -1.53 | -12.69 | -21.08 | -23.34 |
| 28 | -18.26 | -8.06 | 2.88 | 14.07 | 21.42 | 23.29 | 19.05 | 9.81 | -1.92 | -13.03 | -21.26 | -23.30 |
| 29 | -18.00 | -18.00 | 3.27 | 14.38 | 21.58 | 23.24 | 18.81 | 9.45 | -2.31 | -13.36 | -21.43 | -23.24 |
| 30 | -17.73 | -17.73 | 3.66 | 14.69 | 21.73 | 23.19 | 18.58 | 9.10 | -2.69 | -13.69 | -21.60 | -23.18 |
| 31 | -17.45 | -17.45 | 4.05 | 4.05 | 21.88 | 21.88 | 18.33 | 8.74 | 8.74 | -14.02 | -14.02 | -23.12 |
Table 9 shows the sunlit days for the northern and southern polar regions for the 2.5 degree resolution.
| Year: 1985; Resolution: 2.5 deg. | ||||
|---|---|---|---|---|
| Hemisphere | Colat. Indicator |
Center Colat. (Deg.) |
First Date for Sunlight |
Last Date for Sunlight |
| North | 1 | 1.25 | 03/18 | 09/26 |
| 2 | 3.75 | 03/12 | 10/02 | |
| 3 | 6.25 | 03/05 | 10/09 | |
| 4 | 8.75 | 02/27 | 10/15 | |
| 5 | 11.25 | 02/20 | 10/22 | |
| 6 | 13.75 | 02/13 | 10/30 | |
| 7 | 16.25 | 02/05 | 11/07 | |
| 8 | 18.75 | 01/27 | 11/16 | |
| 9 | 21.25 | 01/15 | 11/27 | |
| South | 64 | 158.75 | 07/17 | 05/26 |
| 65 | 161.25 | 07/30 | 05/14 | |
| 66 | 163.75 | 08/08 | 05/05 | |
| 67 | 166.25 | 08/17 | 04/26 | |
| 68 | 168.75 | 08/24 | 04/19 | |
| 69 | 171.25 | 08/31 | 04/12 | |
| 70 | 173.75 | 09/07 | 04/05 | |
| 71 | 176.25 | 09/14 | 03/30 | |
| 72 | 178.75 | 09/20 | 03/23 | |
Table 10 gives a sample of the polar day-night indicator values for some latitudes at the 2.5 degree resolution.
| COLAT | CENTER COLAT (Deg.) |
POLAR FLAG | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JAN | FEB | MAR | APR | MAY | JUN | JUL | AUG | SEP | OCT | NOV | DEC | ||
| 1 | 1.25 | 50 | 50 | -18 | 0 | 0 | 0 | 0 | 0 | 26 | 50 | 50 | 50 |
| 3 | 6.25 | 50 | 50 | -5 | 0 | 0 | 0 | 0 | 0 | 0 | 9 | 50 | 50 |
| 5 | 11.25 | 50 | -20 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 22 | 50 | 50 |
| 7 | 16.25 | 50 | -5 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 | 50 |
| 9 | 21.25 | -15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 27 | 50 |
| 64 | 158.75 | 0 | 0 | 0 | 0 | 26 | 50 | -17 | 0 | 0 | 0 | 0 | 0 |
| 66 | 163.75 | 0 | 0 | 0 | 0 | 5 | 50 | 50 | -8 | 0 | 0 | 0 | 0 |
| 68 | 168.75 | 0 | 0 | 0 | 19 | 50 | 50 | 50 | -25 | 0 | 0 | 0 | 0 |
| 70 | 173.75 | 0 | 0 | 0 | 5 | 50 | 50 | 50 | 50 | -7 | 0 | 0 | 0 |
| 72 | 178.75 | 0 | 0 | 23 | 50 | 50 | 50 | 50 | 50 | -20 | 0 | 0 | 0 |
Please refer to the Temporal Coverage Map Section of this document for the archival status of the ERBE S-4 product.
ERBE data records are stored as binary integers in the ERBE native format. When ordering this data set, the user has the option of receiving the sample read software for this data set. The "README" file for executing this software provides the necessary information to obtain data records from this data set.
A general description of data granularity as it applies to the IMS appears in the EOSDIS Glossary.
The S-4 Output Product contains two types of data files: scanner files (files 4 through 10 in Table 11) which consist of the scanner input data file, and the resulting nested, zonal, and global data files; and nonscanner files (files 11 through 26 in Table 11) which consist of the nonscanner input data files and the resulting nested (if any), zonal, and global file(s).
The maximum number of records possible for each file is shown in Table 11. The actual number of records will depend upon which regions were represented in the input files. For example, if regions 1 through 144 were not present on the scanner input tape, then the actual number of records present on the S-4 Output Product will be 10224. This in turn, may affect the nesting process and may affect the total number of records produced. The scanner files normally include clear-sky data and have a record format which is different than that for the nonscanner files. These formats are discussed below.
| File | S-4 Filename* | Description | Max. No. Records |
No. Data Values per Record |
No. 8-bit Bytes per Record |
Max. No. Bytes per File |
|---|---|---|---|---|---|---|
| 1 | s4_01_prokey_yymms | ERBE header record | 1 | 1 | 30 | 30 |
| 2 | s4_02_sscalf_yymms | Scanner scale factors | 1 | 675 | 1290 | 1290 |
| 3 | s4_03_nscalf_yymms | Nonscanner scale factors | 1 | 360 | 720 | 720 |
| 4 | s4_04_sc2.5_yymms | NFOV input information | 10368 | 675 | 1290 | 13374720 |
| 5 | s4_05_sc5.0_yymms | 2.5 deg. nested to 5.0 deg. from NFOV input | 2592 | 675 | 1290 | 3343680 |
| 6 | s4_06_sc10.0_yymms | 5.0 deg. nested to 10.0 deg. from NFOV input | 648 | 675 | 1290 | 835920 |
| 7 | s4_07_sc2.5z_yymms | 2.5 deg. zonal from NFOV input | 72 | 675 | 1290 | 92880 |
| 8 | s4_8_sc5.0z_yymms | 5.0 deg. zonal from NFOV input | 36 | 675 | 1290 | 46440 |
| 9 | s4_09_sc10z_yymms | 10.0 deg. zonal from NFOV input | 18 | 675 | 1290 | 23220 |
| 10 | s4_10_scglb_yymms | Global from NFOV input | 3 | 675 | 1290 | 3870 |
| 11 | s4_11_mnf5.0_yymms | MFOV-NF input information | 2592 | 360 | 720 | 1866240 |
| 12 | s4_12_mnf10_yymms | 5.0 deg. nested to 10.0 deg. from MFOV-NF input | 648 | 360 | 720 | 466560 |
| 13 | s4_13_mnf5z_yymms | 5.0 deg. zonal from MFOV-NF input | 36 | 360 | 720 | 25920 |
| 14 | s4_14_mnf10z_yymms | 10.0 deg. zonal from MFOV-NF input | 18 | 360 | 720 | 12960 |
| 15 | s4_15_mnfglb_yymms | Global from MFOV-NF input | 2 | 360 | 720 | 1440 |
| 16 | s4_16-wnf5.0_yymms | WFOV-NF input information | 2592 | 360 | 720 | 1866240 |
| 17 | s4_17_wnf10_yymms | 5.0 deg. nested to 10.0 deg. from WFOV-NF input | 648 | 360 | 720 | 466560 |
| 18 | s4_18_wnf5z_yymms | 5.0 deg. zonal from WFOV-NF input | 36 | 360 | 720 | 25920 |
| 19 | s4_19_wnf10z_yymms | 10.0 deg. zonal from WFOV-NF input | 18 | 360 | 720 | 12960 |
| 20 | s4_20_wnfglb_yymms | Global from WFOV-NF input | 2 | 360 | 720 | 1440 |
| 21 | s4_21_msf10_yymms | MFOV-SF input information | 648 | 360 | 720 | 466560 |
| 22 | s4_22_msf10z_yymms | 10.0 deg. zonal from MFOV-SF input | 18 | 360 | 720 | 12960 |
| 23 | s4_23_msfglb_yymms | Global from MFOV-SF input | 1 | 360 | 720 | 720 |
| 24 | s4_24_wsf10_yymms | WFOV-SF input information | 648 | 360 | 720 | 466560 |
| 25 | s4_25_wsf10z_yymms | 10.0 deg. zonal from WFOV-SF input | 18 | 360 | 720 | 12960 |
| 26 | s4_26_wsfglb_yymms | Global from WFOV-SF input | 1 | 360 | 720 | 720 |
| TOTALS | 21666 | --- | --- | 23429490 | ||
*yy represents the year (e.g., 89 - 1989); mm represents the number value of a month (e.g., 01 = January, 12 = December)
s represents the satellite code:
1 = NOAA-9
2 = ERBS
3 = NOAA-10
4 = NOAA-9/NOAA-10
5 = ERBS/NOAA-9
6 = ERBS/NOAA-10
7 = NOAA-9/ERBS/NOAA-10
The cumulative total bits for a single scanner record (or the scanner scale factor record) is 10320 bits. These are grouped into 32-, 16-, and 8-bit words as shown in Table 12.
The actual data items are listed in Table 16 in the same order as they appear on tape and are defined in the Variable Description/Definition Section. This format is used in files 4 through 10 as listed in Table 11.
| Bits per Word | No. of Words | Bits | Cumulative Total Bits |
|---|---|---|---|
| 32 | 90 | 2880 | 2880 |
| 16 | 345 | 5520 | 8400 |
| 8 | 240 | 1920 | 10320 |
The cumulative total bits for a single nonscanner record (or the nonscanner scale factor record) is 5760 bits. These are grouped in 32-, 16-, and 8-bit words as shown below in Table 13.
The actual data items are listed in Table 17 in the same order as they appear on tape and are defined in the Variable Description/Definition Section. This format is used in files 11 through 26 as listed in Table 11.
| Bits per Word | No. of Words |
Bits | Cumulative Total Bits |
|---|---|---|---|
| 32 | 60 | 1920 | 1920 |
| 16 | 180 | 2880 | 4800 |
| 8 | 120 | 960 | 5760 |
The S-4 Output Product contains 26 files as shown in Table 11. The first file contains the standard ERBE header record, the second file contains the scanner scale factors, and the third file contains the nonscanner scale factors. Files 4 through 26 contain the data records.
The archival status of this product at the Langely ASDC is found in the Temporal Coverage Map Section. The S-4 files can be obtained on 9-track, 8mm, or 4mm tape media or as electronic disk files via FTP. When the user is connected to the on-line Langley ASDC system, he will be able to select a particular data set pertaining to the ERBE S-4 data in which he is interested. The name of the S-4 set, which the user will see as he orders his data is ERBE_S4_NAT. The names of the S-4 files which the user will receive from the ASDC are listed in column 2 of Table 11. Column 3 of the same table gives a description of each file.
The first file on the S-4 Output Product contains one header record which identifies the data on the tape. It is a 30-byte record formatted as 8-bit bytes and defined in Table 14.
| Bytes | Description | Value | Interpretation |
|---|---|---|---|
| 1-2 | Subsystem Indicator | 1-7 | The subsystem outputting the data product is: 1 - Telemetry 2 - Ephemeris 3 - Attitude 4 - Merge/FOV/Count Conversion 5 - Inversion 6 - Daily Data Base and Monthly Time/Space Averaging 7 - Output Products |
| 3-4 | Product Code | 1-99 | Each subsystem assigns its output (tape, disc, paper, plot, etc.) a unique number for identification. See Table 1 in Data Products Catalog for individual subystem definitions. |
| 5-6 | Spacecraft Indicator | 1-7 | The data is from the following combination of spacecraft: 1 - NOAA-9 only 2 - ERBS only 3 - NOAA-10 only 4 - NOAA-9 and NOAA-10 5 - NOAA-9 and ERBS 6 - NOAA-10 and ERBS 7 - NOAA-9 and NOAA-10 and ERBS |
| 7-8 | Whole Julian date (high-order part) | e.g., 244 | Leftmost 3 digits of the 7-digit whole part of the intiial Julian date. |
| 9-10 | Whole Julian date (low-order part) | e.g., 5700 | Rightmost 4 digits of the 7-digit whole part of the initial Julian date. |
| 11-12 | Fractional Julian date | e.g., 5000 | First 4 digits of the fractional part of the initial Julian date times 10000. |
| 13-14 | Processed Version Counter | 1-99 | A counter initially set to 1 and incremented by one each time the product is reprocessed. |
| 15-16 | Year Processed | e.g., 84 | The last two digits of the year of process date. The process date is the date (local time) when the data product was processed (or reprocessed) at Langley Research Center, Hampton, VA. |
| 17-18 | Month Processed | 1-12 | Month of the process date. January is 1 and December is 12. |
| 19-20 | Day Processed | 1-31 | Day of the process date. |
| 21-22 | Hour Processed | 0-23 | Hour of the process date. |
| 23-24 | Minute Processed | 0-59 | Minute of the process date. |
| 25-25 | Second Processed | 0-59 | Second of the process date. |
| 27-30 | Spares | 0 | Zero-filled spares to produce a record which is multiple of 8-, 16-, and 60- bits. |
Table 15 shows an example of the S-4 header.
| Bytes | Description | Example | Note |
|---|---|---|---|
| 1-2 | Subsystem Indicator | 7 | The subsystem indicator for the S-4 Output Product will always be 7. |
| 3-4 | Product Code | 1 | The S-4 Output Product Subsystem has arbitrarily defined the product code for the tape to be 1 for scanner plus nonscanner processing S-4N, 2 for nonscanner only processing S-4N. |
| 5-6 | Spacecraft Indicator | 2 | A number 1-7 will appear here depending on whether data is for a single satellite or a combination of satellites. See Table 14. |
| 7-8 | Whole Julian date (high-order part) | 244 | The initial Julian date for this example is 2445700.5000 which corresponds to midnight on January 1, 1984. |
| 9-10 | Whole Julian date (low-order part) | 5700 | The whole Julian date for the first day of the month. |
| 11-12 | Fractional Julian date | 5000 | The fractional Julian date will be 0.5. |
| 13-14 | Processed Version Counter | 1 | A value of 1 means that the S-4 product has been processed one time and not reprocessed. |
| 15-16 | Year Processed | 85 | For this example, the S-4 product was processed on February 3, 1985 at 9 P.M. 48M54S. |
| 17-18 | Month Processed | 2 | |
| 19-20 | Day Processed | 3 | |
| 21-22 | Hour Processed | 21 | |
| 23-24 | Minute Processed | 48 | |
| 25-25 | Second Processed | 54 | |
| 27-30 | Spares | 0 |
The second file contains the integer scanner scale factors. This file contains the same number of scale factor values as there are scanner data values. Table 16 lists a scanner output record and includes a column which lists the corresponding scanner scale factors.
| Item Name | Data Type | No. of Values per Region |
Starting Item No. |
Ending Item No. |
Scale Factor |
Cumulative No. Bits |
Minimum Value |
Maximum Value |
|---|---|---|---|---|---|---|---|---|
| 32-bit words: | ||||||||
| FILE ID | - | 1 | 1 | 1 | 1 | 32 | 1 | 7 |
| TSOLRD | MONTHLY (DAY) | 1 | 2 | 2 | 100 | 64 | 0 | 500000 |
![]() |
MONTHLY (DAY) | 1 | 3 | 3 | 100 | 96 | -200 | 200 |
CS |
MONTHLY (DAY) | 1 | 4 | 4 | 100 | 128 | -200 | 200 |
| TSOLRDCS | MONTHLY (DAY) | 1 | 5 | 5 | 100 | 160 | 0 | 500000 |
![]() |
MONTHLY (HOUR) | 1 | 6 | 6 | 100 | 192 | -200 | 200 |
| TSOLRH | MONTHLY (HOUR) | 1 | 7 | 7 | 100 | 224 | 0 | 500000 |
CS |
MONTHLY (HOUR) | 1 | 8 | 8 | 100 | 256 | -200 | 200 |
| TSOLRHCS | MONTHLY (HOUR) | 1 | 9 | 9 | 100 | 288 | 0 | 500000 |
| SOLARD | DAILY | 31 | 10 | 40 | 100 | 1280 | 0 | 500000 |
| SOLARH | HOURLY | 24 | 41 | 64 | 100 | 2048 | 0 | 500000 |
| SOLARHCS | HOURLY | 24 | 65 | 88 | 100 | 2816 | 0 | 500000 |
| SPARE | - | 2 | 89 | 90 | 1 | 2880 | 127 | 127 |
| Total number of bits = 32 x 90 = 2880 | ||||||||
| 16-bit words: | ||||||||
| Region # | - | 1 | 91 | 91 | 1 | 2896 | 1 | 10368 |
| Date: YYMM | - | 1 | 92 | 92 | 1 | 2912 | 8411 | to present |
| Spacecraft ID | - | 1 | 93 | 93 | 1 | 2928 | 1 | 7 |
![]() |
MONTHLY (DAY) | 1 | 94 | 94 | 10 | 2944 | 0 | 400 |
![]() |
MONTHLY (DAY) | 1 | 95 | 95 | 10 | 2960 | 0 | 800 |
| ALBEDO | MONTHLY (DAY) | 1 | 96 | 96 | 1000 | 2976 | 0 | 1 |
CS |
MONTHLY (DAY) | 1 | 97 | 97 | 10 | 2992 | 0 | 400 |
CS |
MONTHLY (DAY) | 1 | 98 | 98 | 10 | 3008 | 0 | 800 |
| ALBEDOCS | MONTHLY (DAY) | 1 | 99 | 99 | 1000 | 3024 | 0 | 1 |
![]() |
MONTHLY (HOUR) | 1 | 100 | 100 | 10 | 3040 | 0 | 400 |
![]() |
MONTHLY (HOUR) | 1 | 101 | 101 | 10 | 3056 | 0 | 800 |
| ALBEDO | MONTHLY (HOUR) | 1 | 102 | 102 | 1000 | 3072 | 0 | 1 |
CS |
MONTHLY (HOUR) | 1 | 103 | 103 | 10 | 3088 | 0 | 400 |
CS |
MONTHLY (HOUR) | 1 | 104 | 104 | 10 | 3104 | 0 | 800 |
| ALBEDOCS | MONTHLY (HOUR) | 1 | 105 | 105 | 1000 | 3120 | 0 | 1 |
![]() |
DAILY | 31 | 106 | 136 | 10 | 3616 | 0 | 400 |
![]() |
DAILY | 31 | 137 | 167 | 10 | 4112 | 0 | 800 |
| ALBEDO | DAILY | 31 | 168 | 198 | 1000 | 4608 | 0 | 1 |
CS |
DAILY | 31 | 199 | 229 | 10 | 5104 | 0 | 400 |
CS |
DAILY | 31 | 230 | 260 | 10 | 5600 | 0 | 800 |
| ALBEDOCS | DAILY | 31 | 261 | 291 | 1000 | 6096 | 0 | 1 |
![]() |
HOURLY | 24 | 292 | 315 | 10 | 6480 | 0 | 400 |
![]() |
HOURLY | 24 | 316 | 339 | 10 | 6864 | 0 | 1000 |
| ALBEDO | HOURLY | 24 | 340 | 363 | 1000 | 7248 | 0 | 1 |
CS |
HOURLY | 24 | 364 | 387 | 10 | 7632 | 0 | 400 |
CS |
HOURLY | 24 | 388 | 411 | 10 | 8016 | 0 | 1000 |
| ALBEDOCS | HOURLY | 24 | 412 | 435 | 1000 | 8400 | 0 | 1 |
| Total number of bits = 16 x (435 - 90) = 5520 | ||||||||
| 8-bit words: | ||||||||
| NDLW | DAILY | 31 | 436 | 466 | 1 | 8648 | 0 | 24 |
| NDSW | DAILY | 31 | 467 | 497 | 1 | 8896 | 0 | 24 |
| NDLWCS | DAILY | 31 | 498 | 528 | 1 | 9144 | 0 | 24 |
| NDSWCS | DAILY | 31 | 529 | 559 | 1 | 9392 | 0 | 24 |
| NHLW | HOURLY | 24 | 560 | 583 | 1 | 9584 | 0 | 31 |
| NHSW | HOURLY | 24 | 584 | 607 | 1 | 9776 | 0 | 31 |
| NHLWCS | HOURLY | 24 | 608 | 631 | 1 | 9968 | 0 | 31 |
| NHSWCS | HOURLY | 24 | 632 | 655 | 1 | 10160 | 0 | 31 |
| SPARES | - | 20 | 656 | 675 | 1 | 10320 | 127 | 127 |
| Total number of bits = 8 x (675 - 435) = 1920 | ||||||||
NOTE: CS at the end of an item name indicates that the item is for clear-sky conditions only.
The scanner scale factors file contains 10320 bits which are divided into 32-, 16-, and 8-bit words giving a total of 675 scale factors as shown in the Data Granularity Section. These quantities are used to scale the integer data quantities in each of the scanner data files (files 4 through 10 in Table 11) as follows:
ith Real Scanner Quantity = (ith Integer Scaled Quantity Rrom File) / (ith Scale Factor)
The third file contains the integer nonscanner scale factors written in the same order as their corresponding nonscanner data items as shown in Table 17.
| Item Name | Data Type | No. of Values per Region |
Starting Item No. |
Ending Item No. |
Scale Factor |
Cumulative No. Bits |
Minimum Value |
Maximum Value |
|---|---|---|---|---|---|---|---|---|
| 32-bit words: | ||||||||
| FILE ID | - | 1 | 1 | 1 | 1 | 32 | 8 | 23 |
| TSOLRD | MONTHLY (DAY) | 1 | 2 | 2 | 100 | 64 | 0 | 500000 |
![]() |
MONTHLY (DAY) | 1 | 3 | 3 | 100 | 96 | -200 | 200 |
![]() |
MONTHLY (HOUR) | 1 | 4 | 4 | 100 | 128 | -200 | 200 |
| TSOLRH | MONTHLY (HOUR) | 1 | 5 | 5 | 100 | 160 | 0 | 500000 |
| SOLARD | DAILY | 31 | 6 | 36 | 100 | 1152 | 0 | 500000 |
| SOLARH | HOURLY | 24 | 37 | 60 | 100 | 1920 | 0 | 500000 |
| Total number of bits = 32 x 60 = 1920 | ||||||||
| 16-bit words: | ||||||||
| Region # | - | 1 | 61 | 61 | 1 | 1936 | 1 | 2592 |
| Date: YYMM | - | 1 | 62 | 62 | 1 | 1952 | 8411 | to present |
| Spacecraft ID | - | 1 | 63 | 63 | 1 | 1968 | 1 | 7 |
![]() |
MONTHLY (DAY) | 1 | 64 | 64 | 10 | 1984 | 0 | 400 |
![]() |
MONTHLY (DAY) | 1 | 65 | 65 | 10 | 2000 | 0 | 800 |
| ALBEDO | MONTHLY (DAY) | 1 | 66 | 66 | 1000 | 2016 | 0 | 1 |
![]() |
MONTHLY (HOUR) | 1 | 67 | 67 | 10 | 2032 | 0 | 400 |
![]() |
MONTHLY (HOUR) | 1 | 68 | 68 | 10 | 2048 | 0 | 800 |
| ALBEDO | MONTHLY (HOUR) | 1 | 69 | 69 | 1000 | 2064 | 0 | 1 |
![]() |
DAILY | 31 | 70 | 100 | 10 | 2560 | 0 | 400 |
![]() |
DAILY | 31 | 101 | 131 | 10 | 3056 | 0 | 800 |
| ALBEDO | DAILY | 31 | 132 | 162 | 1000 | 3552 | 0 | 1 |
![]() |
HOURLY | 24 | 163 | 186 | 10 | 3936 | 0 | 400 |
![]() |
HOURLY | 24 | 187 | 210 | 10 | 4320 | 0 | 1000 |
| ALBEDO | HOURLY | 24 | 211 | 234 | 1000 | 4704 | 0 | 1 |
| GEOTYPE | - | 1 | 235 | 235 | 1000 | 4720 | 0 | 1 |
| SPARES | - | 5 | 236 | 240 | 1 | 4800 | 127 | 127 |
| Total number of bits = 16 x (240 - 60) = 2880 | ||||||||
| 8-bit words: | ||||||||
| NDLW | DAILY | 31 | 241 | 271 | 1 | 5048 | 0 | 24 |
| NDSW | DAILY | 31 | 272 | 302 | 1 | 5296 | 0 | 24 |
| NHLW | HOURLY | 24 | 303 | 326 | 1 | 5488 | 0 | 31 |
| NHSW | HOURLY | 24 | 327 | 350 | 1 | 5680 | 0 | 31 |
| DEAD-SCANNER FLAGS | - | 3 | 351 | 353 | 1 | 5704 | 0 | 32767 |
| SPARES | - | 7 | 354 | 360 | 1 | 5760 | 127 | 127 |
| Total number of bits = 8 x (360 - 240) = 960 | ||||||||
The nonscanner scale factors file contains 5760 bits which are divided into 32-, 16-, and 8-bit words giving a total of 360 scale factors as shown in the Data Granularity Section. These quantities are used to scale the corresponding integer data quantities in each of the nonscanner data files (files 11 through 26 in Table 17) as follows:
ith Real Nonscanner Quantity = (ith Integer Scaled Quantity From File) / (ith Scale Factor)
An output summary report is created when the S-4 product is produced. Because the output is created sequentially, it is impossible to store the header information such as the number of records in each file. If one of the five input files is missing, the corresponding output files will each contain a record of fill values (also known as default values) according to the byte size of the data within that one record, or they will contain a record of ones. Table 18 lists the fill values.
| Bits per Word | Fill Value |
|---|---|
| 32 | 2147483647 |
| 16 | 32767 |
| 8 | 127 |
To illustrate the file structure when one or more input files are missing, a printed summary for the output tape is shown in Figure 3 and Figure 4; "file empty" indicates a record of ones or fill values. When reading the S-4 output product, the processing date must be checked to see if the run date was before or after February 1992. Data processed before February 1992 will have these records filled with ones. Data processed after this date will have one record of fill values.
Also if some regions are missing from the input files, the output files may contain less than the maximum possible number of records.
There are a number of steps in the processing of the ERBE data (see Flowchart Figure). The mathematics involved in each of these steps is beyond the scope of this document. However, interested readers are referred to the following: NASA Reference Publication 1184, Angular radiation models for Earth-atmosphere system, Volume 1: Shortwave radiation, and Volume 2: Longwave radiation; NASA Technical Paper 2670, Calculation and accuracy of ERBE scanner measurement locations; and Smith (Reference 15).
The input to the standard S-4 product is provided by the Monthly Time/Space Averaging Subsystem, which accumulates data for each region into a 32x25 matrix (see Data Matrix Figure). There is a 31x24 submatrix within the larger matrix with each row representing one day of the month and each column representing a local hour for the region. The 25th column contains the daily averages for the month, referred to as the daily averages. The 32nd row contains the hourly averages for the month, referred to as the monthly hourly averages. The lower right-hand box contains the average of the daily averages, referred to as the monthly (day) average, and the average of the monthly hourly averages, referred to as the monthly (hour) average. The daily, monthly hourly, monthly (day), and monthly (hour) averages are calculated and stored in a regional average data base in the Monthly Time/Space Averaging Subsystem and passed to the S-4 Output Products Subsystem (Reference 5). These values are used to provide the nested, zonal, and global averages mentioned earlier.
Up to five separate types of data can be received from Monthly Time/ Space Averaging. One or more (up to four) of these types of data may be missing without upsetting the processing. The five different types of data are:
The Langley Research Center (LaRC) has the responsibility of processing and validating all science data from the ERBE mission and of distributing the resulting data products to the science community. The ERBE data processing system at LaRC uses a modular software subsystems approach to process the ERBE data, starting with the input telemetry and ephemeris data from Goddard Space Flight Center (GSFC) and NOAA and ending with the production of the required science data products.
The diagram in the Flowchart Figure shows the major steps in the science data processing, together with the primary input and output data products. The first step in this processing procedure is to ingest 24 hours of telemetry data from the ERBS, NOAA-9, or NOAA-10 spacecraft into the front-end processing subsystem of the Data Processing System. The processing at this step accounts for spacecraft differences and for differences in the data acquisition and handling systems of the ERBS and TIROS N satellites. The data are organized into a format that is common to data from GSFC and NOAA. Extensive data quality editing and evaluation are performed, including the checking of quality flags appended by the tracking networks and processing systems at GSFC and NOAA. The operational status of the instruments is determined, and all instrument housekeeping data and selected spacecraft housekeeping measurements are converted to engineering units and edited. Point vectors for the optical axes of the detectors are calculated in a local horizon coordinate system at the spacecraft.
The 8-day ephemeris data sets are processed and validated separately before combining them with the corresponding telemetry data. Orbital data are tested for consistency with data from the previous week, and tests are performed to verify the consistency of the orbit calculations between 1-minute data points. The tests include checks for in-plane and out-of-plane consistency and precision. The routine verification processing and other analyses performed to verify the accuracy of the ephemeris data have generally demonstrated accurate orbit determination for both the ERBS and NOAA spacecraft.
The next major processing stage begins with the merging of the output data from telemetry processing with data output from the ephemeris processing. The FOV locations on a surface at the TOAare determined for every radiometric measurement. The FOV locations are more critical for the scanner measurements than those of the nonscanner because of the small FOV of the scanner instrument. A FOV accuracy analysis has shown that the calculated locations of the scanner measurements are well within the FOV footprint of the instrument on the Earth.
At this processing stage, the raw measurements for each radiometric detector are also converted to incident radiances at the spacecraft. The conversion algorithms employ calibration coefficients that are based primarily on ground-based calibration data, but which are updated with results from in-flight calibrations.
In the inversion processing stage, data from the scanner detectors are used to identify the type of scene or source at the TOA that produced the raw radiometric measurements. Based on the scene type and geographical location, the scanner measurements are adjusted to account for changes in the spectral response in each detector. Using the selected scene-type, one of several angular directional models is selected for inverting or reducing the measurements from satellite altitude to radiant fluxes at the TOA. The nonscanner measurements are inverted using scene information determined during scanner data processing and two different inversion algorithms. One algorithm employs geometric shape factors and the other employs numerical filtering.
The time-ordered estimates of TOA fluxes are sorted into spatial sequences for both the scanner and nonscanner measurements, grouping all estimates for a month together on a regional basis. A full calendar month of estimates is then retrieved for each region of the Earth. Hourly, daily, and monthly estimates of several different parameters are derived by interpolation using directional models that describe the temporal variation of the radiation budget components. Archival products of monthly averages of radiation components for both the scanner and nonscanner are produced at this point.
Several archival products are produced at the final stage of data processing. The nested averages product gives values of the scanner and nonscanner fluxes from each instrument averaged over various spatial scales. The processing at this stage also combines data from all available spacecraft to produce a combined-satellite product of TOA fluxes averaged over the same spatial scales. An archival product for solar monitor measurements is also produced to provide time histories of solar calibration data. Finally, a scene validation product is produced that combines ERBE data with measurements from the AVHRR and the HIRS instruments. Data from these two NOAA instruments are used to validate the scene identification algorithm. Currently all archival data products are distributed first to the ERBE Science Team for review and validation and then to LaRC ASDC for archival.
Processing changes are described in the Special Corrections/Adjustments Section below.
Several modifications have been made to Monthly Time/Space Averaging Algorithms which affected the S-4 product in the following areas:
Monthly shortwave averages are calculated using the monthly mean albedo and the sum of the integrated daily solar incidence of all days (N) of the month:
(6)
(
and S(d) are defined in Reference 2)
An alternate definition of monthly average values may be expressed in terms of monthly hourly averages. In this case, calculate the average for each of the 24 local hours using only the days with measurements and then take the mean of the local hour averages. The calculation of the monthly hourly average albedo and SWF are the same as Equation 12 (Reference 2) and Equation 6 respectively, whether one first sums through the days or the hours of the month. Obviously, shortwave interpolation cannot take place on a given day if there are no shortwave measurements for that day.
In general,
is not equal to
as defined by Equation 18 (Reference 2) and Equation 13
(Reference 2) respectively, differing by the usage of the longwave interpolated
values on days for which there were no longwave measurements. This difference
can be significant if several days of measurements are missing. If there are no
shortwave measurements for a given month and the monthly total integrated solar
incidence is greater than zero, the solar and net parameters of these regions
are not used in the global averages. Some of these regions lie on the latitude
belt where the solar terminator occurs with the seasonal movement of the solar
declination. Naturally, if the monthly total integrated solar incidence equals
zero, the shortwave portion of Equation 18 (Reference 2)
and Equation 13 (Reference 2) is zero. The sampling problems outlined in this
paragraph will ultimately have to be dealt with outside the context of ERBE
operational software.
The shortwave parameters of the monthly clear-sky averages are the same as the monthly averages, except that clear-sky measurements are used. The same holds true for the longwave parameters for ocean, snow, and coast geotypes. Over land and desert geotypes, however, the lack of clear-sky longwave measurements on a daily basis or even on a monthly time-scale as in tropical convective regions, discourage any type of daily modeling. Therefore, a half-sine model is best applied after the clear-sky longwave measurements have been sorted by local hour. This will better account for the clear-sky diurnal variation, assuming that the clear-sky longwave diurnal range exceeds the day-to-day fluctuations for a given local hour. This way, the bias toward either daytime or night time clear-sky measurements have been reduced. First, the monthly hourly LWF MLW(h) as defined by Equation 16 (Reference 2) is calculated, but only clear-sky longwave measurements are used. The same conditions as defined by the LW half-sine model section apply, except that the least squares fit is weighted by the number of measurements for the local hour, and the night time average is the mean of all night time clear-sky longwave measurements. This method is used for both the monthly daily and monthly hourly clear-sky longwave averages for land and desert regions.
An additional change was made to the clear-sky averaging algorithm that corrects