Hi Andrea,
Thank you very much for your quick response. ESRI tested their WCS
clients using Geoserver 1.7.2. I also tested with the cited URL. It appears
ArcGIS is fully compatible with Geoserver 1.7.2.
To enlarge a bigger Geoserver user community, I believe Geoserver
should be implemented with the most flexible solutions especially if such
solution was there in previous release. I understood the same is applicable
on client side. However, it a surprise to some clients that a working
solution suddenly disappears in a new release.
On Thu, Sep 29, 2011 at 4:32 AM, Andrea Aime
<[email protected]>wrote:
> On Thu, Sep 29, 2011 at 10:37 AM, quan huynh <[email protected]> wrote:
>
>> Hi all,
>>
>> After trouble shooting the issue with ESRI (ArcGIS), it turned out
>> that ArcGIS was tested using an older version of geoserver (GeoServer
>> 1.7.2.). The describe coverage query string does not contain identifier.
>> Here is the whole URL:
>>
>>
>> http://apps.who.int/tools/geoserver/ows?REQUEST=DescribeCoverage&SERVICE=WCS&VERSION=1.0.0
>>
>> This was O.K. with 1.7.2. It returns the description of all
>> coverages. In the latest stable Geoserver release, without specifying the
>> identifier MissingParameterValue exception was returned.
>>
>> Does any one know if this change is intentional, and the rationale
>> behind it?
>>
>
> I can't comment on wheter the change is intentional, but it's a valid one.
> The WCS 1.0 specification says:
>
> If the Coverage element is absent, the server may return full descriptions
> of every coverage offering
> available, or return a service exception
>
> GeoServer goes for the second option, which is a valid one, a compliant
> client should be able
> to support this case too.
>
> That said, changing the code to support also the lack of said parameter
> should not be too hard.
> This of course does not mean that will magically make ArcGis work, the next
> step is ArcGis
> understanding the response and performing a GetCoverage request that
> GeoServer understands,
> if the ArcGis client has not been written considering all the possible
> cases in the spec
> there might be more failures ahead (and GeoServer could have its own bugs
> there too).
>
> Cheers
> Andrea
>
>
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
