WCS Servers (and a few clients too)

---

Rich Signell <rsignell@usgs.gov>

We have a lot of global and regional bathymetry available through the TDS WCS at
http://coast-enviro.er.usgs.gov/thredds/bathy_catalog.html
but I guess you already have plenty of those.

---

Roy Mendelssohn <Roy.Mendelssohn@noaa.gov>

All the satelite data on our thredds server http://oceanwatch.pfeg.noaa.gov/thredds

---

Dominic Lowe <d.lowe@rl.ac.uk>

Feel free to try:
http://ndgbeta.badc.rl.ac.uk/wcs/badc.nerc.ac.uk__NDG-A0__AWQX8gTc?Service=WCS&request=GetCapabilities&Version=1.0.0

It serves 1.0.0 and (to some extent) 1.1.0. However it only returns NetCDF so
may not be much use for your experiment. For 1.1.0 it will return NetCDF
encoded alongside the coverages XML document as a MultipartMime - I'd be
interested to know if the ArcGIs client decodes it.

As an aside, the python WCS client library I was working on has now been
released as part of the OWSLib library:
http://pypi.python.org/pypi/OWSLib/0.3

---

Rob Weingruber <weingrub@rap.ucar.edu>

We have a WCS 1.1.1 SOAP server at http://weather.aero/wcs/soap

It's not very robust, and we're working on one that is a little more.

Let us know how it goes/doesnt go, as that could be some helpful feedback...

---

Mary Jo Brodzik <brodzik@wuzzles.colorado.edu>

The NSIDC Atlas of the Cryosphere has a WCS server enabled, thanks to the
efforts of John Maurer.  You're welcome to take a look at

 *  Northern Hemisphere:

http://nsidc.org/cgi-bin/atlas_north?service=WCS&request=GetCapabilities

 *  Southern Hemisphere:

http://nsidc.org/cgi-bin/atlas_south?service=WCS&request=GetCapabilities

With more info on OGC services from the Atlas at:

http://nsidc.org/data/atlas/ogc_services.html

If you have questions, contact John at maurerj@nsidc.org.  I'm sure he'll
be interested to learn what your experience is.

---

Maarten Plieger <plieger@knmi.nl>

We have a WCS 1.0.0 server with the following address:

http://geoservices.knmi.nl/cgi-bin/mapserver-5.0.2.fcgi?SERVICE=WCS&VERSION=1.0.0&REQUEST=GETCAPABILITIES

The WCS currently serves Sciamachy tropospheric NO2 data. The output
format can be a 16bit-geoTiff or a AAIGRID file which are both supported
by ArcGIS. We are still working on netCDF support. The server is UMN
MapServer 5.0.2 with GDAL for reading and writing the data.

We are interested whether this works/does not work with the ArcGIS WCS
client.. Suggestions are welcome.

---

Wenli Yang (GSFC-610.2)[GMU]<wenli.yang-1@nasa.gov>

GMU has implemented a WCS server supporting multiple file formats including GeoTiff.  The URLs are:

http://data.laits.gmu.edu:8080/cgi-bin/wcs110?
http://geobrain.laits.gmu.edu/cgi-bin/wcs110?

Although named wcs110, the server also supports v1.0.0. Please note that the first URL has a slower network (T1) and the second URL has a fast network (Internet II).  However the GetCapabilities and DescribeCoverage responses from the 2nd URL are extremely large (close to 50MB and 200 MB respectively) due to the huge data volume.  We are in the process of splitting our data products and serve them through multiple server instances.

The server has been tested and used in several NASA funded projects, one of which is the GeoBrain project (http://geobrain.laits.gmu.edu:81/OnAS/  http://geobrain.laits.gmu.edu/).

The developer of the server is Dr. Peichun Li.  He can be reached at pli4@gmu.edu, if there are any questions regarding the server.  He also provides some notes on using the server at http://data.laits.gmu.edu:8080/pli/www/wcs110.htm.

---

Ben Domenico <ben@unidata.ucar.edu>

The Unidata prototype THREDDS Data Server "motherlode" has a WCS 1.0 interface for accessing most of the gridded datasets.

  http://motherlode.ucar.edu:8080/thredds/catalog.html

---

Mattia Santoro <santoro@imaa.cnr.it> and
Enrico Boldrini <boldrini@imaa.cnr.it>

The WCS-1.1 server is avaiable at the URL:
http://kronos.pin.unifi.it:8080/wcs-1.1.0-service/ogc-wcs

This server supports only georectified coverages (so it is not completely compliant with WCS 1.1 specifications), you can find more details about the supported features of this service at:
http://zeus.pin.unifi.it/joomla/index.php?option=com_content&task=view&id=65&Itemid=97


The GI-go GeoBrowser can perform discovery and access of geographic data from different services through an easy to use interface.

The tool is available for use and download at http://zeus.pin.unifi.it/gi-go

It is a client for: WCS 1.0, WCS 1.1, WMS 1.3.0 and CSW/ISO 2.0.2

---

Comments

---

Roy Mendelssohn <Roy.Mendelssohn@noaa.gov>

The EDC tool works with OPeNDAP grids  (non-projected), but it has the added feature, like in IDV  (and in fact stolen from IDV - yeah open source!) that if it is a THREDDS catalog than the catalog can be used to browse the data and metadata, subset the data (using the visual interface from ncBrowse), and make the download.  It does make use of the ESRI netcdf interface, which has a lot of problems and limitations.  Even worse, 9.3 changes the interface, so it breaks the plugin.  We hope to get  funds to get a 9.3 version built, as well as add a lot of the in situ services we support in ERDDAP.

There is a standalone version that just browses the data and downloads netcdf.  That is pure java., built on the netcdf-java library.  So one way to view it is the front end can do anything the netcdf-java library can do, the backend depends on features in ESRI for importing certain types of data.  We do demos of the tool if you guys are ever interested.

---

 

Steve Kopp <skopp@esri.com>

 ... you are correct, netCDF is not part of the WCS support in arcGIS 9.3.