Wrap grdclip

[willschlitzer]

Wraps the gmt function grdclip.

Fixes #

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If adding new functionality, add an example to docstrings or tutorials.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

• /format: automatically format and lint the code
• /test-gmt-dev: run full tests on the latest GMT development version

[seisman]

Repeat the option for as many intervals as are needed.

It's impossible to repeat the option in Python.

[weiji14]

What if we could do it like frame (-B) in fig.basemap and pass in a list? Something like between=['0/2/1', '3/5/4']? Or a list of tuples like between=[(0, 2 ,1), (3, 5 ,4)] that expands to -Sb0/2/1 -Sb3/5/4 in GMT.

[seisman]

between=[(0, 2 ,1), (3, 5 ,4)] makes sense to me, but it needs more coding afforts.

[willschlitzer]

This is fixed in 1046419. Regarding @weiji14's suggestion, I'm assuming that would require a change to kwargs_to_strings()? Assuming so, I would prefer for this current method to be accepted as is, and a future pull request can be submitted once kwargs_to_strings is updated.

[weiji14]

Actually I was thinking of handling this feature by changing Sb='sequence'. Perhaps implementing a sequence_tuple? But yes, this can be done in a separate enhancement PR.

[seisman]

this can be done in a separate enhancement PR.

I agree.

[weiji14]

Good work @willschlitzer! After you merge this in (remember to tidy the commit message), please open up an issue to handle the enhancement mentioned at #1261 (comment). Thanks!