Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty CRS code in CRS-parameter #6

Closed
bermud opened this issue Sep 16, 2014 · 5 comments

Comments

Projects
None yet
2 participants
@bermud
Copy link
Contributor

commented Sep 16, 2014

Originally reported by Fischer, Jean-Michel 2013-10-30
Closed 2014-05-06 05:23:48
https://portal.opengeospatial.org/services/srv_public_issues.php?call=viewIssue&issue_id=885

Original Issue Details:
The parameter CrS is empty for some tests.

The SUT defines the CRS in the parent layer:

http://services.interactive-instruments.de/cite2013wfs/cite/cgi-bin/wms/wms/wms?request=GetCapabilities&version=1.3

Maybe it has something to do with issue 783?

The empty CRS-code appears in the following tests:

Test getmap:bbox-inherited
Test getmap:styles-some-default
Test getmap:first-style-invalid
Test getmap:second-style-invalid
Test getmap:each-style
Test getmap:styles-direct
Test getmap:each-layer

@bermud bermud added this to the r9 milestone Sep 16, 2014

@bermud

This comment has been minimized.

Copy link
Contributor Author

commented Sep 16, 2014

The cause for the behaviour is, that your service makes use of inheritance for BBOX and CRS parameters only. One way to solve the issues for the certification process would be to repeat those parameters for every layer. Nevertheless, I am currently looking into the issue.

Entered By: Goerke, Sebastian - 2013-11-14 05:04:46

@bermud

This comment has been minimized.

Copy link
Contributor Author

commented Sep 16, 2014

It seems, that every of the mentioned tests has to be modified.
After reviewing all issues, I will post here, when this will be fixed.

Entered By: Goerke, Sebastian - 2013-11-14 05:12:47

@bermud

This comment has been minimized.

Copy link
Contributor Author

commented Sep 16, 2014

Sebastian,

Intergraph has also seen this problem. Sure we could put the bbox at each layer, but that seems like we are coding around a problem in the CITE tests. Besides "Test getmap:bbox-inherited" seems like it should be testing this exact thing and yet it is interpreting it incorrectly too. Here's the assertion for that test:

Assertion: When a GetMap request contains a layer whose BoundingBox is inherited from a parent layer, then the response is valid.

Am I missing something here?

Entered By: Tillman, Stan - 2013-11-18 14:21:03

@bermud

This comment has been minimized.

Copy link
Contributor Author

commented Sep 16, 2014

In the following WMS 1.1.1 Tests the same problem occurs:

Test wms:wmsops-getmap-each-style
Test wms:wmsops-getmap-each-layer
Test wms:wmsops-getmap-layer-encoded-name

Is it ok to report this here or should I open a new issue for WMS 1.1.1?

Entered By: Fischer, Jean-Michel - 2013-11-26 05:24:11

@bermud

This comment has been minimized.

Copy link
Contributor Author

commented Sep 16, 2014

Closed in revision 1c8a991
Entered By: Goerke, Sebastian - 2014-05-06 05:23:48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.