visgl / visgl/deck.gl

[Bug] Google Photorealistic 3d tile overlaps another layer, the overlapping layer may or may not be displayed.

Open
#7,941 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

I am using Google Photorealistic 3d tiles overlaid with GeoJsonLayer.
TerrainExtention is used for GeoJsonLayer.

When the map is moved, features in the GeoJsonLayer may or may not be displayed.
It is not that some features are missing, but that they are sometimes shown and sometimes not shown at all.

When they are not displayed, the TerrainExtension does not work and they appear to be under the Google 3D tile.

Is this a bug? Is there a workaround?

https://github.com/visgl/deck.gl/assets/5762369/e7dc58f1-86a1-4587-aba6-b96e6a354dc4

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

Overlays should always be visible.

Steps to Reproduce

Codepen
https://codepen.io/chaki1019/pen/eYQYovN

*API KEY is required.

Environment
  • Framework version: deck.gl 8.9.18
  • Browser: Chrome
  • OS: mac (M2)
Logs

No response

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.

Research direction

Start with the linked CodePen reproduction using deck.gl 8.9.18, then inspect the GeoJsonLayer and TerrainExtension behavior when Google Photorealistic 3D tiles are present. Compare frames where the overlay is visible and hidden; done means the GeoJsonLayer remains visible while the map is moved.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
computer-graphics, data-visualization, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.