Magnetic coordinates and lines drawing across the world map
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- data-visualization
Research direction
Start by reproducing the magnetic-coordinate map shown in figure_1 and trace how Basemap.call() transforms coordinates before _readboundarydata() creates coastlines and polygons. Read the existing east/west dateline-crossing logic to determine how it relates to projection boundaries. Done means coastlines and polygons are correctly broken at the left and right plot edges for magnetic coordinates.
Written by the indexing model from the issue text.
Description
I'm extending basemap to work with magnetic coordinates. Basically, latitude longitude are converted to/from magnetic coordinates during calls to Basemap.__call__(). However, I get results like this:
It seems that coastlines/polygons are not properly "broken" on the left/right plot edges. I suspect I have to change something in _readboundarydata() to fix this (since that's where the coastlines and polygons are initiated), and I have had a look at it, but I do not really see what I would need to change. I don't even see how this is handled in the normal (geographic coordinates) case. There are some references to the crossing of east/west datelines, are these "datelines" the left/right map boundaries in projections like the above? I don't really understand what this part of the code accomplishes.
Any tips?
- 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
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·