Globe projection rendering issues around the poles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
**mapbox-gl-js version**:
v2.9.1
**browser**:
Tested with the same outcome in latest versions of Google Chrome, Firefox and Safari.
### Steps to Trigger Behavior
Draw a polyline passing near the North Pole, use satellite map (I used the [bathymetry map](https://www.mapbox.com/blog/new-bathymetry-tileset-and-style-for-marine-maps)).
### Link to Demonstration
I can email a link if need be, not a public site.
### Bugs
1. Layers are not always fetched at a higher resolution on floating point zoom, such as when scrolling, causing the viewport to remain a low-res raster indefinitely (note vector layer is also rasterized), see 1.png. Resolves if I zoom in more.
2. Little white dots along tile boundaries (subtle, but highlighted with orange arc superimposed on the image under the dots), see 1.png. More glaring when panning.
3. Clipping causing large white triangles/polygons near the pole, see 2.png.
4. A red polyline near the pole shows as an enormous red polygon (interpolation to fill the gap near the pole also affecting layers on top of the base style?), see 2.png.


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 reproducing the reported pole-crossing behavior using the stated v2.9.1 steps, the bathymetry map, and the attached images; no source file, test, or public demonstration is identified. Done means addressing the four reported symptoms: low-resolution tiles, tile-boundary dots, polar clipping, and the oversized polyline polygon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- computer-graphics, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100