Opened 13 years ago

Closed 12 years ago

#3105 closed defect (fixed)

WCS 1.1.1 GetCapabilities request does not support the sections

Reported by: nsavard Owned by: warmerdam
Priority: normal Milestone: 5.6 release
Component: WCS Server Version: 5.4
Severity: normal Keywords: ogc, cite, test, wcs, 1.1.1, getcapabilities, sections
Cc: tomkralidis

Description (last modified by warmerdam)

"sections" parameter is not supported for a WCS 1.1.1 GetCapabilities request. This makes the capabilities response to not validate and the OGC test failed.

The request is: http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs111_ogc_cite?service=WCS&request=GetCapabilities&sections=OperationsMetadata,Contents

The OGC CITE test engine is: http://cite.opengeospatial.org/te2/

Log for test s0008/d1e329_1

Test wcs:GetCapabilities-main (s0008/d1e329_1)

Assertion: All assertions for "GetCapabilities" conformance are satisfied.

Request d1e369_1:
   Method: GET
   URL: http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs111_ogc_cite?service=WCS&request=GetCapabilities&sections=OperationsMetadata,Contents
   Response from parser ctlp:XMLValidatingParser:
      
   Messages from parser ctlp:XMLValidatingParser:
        Validation error:
  cvc-elt.1: Cannot find the declaration of element 'Capabilities'.
1 validation error detected.


Message d1e411_1:
   
 

Message d1e413_1:
   The service metadata document has version  but expected to find 1.1.1 as the highest protocol supported. See OGC 06-121r3 subclause 7.3.2.

Message d1e415_1:
   
 

Message d1e490_1:
   The server seems to have a problem with handling the GetCapabilities sections parameter. No tests will be performed.

Message d1e496_1:
   The EqualUpdateSequence value is .

Message d1e498_1:
   The URL for KVP encoding is .

Message d1e500_1:
   The URL for XML encoding is .

Message d1e512_1:
   XML encoding is not supported.

Message d1e524_1:
   sections-supported: false.

Result: Failed

Change History (21)

comment:1 by warmerdam, 13 years ago

Cc: warmerdam added

If desired, I would be willing to implement this feature. It clearly is something I should have done the first time around. Let me know.

comment:2 by nsavard, 13 years ago

comment:1 Frank, waiting for Tom to comment.

comment:3 by tomkralidis, 13 years ago

Cc: tomkralidis added; warmerdam removed
Owner: changed from tomkralidis to warmerdam

Thanks Frank. I'll check your changes once committed.

comment:4 by warmerdam, 13 years ago

Description: modified (diff)
Status: newassigned

comment:5 by warmerdam, 13 years ago

I have implemented support in trunk for SECTIONS (r9291) and some testing in the autotest suite (r9291).

The support is case sensitive for the argument to Sections in the URL - should it be? If testing goes well in trunk, an I can back port this if it is deemed appropriate.

BTW, I get a lot of failures in the msautotest/wcs tests - alot related to filtering. Should the following be sufficient?

warmerda@gdal64[122]% mapserv -v
MapServer version 5.5.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=THREADS SUPPORTS=GEOS INPUT=EPPL7 INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

in reply to:  5 comment:6 by tomkralidis, 13 years ago

Replying to warmerdam:

I have implemented support in trunk for SECTIONS (r9291) and some testing in the autotest suite (r9291).

Nice! This works as expected. All results are valid XML (checked with XML Spy 2009).

The support is case sensitive for the argument to Sections in the URL - should it be? If testing goes well in trunk, an I can back port this if it is deemed appropriate.

Should be case-sensitive (i.e. Contents instead of CONTENTS).

What happens if the section value passed is an invalid one (i.e. sections=foo, or even sections=ServiceProvider,foo)? OWS 1.1 says (document 06-121r3 http://portal.opengeospatial.org/files/?artifact_id=20040), from Table 3:

NamesDefinitionData type and valueMultiplicity and use
sections Sections Unordered list of zero or more names of requested sections in complete service metadata document Sequence of Character String type, each not empty. Value is list of section names. Allowed section names are specified by each Implementation Specification Zero or one (optional). When omitted or not supported by server, return complete service metadata

Norm: can you run the new build through the CITE test and see what gives?

BTW, I get a lot of failures in the msautotest/wcs tests - alot related to filtering. Should the following be sufficient?

warmerda@gdal64[122]% mapserv -v
MapServer version 5.5.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=THREADS SUPPORTS=GEOS INPUT=EPPL7 INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

I get 5/22 tests failing (on fc11):

version = MapServer version 5.5.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=PDF OUTPUT=SWF OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=GEOS INPUT=EPPL7 INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

...

   test wcs_getcov_grd_11.dat
*    results dont match, TEST FAILED.
   test wcs_getcov_grd_11_imagecrs.dat
*    results dont match, TEST FAILED.
   test wcs_getcov_grd_11_4326.dat
*    results dont match, TEST FAILED.
   test wcs_getcov_grd_11_wgs84.dat
*    results dont match, TEST FAILED.
   test wcs_getcov_gdpng8_11.dat
*    results dont match, TEST FAILED.


comment:7 by nsavard, 13 years ago

RE comment:5

I noticed this also on Ubuntu Intrepid. Your switches are correct.

Tom and I noticed that these two tests failed a long time ago: test wcs_getcov_gdpng8_11.dat test wcs_getcov_grd_11_wgs84.dat

New:There have been a small changes in the following tests (checked in OpenEv): test wcs_16_repro.tif test wcs_16_ds.tif test wcs_16.tif

New: I cannot open these two images in OpenEv but when I do the GetCoverage request in the browser I can see the generated image. Don't know why. test wcs_bilinear.png test wcs_simple.png

comment:8 by nsavard, 13 years ago

RE comment:6 Norm: can you run the new build through the CITE test and see what gives?

comment:9 by nsavard, 13 years ago

RE comment:6 Norm: can you run the new build through the CITE test and see what gives?

Yes Tom I'll do it.

comment:10 by nsavard, 13 years ago

RE comment:6

GetCapabilities section parameter works but the OGC CITE test failed with the error message as shown in the ticket description. It seems that the "Capabilities" tag is not expected.

comment:11 by warmerdam, 13 years ago

Are we missing some sort of name space prefix for the Capabilities tag or something? I get quite lost in these aspects of XML. Tom? thoughts?

in reply to:  11 comment:12 by tomkralidis, 13 years ago

Replying to warmerdam:

Are we missing some sort of name space prefix for the Capabilities tag or something? I get quite lost in these aspects of XML. Tom? thoughts?

The namespace prefix is not needed in this case, since the default namespace is xmlns="http://www.opengis.net/wcs/1.1".

Having said this, GeoServer seems to do the same thing:

http://sigma.openplans.org/geoserver/ows?service=WCS&request=GetCapabilities&version=1.1.1&sections=OperationsMetadata,Contents

So I'm not sure what's up. Norm: can we get more details on the failed assertion? Or query the CITE folks?

One other thing we'll want to check is whether we should throw an exception if an unknown WCS section name is passed, i.e.:

http://sigma.openplans.org/geoserver/ows?service=WCS&request=GetCapabilities&version=1.1.1&sections=OperationsMetadata,Contents,Foo

comment:13 by nsavard, 13 years ago

Tom: I'll post a question to them.

comment:14 by nsavard, 13 years ago

Tom: Before I sent an email I validated the capabilities response and found that there is a problem. Could you check ticket 3118 (http://trac.osgeo.org/mapserver/ticket/3118)?

comment:15 by nsavard, 13 years ago

I posted a question to the forum and I'm waiting for their answer.

comment:16 by tomkralidis, 13 years ago

Norm: I wonder if you ran this test again pointing to the right schema (per #3118) if you get different results?

comment:17 by nsavard, 13 years ago

Tom: I'm pointing to the valid schema. Am I? See my Web object below.

WEB

TEMPLATE template.html METADATA

#These ones does not validate #"ows_schemas_location" "http://schemas.opengis.net/" #Downloaded from http://test.schemas.opengis.net/wcs111/wcs111.zip "ows_schemas_location" "http://dev1.lan.mapgears.com/manwe/schemas" #"ows_schemas_location" "http://test.schemas.opengis.net/" # OGC:WCS "ows_title" "CITE:OGC_CITE WCS 1.1.1 Server" "ows_label" "UMN Test WCS Server" "ows_keywordlist" "WCS,MODIS,NDVI" "ows_description" "WCS Server to run OGC CITE Tests" "ows_onlineresource" "http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs111_ogc_cite?" "ows_service_onlineresource" "http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs111_ogc_cite?"

"ows_metadatalink_href" "http://dev1.lan.mapgears.com/manwe/index.html" "ows_fees" "none" "ows_updatesequence" "1" "ows_accessconstraints" "None" "ows_contactperson" "contactperson" "ows_contactorganization" "contactorganization" "ows_contactposition" "self" "ows_contactelectronicmailaddress" "xxx@…" "ows_contactvoicetelephone" "+xx-xxx-xxx-xxxx" "ows_contactfacsimiletelephone" "+xx-xxx-xxx-xxxx" "ows_HoursOfService" "0800h - 1600h EST" "ows_ContactInstructions" "during hours of service" "ows_role" "staff" "ows_address" "123 SomeRoad Road" "ows_city" "Toronto" "ows_stateorprovince" "Ontario" "ows_postcode" "xxx-xxx" "ows_country" "Canada" "ows_abstract" "This is a WCS 1.1.1 server."

END

IMAGEURL "/tmp/" IMAGEPATH "/tmp/ms_tmp/"

END

comment:18 by nsavard, 13 years ago

Tom: I'm pointing to the valid schema. Am I? See my Web object below (better formating).

 
  WEB
    TEMPLATE template.html
    METADATA
      #These ones does not validate
      #"ows_schemas_location" "http://schemas.opengis.net/"
      #Downloaded from http://test.schemas.opengis.net/wcs111/wcs111.zip
      "ows_schemas_location" "http://dev1.lan.mapgears.com/manwe/schemas"
      #"ows_schemas_location" "http://test.schemas.opengis.net/"
      # OGC:WCS
      "ows_title" "CITE:OGC_CITE WCS 1.1.1 Server"
      "ows_label" "UMN Test WCS Server"
      "ows_keywordlist" "WCS,MODIS,NDVI"
      "ows_description" "WCS Server to run OGC CITE Tests"
      "ows_onlineresource" "http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs111_ogc_cite?"
      "ows_service_onlineresource" "http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs111_ogc_cite?"

      "ows_metadatalink_href" "http://dev1.lan.mapgears.com/manwe/index.html"
      "ows_fees"              "none"
      "ows_updatesequence"   "1"
      "ows_accessconstraints" "None"
      "ows_contactperson" "contactperson"
      "ows_contactorganization" "contactorganization"
      "ows_contactposition" "self"
      "ows_contactelectronicmailaddress" "xxx@xxxxxxx.xxx"
      "ows_contactvoicetelephone" "+xx-xxx-xxx-xxxx"
      "ows_contactfacsimiletelephone" "+xx-xxx-xxx-xxxx"
      "ows_HoursOfService" "0800h - 1600h EST"
      "ows_ContactInstructions" "during hours of service"
      "ows_role" "staff"
      "ows_address"     "123 SomeRoad Road"
      "ows_city" "Toronto"
      "ows_stateorprovince" "Ontario"
      "ows_postcode" "xxx-xxx"
      "ows_country" "Canada"
      "ows_abstract" "This is a WCS 1.1.1 server."
 
      END
    IMAGEURL "/tmp/"
    IMAGEPATH "/tmp/ms_tmp/"
  END

comment:19 by tomkralidis, 13 years ago

That's fine. Make sure you have the latest set of schemas (http://schemas.opengis.net/SCHEMAS_OPENGIS_NET.zip). Or, if you comment out ows_schemas_location, the code will default the value to http://schemas.opengis.net/

comment:20 by tomkralidis, 13 years ago

FYI I believe this may be related on #3086.

comment:21 by warmerdam, 12 years ago

Milestone: 5.6 release
Resolution: fixed
Status: assignedclosed

As I understand it, the only remaining issue is related to whether the cite test recognises the Capabilities in the returned document and this seems to be related to using the correct schemas.

This does not seem closely related to the original topic of this ticket. If schema problem persists and is not covered elsewhere, perhaps you could create a new ticket for the issue Normand?

Note: See TracTickets for help on using tickets.