clabels plotting outside of projection limb
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- data-visualization
Research direction
Start with the linked Jupyter notebook and reproduce the contour-label placement using the reported Basemap and Matplotlib versions. Compare the unmasked plot with the masked-data result, then investigate Basemap's projection-limb handling around pyplot.clabel and review matplotlib/basemap#290. Done means labels appear only on visible contours for a projected subset of the globe.
Written by the indexing model from the issue text.
Description
- OS: Mac OS 10.11.4 (El Capitan)
- Matplotlib version: 1.5.1
- Basemap version: 1.0.7
- Both installed via anaconda
This issue was originally created in the matplotlib repo, but it was discussed there (matplotlib/matplotlib#6436) and decided that it should be against basemap.
The issue is that when I plot data over a basemap, and the region plotted is a subset of the globe, calling matplotlib.pyplot.clabel will place some clabels outside of the projection limb. I'm assuming it's because pyplot will create all the clabels first, and then plot the appropriate subset of data.
To illustrate this issue, here's a Jupyter notebook. The plot of the masked data represents the plot I would have expected pyplot to produce in the first place. If I choose to plot a small subset of data, clabels should be place on all visible contours, regardless of what region I plot.
Note that matplotlib/basemap#290 did not fix the issue. I can confirm that even with the basemap master compiled myself, clabels still have that issue.
- 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
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100