Skip to content

File format issues #9

@jkfindeisen

Description

@jkfindeisen

I'm implementing a reader for the OBF file format as it is described in this documentation (see fileformat.rst) in Python. While doing this some issues occurred. They might require updates to the document or maybe simple clarifications.

  • The value of the OMAS_BF_MAX_DIMENSIONS constant is not specified, it seems to be 15.

  • The data type of OMAS_DT is not specified, it seems to be uint32.

  • The tag dictionary has an empty key at the end.

  • The stack footer comes with versions containing letters like 1A or 5A, but the stack header format version field only contains numbers. How can one determine which footer is present for cases like 1A or 5A?

  • The interleaved storage of the stack data introduced in stack format version 6 is a bit more complicated. Are there example files available for testing this?

  • Some old files (from pre 2008) cannot be read because strings were still encoded in latin and cannot be read in utf-8 if they contain for example "µ". A fallback encoding of "iso-8859-1" in case "utf-8" fails can read these stacks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions