[Feat] Allow to move deck.gl layers over Google Maps Layers (labels, POIs...)
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
When using deck.gl with Vector Google Maps, labels, POIs and other Google Maps layers are placed over Deck.gl layers as it can be seen in the image:
That's not happening with rasterized Google Maps as everything is an image and layers are placed over the image.
Proposal
It would be great to be able to decide if we want to have Google Maps Layers over Deck.gl layers or not. In some cases I guess it is ok to have Google Maps Layers on top, but in others like our case, it is not really useful to have them over.
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 files, tests, or entry points are identified in the issue. Start by tracing deck.gl's Google Maps vector integration and how Google Maps layers are ordered relative to deck.gl layers; define the supported layer-ordering behavior and its configuration surface before implementation.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100