NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Arliss,
As usual, your questions get right to the heart of the matter. I'll start with
my own quick response, with the caveat that other GALEON participants will have
perhaps different views (especially on the priorities) and more detailed input
as we progress.
My responses:
1) Which type(s) of ISO 19123 coverage is this?
Gridded Data
Unstructured DiscretePointCoverage
Structured DiscreteGridPointCoverage
Swath DiscreteSurfaceCoverage
Point Observation Data
Unconnected DiscretePointCoverage
Station observation /Timeseries DiscretePointCoverage
Trajectory
General DiscretePointCoverage or
DiscreteCurveCoverage
Profile DiscretePointCoverage
Radial DiscreteSurfaceCoverage or
DiscreteCurveCoverage
2) What domain dimensions are needed?
One of the main points of the aviation-related local forecast use case is to emphasize the need for
full 3D plus model-run-time and valid-forecast-time. There is also a need for "time relative
to the present" e.g. the latest forecast or observations during the last two hours.
Moreover, in the research community, there will be a demand for access to the "raw" data
which, in many cases, includes an elevation dimension which is non-spatial, e.g., pressure in the
atmosphere or density in the ocean. Perhaps this last topic belongs in the response to the next
question relating to axes.
3) What range data structures are needed (called fields and axes in WCS 1.1)?
I may have covered some of the needs for special "axes" in item 2) above. But, in general, this is going to require more research on my part. If I understand it correctly, the actual data structures for the fields will be different for different data categories and, in some cases, will be different for different fields within a dataset. This is the area where most of the work is needed in order to come up with "application profiles."
4) What are the relative priorities among these types of data? Below are Ben's priorities expressed in terms of the order in which Unidata will be working on them (But please NOTE WELL that others will have other priorities, e.g., the coastal ocean modelling community will be working on irregular grids first whereas hydrology folks will probably be most interested in station obs and radar) 1. Structured Grids (the main focus of GALEON 1 and the CF conventions for netCDF) 2. Station Observations (Currently working on netCDF conventions for Observational datasets) 3. Vertical Profiles (e.g. wind profiler data, balloon or moored buoy CTD soundings) 4. Point Data (e.g. lightning strike data) 5. Radar Radial (e.g., NEXRAD level 2 volume scans) Perhaps some of this would be useful for discussion during the GALEON session at Wednesday's WCS.SWG telecon. -- Ben On Feb 18, 2008 8:39 AM, Whiteside, Arliss E (US SSA) < arliss.whiteside@xxxxxxxxxxxxxx> wrote:
Ben, Thanks for writing this good start. I for one would like some more detailed information about the listed types of data: 1) Which type(s) of ISO 19123 coverage is this? 2) What domain dimensions are needed? 3) What range data structures are needed (called fields and axes in WCS 1.1)? 4) What are the relative priorities among these types of data? Arliss
galeon archives: