tilelive-copy hangs at minzoom of 5 or more
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 540
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
I am using tilelive-copy to generate mbtiles. If I specify a minzoom of 5 or more, it hangs. It works fine for minzoom 4, 3, 2, 1. The mapnik xml is attached (change minzoom to whatever is passed through the CLI) and also the data file.
tracts_data.xml.zip
The tracts.sqlite
tracts.sqlite.zip
file is attached.
Hangs
./tilelive-copy bridge:////Users/mehtab/projects/mbtiles-automation/app/data/tracts_data.xml mbtiles:////Users/mehtab/projects/mbtiles-automation/app/data/tracts.mbtiles --scheme=pyramid --minzoom=5 --maxzoom=16 --bounds=-180,-85.0511,180,85.0511 --slow=1000 --timeout=120000
Does not hang
./tilelive-copy bridge:////Users/mehtab/projects/mbtiles-automation/app/data/tracts_data.xml mbtiles:////Users/mehtab/projects/mbtiles-automation/app/data/tracts.mbtiles --scheme=pyramid --minzoom=4 --maxzoom=16 --bounds=-180,-85.0511,180,85.0511 --slow=1000 --timeout=120000
Help!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tilelive-copy CLI and reproduce the difference between --minzoom=5 and --minzoom=4 using the attached tracts_data.xml and tracts.sqlite files. Trace where the pyramid scheme processes these inputs and verify that minzoom 5 and higher complete without hanging while the existing minzoom 4 case still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100