Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

mbgl-render didn't use local mbtiles

See original GitHub issue

Issue Description

I use raster png files as mbtiles but my picture is empty

mbgl-render -r 1 -c 51.388,35.7026228 -z 12 -t /home/ali/disk2/tiles/raster ~/Programming/map/TileProvider/dynamic/style_raster_test.json test.png 512 512

Issue Analytics

State:
Created 4 years ago
Comments:11

Top GitHub Comments

1reaction

brendan-wardcommented, Jan 26, 2019

@aliir74 are your tiles stored as individual PNG files on disk, or are they stored within an mbtiles file? If the former, we don’t support the use case, you would need to put a tile server in front of your tiles rather than fetching straight from disk.

In theory, someone could develop and add the functionality to use tiles directly from disk in the way you are trying to do here, but that is not something I’m available to tackle right now.

the mbtiles:// source is a convenience method for connecting directly to an mbtiles file (spec here: https://github.com/mapbox/mbtiles-spec) on disk, since we have a known pathway for querying all information we need about the tileset from the mbtiles file.

0reactions

aliir74commented, Feb 6, 2019

I changed my style address to below and the code worked. Thanks for your support!

"sources": {
    "high_update": {
      "type": "vector",
      "tiles": [
        "mbtiles://high-very-little/{z}/{x}/{y}"
      ],
      "minzoom": 3,
      "maxzoom": 16
    },
    "low_update": {
      "type": "vector",
      "tiles": [
        "mbtiles://low-very-little/{z}/{x}/{y}"
      ],
      "minzoom": 3,
      "maxzoom": 16
    }
  }