While exploring various WMTS services, I've observed that sometimes x, y pair displayed in TopLeftCorner tag of TileMatrix tags defined in TileMatrixSet have succession changed to y, x.
There are at least two samples of AFAIK wrong succession. See for example:
(for EPSG:2180 TileMatrixSet and EPSG:4326 TileMatrixSet), and
(for 3006 TileMatrixSet and WGS84 TileMatrixSet).
In the latter example, succession used in definition of TopLeftCorner:
is in contradiction with definition of BoundingBox a few lines above:
<ows:BoundingBox crs="urn:ogc:def:crs:EPSG:6.3:3006"> <LowerCorner>-1200000.000000 4305696.000000</LowerCorner> <UpperCorner>2994304.000000 8500000.000000</UpperCorner> </ows:BoundingBox>
despite the fact that LowerCorner, UpperCorner and TopLeftCorner should use the same ows:PositionType definition from schemas-opengis-net-ows-1.1.0-owsCommon.xsd:
Position instances hold the coordinates of a position in a coordinate reference system (CRS) referenced by the related "crs" attribute or elsewhere.
I wonder how to copy with such discrepancies when processing WMTS GetCapabilities response automatically. Is this problem addressed in some way in existing software packages?