Hi,

I used the trunk version now and it also gives errors. I think the
namespaces in the capabilities response I get back seem to be not
correct, e.g. the xml header shows this:

<wcs:Capabilities xmlns:wcs="http://www.opengis.net/wcs/1.1.1";
xmlns:gml="http://www.opengis.net/gml";
xmlns:ns7="http://www.opengis.net/wcs/1.1";
xmlns:ows="http://www.opengis.net/ows/1.1";
xmlns:smil20="http://www.w3.org/2001/SMIL20/";
xmlns:smil20lan="http://www.w3.org/2001/SMIL20/Language";
xmlns:wcst="http://www.opengis.net/wcs/1.1/wcst";
xmlns:xlink="http://www.w3.org/1999/xlink";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="1.1.1"
xsi:schemaLocation="http://www.opengis.net/wcs/1.1.1
http://schemas.opengis.net/wcs/1.1.1/wcsAll.xsd
http://www.opengis.net/ows/1.1
http://schemas.opengis.net/ows/1.1.0/owsAll.xsd
http://www.w3.org/1999/xlink
http://schemas.opengis.net/xlink/1.0.0/xlinks.xsd
http://www.opengis.net/gml
http://schemas.opengis.net/gml/3.1.1/base/gmlBase.xsd
http://www.w3.org/2001/SMIL20/
http://schemas.opengis.net/gml/3.1.1/smil/smil20.xsd
http://www.w3.org/2001/SMIL20/Language
http://schemas.opengis.net/gml/3.1.1/smil/smil20-language.xsd";>

There are several things that seem strange to me, e.g. wcs NS is set
to 1.1.1. although the requested version was 1.1.0, I'd say that is an
implementation bug of the remote service. But also ows namespace is
set (I'd say correctly to "http://www.opengis.net/ows/1.1";) but in
wcs110.py it uses different locations, sometimes
{http://www.opengis.net/wcs/1.1/ows} or {http://www.opengis.net/ows}.
Shouldn't it use the nspath function from util.py at this point?

At the moment with some changes to the namespace handling, I can
succesfully create a WCS object, with some information (e.g. title
...) but unfortunately the wcs:Contents section is empty.

I will dig a little deeper and let you know.

Cheers, Michael


2011/2/18 Michael Schulz <[email protected]>:
> Hi Tom,
>
> thanks, not yet accessible ...
> Ok, I'll have a look at the trunk version.
>
> Thanks for hint, Michael
>
>
> 2011/2/18 Kralidis,Tom [Ontario] <[email protected]>:
>>
>>
>>> -----Original Message-----
>>> From: [email protected]
>>> [mailto:[email protected]] On Behalf Of
>>> Michael Schulz
>>> Sent: Friday, 18 February 2011 10:06
>>> To: [email protected]
>>> Subject: [Community] owslib wcs 1.1.0 connection
>>>
>>> Hi,
>>>
>>> just joined the list, hello to all.
>>>
>>> I want to use owslib for accessing web coverage services and
>>> I can't seem to connect to WCS 1.1.0 services, whereas
>>> everything works fine for version 1.0.0. I get this error:
>>>
>>> Traceback (most recent call last):
>>>   File "/home/webuser/wps/processes/gdalfetchwcsbbox.py",
>>> line 209, in <module>
>>>
>>> testWCS('http://its.not.my.server/','wc_30s_CCCMA_A2a_2050_tma
>> x_2',(-5,40,0,45))
>>>   File "/home/webuser/wps/processes/gdalfetchwcsbbox.py",
>>> line 91, in testWCS
>>>     wcs = WebCoverageService(url,version='1.1.0')
>>>   File
>>> "/usr/local/lib/python2.6/site-packages/OWSLib-0.3.1-py2.6.egg
>> /owslib/wcs.py",
>>> line 22, in WebCoverageService
>>>     return
>>> wcs110.WebCoverageService_1_1_0.__new__(wcs110.WebCoverageServ
>> ice_1_1_0,url,
>>> xml)
>>>   File
>>> "/usr/local/lib/python2.6/site-packages/OWSLib-0.3.1-py2.6.egg
>> /owslib/coverage/wcsBase.py",
>>> line 34, in __new__
>>>     obj.__init__(url, xml)
>>>   File
>>> "/usr/local/lib/python2.6/site-packages/OWSLib-0.3.1-py2.6.egg
>> /owslib/coverage/wcs110.py",
>>> line 53, in __init__
>>>     self.identification=ServiceIdentification(elem)
>>>   File
>>> "/usr/local/lib/python2.6/site-packages/OWSLib-0.3.1-py2.6.egg
>> /owslib/coverage/wcs110.py",
>>> line 225, in __init__
>>>     self.title = elem.find('{http://www.opengis.net/ows}Title').text
>>> AttributeError: 'NoneType' object has no attribute 'find'
>>>
>>> But the xml response is alright and the namespaces are
>>> defined correctly (it works with the same server in 1.0.0).
>>>
>>> Anyone has an idea what could be wrong?
>>
>> Is the WCS server you are connecting to available to test?
>>
>> I'm guessing that the WCS you are hitting uses the WCS-namespace'd
>> elements for ServiceIdentification.  This looks to have been fixed in
>> svn trunk.
>>
>> ..Tom
>> _______________________________________________
>> Community mailing list
>> [email protected]
>> http://lists.gispython.org/mailman/listinfo/community
>>
>
>
>
> --
> -----------------------------------------------------------
> Michael Schulz
> [email protected]
>



-- 
-----------------------------------------------------------
Michael Schulz
[email protected]
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community

Reply via email to