Difference between revisions of "Streaming and or netCDF File"
From Earth Science Information Partners (ESIP)
Line 1: | Line 1: | ||
<noinclude>{{AQ CoP Solta2011 Backlinks}} | <noinclude>{{AQ CoP Solta2011 Backlinks}} | ||
− | This page is for summarizing the discussion on the topic of streaming vs file transfer. Se also the discussion for this page. | + | This page is for summarizing the discussion on the topic of streaming vs file transfer. Se also the extensive [[http://wiki.esipfed.org/index.php/Talk:Streaming_and/or_netCDF_File | discussion]] for this page. |
=== Data Streaming ...=== | === Data Streaming ...=== |
Revision as of 04:34, July 16, 2011
< Back to | Workshops | Air Quality Data Network
This page is for summarizing the discussion on the topic of streaming vs file transfer. Se also the extensive [| discussion] for this page.
Data Streaming ...
- streaming,
Streaming netCDF
Russ Rew of Unidata points out that
CF-netCDF and WCS 1.1 for data exploration and analysis
CF-netCDF is a strongly typed data structure for multidimensional data cubes
- netCDF gives the storage and data access facility;
- CF gives it the semantic clarity and specificity.
WCS 1.1 data access protocol uses a simple parameter-space-time data query language
- give me the data for specific Obs parameter, 3D Bounding box, time range.
- The return payload is a slice or dice (sub-cube) subset of the original data along well defined dimensional axes and boundaries.
CF-netCDF data model and WCS 1.1 data access protocol are structurally compatibe
- Observations/Models variables >> map to CF-netCDF ???
- WCS 1.1 Coverage >>> maps to >>> Dataset, i.e. a set of homogeneous observations that share space/time dimensions. It may be a specific model, obs network etc.
- WCS 1.1 Field >>> maps to >>> Observation or model Parameter, i.e. AOT, ColumnNO2, SurfaceSo4