xref #1318 and #2722.
When working on the tutorial for table inputs in PyGMT, I realized that the behavior of table inputs are still inconsistent.
Generally speaking, there are two different ways to pass tables into PyGMT: via data or via x/y/z. For data, it can be a file, a pandas.DataFrame, a 2-D NumPy array. Currently, some functions/methods don't support x/y/z. We need to check all methods/functions to make sure they have consistent behavior for table inputs.
This issue is a central place to track the progress. Here is the list of methods/functions that we may need to check:
xref #1318 and #2722.
When working on the tutorial for table inputs in PyGMT, I realized that the behavior of table inputs are still inconsistent.
Generally speaking, there are two different ways to pass tables into PyGMT: via
dataor viax/y/z. Fordata, it can be a file, a pandas.DataFrame, a 2-D NumPy array. Currently, some functions/methods don't support x/y/z. We need to check all methods/functions to make sure they have consistent behavior for table inputs.This issue is a central place to track the progress. Here is the list of methods/functions that we may need to check:
binstatsblockm*contour[dataorx/y/z]filter1dgrdtrackhistograminfolegendmecanearneighborplotplot3dprojectrose[dataorlength/azimuth]selectsph2grdsphdistancesphinterpolatesurface[dataorx/y/z]ternarytexttriangulate[dataorx/y/z]velowiggle[dataorx/y/z]xyz2grd[dataorx/y/z]x2sys_cross