This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
I have updated our service CF-1.5, CF:featureType = "point" http://webapps.datafed.net/ogc_EPA.wsfl?SERVICE=WCS&REQUEST=GetCoverage&VERSION=1.0.0&CRS=EPSG:4326&COVERAGE=AIRNOW.pmfine&TIME=2008-12-19T15:00:00&BBOX=-130,24,-65,52,0,0&WIDTH=-1&HEIGHT=-1&DEPTH=-1&FORMAT=NetCDF-tableCF-1.5, CF:featureType = "stationTimeSeries", 5.8.2.1 Multidimensional representation
http://webapps.datafed.net/ogc_EPA.wsfl?SERVICE=WCS&REQUEST=GetCoverage&VERSION=1.0.0&CRS=EPSG:4326&COVERAGE=AIRNOW.pmfine&TIME=2008-12-19T15:00:00&BBOX=-130,24,-65,52,0,0&WIDTH=-1&HEIGHT=-1&DEPTH=-1&FORMAT=NetCDF-sts In the website, "point" was spelled with lowercase, so I used it.The format names in query, NetCDF-table and NetCDF-sts I have just made up, WCS spec should standardize them.
Kari John Caron wrote:
Hi Rudy: This is the proposed conventions that we will use: http://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions Its not official yet, so things may change in it. We do not yet have any WCS services that use this, but we are working on this now. The file i downloaded from your service would satisfy this convention with the following changes to the global attributes::Conventions = "CF-1.5"; (it may be in 1.5 or later, have to wait and see):CF\:featureType = "Point"; (was CF\:pointFeature) as i said, this convention has not yet been adopted, so there may be some adjustments for the final version. very cool service, thanks for the info. Rudolf Husar wrote:Hi John, You may recall that couple of years ago we adopted a semi-standard implementation of the WCS for point data and used internally for our datasets in DataFed. This would be a good time to revisit and compare/reconcile with your approach. Here are links to a typical point dataset. AQS_d daily point monitoring dataset viewed in DataFed browser http://webapps.datafed.net/datafed.aspx?dataset_abbr=AQS_D WCS Access Front Page http://webapps.datafed.net/wcs_query.aspx?dataset_abbr=AQS_D&view_id=map¶m_abbr=pm25&datetime=2007-05-27T00:00:00&lat_min=24&lat_max=52&lon_min=-130&lon_max=-65 <http://webapps.datafed.net/wcs_query.aspx?dataset_abbr=AQS_D&view_id=map¶m_abbr=pm25&datetime=2007-05-27T00:00:00&lat_min=24&lat_max=52&lon_min=-130&lon_max=-65> WCS GetCoverage that returns a netCDF-table http://webapps.datafed.net/ogc_EPA.wsfl?SERVICE=WCS&REQUEST=GetCoverage&VERSION=1.0.0&CRS=EPSG:4326&COVERAGE=AQS_D.pm25&TIME=2007-05-27T00:00:00&BBOX=-130,24,-65,52,0,0&WIDTH=-1&HEIGHT=-1&DEPTH=-1&FORMAT=NetCDF-table <http://webapps.datafed.net/ogc_EPA.wsfl?SERVICE=WCS&REQUEST=GetCoverage&VERSION=1.0.0&CRS=EPSG:4326&COVERAGE=AQS_D.pm25&TIME=2007-05-27T00:00:00&BBOX=-130,24,-65,52,0,0&WIDTH=-1&HEIGHT=-1&DEPTH=-1&FORMAT=NetCDF-table> Would you mind dropping me a pointer to your point data encoding in netCDF for WCS 1.? Example WCS GetCoverage that returns your point netCDF? Regards Rudy