Closed mkbarker closed 1 year ago
👋 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.
The triangular feature is most likely due to a dimension (say length of a column) that is off by 1 and hence points are placed successively off by one as we go across. This also explains why the triangle might go the other way (the dimension is 1 less or 1 more).
GMT 6.4.0 'surface' routine crashes with this:
gmt blockmedian Site01_scatInterp_v1_final_adj.xyzi -bi4 -R-19/-3/-20/-4 -I0.005 -C -bo3 -r | gmt surface -r -bi3 -R-19/-3/-20/-4 -I0.005 -T0.75 -Gtmp.grd -C0.001 -Ll-11 -Lu11 -Vd
If I leave out the -L flags, then it doesn't crash, but the resulting grid file (tmp.grd) is not correct (it looks like two big triangles).
If I leave out the -r flags (from both blockmedian and surface), then it doesn't crash, and the resulting grid file is correct, but it is gridline registered, which is not what I want.
If I decrease the resolution to 0.01 instead of 0.005 (and keep the -r and -L flags), then it produces the correct pixel-registered grid file.
Full script that generated the error
Link to input file. 1
Full error message
Actual outcome
Incorrect grid file with two triangle-like features:
Expected outcome
Correct grid file with topography:
System information
gmt --version
): 6.4.0