Please enable JavaScript.

Coggle requires JavaScript to display documents.

Existing Data Search and Access Terminology, Note: CMR's Documentation…

- - - - Original data from an instrument. If compression, reformatting, packetization, or other translation has been applied to facilitate data transmission or storage, those processes will be reversed so that the archived data are in a PDS-approved archive format.
    - - Data converted to physical units, which makes values independent of the instrument.
    - - Data converted to physical units, which makes values independent of the instrument.
    - - Results that have been distilled from one or more calibrated data products (for example, maps, gravity or magnetic fields, or ring particle size distributions). Supplementary data used to interpret observational data, such as calibration tables or tables of viewing geometry, should also be classified as derived data if not easily matched to one of the other categories.
  - - - Reconstructed, unprocessed instrument and payload data at full resolution, with any and all communications artifacts (e.g., synchronization frames, communications headers, duplicate data) removed. (In most cases, the EOS Data and Operations System (EDOS) provides these data to the data centers as production data sets for processing by the Science Data Processing Segment (SDPS) or by a SIPS to produce higher-level products.)
    - - Reconstructed, unprocessed instrument data at full resolution, time-referenced, and annotated with ancillary information, including radiometric and geometric calibration coefficients and georeferencing parameters (e.g., platform ephemeris) computed and appended but not applied to Level 0 data.
    - - Level 1A data that have been processed to sensor units (not all instruments have Level 1B source data).
    - - Derived geophysical variables at the same resolution and location as Level 1 source data.
    - - Variables mapped on uniform space-time grid scales, usually with some completeness and consistency.
    - - Model output or results from analyses of lower-level data (e.g., variables derived from multiple measurements).
  - - - Engineering
      - Level 0
      - Level 2
      - Level 1
- - - - HeadlessService
        Services which are intended to be primarily exercised through an HTTPS bested API. In the EOSDIS, a user may interact with the service through either a rich client user interface, such as IDV or panoply or via a user-specific script. An example is the OGC Web Map Service, which can be consumed by a number of tools, including IDV, ArcGIS, qgis, and Google Earth.
      - FullStackService
        Services that provide interaction with the data through both a rich web front end and an HTTPS API. The AppEEARS tool provides an example of this class.
    - - WebTools
        Rich web interfaces providing interaction with the data, but lacking a robust, well-advertised API. AN example of this class is the State of the Ocean tool.
      - LocalTools
        Tools which must be downloaded to the user’s processing platform in order to use them. examples of these include local GUI tools like Panoply and command line tools such as NCO.