Shiftdata breaks pcolormesh wrapping

Open
#183 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
matplotlib, numpy, python

Research direction

Start by running the provided Basemap 1.0.7 reproduction with pcolormesh and compare the lon_0=0 and lon_0=180 plots. Inspect the shiftdata path used by pcolormesh wrapping; done means the extra row and column remain ignored and the shifted plot matches the expected global grid.

Written by the indexing model from the issue text.

Description

I have a data grid which spans the whole globe from -180 -> 180. pcolormesh can plot this OK if I have lon_0=0 in which case Basemap doesn't have to do any wrapping
pcolormesh_ok

However if I do this for lon_0=180 (where Basemap has to shift some data), I get the following incorrect plot:
pcolormesh_bad

The code I have used for this is (using 1.0.7):

    import numpy as np
    from mpl_toolkits.basemap import Basemap
    import matplotlib.pyplot as plt
    x = np.arange(-180, 190, 10)
    y = np.array([40, 50, 60])
    data = np.arange(72).reshape((2, 36))
    xv, yv = np.meshgrid(x, y)
    # Add an empty row and column of data so that the data is the same shape as X,Y
    wider_data = np.ma.zeros(xv.shape)
    for index, v in np.ndenumerate(data):
        wider_data[index] = data[index]
    for lon in (0, 180):
        map = Basemap(lon_0=lon)
        map.drawparallels(np.arange(-90, 90, 20), labels=[1, 1, 0, 1])
        map.drawmeridians(np.arange(-180, 180, 30), labels=[1, 1, 0, 1])
        map.pcolormesh(xv, yv, wider_data, latlon=True)
        map.drawcoastlines()
        plt.show()

I suspect that this problem is related to https://github.com/matplotlib/basemap/issues/182 because to get around that issue, I have had to add an empty row and column to the data. This should still be OK though, since that extra data should just be ignored (from the pcolormesh docs).

However, what actually happens is that the empty row gets moved around because shiftdata doesn't know it should ignore and so the plot is wrong.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matplotlib/basemap

All issues in matplotlib/basemap

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.