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

QGIS does not handle WMTS layers that use EPSG:5042 correctly #59111

Open
2 tasks done
cmorriscmps opened this issue Oct 16, 2024 · 1 comment
Open
2 tasks done

QGIS does not handle WMTS layers that use EPSG:5042 correctly #59111

cmorriscmps opened this issue Oct 16, 2024 · 1 comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! WMTS data provider

Comments

@cmorriscmps
Copy link

cmorriscmps commented Oct 16, 2024

What is the bug or the crash?

  1. WMTS layers with a TileMatrixSet that uses EPSG:5042 that have a BoundingBox for EPSG:5042 will not display at all.
  2. WMTS layers with a TileMatrixSet that uses EPSG:5042 that do not have a BoundingBox for EPSG:5042 will display, but not at the correct location.
  3. WMTS layers with a TileMatrixSet that uses the related CRS EPSG:5041 do work correctly.

Steps to reproduce the issue

Download https://raw.githubusercontent.com/cmorriscmps/staticwmts/refs/heads/main/bounds.csv and https://raw.githubusercontent.com/cmorriscmps/staticwmts/refs/heads/main/pole.csv to your local file system.

To test number 1:

  • Create a new project (Project->New)
  • Go to Layer->Add Layer->Add WMS/WMTS Layer
    -- Create a New WMTS using URL https://raw.githubusercontent.com/cmorriscmps/staticwmts/refs/heads/main/antarctic.xml
    -- Connect to the WMTS and add the BlueMarble layer
  • Go to Layer->Add Layer->Add Vector Layer
    -- For source type, select File
    -- For source, select the pole.csv file
    -- In Options, enter x for X_POSSIBLE_NAMES and y for Y_POSSIBLE_NAMES.
    -- Press the Add button.
  • Go to Layer->Add Layer->Add Vector Layer
    -- For source type, select File
    -- For source, select the bounds.csv file
    -- In Options, enter x for X_POSSIBLE_NAMES and y for Y_POSSIBLE_NAMES.
    -- Press the Add button.
  • Right click on the bounds layer in the Layers panel and Zoom to the layer.

You will see points at the lower-left and upper-right bounds of the tile matrix and at the pole. You will not see any imagery from the WMTS.

To test number 2, repeat the steps but use https://raw.githubusercontent.com/cmorriscmps/staticwmts/refs/heads/main/antarctic_no_bb.xml for the WMTS URL. You will see imagery from the WMTS, but it will not be within the boundary points.

To test number 3, repeat the steps but use https://raw.githubusercontent.com/cmorriscmps/staticwmts/refs/heads/main/arctic.xml for the WMTS URL. You will see imagery from the WMTS, located properly within the boundary points.

Versions

QGIS version
3.38.3-Grenoble
QGIS code revision
37f9e6e
Qt version
5.15.13
Python version
3.12.6
GDAL/OGR version
3.9.2
PROJ version
9.4.0
EPSG Registry database version
v11.004 (2024-02-24)
GEOS version
3.12.2-CAPI-1.18.2
SQLite version
3.45.1
PDAL version
2.6.3
PostgreSQL client version
16.2
SpatiaLite version
5.1.0
QWT version
6.2.0
QScintilla2 version
2.14.1
OS version
Windows 11 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

@cmorriscmps cmorriscmps added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Oct 16, 2024
@cmorriscmps
Copy link
Author

Screen shot of problem 2.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! WMTS data provider
Projects
None yet
Development

No branches or pull requests

2 participants