Mitchell Bösecke (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A142b1920-d511-42d9-aec4-d0be666c3f55
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNWMyMzFmMjc3MTlhNDZmMTg1YjVhN2UzMjIxNTNkODAiLCJwIjoiaiJ9
) / Bug (
https://osgeo-org.atlassian.net/browse/GEOS-10902?atlOrigin=eyJpIjoiNWMyMzFmMjc3MTlhNDZmMTg1YjVhN2UzMjIxNTNkODAiLCJwIjoiaiJ9
) GEOS-10902 (
https://osgeo-org.atlassian.net/browse/GEOS-10902?atlOrigin=eyJpIjoiNWMyMzFmMjc3MTlhNDZmMTg1YjVhN2UzMjIxNTNkODAiLCJwIjoiaiJ9
) WMTS GetCapabilities from Geoserver provides WebMercatorGrid MatrixSet with
wrong axis order (
https://osgeo-org.atlassian.net/browse/GEOS-10902?atlOrigin=eyJpIjoiNWMyMzFmMjc3MTlhNDZmMTg1YjVhN2UzMjIxNTNkODAiLCJwIjoiaiJ9
)
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 (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A142b1920-d511-42d9-aec4-d0be666c3f55
)
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:
<TileMatrixSet>
<ows:Identifier> WebMercatorQuad </ows:Identifier>
<ows:SupportedCRS> urn:ogc:def:crs:EPSG::3857 </ows:SupportedCRS>
<TileMatrix>
<ows:Identifier> 0 </ows:Identifier>
<ScaleDenominator> 5.59082264028717E8 </ScaleDenominator>
<TopLeftCorner> 2.003750834E7 -2.003750834E7 </TopLeftCorner>
<TileWidth> 256 </TileWidth>
<TileHeight> 256 </TileHeight>
<MatrixWidth> 1 </MatrixWidth>
<MatrixHeight> 1 </MatrixHeight>
</TileMatrix>
...
</TileMatrixSet>
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 (
https://github.com/openlayers/openlayers/blob/main/src/ol/source/WMTS.js#L451 )
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 (
http://docs.opengeospatial.org/is/17-083r2/17-083r2.html#63 ) 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?
(
https://osgeo-org.atlassian.net/browse/GEOS-10902#add-comment?atlOrigin=eyJpIjoiNWMyMzFmMjc3MTlhNDZmMTg1YjVhN2UzMjIxNTNkODAiLCJwIjoiaiJ9
) Add Comment (
https://osgeo-org.atlassian.net/browse/GEOS-10902#add-comment?atlOrigin=eyJpIjoiNWMyMzFmMjc3MTlhNDZmMTg1YjVhN2UzMjIxNTNkODAiLCJwIjoiaiJ9
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100218-
sha1:518c67a )
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
