Tile Pack Batches
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 296
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Mapbox iOS SDK hints that it may be possible to customize the batch sizing of tile packs. I would like to create a batch for 11-12 since I don't need >=13 and it's throwing me over the 750 limit.
` The zoom leveling scheme for the tile batches can be defined in Tile JSON, otherwise the default scheme is used...`
```swift
@property (nonatomic, readonly, nonnull, copy) NSString *styleURI;
/**
* Minimum zoom level for the tile package.
*
* Note: the implementation loads and stores the loaded tiles
* in batches, each batch has a pre-defined zoom range and it contains
* all child tiles within the range. The zoom leveling scheme for the tile
* batches can be defined in Tile JSON, otherwise the default scheme is used:
* - Global coverage: 0 - 5
* - Regional information: 6 - 10
* - Local information: 11 - 14
* - Streets detail: 15 - 16
*
* Internally, the implementation maps the given tile pack zoom range
* and geometry to a set of pre-defined batches to load, therefore
* it is highly recommended to choose the `minZoom` and `maxZoom` values
* in accordance with the tile batches zoom ranges (see the list above).
*/
```
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
No repository file, test, or implementation entry point is identified in the issue. Start by reviewing the Tile JSON specification and the referenced Mapbox iOS SDK behavior, then determine whether customizable zoom batch ranges belong in the specification; done should be a decided, documented scope for supporting the requested 11–12 batch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100