[Geoserver-devel] [JIRA] (GEOS-8742) CRS:84 is shown FIRST in the WMS GetCapabilities even if it is not declared, causing delays in providing the response

_Failed_to_Retrieve · May 14, 2018, 7:41am

Iurie Maxim created an issue

CRS:84 is shown FIRST in the WMS GetCapabilities even if it is not declared, causing delays in providing the response

Issue Type:	Bug
Assignee:	Unassigned
Created:	14/May/18 9:41 AM
Environment:	Even if trough https://osgeo-org.atlassian.net/browse/GEOS-1830 it is now possible to limit the number of CRS exposed in the GetCapabilities document of the WMS, the bounding box of the data in CRS:84 appears first in the list in the GetCapabilities document even if the CRS:84 is not provided in the list of supported CRS in the Geoserver interface. Because the CRS:84 is shown FIRST in the list, the INSPIRE Validator assumes this is the default CRS in which the data is stored in the database and consequently the test fails to provide the image in due time for a large database. In section 7.2.4.6.8 BoundingBox of the WMS standard is written ”A Layer shall not provide a BoundingBox for a CRS it does not support. Conversely, a Layer may support CRSs for which it does not provide a BoundingBox: a server that has the ability to transform data to different CRSs may choose not to provide an explicit BoundingBox for every possible CRS available for each Layer. The server should provide BoundingBox information for at least the native CRS of the Layer (that is, the CRS in which the Layer is stored in the server’s database). ” We assume that the first one listed CRS should be default one in which the data is stored in the database. In INSPIRE the native/default CRS should not be in any case CRS:84. So either CRS:84 should not be provided at all in the GetCapabilities document if it is not listed by the user as supported CRS, either if there is a reason to keep this CRS:84 in the GetCapabilities document, then it should be the LAST one in the list (and not the FIRST as it is now). Example: Only 3035, 3857, 4258 & 4326 CRS are declared, but the request http://gmlid.eu/RO/ENV/PADS/WMS?service=WMS&request=GetCapabilities is listing CRS:84 bounding box FIRST in the list. <BoundingBox CRS=“CRS:84” minx=“19.89845971056449” miny=“42.60851659662052” maxx=“31.920387534192024” maxy=“48.91485268358077”/> <BoundingBox CRS=“EPSG:3035” minx=“2387242.0” miny=“5112395.5” maxx=“2925234.25” maxy=“5954230.5”/> <BoundingBox CRS=“EPSG:3857” minx=“2215086.4025505083” miny=“5252572.658584902” maxx=“3553361.2862302135” maxy=“6260426.012935738”/> <BoundingBox CRS=“EPSG:4258” minx=“42.60851659662052” miny=“19.89845971056449” maxx=“48.91485268358077” maxy=“31.920387534192024”/> <BoundingBox CRS=“EPSG:4326” minx=“42.60851663710712” miny=“19.898459710564484” maxx=“48.914852723390496” maxy=“31.920387534192024”/> Iurie
Priority:	Medium
Reporter:	Iurie Maxim

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085-sha1:1febeb8)