From Sensor to Archive: Observational Data Services at NCARs Earth - - PowerPoint PPT Presentation

from sensor to archive observational data services at
SMART_READER_LITE
LIVE PREVIEW

From Sensor to Archive: Observational Data Services at NCARs Earth - - PowerPoint PPT Presentation

From Sensor to Archive: Observational Data Services at NCARs Earth Observing Laboratory Mike Daniels Computing, Data and Software Facility NCAR/Earth Observing Laboratory NSF Aircraft operated by EOL G-V over the Colorado Rockies C-130


slide-1
SLIDE 1

From Sensor to Archive: Observational Data Services at NCAR’s Earth Observing Laboratory

Mike Daniels Computing, Data and Software Facility NCAR/Earth Observing Laboratory

slide-2
SLIDE 2

NSF Aircraft operated by EOL

C-130 near Kiribati (Christmas Island) G-V over the Colorado Rockies

www.eol.ucar.edu

slide-3
SLIDE 3

NSF Radars and Lidars operated by EOL

ELDORA airborne radar in Guam S-PolKa radar in the Maldive Islands

www.eol.ucar.edu

slide-4
SLIDE 4

NSF Surface Instrumentation, Profilers and Sondes operated by EOL

Tower setup in Owens Valley, California Wind profiler in Miami (mobile and fixed) Upsondes (mobile and fixed) Dropsondes (from various airborne platforms)

www.eol.ucar.edu

slide-5
SLIDE 5

Other supplementary field project data (domestic and foreign)

Radar networks Mesonets Model Output Satellite Data

www.eol.ucar.edu

slide-6
SLIDE 6

A Timeline for CDS Field Project Responsibilities

Year

  • 1

Year +1

Field Ops and Data Collection

Finalize Data Management Plan

Year Year +2 (and beyond)

Local and/or Remote Monitoring and Support Instrumentation Upload and Testing Software Development for New Instrument Interfaces, Displays

  • r Upgrades

Systems Shakedown, Field Network Installed Site Survey

Final Data Staged Integrated Data Staged Preliminary Data Staged QC’d data from PIs Ops Planning Meeting On-line Field Catalog Operational Draft DM Plan Final Specs from PIs and Planning Meeting Data Questionnaire Finalize Operations Plan Complete Operations Summary (WWW) Operational Data Staged to EMDAC data management system Data Analysis Workshop

www.eol.ucar.edu

slide-7
SLIDE 7

Expanding the Internet to New and Unusual Places

Aircraft Kiribati (aka Christmas Island) Balloons

www.eol.ucar.edu

slide-8
SLIDE 8

NSF Platform Data Accessed in Real-time, and Ingested into Models Integrated Displays, Troubleshooting and Mission Coordination

The New EOL Data System

QC/QA Processing, Special Products, Revision Tracking and Archiving

Through comprehensive data services, our mission is to improve the quality and preservation of data files and datasets and maintain the integrity of the associated metadata, software and infrastructure.

More Eyes on Data

CatB: “Given enough eyeballs, all bugs are shallow.”

Stewardship of Data Services

www.eol.ucar.edu

slide-9
SLIDE 9

www.eol.ucar.edu

Data Citation and Persistent Locator Issues

slide-10
SLIDE 10

www.eol.ucar.edu

Difficulty in Tracking Publications

  • Process: manually search Web of Science and other
  • nline citation indexes for text such as “C-130”, “S-Pol”,

“INDOEX”, etc.

  • Very labor intensive
  • In 2007, this took approximately 4 months of work

Updated metrics 1997 to 2007

1997 2000 2005

It’s important to show the results of and types of research accomplished with

  • ur facilities and data
slide-11
SLIDE 11

DOI as a service? The Field Catalog: NSF’s Internet Hub for Field Projects

Model and Forecast Products Mission Summaries and Status Reports Research Products Operational Products …with links to Google Earth visualizations, data files, chat, forums, etc.

www.eol.ucar.edu

slide-12
SLIDE 12

DOIs for Software? EOL’s Diverse Platform Support

Data acquisition software, real-time displays, analysis software, communications (satcom/WAN) and QC tools for data EOL manages

Engineered software and data systems that are at the heart of state-of-the-art observing systems

  • S-Pol Radar
  • Integrated Sounding

System

  • G-V
  • C-130
  • Scanning Atmospheric

Backscatter Lidar

  • Electra Doppler Radar
  • Python Environment for

Radar Processing

  • Reorder and translators
  • Raman-Shifted Eyesafe

Atmospheric Lidar

  • Scientific Data Processing
  • CP-2 signal processor
  • NIDAS
  • Aeros
  • FORAY
  • AVAPS
  • Integrated Surface Flux

System

  • NIMBUS
  • Multiple Antenna Profiling

Radar

  • Solo Radar Editor
  • Driftsonde
  • Ncplot,ncpp,xpms2d
  • Rapid Dow
  • Zebra
  • NEXRAD
  • Ka Band Radar
  • TDLS
  • GAUS
  • Field-Programmable Gate

Arrays Diverse Software Engineering:

slide-13
SLIDE 13

DOIs for Data: CDS Data Management

FTP Web Field Catalog Email Snail Mail Ingest Streams QA/QC Processing and Tracking

“value-added” Composites and Format Conversions

Various Dataset Sources Archive and Distribution Media

slide-14
SLIDE 14
  • Surface Heat Budget of the Arctic Ocean

(SHEBA)

  • Western Arctic Shelf-Basin Interactions

(SBI)

  • Arctic System Science (ARCSS)
  • Arctic Transitions in the Land-Atmosphere

System (ATLAS)

  • International Tundra Experiment (ITEX)
  • Cooperative Arctic Data Information

System (CADIS, A-CADIS)

  • Bering Sea Projects
  • Bering Sea Integrated Ecosystem

Research Program (BSIERP)

  • Bering Sea Ecosystem Study (BEST)

DOIs for data acquired from non-EOL sources: e.g. supported arctic projects

We also support hydrology, oceanography and atmospheric chemistry data via outside funding

slide-15
SLIDE 15

What granularity for EOL DOIs and when are they issued?

  • Given a large project with aircraft, soundings, radars, model
  • utput and satellite data do we:

– Assign a DOI for each data file? – Assign one DOI for all datasets for the project? – Assign separate DOIs for datasets from each major platform? – What about ancillary data? Do we assign DOIs or does the providing institution?

  • We are thinking to assign DOIs for each major platform data

associated with the project (e.g. C-130, S-Pol), outside datasets that we have “value-added”, and data for which no DOI exists

  • It may be beneficial to only issue DOIs when processed data

are released so as to prevent pubs from referencing preliminary data

slide-16
SLIDE 16

www.eol.ucar.edu

What text (esp authors and contributors) do we use for data citations?

  • Main Project PIs have spent years in forming this

research project (authors)

  • Others spend much time acquiring data in the field

project phase (contributors, maybe list EOL itself?)

  • Our group (CDS) will be responsible for maintaining the

integrity of the DOI itself (publisher)

  • It might be beneficial for data quality and distribution

experts to be listed so they can be consulted for dataset questions (contributors)

  • This decision is expected to require Lab Management

approval

slide-17
SLIDE 17
  • Data and Metadata Rescue
  • Collect and Digitize Project

Documentation

  • Digitize items such as Aircraft Videos
  • Media and Format Migration

(e.g. GENPro to NetCDF)

  • NCAR Iron Mountain Archives
  • Sounding Legacy Project (w/CSU)
  • T-28 Aircraft Facility Archive
  • Long-term Archive

(e.g. MSS to HPSS transition)

How far back do we go? EOL Legacy Data Projects

slide-18
SLIDE 18

Mike Daniels, EOL/CDS daniels@ucar.edu NCAREOL

Thank you!

www.eol.ucar.edu