LocalTileFile implementation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Target Use case
A localTileFile layer would make it far easier for general users to work with deck.gl, by simplifying the process of accessing local {z}/{x}/{y} tile data. Being able to create application that work from a single machine particularly with sensitive local data is a major use case
Proposed feature
Suggest creating a LocalTileFile layer similar to what has been done recently in Ipyleaflet see https://ipyleaflet.readthedocs.io/en/latest/api_reference/local_tile_layer.html
To Do List
- Add label and assign to milestone
- Coding
- Doc update
- What’s new update
- Test
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 by reviewing deck.gl's existing layer implementations and the linked ipyleaflet LocalTileLayer documentation. Clarify the expected API for accessing local {z}/{x}/{y} tile data, then define the coding, documentation, what's-new, and test work needed for a complete LocalTileFile feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100