grdtrack -E struggles

Added by John 5 months ago

I'm working with a lon/lat 0.5° grid cap that surrounds the South Pole (north to -60° lat, i.e., -R-180/180/-90/-60). I'd like to use grdtrack to sample the grid along a specific meridian.

Given the grid file (wedsn) and a specific longitude (lon), an error message results when trying:

> grdtrack -G$wedsn -E$lon/-60,$lon/-90+i0.125d > t1.xyz
grdtrack [ERROR]: Syntax error -E: Valid coordinate codes are [lcr][bmt] and z[+-]
ERROR: Caught signal number 11 (Segmentation fault) at
0 libgmt.6.dylib 0x000000010c10b58e GMT_grdtrack + 9038
1 ??? 0x0000000000000030 0x0 + 48
Stack backtrace:
0 libgmt.6.dylib 0x000000010bee8a63 sig_handler + 579
1 libsystem_platform.dylib 0x00007fffb0d5db3a _sigtramp + 26
2 ??? 0x0000000000000000 0x0 + 0
3 libgmt.6.dylib 0x000000010bf000f0 GMT_Call_Module + 272
4 grdtrack 0x000000010bedef7e main + 1038
5 libdyld.dylib 0x00007fffb0b4e235 start + 1

The -E error indicates that grdtrack is oblivious to the fact that I gave it start/stop style of instruction. Is there a syntax error that I'm committing? Thanks!


Replies (3)

RE: grdtrack -E struggles - Added by John 5 months ago

Figured it out - I was using a comma between coordinate pairs when it should be a slash.

I.e., the specification should be -E$lon/-60/$lon/-90+i0.125d this works

RE: grdtrack -E struggles - Added by Joaquim 5 months ago

John, it helps a lot that the trouble reports come with a reproducible example by us. Script snippets like -E$lon/-60,$lon/-90+i0.125d are hardly usable.

RE: grdtrack -E struggles - Added by John 5 months ago

See my edited previous posting - I figured it out. It was my inserting a comma where a slash was needed. Man page has -Eline[,line] and I mistook that comma as a separator for the start/stop.

(1-3/3)