You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rename outfile parameter in surface to be outgrid #1441
As mentioned at #1439 (comment), most PyGMT functions which return a grid output have a parameter called outgrid, but the surface function uses outfile. It would be best to standardize the name to be outgrid instead.
This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is data or table for all modules moving forward. Currently, this is the distribution:
data parameter: surface, wiggle, velo, rose, plot3d, plot, contour table parameter: blockmedian, blockmean, histogram
other: grdtrack (points), text (textfiles)
It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]
This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is data or table for all modules moving forward. Currently, this is the distribution:
data parameter: surface, wiggle, velo, rose, plot3d, plot, contour table parameter: blockmedian, blockmean, histogram
other: grdtrack (points), text (textfiles)
It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]
Perhaps we need to open a separate issue to discuss it.
This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is data or table for all modules moving forward. Currently, this is the distribution: data parameter: surface, wiggle, velo, rose, plot3d, plot, contour table parameter: blockmedian, blockmean, histogram
other: grdtrack (points), text (textfiles)
It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]
Perhaps we need to open a separate issue to discuss it.
Activity
maxrjones commentedon Aug 18, 2021
This is somewhat related - I am not sure if it's worth a deprecation but I think we should decide on whether the parameter for tabular input is
dataortablefor all modules moving forward. Currently, this is the distribution:dataparameter: surface, wiggle, velo, rose, plot3d, plot, contourtableparameter: blockmedian, blockmean, histogramother: grdtrack (
points), text (textfiles)It would also be worthwhile to set a consistent order for the positional arguments x, y, [z], data, [outfile]
maxrjones commentedon Aug 19, 2021
@obaney will be working on this issue!
seisman commentedon Sep 1, 2021
Perhaps we need to open a separate issue to discuss it.
weiji14 commentedon Sep 1, 2021
Yep, just opened #1479. Let's discuss there.