NIM059938 for ArcGIS for Desktop

Bug ID Number	NIM059938
Submitted	August 11, 2010
Last Modified	June 5, 2024
Applies to	ArcGIS for Desktop
Version found	10.0
Operating System	Windows OS
Operating System Version	XP
Status	Will Not Be Addressed

Additional Information

We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.

Workaround

Add service as version 1.0.0. The above work around is not consistent, though. For example, it works with <a href="http://mapserver.ngdc.noaa.gov/cgi-bin/public/etopo1/etopo1.tif?request=GetCapabilities&service=WCS" target="_blank">http://mapserver.ngdc.noaa.gov/cgi-bin/public/etopo1/etopo1.tif?request=GetCapabilities&service=WCS</a>, but does not work with <a href="http://v2.suite.opengeo.org/geoserver/wcs" target="_blank">http://v2.suite.opengeo.org/geoserver/wcs</a>?Another workaround I found that works is to add the WCS service URL using the "Add WMS service" in ArcMap or ArcCatalog or a Web ADF application: Add WMS Server, then paste in the URL <a href="http://v2.suite.opengeo.org/geoserver/wcs" target="_blank">http://v2.suite.opengeo.org/geoserver/wcs</a>?, and Get Layers. When you add one of the layers into ArcMap, ArcCatalog, or a Web ADF application, the raster dataset displays as expected, and the Identify tool works just as expected for a WCS service - you are able to identify the attribute value of each pixel in the raster.