mapbox / mapbox/rio-mbtiles

missing tile table

Open
#79 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
137
Forks
36
PR merge metrics
No merged PRs in 30d

Description

when i use the command
`rio mbtiles --zoom-levels 1..5 -j 8 1.tif -o 2.mbtiles`

it comes out with a few warnings like
`D:\Anaconda\envs\rio\lib\site-packages\mercantile\__init__.py:79: FutureWarning: Mercantile 2.0 will require tile x and y to be within the range (0, 2 ** zoom)
FutureWarning,
D:\Anaconda\envs\rio\lib\site-packages\mercantile\__init__.py:79: FutureWarning: Mercantile 2.0 will require tile x and y to be within the range (0, 2 ** zoom)
FutureWarning,
D:\Anaconda\envs\rio\lib\site-packages\mercantile\__init__.py:79: FutureWarning: Mercantile 2.0 will require tile x and y to be within the range (0, 2 ** zoom)
FutureWarning,`

And the mbtiles format result cannot be opened for missing tiles table.

I know few about this field, please help me if you know why this happens, thank you!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the `rio mbtiles` command with the reported zoom levels and inspect the generated MBTiles SQLite file for its tables. Check how the command handles the Mercantile tile-coordinate warnings and determine why the `tiles` table is absent. Done means the command produces an MBTiles file that opens with the expected tiles table.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sqlite
Domain
cli, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.