Petascope_Adjustment to pass conformance tests

[Vlad Frasineanu]

Petascope has been developing some OGC web services (WCS, WMS) and it needs to pass the conformance tests ​http://cite.opengeospatial.org/teamengine/ to prove its followed OGC standards correctly. This can lead to a lot of changes (I just assume) if many tests will be failed.

The failing tests should be fixed. The log files are attached here.

[Bang Pham Huu]

can anyone give me some idea what is this tests and what is the xml inside the attachment files ?

[Vlad Frasineanu]

Here is the link to the test results:
​http://cite.opengeospatial.org/teamengine/viewSessionLog.jsp?session=s0025
You need to login there with the account rasdaman/rasdaman and you will be able to see the results in more detail.

I will write a tutorial next days about how to update the VM that is running rasdaman and rerun the tests with new changes.

[Bang Pham Huu]

thanks Vfras, so I understand your work is setup a WM which the OGC test services can run the test on it and you collect all the log files into the attachment files. I have a question, which services did you test? I will play with these test a little more to see what they test and what they expect to check test is failed.

[Bang Pham Huu]

So we want to make sure WCS can pass the conformance test version 2.0.1. I checked some results (it shows that the output of WCS is not valid completely GML XSD 2.0.1 ​http://schemas.opengis.net/wcs/). And this need to be fixed first by using this tool to validate output GML from Petascope (e.g: GetCoverage, DescribeCoverage, GetCapabilities) and OGC WCS Schema ​http://www.eisenhutinformatik.ch/gml/gmlcheck/.

Also, current the test endpoint for conformance is down, due to Rasql cannot start (someone need to restart rasdaman on this server)

http://kahlua.eecs.jacobs-university.de/conformance?SERVICE=WCS&VERSION=2.0.1&REQUEST=DescribeCoverage&CoverageId=test_mr

Metadata for coverage 'test_mr' is not valid, reason: 
RasManager Error: Could not connect to RasServer.

I installed TEAMengine in my computer but the speed is much slower (test by console, not by Web Application as it has some errors when deploy locally), compared to test online from OGC cite onto the public endpoint.

[Bang Pham Huu]

so the purpose now is reduce to pass WCS 2.0.1 (WCS_Core), before it fails in many tests of other test selection, then I could not resolve for all cases. After fixing to valid WCS Schema, here are the failed cases:

+ Test wcs:getcoverage_not_exception (View Details): Failed ([FAILURE] The result should not contain an ows:Exception.)
+ Test wcs2:OWSCommon_exception (View Details): Failed (OWS common: test HTTP status codes for OGC Exceptions.)
+ Test wcs2:OWSCommon_exception (View Details): Failed (OWS common: test HTTP status codes for OGC Exceptions.)
+ Test wcs2:OWSCommon_exception (View Details): Failed (OWS common: test HTTP status codes for OGC Exceptions.)
+ Test wcs2:OWSCommon_exception (View Details): Failed (OWS common: test HTTP status codes for OGC Exceptions.)
+ Test wcs2:get-kvp-core-req42 (View Details): Failed (the coverage description should be equal)

Passed: 113
Failed: 7

[Bang Pham Huu]

so up to now, Petascope passed all the tests for WCS_Core 2.0.1

   Assertion: Req43: For the transmission of all operation requests and responses, WCS implementations shall support at least one WCS protocol extension, that is: an extension whose URI starts with http://www.opengis.net/spec/WCS_protocol-binding_.
            Test wcs2:req43 Passed
         Test wcs2:core-main Passed
      Test wcs2:main_test Passed
   Test wcs2:main Passed
Suite wcs2:suite Passed

but there is a bug I still could not find out is inside the XML of output from Petascope or due to TeamEngine when it creating the report in HTML (it is not important up to now as the log shows the test suited was passed, but just let you want to know if OGC consultant asked about the report). And without the test report, it is impossible to find the reason test fails if any (so must consider about finding this problem later).

http://cite.opengeospatial.org/te2/viewSessionLog.jsp?session=s0076&stop=undefined&t=1478160086902

org.apache.jasper.JasperException: javax.servlet.ServletException: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; lineNumber: 161; columnNumber: 754; An invalid XML character (Unicode: 0xc) was found in the element content of the document.
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:556)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:462)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)

[Dimitar Misev]

Is this report from the official OGC team engine?

[Bang Pham Huu]

Replying to dmisev:

Is this report from the official OGC team engine?

yes, it is from running log.

[Dimitar Misev]

That's great news.

[Bang Pham Huu]

The patch was applied, thanks for all supports. (note: in petascope.properties: xml_validation=true when run the OGC CITE test.

[Dimitar Misev]

I think we should test the extensions as well, not just core.

[Bang Pham Huu]

the patch was applied, so Petascope will not test EOWCS extension and CRS extension which needs to be updated from OGC CITE for test suit (other fixable for this extension was done in Petascope).

[Peter Baumann]

hm, does this mean that the CRS extension is not available any more to rasdaman users?

[Bang Pham Huu]

Replying to pbaumann:

hm, does this mean that the CRS extension is not available any more to rasdaman users?

No, I meant it was fixed in Petascope but as OGC CITE test suite has bugs so it cannot pass this test suite for CRS extension completely and nothing was taken from Petascope, the patch added/fixed petascope correctly and did not remove any features.

[Peter Baumann]

are you sure it can be used? I believe mentioning the CRS Extension in the Capabilities Profile has been disabled which tells clients that it is not supported. Maybe I am missing something.

[Bang Pham Huu]

You're right that we don't show the list of crss from epsg database in GetCapabilities as this list is too long. However that is all from CrsExtension is hided and if one want to display this list, there is a configuration in petascope.properties to enable it. Other features for CrsExtension like Crs transform still work normally.

[Dimitar Misev]

I mentioned to Bang that we should show something like ​http://www.opengis.net/def/crs/EPSG/0/ by default?