[Geoserver-devel] [JIRA] (GEOS-10902) WMTS GetCapabilities from Geoserver provides WebMercatorGrid MatrixSet with wrong axis order

_Failed_to_Retrieve · March 21, 2023, 10:32pm

WMTS GetCapabilities from Geoserver provides WebMercatorGrid MatrixSet with wrong axis order

Issue Type:	Bug
Affects Versions:	2.22.0
Assignee:	Unassigned
Components:	GWC, WMTS
Created:	21/Mar/23 11:32 PM
Environment:	Geoserver 2.22.0 deployed to Wildfly using integrated GWC
Priority:	Medium
Reporter:	Mitchell Bösecke

In Geoserver, I’m fetching a WMTS capabilities document and the built-in WebMercatorGrid matrix set seems to have the axis order in northing/easting, but my understanding is that EPSG:3857 is defined by EPSG as having an axis order of easting/northing.

Here is the relevant section of the XML returned by Geoserver:

&lt;TileMatrixSet&gt;
  &lt;ows:Identifier&gt;WebMercatorQuad&lt;/ows:Identifier&gt;
  &lt;ows:SupportedCRS&gt;urn:ogc:def:crs:EPSG::3857&lt;/ows:SupportedCRS&gt;
  &lt;TileMatrix&gt;
    &lt;ows:Identifier&gt;0&lt;/ows:Identifier&gt;
    &lt;ScaleDenominator&gt;5.59082264028717E8&lt;/ScaleDenominator&gt;
    &lt;TopLeftCorner&gt;2.003750834E7 -2.003750834E7&lt;/TopLeftCorner&gt;
    &lt;TileWidth&gt;256&lt;/TileWidth&gt;
    &lt;TileHeight&gt;256&lt;/TileHeight&gt;
    &lt;MatrixWidth&gt;1&lt;/MatrixWidth&gt;
    &lt;MatrixHeight&gt;1&lt;/MatrixHeight&gt;
  &lt;/TileMatrix&gt;
  ...
&lt;/TileMatrixSet&gt;

The top left corner is shown as “2.003750834E7 -2.003750834E7” but I believe it should be reversed.

This is causing problems with OpenLayers as a client (layer doesn’t show up at all). The client should be intelligent enough to detect projects with reversed axis orders but I don’t think EPSG:3857 is supposed to have a reversed axis order? Looking at the official spec for the WebMercatorQuad tile matrix set lists the top left corner as -20037508.3427892 20037508.3427892. This is expected and differs from the order I get from Geoserver.

If I switch to the legacy “EPSG:900913” matrix set provided by Geoserver, everything works as expected.

Is this a bug in Geoserver or am I misunderstanding something?

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#100218-sha1:518c67a)