We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
I'm downloading this tile to a MBTiles: http://tile.thunderforest.com/cycle/4/8/5.png So the image has this Parameter: zoomlevel: 4 tilecolumn: 8 tilerow: 5
I have following code:
from landez import MBTilesBuilder mb = MBTilesBuilder(tiles_url="http://tile.thunderforest.com/cycle/{z}/{x}/{y}.png",filepath="C:\\Temp\\test.mbtiles") mb.add_coverage(bbox=(8.0, 47.0, 8.1, 47.1), zoomlevels=[4]) mb.run()
When I extract the tile out of the MBTiles, I get the correct Image but the wrong filename; 10.png instead of 5.png
By examining the mbtiles file I see following zoomlevel: 4 tilecolumn: 8 tilerow: 10
Why did the tilerow messed up? I have even tried using cache_scheme="wmts" but this did not change anything.
cache_scheme="wmts"
Any Idea how to get this fixed?
The text was updated successfully, but these errors were encountered:
4/8/10 is the Google naming scheme for 4/8/5 that other schemes (notably OSM) use.
4/8/10
4/8/5
You can see this in action here (the map shows both IDs): https://www.maptiler.com/google-maps-coordinates-tile-bounds-projection/#4/-4.76/48.49
Sorry, something went wrong.
No branches or pull requests
I'm downloading this tile to a MBTiles:
http://tile.thunderforest.com/cycle/4/8/5.png
So the image has this Parameter:
zoomlevel: 4
tilecolumn: 8
tilerow: 5
I have following code:
When I extract the tile out of the MBTiles, I get the correct Image but the wrong filename; 10.png instead of 5.png
By examining the mbtiles file I see following
zoomlevel: 4
tilecolumn: 8
tilerow: 10
Why did the tilerow messed up? I have even tried using
cache_scheme="wmts"
but this did not change anything.Any Idea how to get this fixed?
The text was updated successfully, but these errors were encountered: