Ortho projection fails at south pole in pcolormesh
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
- matplotlib, python
- Domain
- data-visualization
Research direction
Reproduce the issue with the provided north- and south-pole Basemap examples using pcolormesh and pcolor, then inspect the Basemap pcolormesh implementation and its projection handling. The fix is complete when south-pole orthographic pcolormesh produces the same correct map as pcolor without regressing the north-pole case.
Written by the indexing model from the issue text.
Description
I am plotting gridded satellite data using basemap 1.0.7 (I can't get 1.0.8 via pip yet). The grid is 0.25 degrees resolution, global coverage.
For polar views, I use pcolormesh. It works fine for the north polar view:
bmap = Basemap(projection='ortho', lat_0=90, lon_0=270, resolution='c')
show_map = bmap.pcolormesh(lons, lats, darray, vmin=vminval, vmax=vmaxval,
norm=norm, cmap=this_cmap, alpha=1.0, latlon=True)
but the corresponding map centered on the south pole plots garbage:
bmap = Basemap(projection='ortho', lat_0=-90, lon_0=270, resolution='c')
show_map = bmap.pcolormesh(lons, lats, darray, vmin=vminval, vmax=vmaxval,
norm=norm, cmap=this_cmap, alpha=1.0, latlon=True)
However, pcolor plots correctly at the south pole. This one is fine:
bmap = Basemap(projection='ortho', lat_0=-90, lon_0=270, resolution='c')
show_map = bmap.pcolor(lons, lats, darray, vmin=vminval, vmax=vmaxval,
norm=norm, cmap=this_cmap, alpha=1.0, latlon=True)
In this case, my gridded data array is pretty small and the time difference between pcolormesh and pcolor is negligible, but I'm guessing this is something that ought to be fixed, unless it already has been addressed in 1.0.8.
- Dominant language
- Python
- Stars
- 817
- Forks
- 395
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from matplotlib/basemap
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
matplotlib/basemap#368 ·
-
Python 3.14 wheels Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
matplotlib/basemap#652 · 2 comments · 5 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
matplotlib/basemap#649 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
matplotlib/basemap#646 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
matplotlib/basemap#645 · 2 comments ·
All issues in matplotlib/basemap
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100