Skip to content
This repository has been archived by the owner on Jun 11, 2020. It is now read-only.

Position gap between WMS ans WMTS #1

Open
deregnab opened this issue Apr 18, 2019 · 2 comments
Open

Position gap between WMS ans WMTS #1

deregnab opened this issue Apr 18, 2019 · 2 comments
Assignees

Comments

@deregnab
Copy link

I'm currently trying to use your Docker container in order to run a qgis server in local which will be replaced by a remote one in the future.
I encountered an issue while using WMTS with your server, there is a gap between WMS's position and WMTS's position while I was trying to figure out which one was the best for my usage.

I checked with OpenStreetMap and I found that WMS is working correctly, but WMTS had a difference in the extents which seemed to be the cause of the gap.

I have a project with the following extents for both WMS and WMTS :

wms -535425.6245270000072196,1149635.6791090006008744 : 1600829.6177129996940494,3285890.9213490001857281
wmts 669182.0000000000000000,1808260.0000000000000000 : 756362.0000000000000000,1887030.0000000000000000

the gap becoming wider with some projections (e.g. 3035) resulting in tiles formed in a weird way.

Is the docker expected to work with WMTS?

@rldhont
Copy link
Contributor

rldhont commented Apr 18, 2019

Hi @deregnab,

It's an issue in QGIS Server. I have to redo the way to work with precisions and extents.

@deregnab
Copy link
Author

Thanks for your reply

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

No branches or pull requests

2 participants