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

WMTS not working with EPSG:3948 and 2154 since 2023.02.00-RC*-geOrchestra deployments #660

Open
rgoffinet opened this issue Oct 25, 2023 · 1 comment

Comments

@rgoffinet
Copy link

rgoffinet commented Oct 25, 2023

Describe the bug
Since the deployment of 2023.02.00-RC*-geOrchestra releases, we can't use WMTS services in MapStore contexts using EPSG:2154 or EPSG:3948.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new Mapstore context
  2. Add as basemap a WMTS with geowebcache for EPSG:3857 and EPSG:2154 or 3948 projections
  3. Switch between SRS : you'll see that the WMTS only works with EPSG:3857. For the others ESPGs, no requests are send by MS in the browser consol and no error message is displayed.

Expected behavior
Beeing able to switch beetween SRS in our contexts using WMTS, as we do in 2022.02.02.

Screenshots
WMTS_dfftCRS_202302RC_issue

Desktop :

  • Browser : firefox 102.14 (32bits) ; chrome 116.0.5845 (64 bits) ; Edge 115.0.1901 (64 bits)
  • MapStore : 2023.02 RC1, RC2 & RC3

Additional context

  • The WMTS we use in this example works fine in 2022.02.02.
  • WMS works fine, only WMTS are concerned by this issue.
@catmorales
Copy link
Collaborator

@tdipisa could you, please, check this issue, we have seen a regression in the RC3 with this use case.
We'll be needing it very soon.
Thank you so much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants