[Bug] Pixelated Layers on GoogleMapsOverlay using WebGL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
When using the GoogleMapsOverlay interleaved with a vector base map the lines become blurry. After some digging it has something to do with the canvas size vs the rendered canvas. useDevicePixel is set to true by default, but to remove the blur it needs to be even higher. However doing this will completely break the map.
Not sure how to fix this and for now I'm just not using interleaved.
Flavors
- React
- Python/Jupyter notebook
- MapboxLayer
- GoogleMapsOverlay
- CartoLayer
- DeckLayer/DeckRenderer for ArcGIS
Expected Behavior
No response
Steps to Reproduce
Use the standard GoogleMapsOverlay with default settings on a vector Google Map. The lines will then be blurry when compared to a non vector map.
You can see a comparison below.
Environment
- Framework version: 8.8.13
- Browser: Brave
- OS: MacOS Monerey 12.3.1
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 with the standard GoogleMapsOverlay using default settings on a vector Google Map, then compare its line rendering with a non-vector map and the non-interleaved configuration. Done means the lines render sharply while GoogleMapsOverlay remains interleaved, without increasing the pixel ratio enough to break the map.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- computer-graphics, data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100