Wanted to check if this was resolved. I'm also seeing internally at Esri for input, but would be good to have a more clear description of the issue. We follow the spec and passed the compliance tests so at least something is correct there.
I have a public WCS we can use for testing: http://geoss.esri.com/arcgis/services/gmed_physical/bo_sst_mean/ImageServer/WCSServer?request=GetCapabilities&service=WCS that's on my server so I can do some configuration as needed. This service shows: xmlns="http://www.opengis.net/wcs/1.1"; xmlns:ows="http://www.opengis.net/ows/1.1"; Which seems to be in line with the spec. What is not working for you? Marten From: openlayers-dev-boun...@lists.osgeo.org [mailto:openlayers-dev-boun...@lists.osgeo.org] On Behalf Of Bart van den Eijnden Sent: Monday, May 26, 2014 1:36 AM To: Christopher Eykamp Cc: openlayers-dev@lists.osgeo.org Subject: Re: [OpenLayers-Dev] ESRI // WCS DescribeCoverage 1.1.0 Have you run the ArcGIS response through an XML validator? Can you share the full response including all the (non-public) schemas it references? Best regards, Bart -- Bart van den Eijnden Front-end Developer | Boundless @boundlessgeo On 26 May 2014, at 10:32, Bart van den Eijnden <bart...@boundlessgeo.com<mailto:bart...@boundlessgeo.com>> wrote: Hey Chris, the way to verify who is right is to look at the schema, so: http://schemas.opengis.net/wcs/1.1/wcsDescribeCoverage.xsd it defines: xmlns:ows="http://www.opengis.net/ows/1.1"; so this is the correct namespace URI to use. Best regards, Bart -- Bart van den Eijnden Front-end Developer | Boundless @boundlessgeo On 26 May 2014, at 10:30, Christopher Eykamp <christopher.eyk...@tudor.lu<mailto:christopher.eyk...@tudor.lu>> wrote: Hi Tim, Thanks for the reply. I am less familiar with the standards than you are, so can you tell me how one can determine that the second schema is for WCS 1.1.0, and not the first? From the names, I would conclude that the first is correct, and that the second is... also correct? In any event, I will need to find a way to parse this document (I don't control the server, and our partner who does is probably unable to resolve things on their end). I will look into Bart's suggestion to see if that offers a way forward. Thanks! Chris On 05/23/2014 06:25 PM, Timothy Astle wrote: I believe you've hit an oddity in the WCS schemas. Look at this one: http://schemas.opengis.net/wcs/1.1.0/wcsDescribeCoverage.xsd Now look at this one: http://schemas.opengis.net/wcs/1.1/wcsDescribeCoverage.xsd Do you see a difference in the ows namespace? From what I recall, the second one is correct. A few years ago I was in a similar situation. I'm thinking ArcGIS Server might be generating XML using the wrong schemas. So I believe OL is correct and the "problem" is with ArcGIS Server, leading from the OGC schema confusion. I'd love to know the history behind it. Do you have control over the ArcGIS Server instance? It could be something you want to bring up with ESRI. Cheers, Tim On 23/05/2014 12:19 PM, Christopher Eykamp wrote: Hello, I am getting the attached response from an ArcGIS WCS server, with request DescribeCoverage and protocol version 1.1.0. OpenLayers (latest 1.x from GitHub) cannot retrieve the Title or Abstract attributes because the namespaces referenced in the OpenLayers.Format.WCSDescribeCoverage.v1_1_0 object conflict with what is referenced in the document. Specifically, the OpenLayers namespaces object includes this line: ows: "http://www.opengis.net/ows/1.1";<http://www.opengis.net/ows/1.1> This in turn is used to generate a namespaceAlias lookup, which will return "ows" when looking up "http://www.opengis.net/ows/1.1";<http://www.opengis.net/ows/1.1>. However, in this case, I need "ows" to be mapped to "http://www.opengis.net/ows";<http://www.opengis.net/ows>. If I make that change in the namespaces definition, tests break. Unfortunately, given the way the aliases are defined, I cannot add a second namespace that maps to "ows", which might fix my problem. I am unsure how to proceed. I can't tell if I am encountering a misbehaving server, or if this is just a limitation of the way OpenLayers is architected (hard-coded namespaces that can only have one namespace map to a given alias). Or have I misunderstood something at a more fundamental level? Thanks for your advice! Chris <CoverageDescriptions xmlns="http://www.opengis.net/wcs/1.1";<http://www.opengis.net/wcs/1.1> xmlns:ows="http://www.opengis.net/ows";<http://www.opengis.net/ows> xmlns:owcs="http://www.opengis.net/wcs/1.1/ows";<http://www.opengis.net/wcs/1.1/ows> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";<http://www.w3.org/2001/XMLSchema-instance> xmlns:gml="http://www.opengis.net/gml";<http://www.opengis.net/gml> xsi:schemaLocation="http://www.opengis.net/wcs/1.1 ../wcsDescribeCoverage.xsd http://www.opengis.net/wcs/1.1/ows ../owsDataIdentification.xsd"<http://www.opengis.net/wcs/1.1../wcsDescribeCoverage.xsdhttp:/www.opengis.net/wcs/1.1/ows../owsDataIdentification.xsd>><CoverageDescription><ows:Title>OSDATA.OS_25K_RASTER_1</ows:Title><ows:Abstract/><Identifier>1</Identifier><Domain><SpatialDomain><ows:BoundingBox crs="urn:ogc:def:crs:OGC::imageCRS" dimension="2"><ows:LowerCorner>0 0</ows:LowerCorner><ows:UpperCorner>16273 8848</ows:UpperCorner></ows:BoundingBox><ows:BoundingBox crs="urn:ogc:def:crs:EPSG::4326"><ows:LowerCorner>-2.4975225300277217 57.00034657412791</ows:LowerCorner><ows:UpperCorner>-2.0000237693585987 57.270861907368726</ows:UpperCorner></ows:BoundingBox><GridCRS><GridBaseCRS>urn:ogc:def:crs:EPSG::4326</GridBaseCRS><GridOrigin>-2.4975072449484337 57.27084662228944</GridOrigin><GridOffsets>3.057015857620272e-005 -3.0570158576202496e-005</GridOffsets></GridCRS></SpatialDomain></Domain><Range><Field><Title>Field_1</Title><Abstract>Field_1</Abstract><Identifier>Field_1</Identifier><Definition><owcs:AnyValue/></Definition><NullValue>256</NullValue><NullValue>256</NullValue><NullValue>256</NullValue><owcs:InterpolationMethods><owcs:DefaultMethod>nearest</owcs:DefaultMethod><owcs:OtherMethod>bilinear</owcs:OtherMethod><owcs:OtherMethod>bicubic</owcs:OtherMethod></owcs:InterpolationMethods><Axis identifier="BAND"><AvailableKeys><Key>1</Key><Key>2</Key><Key>3</Key></AvailableKeys><owcs:DataType>Byte</owcs:DataType></Axis></Field></Range><SupportedCRS>urn:ogc:def:crs:EPSG::4326</SupportedCRS><SupportedCRS>urn:ogc:def:crs:EPSG::4326</SupportedCRS><SupportedFormat>image/GeoTIFF</SupportedFormat><SupportedFormat>image/NITF</SupportedFormat><SupportedFormat>image/HDF</SupportedFormat><SupportedFormat>image/PNG</SupportedFormat></CoverageDescription></CoverageDescriptions> _______________________________________________ Dev mailing list d...@lists.osgeo.org<mailto:d...@lists.osgeo.org> http://lists.osgeo.org/mailman/listinfo/openlayers-dev -- Tim Astle Development Manager Web Technologies CARIS<http://www.caris.com/> 115 Waggoners Lane Fredericton, New Brunswick Canada E3B 2L4 Tel: +1.506.458.8533 Fax: +1.506.459.3849 www.caris.com<http://www.caris.com/> CARIS 2014 June 2-5, 2014 | Brest, France | 2-5 juin, 2014 Join us in France at CARIS 2014 as we focus on Developing the Blue Economy. www.caris.com/caris2014/<http://www.caris.com/caris2014/> Venez nous rejoindre en France pour CARIS 2014 et appuyons ensemble l'Économie Bleue. www.caris.com/caris2014-fr/<http://www.caris.com/caris2014-fr/> Download your free copy of CARIS Easy View today! www.caris.com/easyview<http://www.caris.com/easyview> _________________________________________________________________________ This email and any files transmitted with it are confidential and intended only for the addressee(s). If you are not the intended recipient(s) please notify us by email reply. You should not use, disclose, distribute or copy this communication if received in error. Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of the company. No binding contract will result from this email until such time as a written document is signed on behalf of the company. _______________________________________________ Dev mailing list d...@lists.osgeo.org<mailto:d...@lists.osgeo.org> http://lists.osgeo.org/mailman/listinfo/openlayers-dev _______________________________________________ Dev mailing list d...@lists.osgeo.org<mailto:d...@lists.osgeo.org> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
_______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
