Skip to content
This repository was archived by the owner on Apr 5, 2026. It is now read-only.

Add enough new content to be able to write a SAS7BDAT#19

Merged
BioStatMatt merged 1 commit into
BioStatMatt:masterfrom
davidcostanzo:updates
Feb 27, 2026
Merged

Add enough new content to be able to write a SAS7BDAT#19
BioStatMatt merged 1 commit into
BioStatMatt:masterfrom
davidcostanzo:updates

Conversation

@davidcostanzo

Copy link
Copy Markdown

The change adds enough new content to be able to write a SAS7BDAT. It:

  • Provides a page number sequence that is >256 pages long.
  • Documents more fields on the SAS7BDAT header and Row Size subheader.
  • Documents more name flags in the Column Attributes subheader.
  • Documents the ordering/padding rules for how columns are pysically laid out in a data row.
  • Documents the ordering of the page types: meta* - mix? - data* - amd?
  • Includes information about the "deleted flags" that appears after the packed binary data.
  • Generalizes the concept of a "text reference" and its usage in other subheaders.
  • Introduces the concept of a "subheader reference".
  • Adds some more observations to the Column List subheader, although not enough to explain it.
  • Documents the location of width/digits for FORMAT to "Column Format and Label subheader".
  • Adds information for the INFORMAT to "Column Format and Label subheader".

It also includes some minor consistency fixes, like standardizing on the use of the term "meta-information".

It:
- Provides a page number sequence that is >256 pages long.
- Documents more fields on the SAS7BDAT header and Row Size subheader.
- Documents more name flags in the Column Attributes subheader.
- Documents the ordering/padding rules for how columns are pysically laid out in a data row.
- Documents the ordering of the page types: meta* - mix? - data* - amd?
- Includes information about the "deleted flags" that appears after the packed binary data.
- Generalizes the concept of a "text reference" and its usage in other subheaders.
- Introduces the concept of a "subheader reference".
- Adds some more observations to the Column List subheader, although not enough to explain it.
- Documents the location of width/digits for FORMAT to "Column Format and Label subheader".
- Adds information for the INFORMAT to "Column Format and Label subheader".

It also includes some minor consistency fixes, like standardizing on the use of the term "meta-information".
dcostanz pushed a commit to FredHutch/sas7bdat-specification that referenced this pull request Jul 30, 2025
1. Provides a page number sequence that is >256 pages long.
2. Documents more fields on the SAS7BDAT header and Row Size subheader.
3. Documents more name flags in the Column Attributes subheader.
4. Documents the ordering/padding rules for how columns are pysically laid out in a data row.
5. Documents the ordering of the page types: meta* - mix? - data* - amd?
6. Includes information about the "deleted flags" that appears after the packed binary data.
7. Generalizes the concept of a "text reference" and its usage in other subheaders.
8. Introduces the concept of a "subheader reference".
9. Adds some more observations to the Column List subheader, although not enough to explain it.
10. Documents the location of width/digits for FORMAT to "Column Format and Label subheader".
11. Adds information for the INFORMAT to "Column Format and Label subheader".
12. It also includes some minor consistency fixes, like standardizing on the use of the term "meta-information".

This is identical to a PR submitted to the source repository: BioStatMatt#19
@BioStatMatt
BioStatMatt merged commit e5958fd into BioStatMatt:master Feb 27, 2026
dcostanz pushed a commit to FredHutch/sas7bdat-specification that referenced this pull request Mar 25, 2026
This was to get BioStatMatt#19.
I have since moved the files which were modified by that PR, so I
removed the changes.  However, since I had authored the PR, the changes
in it have already been included in sas7bdat.rst and several mistakes in
the PR have since been fixed.

The end result of this merge is that this fork accepted nothing from the
upstream form.  The primary reason for doing this so that GitHub stops
showing that this fork is behind the upstream fork.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants