Skip to content

Dictionary_Ingested

Tad Slawecki edited this page Dec 19, 2018 · 6 revisions

Data Dictionary: Ingested Data

Ingested data are datasets in the GLOS DMAC that are processed and stored indefinitely for user access. There are three types of ingested GLOS DMAC data:

Sensors

Near-realtime sensors are deployed by a number of different parties throughout the Great Lakes. Observations are pushed by the data owners to GLOS via FTP. The observations are processed by the GLOS DMAC and stored in several formats:

  • OBS DB PostgreSQL database (LOCATION)

  • 52N SOS PostgreSQL database

  • Buoy NetCDF aggregations (LOCATIONS w, w/o QARTOD)

  • HABs netCDF aggregation (subset of sensors laid out in alternate netCDF format/directory structure) (LOCATION)

Models

NOAA-GLERL uses GLOS to provide access to results from its experimental model nowcasts and forecasts. GLERL sends updated 24-hour nowcasts every six hours and 120-hour forecasts every twelve hours to GLOS in netCDF format via FTP. GLERL also sends 50-day roll-ups that aggregate the past 50 days of nowcast and forecast model results into a single file, and provides an annual roll-up at the end of the year. GLERL runs both 2-D and 3-D models for each of the Great Lakes, and also provides selected forcing functions:

  • 2-D model parameters (LOCATION AND NAMING SCHEME)

    • parameter 1
    • parameter 2
  • 3-D model parameters (LOCATION AND NAMING SCHEME)

  • Forcing functions (LOCATION AND NAMING SCHEME)

Satellite

Michigan Tech Research Institute processes satellite imagery to produce cloud-free images of individual Great Lakes showing various derived products. The images are transmitted to GLOS by FTP.

  • Natural color (LOCATION AND NAMING SCHEME)
  • Others
Clone this wiki locally