A facility not funded by NASA that processes, archives, and distributes Earth science data useful for Global Change research with which a working agreement has been negotiated by the EOS program.
The agreement provides for the establishment of the degree of connectivity and interoperability between EOSDIS and the ADC needed consistent and compatible with EOSDIS services. Such data-related services to be provided to EOSDIS by the ADC can vary considerably for each specific case.

Software delivered to the SDPS by a science investigator (PI, TL, or II) to be used as the primary tool in the generation of science products. The term includes executable code, source code, jog control scripts, as well as documentation.

Data other than instrument data required to perform an instrument's data processing.
They include orbit data, attitude data, time information, spacecraft or platform engineering data, calibration data, data quality information, and data form other instruments.

Data that represent spacecraft orientation and onboard pointing information. Attitude data includes:

Attitude sensor data used to determine the pointing of the spacecraft axes, calibration and alignment data, Euler angles or quatermions, rates and biases, and associated parameters. Attitude generated on board i quaternion or Euler angles form. Refined and routine production data related to the accuracy or knowledge of the attitude.

Subsets of a larger data set, other than the directory and guide, generated for the purpose of allowing rapid interrogation (i.e.,browse) of the larger data set by a potential user. For example, the browse product for an image data set with multiple spectral bands and moderate spatial revolution might be and image in two spectral channels, at a degraded spatial resolution. The form of browse data is generally unique for each type of data set and depends on the nature of the data and the criteria used for data selection within the relevant scientific disciplines.

The collection of data required to perform calibration of the instrument science data, instrument engineering data. and the spacecraft of platform engineering data. It includes pre-flight calibration measurements, in-flight calibrator measurements, calibration equation coefficients derived from calibration software routines, and ground truth data that are to be used in the data calibration processing routine.

Refers to the capability of the user interface soft ware of one data set directory or catalog to interact with the user interface at another data set directory or catalog. Three levels of Catalog Interoperability are recognized:

Level 1 Interoperability Simple network interconnectivity among systems.
Level 2 Interoperability catalog systems can exchange limited search and user information .
Level 3 Interoperability catalog systems exchange standard search protocols. This provides "virtual" similarity between different systems

Data sets generated by EDOS using raw instrument or spacecraft packets with space-to-ground transmission artifacts removed, in time order, with duplicate data removed, and with quality/accounting (Q/A) metadata appended. Time span, number of packets, or number of orbits encompassed in a single data set are specified by the recipient of the data. These data sets are equivalent to level zero data formatted with Q/A metadata. For EOS, the data sets are composed of :

- instrument science packets,
- instrument engineering packets,
- observatory housekeeping packets, or
- onboard ancillary packets

with quality and accounting information form each individual packet and the data set itself and with essential formatting information for unambiguous identification and subsequent processing.

Data sets generated by EDOS using raw instrument or spacecraft packets from a single TDRSS acquisition session and delivered to a user within minutes of receipt of the last packet in the session.
Transmission artifacts are removed, but time ordering and duplicat packet removal is limited to packets received during the TDRS contact period.

The platform Command and Data Handling subsystem which conveys commands to the platform and research instruments, collects and formats observatory data, generates time and frequency references for subsystems and instruments, and collects and distributes ancillary data.

A logical set of one more commands which are not stored onboard the observatory for delayed execution, but are executed immediately upon reaching their destination on board. For the U.S. platforms, from the perspective of the EOC, a preplanned command group is preprocessed by, and stored at, the EOC in preparation for later uplink. A real-time command group is unplanned in the sense that it is not preprocessed and stored by the EOC.

"Commercial off-the -shelf" means a product, such as an item, material, software, component, subsystem, or system, sold or traded to the general public in the course of normal business operations at prices based on established catalog or market prices.

Two modes of scheduling. Comprehensive scheduling is the automatic scheduling of a full set of events. Incremental scheduling is interactive scheduling of selected events.
For example, the initial generation of a schedule might user comprehensive scheduling, while the addition of a single event with the desire to avoid perturbing previously scheduled events might user incremental scheduling.

The schedule for and observatory which covers a 7-day period and is generated/updated daily based on the Instrument Activity Specifications for each of the instruments on the respective spacecraft. For an observatory schedule the platform subsystem activity specifications needed for routine platform maintenance and/or for supporting instruments activities are incorporated in the CFS.

Commands and tables which are stored in the memory of the central onboard computer on the platform. The execution of these commands or the result of loading these operational tables occurs sometime following their storage. The term "core-stoed" applies only to the location where the items are sored on the observatory; core-stored commands or tables could be associated with the platform or any of the instruments

Scientific data from other sources used in the interpretation or validation of instrument data products, e.g., ground truth data and/or data products of other instruments. These data are not utilized for processing instrument data.

A request for future data acquisition by and instrument(s) that the user constructs and submits through the IMS. A facility storing, maintaining, and making available data sets for expected use in ongoing and /or future activities. Data centers provide selection and replication of data and needed documentation and, often, the generation of user tailored data products.

Data levels 1 through 4 as defined in the EOS Data Panel Report. Consistent with the CODMAC and ESADS definitions.
Raw Data-Data in their original packets, as received from the observatory, unprocessed by EDOS.

Level 0 :

Raw instrument data at original resolution, time ordered, with duplicate packets removed.

Level 1A :

Level 0 data, which may have been reformatted of transformed reversibly, located to a coordinate system, and packaged with needed ancillary and engineering data.

Level 1B :

Radiometrically corrected and calibrated data in physical units at full instrument resolution as acquired.

Level 2 :

Retrieved environmental variables (e.g., ocean wave height, soil moisture, ice concentration) at the same location and similar resolution as the Level 1 source data.

Level 3 :

Data or retrieved environmental variables that have been spatially and/or temporally resampled (i.e., derived from Level 1 or Level 2 data products). Such resampling may include averaging and compositing.

Level 4 :

Model output and/or variables derived from lower level data which are not directly measured by the instruments. For example, new variables based upon a time series of Level 2 or Level 3 data.

A logically meaningful grouping or collection of similar or related data.

Information describing the characteristics of a data set and its component granules, including format, source instrumentation, calibration, processing, algorithms, etc.

Continuous down-link transmission of selected real-time data over a broad are (non-specific users).

A collection of uniform descriptions that summarize the contents of a large number of data sets. It provides information suitable for making an initial determination of the existence and contents of each data set. Each directory entry contains brief data set information (e.g., type of data, data set name, time and location bounds).

An EOSDIS facility which generates, archives and distributes EOS Standard Products and related information for the duration of the EOS mission. An EOSDIS DAAC is managed by an institution such as a NASA field center or a university, per agreement with NASA. Each DAAC contains functional elements for processing data (the PGS), for archiving and disseminating data (the DADS), and for user services and information management (elements of the IMS).

A high-level group of international scientists which establishes and coordinates the EOS science program policy within the framework of international polar platformactivity.
All data available on-board about health, safety, environment, or status of the platform and instruments.
Platform Engineering Data : The subset of engineering data from platform sensor measurements and on-board computations.
Instrument Engineering Data : All non-science data provided by the instrument.
Housekeeping Data : The subset of engineering data required for mission and science operations.
These include health and safety, ephemeris, and other required environmental parameters.

See Orbit Data

An instrument defined by NASA as having broad significance to the EOS Program and provided by a designated NASA center or foreign agency.

The smallest aggregation of data that is independently managed (i,e., described, inventoried, retrievable). Granules may be managed as logical granules and/or physical granules.

Geophysical parameter data, measured or collected by other means than by the instrument itself, used as correlative or calibration data for that instrument data. includes data taken on the ground or in the atmosphere. Ground truth data are another measurement of the phenomenon of interest; they are not necessarily more "true" or more accurate than the instrument data.

See Engineering Data

Command issued to an instrument or subsystem that is transmitted with minimum delay for immediate execution. Delay would be due only to non-availability of uplink and/or the actual time to transmit the command.

See Comprehensive and Incremental Scheduling

See Ground Truth

Facilities established by an institution that take on some responsibility in support of EOSDIS, or elements of the EOSDIS that function as part of an institution, and represent both EOSDIS and the programs, goals and purpose of the institution.

Data specifically associated with the instrument, either because they were generated by the instrument or included I data packets identified with that instrument. These data consist of instrument science and engineering data, and possible ancillary data.

See Engineering Data

See Engineering Data

Storage of data into the contents of the memory of an insturment's microprocessor, if applicable, These loads could include micro-processor-stored tables, microprocessor-stored commands, or updates to microprocessor software.

Data produced by the science sensor(s) of an instrument, usually constituting the mission of that instrument.

Project-provided facilities at interdisciplinary investigator locations used to pursue EOS-approved investigations and produce higher- level data sets.

A group made up of the Principal Investigators and research instrument Team Leaders associated with the instruments on a single platform. The IWG defines the specific observing programs and data collection priorities for a single platform based on the guidelines from the IIWG.

The plan generated by the instrument representative to the platform's IWG with instrument-specific information to complement the LTSP. The Project Scientist provides the LTIPs for each instrument to the ECS. LTIPs are distributed through the ECS SMC to the EOC and ICCs. It is generated or updated approximately ever six months and covers a period of up to approximately 5 years.

The plan generated by the platform's IWG containing guidelines, policy, and priorities for its observatory. The Project Scientist provides the LTSP to the ECS ; the LTSP is distributed through the ECS SMC to the EOC and ICCs. The LTSP is generated or updated approximately every six months and covers a period of up to approximately 5 years.

Information about data sets which is provided to the ECS by the data supplier or the generating algorithm and which provides a description of the content, format, and utility of the data set. Metadata may be used to select data for a particular scientific investigation.

Integrated EOS flight element, consisting of the platform and the instruments.

Access to information by mail. telephone, facsimile, or other non-direct interface.

Access to information by direct interface to an information data base via electronic networking.

Data created by an operational instrument (i.e., NOAA AMRIR). Data that represent spacecraft locations. Orbit (or ephemeris) data include: Geodetic latitude, longitude and height above an adopted reference ellipsoid (or distance from the center of mass of the Earth); a corresponding statement about the accuracy of the position and the corresponding time of the position (including the time system); some accuracy requirements may be hundreds of meters while other may be a few centimeters.

Complement of instruments for a mission on a spacecraft or platform. The EOS spacecraft and its subsystems without the instruments.

The system responsible for EOS observatory flight software maintenance and flight element simulation. The PTTS houses the EOS command and data handling flight subsystem simulator and the Mission and Simulation Software. These are used for testing flight software loads and data bases, verifying command sequences, supporting training of EOS observatory operators, supporting anomaly resolution activities, and supporting ground system testing.

Data that have been stored on-board the platform for delayed transmission to the ground.

See Command Group

A command issued to an instrument or subsystem to be executed at some later time. These commands will be collected and forwarded during and available uplink prior to execution.

An individual who is contracted to conduct a specific scientific investigation. (An Instrument PI is the person designated by the EOS program as ultimately responsible for the delivery and performance of Standard Products derived from an EOS Instrument Investigation.)

Project-provided facilities at Pi locations used to develop and maintain algorithms, produce data sets, and validate data.

An instrument selected pursuant to the EOS Announcement of Opportunity and provided by a PI and his home institution. Data product generated as part of a research investigation, of wide research utility, requiring too much data or computer power for generation at the investigator SCF, and accepted as candidate Standard Product by the IWG. Prototype Products will be generated at DAACs, but their routine generation is no guaranteed and will not interfere with other Standard Product generation.

See Command Group

Data that are acquired and transmitted immediately to the ground (as opposed to playback data). Delay is limited to the actual time required to transmit the data.

Data products which are considered part of a research investigation and are produced for a limited region or time period, or data products which are not accepted as standard products.

(1) Data products generated as part of a research investigation, of wide research utility, accepted by the IWG and the EOS Program Office, routinely produced, and in general spatially and/or temporally extensive. Standard Level 1 products will be generated for all EOS instruments; standard Level 2 products will be generated for most EOS instruments.

(2) All data products which have been accepted for production at a PGS, including (1) above as well as prototype products.

Project-provided facilities at research instrument team member locations used to develop and test algorithms and assess data quality.