-
Notifications
You must be signed in to change notification settings - Fork 637
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
Missing Sprite images? #1345
Comments
That error in the console doesn't necessarily indicate an issue, bit it does mean there is no matching sprite found that your style asked for. You could have a working sprite sheet an not have every spite the style asks for. For example, osm-bright only includes these icons However the reason you see that warning, is because in style.json there is something like this layer "poi-level-3", which asks for icons like In my own project I ended up trying to add a lot of those missing icons |
Thanks Does anyone know if there is are definitive sprite json/png files I can use that will show everything requested? |
Not that I am aware of. My sprites probably come the closest because I actually tried to add all the icons that I saw were missing in the console errors you mentioned. You are welcome to download the spite files from my theme at https://github.com/acalcutt/wifidb-tileserver-gl/tree/master/tileserver-gl/styles/WDB_OSM |
I've used the docker installation to load the tileserver which works well, and I can view the maps etc
docker run --rm -it -v /docker-sets/maps:/data -p 8080:8080 maptiler/tileserver-gl --file planet.mbtiles --verbose
But when I view the developer toolbar, I see lots of "missing" errors in the console window
i.e. when loading the URL
:8080/styles/osm-bright/#17.23/-34.103519/18.81684
I get around 10 "missing" messages:
util.ts:267 Image "gate_11" could not be loaded. Please make sure you have added the image with map.addImage() or a "sprite" property in your style. You can provide missing images by listening for the "styleimagemissing" map event.
Is this a problem with the docker command, or something I've missed?
The text was updated successfully, but these errors were encountered: