Skip to content

Conversation

@PaulWessel
Copy link
Member

At least as long as GMT modules maintain record-by-record reading (i.e., as UNIX filters), we may not always be able to reliable identify the start of trialing text if the first record has numbers in that column. If that happens, then any trailing text in subsequent columns will be read as NaN and basically lost. Using *-f*colt to explicitly state where trailing text starts makes the determination robust. Closes #5368.

At least as long as GMT modules maintain record-by-record reading (i.e., as UNIX filters), we may not be able to reliable identify the start of trialing text if the first record has numbers in that column.  If that happens, then any trailing text in subsequent columns will be read as NaN and basically lost.  Using -f to explicitly state where trailing text starts makes the determination robust.  Closes #5368.
@PaulWessel PaulWessel added bug Something isn't working new core module feature PR that implements a new core module feature labels Jun 21, 2021
@PaulWessel PaulWessel self-assigned this Jun 21, 2021
@maxrjones maxrjones added the add-changelog Add PR to the changelog label Jun 21, 2021
@PaulWessel PaulWessel merged commit 14af7af into master Jun 21, 2021
@PaulWessel PaulWessel deleted the string-col-type branch June 21, 2021 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

add-changelog Add PR to the changelog bug Something isn't working new core module feature PR that implements a new core module feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

gmtselect issue (gmt6)

3 participants