[Bug] MVTLayer points are only pickable in their originating tiles

Open
#8,134 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

Start by reproducing the issue in the linked CodeSandbox and trace the MVTLayer picking path. Compare picking behavior inside and outside the originating tiles; done means every rendered part of a pickable point responds to the picking API.

Written by the indexing model from the issue text.

Description

bug
Description

I have a layer with many points, the size of which fluctuates enough for their rendered area to "bleed" out of their originating tiles. When this happens the picking API only seems to work for these points within their originating tile.

Flavors
  • Script tag
  • React
  • Python/Jupyter notebook
  • MapboxOverlay
  • GoogleMapsOverlay
  • CartoLayer
  • ArcGIS
Expected Behavior

I'd expect every part of a point rendered by a pickable MVTLayer to be interactive, not just the part which is contained within each points respective tile.

Steps to Reproduce

https://codesandbox.io/s/deckgl-mvt-point-pickable-issue-qhrtp9

Environment
  • Framework version: deck.gl@8.9.0
  • Browser: 116.0.5845.187 (Official Build) (arm64)
  • OS: macOS BigSur
Logs

No response

Dominant language
TypeScript
Stars
14.6k
Forks
2.3k
Avg merge
2d 9h
Merged PRs (30d)
42

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from visgl/deck.gl

All issues in visgl/deck.gl

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.