-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Serving raster tiles source #9280
Comments
@MaxDragonheart please see mapbox/tilejson-spec#51. Relative URLs for tile endpoints are not supported. |
Thank you @sgillies for the answare. Unfortunatly even if I change the url from relative to absolute, using this path |
Do you mean "http://127.0.0.1:8000/static/raster/tiles/quarto/{z}/{x}/{y}.png" I'll also point out that you should include a minzoom and maxzoom when you create the source, so Mapbox-GL knows when tiles are available:
You probably don't mean to add minzoom and maxzoom on the layer though. (Did you really generate tiles all the way to zoom 22? Sounds...excessive?) |
@MaxDragonheart it looks like there are some suggestions here to help you diagnose the problem in your application, so I'm going to close this issue. For future "how do I" questions like this, please refer to our help documentation, and if you can't find the answer there, contact support. This issue tracker is for reporting bugs and feature requests. Thank you! |
I'm trying to add a tiles as source layer on my map based on GeoDjango. I've followed the indication in this example even if is related to the map style.
For generate my tiles I've used gdal2tiles with this simple python's script:
I've used the code below to add my tiles on the map:
In console I see the errors below:
If I use a tile's path
/static/raster/tiles/quarto/20/565480/654951.png
I can see that image.The strange thing is that are called folders and images nonexistent and not the real folders and images.
I think that I use this tiles in wrong way.
Someone can explain to me how I must use this feature in a correct way?
The text was updated successfully, but these errors were encountered: