-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Surface does not accept Cartesian values for spacing #8476
Comments
👋 Thanks for opening your first issue here! Please make sure you filled out the template with as much detail as possible. You might also want to take a look at our contributing guidelines and code of conduct. |
I can reproduce the issue using the GMT CLI, so it's more likely an upstream bug:
I'm transferring the bug report to the upstream GMT repository. |
👋 Thanks for opening your first issue here! Please make sure you filled out the template with as much detail as possible. We appreciate that you took the time to contribute! Please make sure you read our Contributing Guide and abide by our Code of Conduct. |
Description of the problem
The "surface" function does not seem to work with Cartesian (projected) values for the spacing of the new grid, e.g. "e" meters, "k" kilometers. The documentation seems to indicate that it should, and indeed, the blockmean etc. functions are tolerant of projected spacing parameters.
Minimal Complete Verifiable Example
Full error message
System information
The text was updated successfully, but these errors were encountered: