-
Notifications
You must be signed in to change notification settings - Fork 49
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
Local tiles support #165
Comments
local tiles? we didn't even know it worked at all, never tried this. Adding examples here of what did work and and not anymore would help. But we won't garantee quick solution. |
The tiles were named in a fashion similar to Bing tiles, as seen here. So, I have a directory full of tiles with names like 010203010.png (as an exmaple). To make these tiles work with QMS, I would duplicate the Bing service to create a user service. I would then modify the metadata.ini file, changing the url from bing to the local address where my tiles were stored, (e.g. C:\Tiles{q}.png) After the recent updates to QMS, this no longer works. The tiles do not load, nor do they show an error message indicating that the tiles failed to load. |
this is some easter egg kind of use we had no idea existed :) first try switching from native provider to QMS one, under QMS Settings/Tiles etc. and try again |
... though it won't work in QGIS 3 |
Switching off the native renderer did the trick! Any insight as to why the native renderer doesn't allow the tiles to show up? And are there any plans to incorporate the ability to load local tiles in future QMS releases? |
Did you end up trying in 2.x? Native renderer is faster (somewhat), but limited, needs work to cover such rare cases too. Local tiles support would be a nice feature. |
On previous installations of QMS, metadata.ini files could be modified to load local map tiles. The newer updates since QGIS 3.0 has been released have broken this functionality. While this solution was a workaround (local tiles support SHOULD be a part of QMS), it is now broken.
The text was updated successfully, but these errors were encountered: