Skip to content

Conversation

@PaulWessel
Copy link
Member

For whatever reason, while grdinfo t.grd reports a line about the node registration, there was no such item when we asked for a numerical record via -C. So no way of easily determining if a grid is pixel or gridline in a script, other than grepping on the text output. Because the order of outputs was set a long time ago, this PR just adds the missing registration (0 = gridline, 1 = pixel) as the very last item of the record.

For whatever reason, wihle grdinfo t.grd reports a line about the node registration, there was no such item when we asked for a numerical record -C.  So no way of easily determining if a grid is pixel or gridline in a script, other than grepping on the text output.  Because the order of outputs were set a long time ago, this PR just adds registration as the very last item of the record.
@PaulWessel PaulWessel requested a review from seisman May 20, 2020 03:06
Copy link
Member

@seisman seisman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@PaulWessel PaulWessel merged commit a1e72e6 into master May 20, 2020
@PaulWessel PaulWessel deleted the grdinfo-reg branch May 20, 2020 03:36
seisman added a commit to GenericMappingTools/pygmt that referenced this pull request May 27, 2020
In GMT 6.1, `grdinfo` also reports registration code at the end of the output.

See GenericMappingTools/gmt#3359 for upstream changes.
seisman added a commit to GenericMappingTools/pygmt that referenced this pull request May 28, 2020
In GMT 6.1, `grdinfo` also reports registration code at the end of the output.

See GenericMappingTools/gmt#3359 for upstream changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants