mapbox / mapbox/mapnik-omnivore
Deeper max zoom for small data sources
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 44
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
In https://github.com/mapbox/mapnik-omnivore/pull/141 we enforced that a tileset **always** gets built down to at least z6. Still, we have problems with tilesets being generated from very small data sources.
A data source composed of a single point, for example, will get tiled down to z6 and simplification at that zoom level may lead to it appearing in completely the wrong place when viewed at z14.
As a solution, what if we allowed the dataset to continue being tiled at higher and higher max zoom levels as long as the total number of tiles at any zoom level does not exceed some threshold? This would solve the single-point problem, as well as scenarios where a few points are well-clustered. Small datasets spread out across the globe would still be problematic, since we'd probably have to calculate num tiles based on the BBOX of the data source.
cc @mapsam @GretaCB @colleenmcginnis
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
Read pull request #141 and the existing tiling and max-zoom path it changed first. Clarify the tile-count threshold and bounding-box behavior for small datasets, then define validation for a single point, clustered points, and globally distributed points; the issue is done when that behavior is agreed and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100