[Bug] MVT Layer renders tile incorrectly.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
Viewing the attached file representing tile 15/9369/12537 renders incorrectly:
I loaded the tile into QGIS and the geometry is all valid and displays correctly:
Which leads me to believe this is a client-side rendering issue.
Flavors
- Script tag
- React
- Python/Jupyter notebook
- MapboxOverlay
- GoogleMapsOverlay
- CartoLayer
- ArcGIS
Expected Behavior
The polygon interior shouldn't spill out like it is.
Steps to Reproduce
View the tile =D
Environment
- Framework version: v9.0.14
- Browser: Chrome
- OS: Debian Linux
Logs
No response
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 loading the attached tile.mvt.zip with the GoogleMapsOverlay flavor using deck.gl v9.0.14 in Chrome on Debian Linux, then compare the rendered polygon with its QGIS display. Trace the rendering path from GoogleMapsOverlay to identify where the polygon interior spills outside its geometry. Done means the supplied tile renders with the expected polygon interior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100